Submit your listing

The catalog is curated — there are intentionally no open, unauthenticated write endpoints. Listings are added through a reviewed flow, then ingested into the live catalog that agents search.

Before you submit

• Your endpoint is x402-payable and served over HTTPS — see Make an x402 endpoint.
• You have a valid listing entry (id, name, description, mcpUrl, services[]).
• payTo is pinned to your real settlement address and matches your 402 challenge — see pricing & payTo.
• active is true.
• You've read the security requirements.

Submit

Submit your JSON listing entry for review through the operator console. A listing can advertise up to several endpoints; bulk submissions are validated against the schema before ingestion.

Include:

1. Your provider entry JSON (validated against the schema).
2. The settlement address you want to receive USDC at (payTo).
3. A short note on what each capability returns.

To request onboarding, reach out via xdcai.tech.

What happens next

1. Review — the entry is validated and vetted (see security).
2. Ingestion — it's added to the catalog; the payTo recipient is attached.
3. Live — your services appear in marketplace_list and are payable via call.

After you're live

• Verify discovery: npx xdcai marketplace list --search "<your,tags>" and confirm your service ranks.
• Verify payment: call your own endpoint through npx xdcai call <url> and confirm the USDC lands at your payTo.
• Update: to change price, add endpoints, or deactivate, resubmit your entry — edits go through the same review.

tip

Usage builds credibility: marketplace list --sort most-used ranks services by real call volume, so reliable, well-described endpoints surface first.