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.

Can my agent use Algorand, Base, or both?

Yes. An agent may pay and act on Algorand only, on Base only, or on both. Nothing in ranking, eligibility, pricing, or access requires a second chain. Select the payment accept by network. Algorand stays first. Filter the catalog with chain=algorand or chain=base when you want one chain's rows.

Do I have to supply a Base address?

No. An Algorand-only agent is not penalized for omitting a Base address. Wallet routes (/positions, /opportunities/personalized, /eligibility, /plans, Algorand quotes, and swaps) take an Algorand address and nothing else. Leaving out a 0x address does not lower rank, fail the request, or block payment. A Base address is required only on the call that needs it: a Morpho quote (userAddress is 0x…) or a payment signed against the Base accept.

Which USDC asset should I expect?

Use the asset published on the accept you select. On Algorand mainnet the USDC ASA id is 31566704. On Base the asset is Circle USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. Confirm both against live discovery before signing.

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.

Which MCP URL should I use?

Production remote MCP: https://canix402-mcp.compx.io/mcp (Streamable HTTP). Verify with https://canix402-mcp.compx.io/.well-known/mcp. Discovery and the API x402 manifest advertise this URL in mcpServer.url / mcpUrl.

Do I need a wallet mnemonic in the MCP server?

No. The remote MCP is walletless. Your agent or client wallet signs USDC payments and passes paymentSignature when retrying paid MCP tools. Never put mnemonics in MCP server configuration.

Should I use MCP or direct HTTP?

Use MCP when your agent host supports MCP tools (Cursor, Claude Desktop). Use direct HTTP when building a custom client against the Caddy gateway. Both hit the same public gateway for paid data; MCP is a typed pass-through wrapper.

What is the WebMCP demo page?

/webmcp registers the same Canix MCP tools in the page via document.modelContext.registerTool (with navigator.modelContext as a fallback). People fill an opportunities table from those tools in a slide-out panel; agents in ChatGPT’s in-app browser or Chrome with chrome://flags/#enable-webmcp-testing discover the same tools through WebMCP. Canix does not sign or submit. Origin isolation is required — the page never relaxes document.domain.

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://canix402-api.compx.io.