FAQ

Should my agent call the gateway or the upstream API directly?

Use the Caddy gateway URL. x402 enforcement, payment headers, and settlement happen at the gateway edge. Discovery/OpenAPI should also be fetched through the gateway in production.

Why do paid routes return 402 first?

That is expected. The gateway advertises payment requirements through PAYMENT-REQUIRED so your client can sign and retry with PAYMENT-SIGNATURE.

Does the website sign payments for me?

No. Payment signing stays client-side in your agent or wallet integration. This site only documents the flow and links to machine-readable contracts.

Which USDC asset id should I expect?

Use the asset id published in discovery/OpenAPI x402 metadata for the target network. On Algorand mainnet the default documented id is 31566704.

Can I browse opportunities on this website without paying?

No. This site is onboarding documentation only. Opportunity data remains API-only behind x402 payment gates.

How do I test locally?

Run the protocol API and Caddy gateway from the monorepo, then point website env vars to your local gateway URL during development. Production API references in this site use https://api.canix402.compx.io.