What happens today
Resources priced on Arc (Circle's USDC-native L1, chain id 5042) cannot be registered. public.resources.register answers:
No supported networks. Got: [eip155:5042]. Supported: [base, solana]
registerFromOrigin then reports noValidResources, because public catalog rows only register alongside a valid paid resource, and every paid resource on such an origin is on Arc.
The rest of the pipeline works fine: the 402 is read, the accepts are parsed, the description and service name come through. Only the chain gate stops it.
Why Arc may be worth indexing
- USDC is the gas token on Arc, so an x402 resource priced in USDC is the native case there rather than an add-on.
- Circle's facilitator already serves it.
GET https://gateway-api.circle.com/v1/x402/supported lists eip155:5042 with the exact scheme, USDC at 0x3600000000000000000000000000000000000000 (6 decimals) and the batched GatewayWallet at 0x77777777Dcc4d5A8B6E418Fd04D8997ef11000eE.
- Resources that accept payment on Arc are already discoverable elsewhere. In the CDP Bazaar,
https://api.exa.ai/search and https://api.exa.ai/contents carry Arc accepts with the ids arc-usdc-gateway and arc-usdc-circle, next to their Base and Solana options.
A concrete origin, ready to index
https://api.cra-agent.tech sells Arc chain data by the call: base fee forecasts, contract deploy history, RPC health, and executed prices for a pair against USDC.
It is discoverable exactly the way @agentcash/discovery expects. discoverOriginSchema({ target: "https://api.cra-agent.tech" }) returns found: true, source: openapi, 15 endpoints, no warnings, with six paid operations carrying x-payment-info and their x402 options. The spec is at https://api.cra-agent.tech/openapi.json and one of the priced routes is https://api.cra-agent.tech/v1/paid/fx/execution.
Offer
If adding a chain is mainly SUPPORTED_CHAINS plus chain metadata and whatever feeds the per-chain transfer indexing, we are happy to open a PR with the Arc definitions and test it against a live mainnet origin. Tell us how you would want it wired, in particular which data source you use to index transfers per chain, and we will follow that shape rather than guess.
What happens today
Resources priced on Arc (Circle's USDC-native L1, chain id 5042) cannot be registered.
public.resources.registeranswers:registerFromOriginthen reportsnoValidResources, because public catalog rows only register alongside a valid paid resource, and every paid resource on such an origin is on Arc.The rest of the pipeline works fine: the 402 is read, the accepts are parsed, the description and service name come through. Only the chain gate stops it.
Why Arc may be worth indexing
GET https://gateway-api.circle.com/v1/x402/supportedlistseip155:5042with theexactscheme, USDC at0x3600000000000000000000000000000000000000(6 decimals) and the batched GatewayWallet at0x77777777Dcc4d5A8B6E418Fd04D8997ef11000eE.https://api.exa.ai/searchandhttps://api.exa.ai/contentscarry Arc accepts with the idsarc-usdc-gatewayandarc-usdc-circle, next to their Base and Solana options.A concrete origin, ready to index
https://api.cra-agent.techsells Arc chain data by the call: base fee forecasts, contract deploy history, RPC health, and executed prices for a pair against USDC.It is discoverable exactly the way
@agentcash/discoveryexpects.discoverOriginSchema({ target: "https://api.cra-agent.tech" })returnsfound: true,source: openapi, 15 endpoints, no warnings, with six paid operations carryingx-payment-infoand their x402 options. The spec is at https://api.cra-agent.tech/openapi.json and one of the priced routes is https://api.cra-agent.tech/v1/paid/fx/execution.Offer
If adding a chain is mainly
SUPPORTED_CHAINSplus chain metadata and whatever feeds the per-chain transfer indexing, we are happy to open a PR with the Arc definitions and test it against a live mainnet origin. Tell us how you would want it wired, in particular which data source you use to index transfers per chain, and we will follow that shape rather than guess.