x402-discoverable

Make an x402 API discoverable

An API that speaks x402 can take payment — but no agent will pay it until an agent can find it. Getting it into the OpenDexter / x402gle catalog is a distinct step, and it is the one this skill handles.

The catalog does not list an API by reading its description. It auditions it: discovers every paid route, makes a real paid call to each, AI-scores the live response, and synthesizes the agent-callable Skill other agents will use to call it. A passing audition lists the API automatically.

The verb is audition, and it is a subcommand of the OpenDexter CLI.

audition requests a server-side merchant test and can cause paid provider calls and catalog changes. It does not load a local signer or spend through the connected user's governed OpenDexter authority. Obtain explicit approval for the audition itself.

When this skill applies

Use it when the user's API already returns HTTP 402 with a valid payment manifest (if it does not yet, that is the x402-server skill's job — build the paywall first, then come back here).

The one command

npx @dexterai/[email protected] audition <server-url> --json

• Pass a server origin to audition every paid route on the server.
• Pass a single endpoint URL to audition that route (siblings are still discovered from it).
• Always use --json when you are an agent driving this — it is the machine-readable path. Omit it only for a human reading the summary.

No global install is needed; this command requests the exact pinned package version.

What discovery needs from the API

The audition finds paid routes three ways, in order of preference:

1. OpenAPI 3.1 document at /openapi.json (strongly preferred) — with info.x-guidance, a requestBody schema per paid operation, and an x-payment-info block carrying protocols (x402 and/or mpp) and a structured price.
2. /.well-known/x402 — a descriptor listing the paid routes.
3. Bare probe — the URL returns HTTP 402 with a valid payment manifest.