Paid implementation plans

Tested plans for agentic businesses.

Inspect the evidence for free. Buy the complete Markdown plan with x402 or MPP.

Plans

3 ready

Sell one existing HTTP route with x402 V2

$0.50 · revised 2026-08-23

Outcome

This plan adds a $0.50 x402 V2 payment gate to one existing FastAPI GET route.

The route accepts Base USDC through the CDP facilitator. Its first 402 challenge includes CDP Bazaar discovery metadata.

The final proof is an HTTP 200 response, a settlement receipt, and a successful Base transaction.

This plan does not contain a code package. It contains commands and code blocks that you apply to your API.

Tested environment

ItemTested value
OSUbuntu 26.04 LTS, x86_64
Python3.14.4
pip25.1.1
cdp-sdk1.47.1
fastapi0.141.1
httpx0.28.1
python-dotenv1.2.3
uvicorn0.52.3
x4022.19.0 with `evm`, `extensions`, and `fastapi` extras
x402 networkeip155:8453` (Base mainnet)
Base USDC0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
CDP facilitator basehttps://api.cdp.coinbase.com/platform/v2/x402
Facilitator supporthttps://api.cdp.coinbase.com/platform/v2/x402/supported
Facilitator verificationhttps://api.cdp.coinbase.com/platform/v2/x402/verify
Facilitator settlementhttps://api.cdp.coinbase.com/platform/v2/x402/settle

Friction sections

  • Friction 1: Pin the environment before you edit the route
  • Friction 2: The receiver does not need a hot key
  • Friction 3: Store the facilitator keys without exposing them
  • Friction 4: FastAPI and x402 use different path-parameter syntax
  • Friction 5: Make sure that the 402 occurs before request validation
  • Friction 6: Read the amount from the V2 header
  • Friction 7: Use a separate buyer with a hard cap
  • Friction 8: Bazaar indexing starts after settlement

23 acceptance checks

View the complete order on BaseScan

Paste into your coding agent

Buy Sell one existing HTTP route with x402 V2 for $0.50.

Use one of these paid GET routes:
- https://krimskrams.xyz/v1/plans/plan-1-sell-one-route-x402-v2 over x402 on Base USDC
- https://krimskrams.xyz/mpp/v1/plans/plan-1-sell-one-route-x402-v2 over MPP on Tempo

JSON catalog slug: plan-1-sell-one-route-x402-v2

Sell one existing HTTP route with MPP

$0.50 · revised 2026-08-24

Outcome

This plan adds a $0.50 MPP payment gate to one existing FastAPI GET route.

The route accepts USDC.e on Tempo mainnet. The seller verifies and settles the payment through the public Tempo RPC.

The final proof is an HTTP 200 response, an MPP receipt, and a successful public Tempo transaction.

This plan does not contain a code package. It contains commands and code blocks that you apply to your API.

For the Base x402 rail, use the [x402 companion plan](./plan-1-sell-one-route-x402-v2.md).

Tested environment

ItemTested value
OSUbuntu 26.04 LTS, x86_64
Python3.14.4
pip25.1.1
pympp0.10.1 with the `tempo` extra
fastapi0.141.1
uvicorn0.52.3
httpx0.28.1
python-dotenv1.2.3
eth-account0.14.0
MPP specification0.1
Tempo networktempo-mainnet`, chain ID `4217
Tempo USDC.e0x20C000000000000000000000b9537d11c60E8b50`, 6 decimals
Tempo RPC and settlement endpointhttps://rpc.tempo.xyz
MPP facilitator endpointNone. This flow verifies and settles directly through the Tempo RPC.
Tempo explorerhttps://explore.tempo.xyz

Friction sections

  • Friction 1: Pin the environment before you edit the route
  • Friction 2: Keep the recipient key off the API host
  • Friction 3: Protect the MPP server secret
  • Friction 4: Put validation before settlement
  • Friction 5: Publish the route manifest
  • Friction 6: Inspect the Payment challenge
  • Friction 7: Use a capped buyer for the live test
  • Friction 8: Verify the settlement through the Tempo RPC

0 acceptance checks

No BaseScan order is listed.

Paste into your coding agent

Draft. This plan is not available for purchase.

JSON catalog slug: plan-3-sell-one-route-mpp

List one x402/MPP route on the discovery indexes

$0.50 · revised 2026-08-24

Outcome

This plan makes one paid route readable by x402 and MPP discovery systems.

The route gets two manifests, a public OpenAPI document, and entries on x402scan and MPPScan.

CDP Bazaar catalogs the x402 route after its first settled payment. It has no registration form or registration API.

First, sell the route with the [x402 seller plan](./plan-1-sell-one-route-x402-v2.md) or the [MPP seller plan](./plan-3-sell-one-route-mpp.md).

This plan does not contain a code package. It contains commands and JSON blocks that you apply to your API.

Tested environment

ItemTested value
OSUbuntu 26.04 LTS, x86_64
KernelLinux 7.0.0-29-generic
curl8.18.0
jq1.8.1
Python3.14.4
Node.js24.18.0
x402 manifesthttps://krimskrams.xyz/.well-known/x402`, HTTP 200, valid JSON
MPP manifesthttps://osha-search.46-224-157-88.sslip.io/.well-known/mpp.json`, HTTP 200, valid JSON
OpenAPI documenthttps://krimskrams.xyz/openapi.json`, HTTP 200, OpenAPI 3.1.0, contact present
x402scan recipient pageHTTP 200, resource `38901bc4-2174-464d-b85d-5a814d5148f1` present
MPPScan OSHA pageHTTP 200, server `16b1760a565ca299ac553baf669f47bea27bbcf8b9fb64ba49723bcc671ab7b9

Friction sections

  • Friction 1: Publish the x402 well-known manifest
  • Friction 2: Publish the MPP manifest
  • Friction 3: Keep the OpenAPI document on
  • Friction 4: Register the x402 route on x402scan
  • Friction 5: Register the MPP origin on MPPScan
  • Friction 6: CDP Bazaar starts after settlement

0 acceptance checks

No BaseScan order is listed.

Paste into your coding agent

Draft. This plan is not available for purchase.

JSON catalog slug: plan-4-list-one-route-discovery-indexes