Valid HTTP 402 response rate
Read the methodology and exclusions
82.6%3,049 of 3,690 observed probes
Payment assurance for autonomous software
Know what the agent pays for.
MAKO checks price, network, route quality, and buyer policy before an x402 payment, then records signed evidence of settlement and delivery after it.
Observed, not inferredPoint-in-time endpoint behavior. Not adoption, transaction volume, or revenue.
1,855services monitored
2,820payment requirements observed
297eligible price + network mismatches
The assurance gap
A payment can settle and still fail the buyer.
Payment protocols move value. They do not, by themselves, prove that the chosen route was sound, the price matched discovery, or the promised response arrived intact.
01 / Before
The agent sees a price, route, and network.
Discovery records drift. Endpoints fail. The listed price and the 402 response can disagree before a wallet ever signs.
02 / During
Settlement proves money movement.
It does not establish that the response schema, latency, content, and route behavior matched the buyer’s policy.
03 / After
The buyer needs evidence, not a memory.
Without a canonical receipt and delivery record, failure review becomes screenshots, logs, and incompatible accounts of what happened.
What MAKO sees
Probe the payment surface before trusting it.
MAKO’s observatory compares public discovery claims with live 402 behavior. Every number is tied to a timestamp, denominator, and stated limitation.
Mismatch evidence
Comparisons apply only when both listed and observed fields are eligible.
Why the bars use a 10× visual scale
The labels show exact observed rates. The fills are expanded so low single-digit differences remain legible; they are not a shared 0–100 axis.
The MAKO assurance loop
Policy before payment. Evidence after.
The product is a bounded decision and evidence layer around the payment rail. MAKO does not custody funds, automate payouts, or promise recovery.
Preflightallow / review / deny
Evaluate the route
Inventory, manifest validity, price and network agreement, endpoint behavior, and buyer-policy fit.
Settlementsigned receipt
Bind recorded payment evidence
Quoted amount, settled amount, payer, pay-to, transaction reference, and protocol metadata remain attributable.
Deliveryevidence pack
Record the outcome conservatively
Response hash, HTTP outcome, declared schema, and failure evidence separate delivered from failed, not observed, and unknown.
Fixed-scope engagements
Start with a decision you can review.
Both offers begin with qualification and scope confirmation. The approved engagement price is exactly $2,500; no fractional matching surcharge is added.
x402 assurance audit
For teams operating or buying from paid agent endpoints that need a bounded risk and delivery-evidence review.
- Up to 12 routes across two domains
- Discovery, 402, price, network, policy, and failure-map tests
- Signed evidence pack and executive readout
Facilitator design pilot
For facilitator and marketplace teams evaluating preflight evidence, signed outcomes, and a recurring reliability feed.
- Up to eight facilitator routes
- Read-only integration and outcome-contract design
- Go/no-go findings and recurring product proposal
Evidence boundaries
Trust starts with saying what the data cannot prove.
The repository, frozen receipt contract, public sensor snapshot, and bounded AsterPay integration reference are inspectable. None of them is presented as proof of market size or customer revenue.
AsterPay reference: public signer registry observed; sampled demo 402 did not expose the reliability extension.Inspect the integration reference
Receipt contract: canonical signed evidence with conservative delivery states.Read the developer contract
Company: MAKO is built by Chris Dover through Pollinate Research.Founder profile
Next action
Bring one endpoint.
We will confirm fit and scope before any engagement checkout or paid test.