Check an agent-payment prototype before it touches real value.

Agentic commerce is moving from demo rails to payment loops. This browser-only check scores x402, API-payment, and agent-commerce projects for budgets, approvals, receipts, replay protection, webhook proof, remote auth boundaries, and abuse controls.

run check MCP pulse Shipcheck trend sources

privacy: no upload
trend: x402
output: risk report

commerce gate

$ gate agent-payment-flow
rail: x402 / API payment / checkout
checks: budget, approval, receipts
guards: replay, signature, allowlist
evidence: env, webhook, audit log
result: score + launch report

Project name Repo, demo, or docs URL

Project files

Choose a project folder or selected files. Analysis runs locally in the browser.

No files loaded yet.

Paste extra file text

Manual proof Demo can run in sandbox, testnet, dry-run, or zero-value mode. Every autonomous payment path has a spend cap or allowance. Higher-risk purchases require a human approval checkpoint. Payment attempts write a receipt, ledger, or audit event. Failed, disputed, or partial payment states have a documented path.

why now

The money rail is becoming part of the agent stack.

payment scopes

x402

HTTP-native payment loops need guardrails.

Payment headers and 402 flows are easy to demo. The durable product work is spend limits, replay safety, and receipts.

mcp + a2a

Agent tools need economic boundaries.

Once tools can spend, auth scopes and tool permissions become business controls, not just developer docs.

web data

Paid data access raises the support bar.

Agents buying API calls or web data need provenance, quotas, and failure handling before users trust the loop.

launch

Proof beats hype.

A working checkout is not enough. Show sandbox mode, audit trail, abuse controls, and exactly what the agent may buy.

current signal

Sources behind this check.

hackathon

Bright Data Web Data UNLOCKED

May 25-31, 2026 hackathon with tracks for consumer payment agents, B2B FinOps/compliance, and x402 commerce primitives.

open source

rail

x402 developer momentum

Developer docs and recent hackathons are centering pay-per-use APIs and machine-to-machine agent payments.

open source

security

Agent-commerce attack surface

Recent research frames agent payments around discovery, authorization, execution, accounting, and new abuse paths.

open source

production

MCP production readiness

Production agent systems still need identity propagation, timeouts, structured errors, and observability around tools.

open source

offer

Agent-commerce readiness review starts where the free gate leaves off.

Send the repo, payment flow, and demo mode. The paid pass returns a ranked risk report and smallest safe launch path.

send project