Fixed-scope x402 assurance audit

Find the payment failure before your buyer does.

A seven-business-day review of discovery, payment requirements, buyer policy, and delivery evidence across a bounded paid-agent surface.

Engagement price
$2,500 exactly
Route limit
Up to 12 routes across two domains
Delivery
Seven business days after inputs
Review time
One kickoff + one findings readout

What is included

A bounded test surface and a decision-ready evidence pack.

Scope is confirmed before checkout. Tests are read-only and no-payment by default. Any paid-call execution requires a separate written spend cap.

WorkstreamIncluded testDelivered evidence
Route inventoryUp to 12 public HTTP routes on at most two domains; method, path, discovery source, expected price, network, and response shape.Versioned route inventory in Markdown and CSV.
Discovery + schemaManifest reachability, required x402 fields, content type, method/path agreement, schema references, and duplicate or stale entries.Validation register with source URLs and captured timestamps.
Unpaid 402 behaviorThree no-payment probes per route, bounded to 12 seconds each; status, requirements, price, network, pay-to, and error behavior.Price/network/failure map with eligible denominators.
Buyer policyOne policy matrix covering allow/deny/review rules for price, network, domain, pay-to, schema, and settlement requirement.Recommended buyer-policy configuration and exceptions.
Paid-call planTest cases, maximum approved spend, expected output, stop conditions, and evidence capture. Execution is excluded until separately approved.Reviewable paid-call plan; no wallet access requested.
Outcome evidenceReceipt fields, response hash, delivery-state logic, and failure escalation path against the frozen MAKO receipt contract.Redacted signed evidence-pack structure and gap analysis.

Delivery plan

Seven business days, with two decision points.

The clock begins when the route list, expected behavior, and technical owner are confirmed.

Day 0 — scope lock

30-minute kickoff. Confirm the 12-route ceiling, domains, expected price/network, required response shape, and exclusions.

Days 1–2 — inventory and discovery

Freeze the route inventory, validate public manifests, and establish the source-linked test matrix.

Days 3–4 — probe and policy review

Run bounded no-payment tests, map mismatches and failure states, and draft buyer-policy recommendations.

Days 5–6 — evidence and severity review

Assemble the evidence pack, classify findings, and prepare any separately approved paid-call plan.

Day 7 — findings readout

45-minute review with go/no-go decisions, remediation order, and one written factual-correction window within three business days.

Sample deliverable

See the structure before you buy.

The sample is redacted and illustrative. Findings are tied to captured evidence, not generic risk scores.

Finding A-03 · high

Listed network differs from observed payment requirements

Route:

Observed: Directory record declared eip155:; three timestamped 402 responses required a different network.

Buyer impact: A policy that trusts discovery alone can prepare the wrong asset or reject a valid route late.

Acceptance test: Discovery and live requirements agree for three consecutive no-payment probes after remediation.

Evidence: Source URL, request timestamp, response hash, parsed requirement fields, and screenshot-free machine record.

Operating boundaries

Clear responsibilities prevent open-ended scope.

This is an evidence and decision engagement. It is not penetration testing, code remediation, custody, insurance, or an uptime guarantee.

Client responsibilitiesProvide the final public route list, expected behavior, a technical owner, known maintenance windows, and written approval for any paid-call spend.
Acceptance criteriaAll in-scope routes appear in the inventory; every included test has a result or documented blocker; findings contain evidence, severity, owner recommendation, and retest condition; both review sessions are delivered.
ExclusionsSource-code review, exploit testing, wallet/key access, private-data collection, production changes, remediation implementation, legal/compliance opinions, recovery, and ongoing monitoring.
Serious failureMAKO freezes the evidence, stops the affected test path, and notifies the named technical owner within one business day. No destructive validation or public disclosure occurs. A remediation retest is scoped separately unless it fits the original unused route budget.
Monitoring follow-upAn optional recurring service can re-run the agreed no-payment probes, track price/network/schema drift, and issue a bounded evidence digest. Cadence, route ceiling, and price require a separate proposal.