ACP vs AP2: Two Agentic Commerce Protocols Compared
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.
Attribute, budget, and cap the cost of AI agents, tokens, and tool calls.
Learn how to attribute, budget, forecast, and enforce AI agent spend across your organization — the complete FinOps discipline for agentic AI.
Read the guide →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. Learn which spend signals are worth alerting on, why agents are unusually easy to baseline, and how to avoid an alert channel nobody reads.
Denial of wallet attacks do not take your service down — they run up the bill until you take it down yourself. Here is how the attack works against agentic systems and which controls actually 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 most expensive way to run an agent. Learn the routing strategies that hold quality, the ones that quietly cost more, and how routing becomes a governance control.
What AI agents cost in 2026: public model list prices, worked per-task and per-month scenarios, and the budget heuristics that follow.
Set enforceable AI agent budgets with reservation-based enforcement, graduated thresholds, and clear attribution — before overruns reach your invoice.
Provider invoices tell you what you spent, not who spent it. Learn the attribution dimensions that make showback work, why they must come from the session, and how to allocate shared costs honestly.
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.
The full cost-control architecture for AI agents: how budgets, quotas, rate limits, and reservation-based enforcement fit together into one system.
Agent spend is forecastable if you model it as volume times cost per task rather than extrapolating a total. Learn the decomposition, the non-linearities that break naive projections, and what to plan for.
Agent loops resend the same context on every step, which is exactly what prompt caching is for. Learn how to structure prompts for cache hits, what invalidates them, and the security considerations.
Agents that transact need a spend mechanism with reservations, atomicity, and idempotency. Learn the ledger design that makes agent payments auditable and the concurrency bugs that make them wrong.
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 practical FinOps loop for agentic AI: attribute token and tool costs, set multi-level budgets, trigger alerts early, and enforce hard spend limits.
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 enforce hard spend caps: scoped policies, graduated threshold actions, and reservation accounting that stops overruns.
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.