WORKFLOW 02 / AGENT PRE-PAYMENT POLICY

Reject changed payment terms
before your agent signs.

Submit the x402 v2 payment requirement your agent received and compare its network, asset, payee, amount, scheme, resource, and timeout with the policy you expected. The model never receives signing authority.

Inspect fixed example ↗Review integration boundary →

PAID PRODUCT

Challenge audit

$0.01

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

POST /v1/audit/challenge

WHEN TO RUN IT

Before the first payment to an unfamiliar x402 merchant.
When a previously approved merchant changes its payment requirement.
When the requested amount approaches a local per-call or cumulative ceiling.
When marketplace metadata and the live HTTP 402 do not match exactly.

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.

x402 v2 structure, exact-payment scheme, and timeout bounds.
Expected Base network and native-USDC asset.
Expected payee, maximum atomic amount, and canonical resource URL.
Cross-field consistency and high-risk policy mismatches.

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
Fetch the live unsigned HTTP 402 without loading a wallet.
02
Compare every payment field with an owner-controlled allowlist.
03
Send only the payment requirement and expected policy for the paid audit.
04
Keep signing isolated and never retry an ambiguous settlement automatically.

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