# Limitguard lead validation API > Limitguard is a lead validation service for lead generation agencies, B2B marketing and sales teams: it checks the company behind each lead against official business registers (full coverage in the Netherlands and Belgium), EU VAT and sanctions lists, with website age in the company check, and returns proceed, review or block with the source on every line. Developers and AI agents can use its HTTP API, MCP server and A2A service, hosted in the EU. > Free sandbox key, no wallet: POST /v1/keys/create {"email": "you@example.com", "tier": "sandbox"} → lg_sandbox_ key → X-API-Key. Mock data, no charge, 10 req/min. The sandbox covers entity, risk and KYB checks; Lead Verify and the agent check need a live key or an x402 payment. > Paid by x402: Lead Verify $0.10 per lead and agent check $0.005 per wallet; entity check and KYB $0.29 and risk score $0.25 fresh, $0.11 cached ($0.25 KYB) when available; report $0.55; sanctions and wallet screens $0.005; other routes at the account price. API keys, the dashboard and the Claude connector pay the account prices: Lead Verify $0.27 per lead and agent check $0.75 per wallet; $0.11-1.85 per call; entity and risk checks $0.88-1.05 fresh ($1.50 KYB), $0.11 cached ($0.25 KYB) when available (a cache miss returns 404 not_cached, no source is called). - Checks: Dutch and Belgian company registers, EU VAT, sanctions, website domain and country risk, with a score and reasons; available checks depend on the product and the details supplied. Company-register coverage is limited to NL and BE. - Price: agents paying by x402 from $0.005 per call, $0.25-$0.29 per fresh entity, risk or KYB check; API keys and the dashboard from $0.11 per call, $0.88-$1.50 per fresh check on the tiered endpoints, from $0.11 on a cached repeat; a free sandbox key returns mock data. - Access: pay per call with x402 in USDC on Base or Solana with no signup, or use an API key debited from a prepaid balance. API keys and x402 have no subscription; the dashboard has monthly and yearly plans. The monthly request caps on keys are abuse limits, not quotas. - Developers and AI agents: HTTP API at https://api.limitguard.ai, MCP at https://api.limitguard.ai/mcp and A2A at https://api.limitguard.ai/a2a. Integration guide: https://limitguard.ai/developers/. - Hosting: in the EU (API and dashboard in the European Union, database in Ireland). Operator: Ambulatio Consulting BV (KVK 77272471), Breda, the Netherlands. - Lead Verify: $0.27 per lead for Dutch and Belgian companies from an API-key balance, or $0.10 per lead paid per call with x402, over the HTTP API (POST /v1/leads/verify), MCP (verify_lead) and A2A (lead_verify). Whole lists upload in the dashboard at EUR 0.25 per lead. - Agent check: $0.75 per EVM wallet from an API-key balance, or $0.005 paid per call with x402, over the HTTP API (POST /v1/agent/check), MCP (check_agent_wallet) and A2A (agent_check): sanctions address screen, Base balances, and the agent's ERC-8004 identity and open feedback. For developers and AI agents: https://limitguard.ai/developers/?utm_source=llms_txt&utm_medium=agent&utm_campaign=developers&utm_content=lead_lines Lead verification pricing, comparisons and NL/BE company-check guides: https://limitguard.ai/pricing/?utm_source=llms_txt&utm_medium=agent&utm_campaign=pricing&utm_content=buyer_pages, https://limitguard.ai/compare/lead-verification/?utm_source=llms_txt&utm_medium=agent&utm_campaign=compare&utm_content=buyer_pages and https://limitguard.ai/guides/?utm_source=llms_txt&utm_medium=agent&utm_campaign=guides&utm_content=buyer_pages > Base URL: https://api.limitguard.ai > Version: 0.1.0 ## Authentication Two modes: - API Key: `X-API-Key: lg_live_...` header. A key on a PAID tier (indie, starter, growth, pro) holds a prepaid balance; each priced call is debited at the account price in the table. Top up via x402 (POST /v1/keys/upgrade/{tier} or POST /v1/keys/topup/{usd}). A `free` key holds no balance and pays x402 per call; it identifies you and counts your usage, exactly as it always has on MCP. A `sandbox` key gets mock data at no charge on the routes that serve one and pays x402 per call elsewhere, like `free`. - x402 v2: `PAYMENT-SIGNATURE: ` header (pay-per-use USDC; legacy `X-PAYMENT` also accepted) Sandbox: `lg_test_` key prefix (dev/staging only) OR `lg_sandbox_` Redis-backed key → mock data, 10 req/min ## Quality Tiers `X-Response-Quality: cached|fresh|enhanced` (default: fresh). cached = served only from cache; a miss is 404 not_cached and no data source is called. enhanced is retired (#405) on every endpoint below except deep-check: sent anyway, it is served and billed as fresh. ## Core Endpoints (Paid) POST /v1/entity/check Company check: a 0-100 score, a recommendation and the factors behind them; which sources run depends on the identifiers supplied (see below). `entity_name` and `country` are required; identifiers (kvk_number, cbe_number, domain, iban, vat_number, wallet_address) are optional and raise confidence. With none, only country risk and sanctions run (plus a KVK name search for NL), at lower confidence. Price: $0.11 cached / $0.29 fresh by x402; $0.11 cached / $1.05 fresh with an API key or the dashboard (enhanced retired 2026-09-24, #405: served and billed as fresh) Body: entity_name (str), country (ISO-3166), kvk_number?, cbe_number?, domain?, iban?, vat_number?, wallet_address?, wallet_chain? Always run: country risk, sanctions. Each other source runs only when its identifier is sent: registry (kvk_number/cbe_number; NL name search otherwise), KVK annual accounts (kvk_number), domain, IBAN, VAT (VIES), wallet (address format check only, no on-chain lookup). Returns: trust_score (0-100), trust_level, cluster, recommendation, confidence, top_factors, sources_checked POST /v1/entity/deep-check Extended screening. deep (fresh): PEP/RCA exposure from OpenSanctions (the role.pep/role.rca match detail /v1/entity/check fetches and discards), plus insolvency_records from the Dutch Centraal Insolventieregister (NL only; applicable: false for other countries; queried by kvk_number when given, else by name). extended (enhanced): + adverse media screening (dilisense news index). No cached tier; `cached` is served and charged as fresh. Price: $0.88 fresh (deep) / $1.71 enhanced (extended) Body: entity_name (str), country (ISO-3166), kvk_number? (8 digits) Returns: quality, sources_returned, pep_extended {screened, pep_exposure, match_count, matches[], truncated, retrieved_at}, insolvency_records {screened, applicable, jurisdiction, query_by, found, match_count, records[], truncated, retrieved_at}, adverse_media {screened, adverse_media_found, match_count, category_hits, articles[], truncated, retrieved_at} (extended only), processing_time_ms 503 pep_source_unavailable / insolvency_source_unavailable / adverse_media_source_unavailable if a source cannot be reached; not charged. POST /v1/risk/score Quick risk assessment (2 sources: country risk + sanctions). Price: $0.11 cached / $0.25 fresh by x402; $0.11 cached / $0.90 fresh with an API key or the dashboard (enhanced retired 2026-09-24, #405: served and billed as fresh) Body: entity_name (str), country (ISO-3166) Returns: risk_score (0-100), risk_level, recommendation, top_factors POST /v1/kyb/check Know Your Business verification. Price: $0.25 cached / $0.29 fresh by x402; $0.25 cached / $1.50 fresh with an API key or the dashboard (enhanced retired 2026-09-24, #405: served and billed as fresh) Body: entity_id, registration_number, country, entity_name?, vat_number?, domain? Returns: verified (trust score 60+), register_verified, register_checked, sanctions_flagged, kyb_status, trust_score, risk_flags, group_structure POST /v1/reputation/score Trust decay scoring. Price: $0.11 cached / $0.90 fresh (enhanced retired 2026-09-24, #405: served and billed as fresh) Body: entity_name, country (required unless trust_score and cluster are both sent), trust_score? (0-100), cluster?, last_verified_at? (unix), verification_count? GET /v1/reputation/history/{entity_hash} Reputation trend over the last 52 recorded checks. Price: $0.11 GET /v1/wallet/balance?agent_id=... ERC-8004 agent USDC balance (Base mainnet). Price: $0.11. Returns erc8004_agent_id, the registry's own token id for the agent, resolved best-effort (null if it cannot be). POST /v1/mcp/verify-wallet Wallet screening: OFAC SDN address match, on-chain signals (contract check, native and USDC balance, transaction count, first seen on Base) and named risk rules with up to 3 advice items. Price: $0.005 by x402; $0.11 with an API key or the dashboard. Body: wallet_address, chain_id? (CAIP-2, or base/eth/solana/btc) On Base, also returns erc8004_agent_ids and erc8004_reputation (open ERC-8004 on-chain feedback for any agent the wallet owns) as descriptive signals only, never scored. GET /v1/compliance/readiness/{entity_id} EU AI Act readiness score. Price: $0.11. Query: system_type, completed_items[] GET /v1/compliance/alerts Regulatory alerts: daily OFAC/EU/UN sanctions-list changes plus hits on entities and wallets you checked; poll to read; alerts about entities or wallets you checked are also pushed to a webhook registered for sanctions.match.new. Price: $0.11 per call on every API key tier (the dashboard's sanctions-list feed is included in the Growth, Pro and Enterprise workspace plans). Query: jurisdiction, severity, limit, offset POST /v1/reports/entity Per-entity report built from one real check: registry identity, sanctions and PEP screening, domain signals, Dutch annual-accounts financials, trust score (risk.trust_score, 0-100, 100 = best) with the rules that fired, up to 12 findings, a per-source status table and an evidence hash. Price: $0.55 by x402; $1.85 with an API key or the dashboard. Sandbox keys get 403. Body: entity_name + country (plus kvk_number?, cbe_number?, vat_number?, domain?, iban?, wallet_address?) or check_id, never both GET /v1/reports/{report_id} reads it back free (?format=pdf) Also an MCP tool: get_compliance_report (same input; an x402 payment pays the agent price, a key or the Claude connector the account price). POST /v1/agent/check Agent wallet check in one call: OFAC SDN digital-currency address list match, Base USDC and ETH balance, ERC-8004 identity registration and open ERC-8004 feedback (not scored). One verdict (block / review / no_findings) and each part's status. Price: $0.005 by x402; $0.75 with an API key or the dashboard. Sandbox keys get 403. Body: wallet (EVM 0x address), agent_id? (decimal ERC-8004 agentId the wallet claims), domain? (website domain; WHOIS age, mail records, TLS; not scored) Also an MCP tool: check_agent_wallet, and an A2A skill: agent_check (same input; an x402 payment pays the agent price, a key or the Claude connector the account price). POST /v1/leads/verify Lead verify for one NL or BE sales lead: is it a real, active company? KVK/KBO register, plus VAT (VIES), mail server, IBAN and a sanctions-list screen of the company name. Verdict, a 0-100 lead_score, flags and one action per flag. Price: $0.10 by x402; $0.27 with an API key or the dashboard. Sandbox keys get 403. Body: country (NL|BE), company_number? or name?, vat_number?, email?, domain?, address?, iban?, phone? (rejected with 422 until website phone lookup is switched on), target_industries?, target_size? (your ideal customer; fills icp_fit, information only) Also an MCP tool: verify_lead, and an A2A skill: lead_verify (same input; an x402 payment pays the agent price, a key or the Claude connector the account price). POST /v1/entity/light-check Light company check: is the company on the NL (KVK) or BE (KBO) register and active, is its EU VAT number valid (VIES), and does its name match the local OFAC SDN, EU or UN lists? Each part says its own status; no owners, PEP or address match. Price: $0.05 by x402; $0.11 with an API key or the dashboard. Sandbox keys get 403. Body: country (ISO 3166-1 alpha-2), registration_number? and/or vat_number? (one is required) Also an A2A skill: light_check (same input; an x402 payment pays the agent price, a key or the Claude connector the account price). Not an MCP tool. POST /v1/seller/preflight Before an agent pays an x402 seller: the payTo wallet against the OFAC SDN address list, who registered the resource domain and when (RDAP), and that company against the OFAC, EU and UN lists, and whether the payTo is the wallet the seller publishes (its 402, /.well-known/x402) or a lookalike of it. Verdict ok / caution / block with one reason per finding. Price: $0.005 by x402; $0.11 with an API key or the dashboard. Sandbox keys get 403. Body: pay_to, network? (CAIP-2, default eip155:8453), resource_url (https), payer? (your EVM wallet) Also an A2A skill: seller_preflight (same input; an x402 payment pays the agent price, a key or the Claude connector the account price). Not an MCP tool. POST /v1/sanctions/preview Free yes/no sanctions screen of a name against the local OFAC SDN, EU and UN lists: possible_match, lists_checked, list_dates and list_note only. 10 per caller per UTC day (50 per client IP across API keys), then 429. Body: name, country? POST /v1/sanctions/screen The same screen with the matched entries (list, entry_id, matched_name, programmes, countries, listed_on, match_score). Price: $0.005 by x402; $0.11 with an API key or the dashboard. A name match is not a determination. Body: name, country? (orders matches, never excludes one) Also MCP tools: sanctions_preview (free) and sanctions_screen (same input; an x402 payment pays the agent price, a key or the Claude connector the account price). POST /v1/sanctions/wallet Free yes/no check of a wallet address against the OFAC SDN list: sanctioned, lists, as_of, status (ok or stale), source and upgrade. No programmes or entry ids. Its own 10 per caller per UTC day, separate from the name preview, then 429. Body: wallet_address, chain_id? (as POST /v1/mcp/verify-wallet, the full screen at $0.005 by x402; $0.11 with an API key or the dashboard) Also MCP tool wallet_sanctions_preview and A2A skill wallet_sanctions (free). ## Free Endpoints (No Auth) GET /health GET /.well-known/x402.json: x402 Bazaar service listing GET /.well-known/agent.json: A2A Agent Card GET /.well-known/agent-card.json: A2A Agent Card (v0.3+ name) GET /.well-known/mcp.json: MCP tool manifest POST /v1/keys/create: Self-service API key (body: email, tier) GET /v1/self-verify: Limitguard's own trust score GET /llms.txt, /llms-full.txt GET /: Discovery index (links to x402, Agent Card, mcp.json, llms.txt, spec, docs, MCP, A2A, free key) ## Not provided (law, not technology) - DGA status: a Dutch classification (for tax: a director holding at least 5% of the shares), not a register field; BV shareholder registers are private. - UBO register data (NL, BE): closed to the public since CJEU C-37/20 (2022); access is limited to obliged entities, competent authorities and, in some cases, parties with a legitimate interest, so Limitguard cannot resell extracts. - Sanctions screening is a name match: entity, KYB, risk and reputation checks query the OpenSanctions lists; Lead Verify and /v1/sanctions/screen use local copies of the OFAC SDN, EU and UN lists. No ownership or control tracing, no 50% ownership rule. ## A2A (Agent-to-Agent, JSON-RPC 2.0) POST /a2a: A2A v0.3.0 JSON-RPC endpoint named by the Agent Card (`preferredTransport: JSONRPC`). Methods: message/send, tasks/get, tasks/cancel. Skills lead_verify, agent_check, entity_check, risk_score, kyb_check, verify_wallet, wallet_sanctions, light_check, seller_preflight: send one data part `{"skill": "", "input": {}}`. The input and the result are those of the REST route (/v1/leads/verify, /v1/agent/check, /v1/entity/check, /v1/risk/score, /v1/kyb/check, /v1/mcp/verify-wallet, /v1/sanctions/wallet, /v1/entity/light-check, /v1/seller/preflight). A paid-tier key's prepaid balance (X-API-Key) is debited the account price; an x402 payment pays the agent price, as on REST; a sandbox key gets what the REST route gives it (mock data on entity_check, risk_score and kyb_check). No key or no balance → JSON-RPC error -32020 whose data names the price and the REST URL to pay at by x402. A text-only message returns the skill list (free). Example: {"jsonrpc":"2.0","id":1,"method":"message/send","params":{"message":{"kind":"message","role":"user","messageId":"m1","parts":[{"kind":"data","data":{"skill":"risk_score","input":{"entity_name":"Acme B.V.","country":"NL"}}}]}}} → result: a completed Task; artifacts[0].parts[0].data is the REST JSON response. tasks/get {"id": } returns it again for 24 h (same key only). A2A 1.0: send the header A2A-Version: 1.0 and call SendMessage, GetTask, CancelTask or ListTasks on the same URL. Parts carry no kind: a skill call is {"data": {"skill": "", "input": {...}}, "mediaType": "application/json"}. The result is {"task": ...} or {"message": ...}, states are TASK_STATE_*. The 1.0 Agent Card is /.well-known/agent-card.json with A2A-Version: 1.0. Pay with no key, in-band (a2a-x402 v0.2 extension): send the header X-A2A-Extensions: https://github.com/google-agentic-commerce/a2a-x402/blob/main/spec/v0.2 with a priced skill call and no key; the result is a Task in state input-required whose status.message.metadata["x402.payment.required"] is the REST route's x402 PaymentRequired (x402Version 2, accepts in USDC on Base and Solana). Sign one accepts entry, then send message/send with {"taskId": , "metadata": {"x402.payment.status": "payment-submitted", "x402.payment.payload": }} in the message. The answer is the completed Task with metadata x402.payment.receipts; a failed payment is a failed Task with x402.payment.error, and nothing is charged unless the call is served. ## x402 Payment Flow Official x402 v2 client libraries work out of the box (recommended): - Python SDK (API key): pip install limitguard → LimitGuardClient(api_key="lg_live_...") → await client.check_entity("Acme B.V.", country="NL") (PyPI: https://pypi.org/project/limitguard/); sandbox keys work the same way and return mock data - Python SDK (wallet, pay-per-call, no API key): pip install "limitguard[solana]" or "limitguard[evm]" → LimitGuardClient(wallet=SolanaWallet(keypair=...)) or LimitGuardClient(wallet=EvmWallet(account=...)) → the client pays each call's 402 in USDC automatically - Python: pip install "x402[evm,httpx]" → x402Client().register("eip155:*", ExactEvmScheme(account)) + x402_httpx_transport - TypeScript: npm install @x402/fetch @x402/evm viem → wrapFetchWithPaymentFromConfig(fetch, {schemes: [{network: "eip155:*", client: new ExactEvmScheme(account)}], spendControls: {maxAmountPerPayment: "$3"}}) (@x402/fetch refuses any payment over $1 by default. That covers every agent price; set maxAmountPerPayment only for deep-check enhanced ($1.71) or credit ($2.45) and the /v1/keys/upgrade/* and /v1/keys/topup/* purchases) - Quickstart with runnable code: https://docs.limitguard.ai/quickstart?utm_source=llms_txt&utm_medium=agent&utm_campaign=docs&utm_content=x402_clients Wire format A: x402 v2 envelope (what the official clients send), header PAYMENT-SIGNATURE: 1. Request without payment → HTTP 402. Body (and base64 PAYMENT-REQUIRED header) carries accepts[]: {scheme: "exact", network, asset, amount, payTo, maxTimeoutSeconds, extra: {name, version}} 2. Sign EIP-3009 TransferWithAuthorization (EIP-712 domain: name/version from accepts[].extra, chainId from network, verifyingContract = asset) 3. Retry with PAYMENT-SIGNATURE: base64(json({x402Version: 2, accepted: , payload: {signature, authorization: {from, to, value, validAfter, validBefore, nonce}}})) 4. 200 + PAYMENT-RESPONSE header: base64(json({success, transaction, network, payer})) Wire format B: Limitguard flat dialect (also accepted), header PAYMENT-SIGNATURE or X-PAYMENT: base64(json({chainId, amount, sender, recipient, nonce, signature, validAfter, validBefore})) Wire format C: Solana pre-broadcast transfer (solana:* networks only), header PAYMENT-SIGNATURE: base64(json({x402Version: 2, accepted, payload: {txSignature, sender, amount}})). Broadcast the USDC transfer yourself, then send its confirmed signature. No EIP-712 signature and no nonce are required; Limitguard verifies the transaction on-chain and skips its own settlement step. The paying wallet must pay the fee: the fee payer (first signer) must be the transfer authority. A transaction that a facilitator co-signed and paid the fee for is refused. Wire format D: EVM settled transfer, header X-PAYMENT or PAYMENT-SIGNATURE: already sent the USDC yourself? Quote the transaction hash: `X-PAYMENT: 0x<64 hex chars>`, or base64(json({txHash: "0x..."})). No EIP-712 signature and no nonce are required. Limitguard reads the receipt on-chain: the transfer must pay at least the quoted amount in USDC to the advertised payTo, be mined within the last 150 blocks (~5 min on Base), and each transaction hash pays exactly once. The paying wallet must send the transaction itself: the transaction's sender must be the address the USDC comes from. A transfer that a facilitator, bundler or relayer sends for you is refused. Accepted on exactly one EVM chain, which this deployment names in the `network` field of the accepts entry with scheme "settled-transfer", present in every 402 and in GET /x402/supported. Payer needs USDC only (no ETH for gas) in formats A and B: Limitguard submits the transfer on-chain after serving the response. In formats C and D you have already paid the gas yourself. Supported chains: eip155:8453 (Base), solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp (Solana). Testnets (Base Sepolia, Solana Devnet) are not accepted in production: /.well-known/x402.json says testnet_supported false. Can't pay yet? (recovery path, also embedded in every 402 under extensions.bazaar.info) - Free sandbox key, no wallet: POST https://api.limitguard.ai/v1/keys/create {"email": "you@example.com", "tier": "sandbox"} → lg_sandbox_ key → send as X-API-Key - Quickstart: https://api.limitguard.ai/v1/quickstart - x402 docs: https://docs.limitguard.ai/x402-protocol?utm_source=llms_txt&utm_medium=agent&utm_campaign=docs&utm_content=recovery - Website: https://limitguard.ai/?utm_source=llms_txt&utm_medium=agent&utm_campaign=home&utm_content=recovery ## Recommendations GET /v1/sales/recommendations?current_endpoint=/v1/risk/score → Suggests complementary endpoints based on current usage