Skip to main content

limitguard

Official Python SDK for the LimitGuard Trust Intelligence API: entity verification and risk scoring for EU businesses, paid per call in USDC over x402 or covered by a subscription.

Install

pip install limitguard

With Solana wallet support, for agents that pay per call:

pip install 'limitguard[solana]'

Python 3.10 or newer.

Quickstart

import asyncio
from limitguard import LimitGuardClient


async def main():
    async with LimitGuardClient(api_key="lg_live_...") as client:
        result = await client.check_entity("Acme BV", country="NL")
        print(result.trust_score, result.trust_level, result.recommendation)


asyncio.run(main())

check_entity returns a TrustResponse (trust_score 0-100, trust_level, cluster, recommendation, confidence, top_factors). risk_score is the cheaper two-source variant and returns a RiskResponse.

Paying for calls

Two ways to satisfy the API's per-call price, and the client accepts either or both:

You pass What happens
api_key= on a paid tier (indie and up) The subscription covers usage. No per-call payment.
wallet= The client pays each call in USDC over x402 automatically when the API answers 402.
both Calls are paid by the wallet and attributed to the key.

A free-tier key identifies you and tracks usage; it does not pay for calls. On its own it will raise PaymentRequiredError on any paid endpoint. Add a wallet, or upgrade the key.

Wallet example (Solana, needs the [solana] extra and a wallet holding SOL for gas and USDC for payments):

from solders.keypair import Keypair
from limitguard import LimitGuardClient
from limitguard.x402 import SolanaWallet

wallet = SolanaWallet(keypair=Keypair.from_base58_string(private_key))
async with LimitGuardClient(wallet=wallet) as client:
    result = await client.check_entity("Acme BV", country="NL")

A complete agent is in examples/agent_with_wallet.py, included in the source distribution (pip download --no-binary :all: limitguard).

Errors

All exceptions subclass LimitGuardError: AuthenticationError, PaymentRequiredError, RateLimitError, ValidationError, ServerError. The client retries 429 and 5xx responses with backoff before raising.

Links

Version

import limitguard
print(limitguard.__version__)

Releases are tagged sdk-v<version> and published to PyPI from that tag.

Release files for limitguard 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for limitguard 0.1.0
File Size Uploaded
limitguard-0.1.0.tar.gz 9.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for limitguard 0.1.0
File Interpreter ABI Platform
limitguard-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 20.7 kB

Release files / limitguard-0.1.0.tar.gz

Download URL limitguard-0.1.0.tar.gz
Size 9.9 kB
Tags Source
SHA-256 checksum
How to use checksums
dfe29e6f6a727433ed25b1acf6026e1b4efbaf535100a24b97b077df9ce0776e
BLAKE2b-256 checksum
How to use checksums
bcd4eb5f2da383cc43a51fc997674e3fc509fdd4acc0267a1ce03e0f6ff9fa61
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.

Transparency log

Release files / limitguard-0.1.0-py3-none-any.whl

Download URL limitguard-0.1.0-py3-none-any.whl
Size 10.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f4024608ae2658b855925c0cb519f1364246a674b735baeb76f4387b858bfbc5
BLAKE2b-256 checksum
How to use checksums
1cb429b7d77b043d898c77e34c020135a60e9174fcef5245baa95017f37c15e2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 8, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

This release

0.1.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page