Payment intelligence · read only

Know the payment surface before the wallet moves.

Before paying an unknown x402 resource, inspect its payment requirements, price, network, asset, receiver, discovery metadata, and observable operational signals.

Run a free inspection Read the contract

No wallet connection
No payment headers forwarded
No automatic spending

Free endpoint

Inspect without presenting payment credentials

The server performs bounded HTTPS probes only. Targets and every redirect are checked against private and reserved networks.

Machine-readable report

Inspection result

Ready

Submit a public HTTPS x402 resource to see its challenge, policy checks, evidence, and claim boundary.

Canonical agent surface

One decision path. Three capabilities.

01

inspect_x402_endpoint

Use first for a bounded, free read of the live payment challenge.

FREE POST /api/preflight/inspect
02

audit_x402_endpoint

Use when a buyer needs deeper discovery, schema, CORS, redirect, and cache evidence.

$0.05 x402 POST /api/x402/preflight/audit
03

order_x402_remediation

Escalate a blocked or risky audit into a durable remediation intake.

$100 USDC x402 POST /api/x402/preflight/remediation

Evidence, not endorsement

What a report can—and cannot—tell an agent

CHECKS

Observable now

HTTP 402 challenge and x402 version
Scheme, network, asset, amount, and receiver
Bazaar, OpenAPI, llms.txt, and agent metadata
CORS, redirects, content type, cache, latency, and size

BOUNDARY

Not guaranteed

Seller identity, intent, or future availability
Contract safety or downstream business outcome
That a later payment will verify or settle
That the resource remains unchanged after expiry

Fixed-price QA intake

$100 to $150

Native USDC · Base

Turn a risky payment edge into a bounded engagement

Commission deterministic x402 payment-security or agent-QA work with the commercial boundary settled before implementation.

Scope: Exact repository, version, endpoint, and failure matrix.
Acceptance: Clean-checkout reproduction, passing checks, and buyer acknowledgement.
Timing: Typically 48 hours after written technical and payment confirmation.
Payment: Prepayment or escrow preferred; accepted-delivery terms available.

Open the service intake Inspect a sample QA packet

Agent integration

Discover once, call through the interface you already use

HTTP + OpenAPI

Strict request, report, receipt, and error schemas are published at the canonical contract.

Open /openapi.json

Remote MCP

Streamable HTTP tool discovery exposes exactly the same three capabilities and no labs tools.

/mcp

x402 + Bazaar

The unpaid 402 response remains authoritative for live price, network, asset, and receiver.

Open x402 metadata

Labs and legacy endpoints

Existing wallet readiness, market data, weather, repository snapshots, marketplace adapters, and signing helpers remain available for current consumers. They are compatibility surfaces, not primary x402 Preflight capabilities.

See compatibility routes in the manifest