Edge Delivery StudioCloudflare x402 delivery Scope one route

Paid APIs and MCP tools on Cloudflare Workers

Make one useful route payable—without putting wallet keys in your Worker.

We review implementation readiness or launch a bounded x402 v2 flow with exact payment requirements, replay and failure checks, redacted evidence, and rollback.

  • No private keys
  • One fixed route
  • No revenue promise

Failure-first evidence

The useful response stays closed when payment evidence is wrong or ambiguous.

01

Freeze the terms

Network, asset, amount, payTo, route, timeout, facilitator, useful response, and rollback are explicit.

02

Reserve first use

A durable atomic record rejects same-route replay, cross-query rebinding, and concurrent duplicates.

03

Fail closed

Missing state, malformed payloads, verify failure, settlement failure, and ambiguous outcomes never release the result.

04

Show the limits

EIP-3009 signs transfer fields—not the complete URL. The residual risk remains visible in the handoff.

Fixed scope and price

Start with the smallest funded step that resolves the uncertainty.

No production write

x402 Readiness & Failure Review

$199

2 business days after complete inputs

  • One route and buyer outcome
  • Asset, network, facilitator, replay, timeout, privacy, and rollback map
  • Exact implementation and acceptance plan
  • One bounded revision
Request the review

Up to three routes

Paid MCP/API + Migration Evidence

$799

5 business days after complete inputs

  • Everything in the Launch Sprint
  • Up to three bounded routes or MCP tools
  • Discovery metadata and cross-route replay tests
  • Facilitator migration dry run and seven-day review
Request the evidence package

Delivery sequence

Scope, test, deploy, prove, hand off.

No production access is requested until the route, evidence, permissions, change window, and rollback are written down.

  1. 1
    Freeze one outcome

    One method, route, response, price, destination, and acceptance test.

  2. 2
    Exercise failures locally

    Wrong fields, replay, duplicate, failure, timeout, logging, and side-effect behavior.

  3. 3
    Use isolated Cloudflare resources

    Scoped temporary access, exact bindings, bounded test window, captured rollback.

  4. 4
    Deliver evidence

    Source/config diff, lock file, redacted responses, limits, operations, and cleanup.

Eight redacted inputs

Enough context to quote one bounded route.

Email these without passwords, OTPs, seeds, private keys, payment signatures, customer data, or unrestricted credentials.

Email the scope
  1. Buyer and outcomeWho pays and what useful result is released?
  2. Method and routeExample request, response, and acceptance test.
  3. Current WorkerRedacted source, config, bindings, and resource owner.
  4. Side effectsPure/read-only or mutation, job, email, or purchase.
  5. Payment termsAsset, contract, CAIP-2 network, amount, and timeout.
  6. Public destinationCustomer-controlled receive address only.
  7. FacilitatorProvider, limits, account state, and non-secret status.
  8. Change controlPermission mode, backup, rollback, and test window.

Explicit exclusions

A bounded launch is easier to trust.

No wallet custody, token purchase, autonomous refund, smart-contract audit, guaranteed crawler payment, revenue guarantee, legal/tax advice, 24/7 support, unlimited routes, unrestricted production access, or Cloudflare/Coinbase endorsement. Cloudflare Monetization Gateway is not sold as enabled.

Short answers

Before you send access.

Do you need my wallet private key?

No. A customer-controlled public destination is enough. Never send seed or private-key material.

Will agents definitely pay?

No. The delivery proves the technical gate and evidence path, not willingness to pay.

Is the full URL cryptographically signed?

No. EIP-3009 signs transfer fields. We add application comparison and durable first use, and document the remaining risk.

When does work start?

After written scope, complete redacted inputs, and confirmed payment or funded marketplace escrow.