SignalGrid delivers institutional-grade market intelligence as machine-readable signals. AI agents pay per request via x402 USDC micropayments. Governments and banks get sovereign-ready data with full provenance and audit trails.
Paid endpoints, live
Discovery formats
Price per call
Settlement chain
API keys required
Every feature serves both the autonomous agent pulling signals at 3am and the sovereign treasury auditing them at noon.
Every endpoint is metered and settled in USDC over HTTP 402. No API keys, no invoices, no human in the loop — the agent signs and pays per call.
Discovered as native tools by any MCP agent — Claude, GPT, or custom LLMs. tools/list is free; tools/call settles like any other call.
Every response states its dataType (live or reference), the source it came from, the asOf date, and the programme stage. An unverified rail is reported as unverified.
Base settles today. The middleware supports Ethereum, Arbitrum, Optimism, Polygon and Avalanche; a chain only goes live here once it is funded and verified. Celo is not enabled — see /v1/dtcc/status style honesty applied throughout.
A single list price of $0.0001 per call, published per endpoint at /openapi.json — cost an entire workload before spending anything.
VASP licensing status, travel-rule checks, sanctions screening, CBDC corridor reporting and on-chain audit trails for institutional and public-sector due diligence.
Each is tagged in this table as Live or Reference up front, and the paid payload repeats that tag with its source and as-of date, so an agent can tell fetched data from curated reference without trusting this page.
Tokenized money-market fund and deposit yields, read live from the underlying contracts rather than a cached table.
OFAC sanctions screening, travel-rule checks, audit trails, VASP licensing status and agent-identity eligibility.
Programme status for TCH, SWIFT gpi, Visa and Mastercard agent payments, DCIO/Zengin, Lightning and the EU digital euro — with the pilot claims labelled as pilots.
CBDC corridor status and eNaira programme reporting, each tagged with its verification stage and a link to the primary source.
Every endpoint is a plain paid HTTP route and an MCP tool. Discovery is free: /.well-known/x402, /openapi.json, /llms.txt, /agents.txt.
Your agent calls a Keystone route. The server replies 402 Payment Required with the price, asset, chain and pay-to address.
The agent signs a USDC micropayment authorization (EIP-3009) and retries with the payment attached. A facilitator verifies and settles on Base.
The response arrives with its dataType, source, asOf date and programme stage, so the agent can tell live data from curated reference without trusting the copy.
Any MCP-compatible agent discovers this service as native tools — no SDK, no wrapper code. initialize and tools/list are free; tools/call returns an x402 challenge, and paying it settles exactly like the plain HTTP route.
Tokenized money-market-fund and deposit landscape — $0.0001
Sanctions screening and the lists to screen against — $0.0001
SWIFT MT/MX catalogue — takes an mt argument — $0.0001
DTCC operations namespace — control verbs refuse with 403 before any payment — $0.0001
Agent discovers 40 tools · x402 payment auto-managed · zero glue code
Every signal call settles natively in stablecoins via x402. Base settles in production today. Additional chains are in active facilitator verification for banks and sovereign agents.
Banks and card networks ask for more than four payment fields before they will settle. We are not there yet. Here is the list of what does not exist, so nobody spends a procurement cycle discovering it later.
Not implemented. You can buy a screening call — /v1/compliance/sanctions-screen — but there is no ALLOW / REFER / DENY decision attached to each settlement.
Not implemented. Settlement is a plain EIP-3009 transferWithAuthorization. Originator and beneficiary fields are not transmitted.
Not implemented. A permit carries no spending limit, transaction cap, duration or merchant-scope field.
Not implemented. One deployment, no regional pinning, no air-gapped relay. Data does not stay inside your jurisdiction.
Not a product. Every paid response returns the transaction hash in X-X402-Tx, which is the raw material for your own ledger.
Not implemented. No bare-metal, private-cloud or sovereign-tier relay exists today.
If a procurement cycle depends on any of the above, this platform is the wrong dependency right now. The live catalogue is the authoritative list of what is actually callable.
Every paid endpoint is $0.0001 USDC — the same rate for standard programme status and for the heavier compliance and collateral-verification references. No seat count, no subscription, no negotiation — you can cost an entire workload before spending anything, straight from /openapi.json.
/.well-known/x402, /openapi.json, /llms.txt, /agents.txtPOST /mcp, Streamable HTTP)x402 is an open payment protocol built on the HTTP 402 status code. When your agent requests a paid endpoint, the server responds 402 with payment instructions. Your agent signs a USDC micropayment (EIP-3009) and retries the request with payment attached. A facilitator verifies and settles on Base. No credit cards, no API keys, no human in the loop.
A flat $0.0001 USDC per call. There are no tiers and the rate does not vary by endpoint. Every price is published per endpoint at /openapi.json. No subscription, no minimum, no negotiation.
No. Payment is the authentication: your signing key is the credential, so there is nothing to store, rotate or leak. Bring your own funded wallet and you are live on the first call.
Base settles live today. The middleware is built for Ethereum, Arbitrum, Optimism, Polygon and Avalanche, but a chain is only advertised here once it is funded and verified end to end. Celo is not enabled — its facilitator support and exact EIP-3009 domain are still unresolved, and we would rather report that than take a payment we cannot settle.
Use it for due diligence. The compliance routes — sanctions screening, travel-rule checks, on-chain audit trails, VASP licensing status, CBDC corridor reporting — are public, per-call and priced identically to everything else. There is no bespoke on-prem relay, air-gapped deployment or jurisdictional data-residency product today, and we would rather say so than take a procurement cycle for something that does not exist.
No. Nothing here touches documents or personal data. The compliance endpoints read public sources and return public records. If you need document KYC, use a licensed provider directly.
Every response says so itself. dataType is live (fetched from a primary source) or reference (curated and dated). Each programme carries a stage — live, pilot, target or unavailable — plus a source and an asOf date, and unverified routes return an explicit reason instead of a confident-looking stub.
A few thousandths of a cent per call. No card, no key, no subscription.
Get started