This Agentic Payments and x402 Policy explains how automated agents, wallets, scripts, API clients, and workflows may discover and purchase LedgerBrain digital resources using agentic payment methods, including x402-enabled pay-as-you-go access.
This policy supplements the Terms of Use, Privacy Policy, Refund, Return and Cancellation Policy, and Acceptable Use Policy.
1. Scope
LedgerBrain may support:
- account-based access through subscriptions, credits, and API keys;
- one-off purchases through Stripe checkout or invoices;
- pay-as-you-go API calls;
- machine-payment or x402-enabled endpoints for agents and API clients.
Examples may include KYT transaction-risk reports, KYA address-risk reports, KYE entity outputs, and other digital risk-intelligence resources.
2. How x402 access works
A typical x402 flow works as follows:
- An agent or API client requests a paid LedgerBrain resource.
- LedgerBrain returns an HTTP 402 response with payment requirements.
- The agent reviews the amount, currency or token, network, recipient, expiry, endpoint, and resource description.
- The agent authorises payment using its own compatible wallet, payment library, or payment instrument.
- The agent retries the request with the required payment authorisation.
- LedgerBrain verifies the payment or authorisation and returns the purchased resource if the request is valid and accepted.
LedgerBrain may also provide an endpoint catalogue so agents can discover available resources, descriptions, prices, supported networks, and payment requirements before making a paid request.
3. Authority and responsibility for agents
The person or organisation that controls an agent, wallet, API key, workflow, payment method, or integration is responsible for all requests and payments made through it.
You must ensure that each agent has authority to purchase the requested resource and that it operates within your instructions, permissions, budgets, and legal obligations.
You should configure agents with appropriate safeguards, including spending caps, allowlists, rate limits, duplicate-payment protection, idempotency keys, audit logging, human review for unusual activity, and escalation rules for high-value or high-risk requests.
4. Wallets, keys, and custody
LedgerBrain does not require and does not want your private keys, seed phrases, recovery phrases, or signing secrets. Do not send them to LedgerBrain.
LedgerBrain does not custody your crypto assets and does not sign payments for your agent. Payment signing occurs in the wallet, payment library, or payment infrastructure selected and controlled by you or your agent.
You are responsible for securing wallets, private keys, API keys, webhook secrets, agent infrastructure, and payment credentials.
5. Pricing, supported payments, and networks
The current price, currency or token, network, payment recipient, expiry, and other payment requirements are the terms shown at the time of the request or checkout.
Supported payment methods, tokens, chains, networks, minimum amounts, and prices may change. Network fees, gas fees, wallet fees, payment processor fees, failed transfer costs, and exchange-rate changes are your responsibility unless required by law or caused by a LedgerBrain error.
6. Payment verification and delivery
LedgerBrain may verify payment through Stripe, a payment facilitator, blockchain network data, stablecoin settlement records, or other supported payment infrastructure.
LedgerBrain may withhold delivery until payment is authorised, verified, or settled according to the applicable payment method. LedgerBrain may decline, block, or hold a request where the request, account, wallet, transaction, agent, customer, address, or pattern appears unlawful, sanctioned, abusive, fraudulent, unsupported, risky, or inconsistent with our policies.
7. Duplicate payments and failed delivery
Agents should use idempotency keys or equivalent duplicate-protection mechanisms where supported. Agents should not loop indefinitely on payment-required, retryable, failed, or timeout responses.
Refunds, re-delivery, credits, and failed delivery are governed by the Refund, Return and Cancellation Policy.
Pay-as-you-go and x402 payments are generally non-refundable once the requested resource has been successfully delivered, except where required by law or where there is a confirmed duplicate payment, payment verification error, or LedgerBrain delivery error.
8. Audit logs
For each paid request, agents should store a durable record of:
- endpoint and resource requested;
- request ID and report ID;
- price, currency or token, network, and payment reference;
- wallet address or payment method reference where applicable;
- agent identity, user, organisation, or principal authorising the request;
- timestamp;
- response status and error messages.
LedgerBrain may store payment metadata, request metadata, response metadata, wallet addresses, payment references, risk outputs, policy IDs, evidence links, and audit records as described in the Privacy Policy and Terms of Use.
9. No circumvention
You must not use agents, scripts, multiple accounts, rotating wallets, or automated workflows to evade pricing, usage limits, rate limits, authentication, sanctions controls, security controls, duplicate-payment controls, or other restrictions.
10. Contact
For agentic payment, x402, billing, or failed-delivery issues, contact: