x402 Production Runway
These posts are about the Tangle Network protocol, a separate project from Tangle's infrastructure for AI agents. Introduction to Tangle covers the agent infrastructure.
x402 turns an HTTP 402 payment challenge into signed payment terms and a retried request. The Tangle Network is a protocol where independent operators run services: a Blueprint declares the typed Jobs a service accepts, each paid request becomes one Job, a facilitator verifies and settles the payment, and an operator runs the work.
For teams selling pay-per-request services: pricing, quotes, monitoring, deployment, and safe recovery when payment, facilitator, operator, or result state is uncertain.
Start by mapping one HTTP payment to a Job. Then choose a facilitator and set prices; quote and monitor operator work; protect private execution; and deploy, check the rollout, and judge product fit.
- 1 x402 Payments Blueprint: Turn HTTP into a Job
An x402 payment authorizes one Tangle Blueprint job over HTTP; this guide covers settlement, quote expiry, retries, and evidence after execution.
- 2 The x402 Facilitator: Trust, Uptime, and Safer Failure
An x402 facilitator verifies and settles payments; compare hosted, self-hosted, and local options for uptime, trust, and safe failure.
- 3 Pay-Per-Request API Pricing: Wei and Markup
How a price in wei, the smallest unit of the native token, becomes accepted-token units, with decimals, markup, and quote freshness.
- 4 Subscription vs Pay-Per-Request API Pricing
Compare subscription and pay-per-request API pricing across margins, billing work, customer needs, latency, and a hybrid implementation for teams and agents.
- 5 x402 Operator Economics: Pricing Two Payment Paths
x402 operator economics starts by separating HTTP payments from Tangle service fees, then pricing operator costs, stake shares, payouts, and penalties.
- 6 On-Chain Compute Quotes: When to Bind the Operator First
When a signed request-for-quote (RFQ) earns its cost, what the contract checks, and why slashing, a stake penalty, needs evidence first.
- 7 RFQ Job Quotes on Tangle: Fields, Expiry, and Replay
Implement signed RFQ fields, expiry, replay protection, result authorization, and recovery when the selected Tangle operator fails.
- 8 Operator Monitoring: What a Green Health Check Misses
Choose the runtime, heartbeat, quote, payment, and result signals an operator should expose before a service quietly stops accepting work.
- 9 Operator Outage Recovery: When to Reopen Paid Traffic
Diagnose stale heartbeats, expired quotes, and worker failures, then decide which checks must pass before reopening paid traffic.
- 10 Secure Code Execution for AI Agents: TEEs and Payment
What payment, a trusted execution environment (TEE), attestation of the running code, and a result check each prove for a private inference job.
- 11 How to Deploy an AI Agent Service With Remote Providers
Deploy an AI agent service with paid HTTP ingress, remote operators, reproducible runtimes, health checks, and rollback for failed jobs.
- 12 x402 Blueprint Production Deployment Checklist
A rollout checklist that takes an x402 service from development to staging to mainnet, the live network, without silent payment or config failures.
- 13 Payment-Native Infrastructure for AI Agent Products
Which agent products fit per-request payment, such as a changed-file security review, and when a dashboard is still the right product.