WORKFLOW 01 / MERCHANT RELEASE REGRESSION

Catch x402 discovery drift
before the release ships.

Submit a candidate OpenAPI document and receive a deterministic report covering the payment and discovery declarations agents rely on. Run it when a merchant changes routes, prices, schemas, or x402 metadata.

Inspect fixed example ↗Review integration boundary →

PAID PRODUCT

Discovery audit

$0.02

Native Base USDC · one deterministic report · caller-supplied JSON only

POST /v1/audit/discovery

WHEN TO RUN IT

Before publishing a new paid route or changing an existing one.
When a price, payment scheme, network, asset, or payee declaration changes.
When request, success, or HTTP 402 response schemas change.
When marketplace discovery differs from the candidate OpenAPI document.

WHAT IT CHECKS

One narrow job. Machine-readable evidence.

Andromalius inspects the submitted JSON in memory, returns a deterministic finding set, and does not fetch the target service or retain the artifact.

OpenAPI 3.0 or 3.1 structure and paid-operation declarations.
Fixed pricing and x-payment-info coverage.
Documented HTTP 402, request, and success response schemas.
x402 discovery compatibility without crawling the target origin.

RECURRING OUTCOME

Turn a risky change into a repeatable gate.

Use free catalog, OpenAPI, discovery, and fixed-example routes for evaluation. A real caller-supplied audit remains paid and releases output only after successful x402 settlement.

01
Generate the candidate OpenAPI JSON inside the release pipeline.
02
Obtain and locally approve the exact $0.02 Base-USDC requirement.
03
Submit the artifact through a protected, reviewed x402 client.
04
Fail the release on high-risk findings or an ambiguous settlement.

Review the paid call →Open x402scan listing ↗

No wallet connection or payment occurs on this page. United States business users age 18 or older only. Terms · Privacy · Refunds