DEV Community

rambo
rambo

Posted on

AI Agent Receipt Pricing: What Verifiable Execution Receipts Actually Cost in 2026

#ai #agents #devops #pricing

Your agent says it did the thing. The receipt is the part that proves it. This is a buyer's guide to what that proof costs in 2026: what drives the price, the three pricing shapes you will actually encounter, what to check before you pay, and real numbers from one live provider so you can calibrate everything else against something concrete.

Disclosure up front: I run ops for Zambo (zambo.dev), the receipt layer this guide uses for its worked numbers. Every figure below was pulled from live pages on the day this was written, and I will tell you exactly where each one came from. If a vendor cannot do the same for their own pricing, that tells you something.

What you are actually buying

A verifiable execution receipt is a tamper-evident record of what the execution layer actually did: the tool called, the inputs, the outputs, and a hash you can recompute. Not a log line that says "done." Not a summary written by the same model that did the work. A record a third party can check independently.

When you pay for receipts, you are paying for four things, and it helps to price them separately in your head:

  1. Capture. Somebody has to observe the tool call at execution time and write down what happened. Cheap to do, expensive to fake after the fact, which is why capture-at-execution is the whole game.
  2. Depth. A basic receipt says what ran and what came back. A deep receipt carries the full evidence: inputs, outputs, timing, the chain of calls. Depth is where most of the real cost lives, because it is storage and structure, not just a hash.
  3. Retention and hosting. A receipt you cannot retrieve in six months is a souvenir, not proof. Somebody hosts an index, serves the records, keeps them queryable.
  4. Verification. Recomputing a hash is cheap. Running a full verify pass over a chain of calls, or having a hosted agent do it for you, is the part vendors charge for.

Any pricing page that does not let you map its tiers onto those four is selling you a vibe. Keep that test in your pocket for the rest of this guide.

The three pricing shapes you will actually encounter

Shape 1: free tier with hard per-tool limits. The honest version looks like this: a fixed number of calls per tool per day, no account, no credit card, full receipts on every call. The limit is the business model. You get to see a real receipt with your own eyes before spending anything, and the vendor gets a funnel of people who have already touched the product. The dishonest version is "free" that requires a sales call. If the free tier needs a meeting, it is not a free tier, it is a demo with extra steps.

Shape 2: day pass or burst pricing. A flat fee for 24 hours of authenticated access. This exists for one reason: real workloads are spiky. You have a migration weekend, a batch audit, a demo day. You do not want a monthly subscription for a Tuesday. Day passes are the most underrated pricing shape in agent infrastructure, and the vendors that offer them tend to understand how agents actually get used.

Shape 3: subscription passes. Monthly or annual, one connection, ongoing access. This is the shape for production workloads: the agent that runs every day, the pipeline that never sleeps. The honest versions include the extras that production actually needs (quota headroom, audit capacity, provider allowances) instead of nickel-and-diming each one. The dishonest versions are seat-based. Agents do not sit in seats. Any receipt pricing still denominated in seats in 2026 is a SaaS pricing page wearing an agent costume.

The buyer's checklist

Before you pay anyone for execution receipts, get answers to these seven questions. In writing, on a pricing page, not on a call.

  1. Is the hash recomputable by me? If only the vendor can verify the receipt, you have outsourced trust, not created proof. The receipt must carry enough evidence for an independent third party to redo the math.
  2. What is the per-call granularity? Per-tool daily limits are legible. "Credits" that convert to calls at a ratio buried in a footnote are not. Ask what one credit buys, in calls, in writing.
  3. What does a deep receipt cost versus a basic one? Most workloads need basic receipts for routine calls and deep receipts for the calls that matter (payments, production writes, anything audited). If the vendor has one receipt depth, you will overpay for the routine and under-prove the critical.
  4. Where do receipts live, and for how long? A shareable URL per receipt is the minimum. Ask about retention windows and export. Your auditor in eighteen months does not care about the vendor's dashboard.
  5. Does verification work across AI clients? Your work will move between Claude, ChatGPT, Cursor, and whatever ships next quarter. A receipt format that only verifies inside one vendor's walled garden is a tax on switching.
  6. What happens at the limit? Calls pause until reset, or you upgrade, and nothing is ever charged without you choosing it. That is the honest shape. Anything that auto-bills on overage without a hard confirmation is a trap.
  7. Is there an open spec? A receipt format moving toward standardization (Zambo's AER-1 is an individual Internet-Draft, explicitly a work in progress, not a finished standard) is worth more than a proprietary format, because your receipts outlive your vendor relationship.

Real numbers, one live provider

Here is Zambo's actual pricing, pulled live from zambo.dev/pricing/ and zambo.dev/pricing/pay-per-call/ on the day this was written. Pricing on the site is set by the founder, and the pay-per-call page's FAQ is explicit that the Day Pass page is the source of truth for entitlements rather than duplicating them here. I am doing the same: these are the headline numbers, the site has the fine print.

  • Free: $0, forever. 20 calls per tool per day. No account, no credit card. Every call, free or paid, returns a verifiable receipt you can inspect, share, or build on.
  • Day Pass: $1.49 for 24 hours. Authenticated access from the moment you start it. Built for the spiky workloads described above.
  • Zambo Pass Monthly: $49. Ongoing access through one MCP connection, plus the listed pass entitlements.
  • Zambo Pass Annual: $399. One year of the same entitlement set.
  • $ZAMBO holder: $29/month. For verified holders of $10 or more in $ZAMBO.
  • Secondary receipts: $0.10 basic, $0.50 deep, per receipt, on all plans. This is the depth pricing from the checklist's question 3, answered as a number instead of a paragraph. Need receipts beyond your plan's included depth and you pay per receipt, at two depths, on every plan including free.
  • Payment: PayPal, card, or USDC on Base.

The unit economics, done honestly: at 20 calls per tool per day free, a single developer running a daily audit agent across a handful of tools stays free for a long time. The day you need more, $1.49 buys you 24 hours of everything. The per-receipt depth pricing means you are never paying deep-receipt prices for routine calls. That mapping, free calls plus burst plus depth-priced receipts, is exactly the four cost drivers from the top of this guide, each with its own price.

Scale note, because "trust us, it works" is not a number: the public receipt wall at zambo.dev carries more than 34,000 public receipts, and the traffic behind them is predominantly automated operations. That is the point. Receipts are machine-scale infrastructure, and the pricing has to survive machine-scale volumes. Per-receipt depth pricing at ten and fifty cents is what that looks like.

What to do with this

If you are evaluating receipt providers this week, run the seven-question checklist against each pricing page and watch how many questions get answered in writing versus on a call. The vendors with the best answers tend to be the ones with the shortest pricing pages. Then go run twenty free calls somewhere and look at an actual receipt before you believe any of it, including this guide.

Go deeper:

Top comments (0)