x402-discoverable

Make an x402 API discoverable

Use opendexter audition to discover and register an x402 API's routes in the OpenDexter / x402gle catalog. A server origin registers routes. A specific endpoint URL requests an immediate test that can pay the endpoint, evaluate its response, and save a score. Registration and scoring are separate outcomes.

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.

OpenDexter's platform verifier funds the test. Funding the seller's connected wallet does not fund this command. Check the returned result to see whether the test completed.

When this skill applies

Use it when the user's API already returns HTTP 402 with a valid payment manifest. Use the x402-server skill first if the API still needs its paywall.

The one command

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

• Pass a server origin to discover and register its routes without an immediate paid test.
• To request an immediate test, pass a specific endpoint URL.
• Use --json when an agent needs the structured result. Omit it for a human reading the summary. Add --verbose for request references and HTTP response metadata on stderr.

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

Discovery requirements

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

1. OpenAPI 3.1 document at /openapi.json (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. A bare probe of a URL that returns HTTP 402 with a valid payment manifest.

If discovery returns discovery_failed, read its message and warnings. Check that the advertised discovery document is reachable and describes the routes.