x402 Explained: The Stablecoin Rail for Agent Payments
x402 lets agents pay per-request in USDC over HTTP 402, with no human approval step. Adoption as of March 2026, and the governance questions it raises.
Attribute AI agent and model spend; budgets (Team and Enterprise) pause or block new tasks and refuse an over-budget model call through the gateway.
Learn how to attribute, budget, forecast, and enforce AI agent spend across your organization — the complete FinOps discipline for agentic AI.
Read the guide →x402 lets agents pay per-request in USDC over HTTP 402, with no human approval step. Adoption as of March 2026, and the governance questions it raises.
ACP and AP2 both let AI agents complete purchases, but through different mechanisms and governance models. What each one actually does, as of mid-2026.
AP2 authorizes AI agent purchases through signed Mandates, not a single API call. Version, governance, and mechanism as of April 2026.
Static budgets catch the disaster and miss the drift. Which agent spend signals are worth alerting on, why agents are easy to baseline, and how to avoid noise.
Denial of wallet attacks run up the bill until you take your service down yourself. How the attack works against agentic systems and which controls stop it.
Spend caps and request throttling are different levers for controlling runaway AI agents. Learn when each applies, how they compose, and why you need both.
Sending every request to your best model is the costliest way to run an agent. Model routing strategies that hold quality, ones that cost more, and governance.
Calculate AI agent cost per completed task, including failed attempts and retries. Use a reproducible example and a checklist for a defensible benchmark.
Set enforceable AI agent budgets with reservation-based enforcement, graduated thresholds, and clear attribution — before overruns reach your invoice.
Loop-and-burn failures drain AI budgets fast. Learn the blast radius, five root conditions, and the layered controls that stop runaway spend before the invoice.
Agent token usage is forecastable as volume times cost per task, not an extrapolated total. The decomposition, the non-linearities, and what to plan for.
Agent loops resend the same context every step, which is what prompt caching is for. How to structure prompts for cache hits, what breaks them, and the risks.
Agents that transact need a credit wallet with reservations, atomicity, and idempotency. The ledger design that makes agent payments auditable.
Where LLM costs hide in agentic applications, how to attribute them per agent and run, and the reservation-based enforcement that stops overspend at dispatch.
A framework for modeling unit economics in agentic products — cost per task as a variable formula, margin sensitivity, and the drivers that move it.
A decision framework for choosing reserved capacity versus on-demand LLM spend, based on workload predictability, volume confidence, and switching cost.
A procurement checklist for evaluating agentic AI tools across cost structure, integration burden, governance fit, and organizational readiness.
The commercial levers in an LLM provider contract — commitment structure, overage treatment, data-use terms, and portability — and how to evaluate each one.
A method for costing AI agent downtime as a formula across direct, cascading, and recovery terms, so availability investment can be sized rationally.
A decision framework for choosing chargeback or showback to allocate AI agent costs internally, with the data prerequisites and failure modes of each.
A template and cadence for reporting AI agent risk to the board — exposure, control coverage, incidents, and regulatory posture — in board-appropriate language.
A ready-to-use security questionnaire for AI agent and MCP tooling vendors, covering identity, isolation, audit, retention, subprocessors, and exit.
A TCO model structure for AI agents that covers inference spend, tooling, integration, oversight labor, and failure cost — with a worked illustrative example.
How to structure an AI agent business case for a CFO — fully loaded cost, risk-adjusted value, payback framing, and the questions engineering teams miss.
Signed webhook verification, idempotent handlers, reconciliation, and a dunning state machine are the four layers that keep billing state correct.
Per-connection usage tracking attributes every AI request and dollar to its source, enabling accurate chargebacks, capacity planning, and anomaly detection.
How AI marketplaces track MRR, ARR, and per-agent earnings, and manage partner payouts — the outbound money flow that billing dashboards miss.
How Praesidia's budget policies (Team and Enterprise) pause or block new agent tasks at a threshold you set and refuse over-budget gateway model calls.
A prepaid credit ledger with per-agent usage records gives you real-time visibility into AI spend and a hard gate that stops agents before they overspend.
How subscription plans, metered usage, invoices, and enterprise contracts fit together so AI token and tool costs map cleanly to billing.