accepts, and how PAYMENT-SIGNATURE turns the same API request into a paid request.
Preparation
You need to prepare:
No API Token is required when calling the Ace Data Cloud API with X402. The SDK does not include
Authorization in the first request, and the Gateway returns 402 Payment Required and payment requirements; the SDK automatically retries after signing.
Install the SDK
Source code and package addresses:- SDK repository: https://github.com/AceDataCloud/SDK
- X402 Client repository: https://github.com/AceDataCloud/X402Client
- npm:
@acedatacloud/sdk,@acedatacloud/x402-client - PyPI:
acedatacloud,acedatacloud-x402
acedatacloud-x402.
Installation and import check output in a clean temporary environment:
- Both npm packages and PyPI packages are actually published packages, not placeholder names in the documentation.
acedatacloud-x402[cli]installs the CLI, and theapprove-permit2subcommand can be used for Permit2 authorization inuptoscenarios.
The First Request Returns 402
You can first usecurl to see what an unpaid request returns. The following example does not incur charges because it does not carry PAYMENT-SIGNATURE:
accepts array, with a common structure as follows:
PAYMENT-REQUIRED response header in base64 form, making it convenient for clients to read payment requirements without parsing the body.
The program output summary for an unpaid request to the production API is as follows:
- The first request does not carry
AuthorizationorPAYMENT-SIGNATURE, so it returns HTTP 402 and does not incur charges. acceptsis the only trusted signing basis for this request, containing the available networks, schemes, maximum amount, recipient address, and asset address.networkis a CAIP-2 identifier, and clients must match by the CAIP-2 string when selecting a network.- The maximum amount for this minimal
gpt-4o-minichat request is95215atomic USDC, which is0.095215USDC. - Every request should read the current 402 response; do not hardcode example amounts into business code.
Complete the Payment Retry with the SDK
The following is a minimal TypeScript example. It specifiesnetwork: 'base', and the handler selects the Base payment requirement from the current 402 response; the actual amount and recipient address are still subject to accepts:
- The SDK sends a normal API request, without
Authorization. - The Gateway returns
402 Payment Requiredandaccepts. createX402PaymentHandlerselects the payment requirement fornetwork = 'base'and signs aPAYMENT-SIGNATURE.- The SDK retries with the same request body, and the Gateway calls the Facilitator to verify and settle before allowing the request through to the target API.
View Facilitator capabilities
The X402 API does not depend on a resource catalog. The client directly calls a known API, and uses the402 Payment Required and accepts returned in real time by that request as the sole basis for pricing and signing.
The Facilitator’s capability declaration is located at:
/supported, /verify, /settle, and the currently enabled payment networks, and does not list API resources.
Ace Data Cloud’s production Facilitator address is:
kinds lists the networks and schemes supported by the Facilitator. For actual calls, the accepts returned by the API still takes precedence.
Facilitator /supported output:
/supportedindicates that the Facilitator has verification and settlement capabilities for these networks and schemes.- Both Base and Solana support
exact;uptois currently available only on Base. - Whether a specific API allows a certain network is still determined by that API’s 402
accepts.

