# Qatom: full site text Generated from https://www.qatom.ai on 2026-10-14. Each section below is one page of the site, converted to Markdown. --- # Qatom | Built for people and their agents Source: https://www.qatom.ai/ # Let your agents buy and sell. All-in-one. Turnkey. Agentic commerce. They sell Your APIs, data, and services become storefronts that AI agents find, order from, and pay for. You keep 100% of the revenue and the customer relationship. They buy Your own agents discover and purchase the same way, inside spending limits you set, with a verifiable record of every call. [Create your storefront](https://www.qatom.ai/#get-started) [Schedule an Enterprise Demo](https://www.qatom.ai/enterprise-demo) **100,000+** payments in production **0%** platform fees **<1s** settlement Backed by **AWS** Your storefront is discoverable inside - [Image: Claude] - [Image: ChatGPT] - [Image: Microsoft Copilot] - [Image: Gemini] - [Image: Muse] - [Image: WhatsApp] - [Image: iMessage] - [Image: Grok] - [Image: Hermes Agent] Max Launch offer ## Six months of Max, on us. Start a 12-month Max plan and your first six months are free. Full platform, no risk. - Unlimited agents and transactions from day one - Up to 1,000 catalog items, Twin URLs and API keys - Priority onboarding from our team - Cancel any time in your first six months and pay nothing, or move to Pro at $20 per month Ready to start now? [Create your account →](https://dashboard.m.todaq.net/) Questions or want an enterprise estimate? [hello@qatom.ai](mailto:hello@qatom.ai) Pricing ## Flexible plans, from first endpoint to enterprise. Free $0 /mo Launch your first agentic API endpoint with one agent. - 1 agent - Up to 5 catalog items - Up to 25 transactions / month - Account API keys No card needed. Upgrade any time in Settings › Billing. [Create your storefront](https://www.qatom.ai/#get-started) Pro $20.00 /mo Full storefront capabilities for scaling startups and SMBs. - 3 agents - Up to 50 catalog items - Up to 250 transactions / month - Twin URLs and API keys Billed monthly from today. Change or cancel any time in Settings › Billing; changes are prorated. [Create your storefront](https://www.qatom.ai/#get-started) Max $300.00 /mo High-throughput multi-service management with advanced agent routing for growing teams. - Unlimited agents - Up to 1,000 catalog items - Unlimited transactions / month - Twin URLs and API keys Billed monthly from today. Change or cancel any time in Settings › Billing; changes are prorated. First 6 months free on Max → [Create your storefront](https://www.qatom.ai/#get-started) Enterprise Custom $10k+ Private cloud or on-prem, custom asset issuance, forward-deployed engineering. - Private cloud or on-prem - Custom asset issuance - Forward-deployed engineering - Dedicated support and SLA Custom terms for regulated, high-volume deployments. [Talk to us](mailto:hello@todaq.net) The problem ## The agentic commerce gap: your services are invisible to AI buyers. Customer search is shifting into AI chat channels and autonomous apps, yet only 2% of deployed agentic services are commerce-ready today. Providers lose ground because the current workflow is broken. ### 01Tool fragmentation Stitching disparate developer tools, payment gateways, and agent frameworks into one flow is complicated, expensive, and painful. ### 02No sovereign control Customers do not want big platforms holding their data, controlling their money, or mediating their customer relationships. ### 03No spending guardrails Buyers hesitate to deploy purchasing agents without strict, verifiable limits on automated spend. ### 04No convenience for end customers Current solutions cannot offer a combined simple experience for humans and agents alike. [Image: A developer working across live agent dashboards in a night office] The solution ## The all-in-one sovereign commerce platform for AI. Configure your services and easily edit, place selling agents in front of them, and let any human or AI agent discover, order, and pay, conversationally or per call. Traditional APIs Static documentation, then manual setup, then legacy invoicing and high gateway fees. Qatom storefront Instant agentic catalog, live discovery, per-call atomic settlement at 0% fees. How it works ## Live in three steps. 1 ### Build your catalog Add one or thousands of API endpoint catalog items. 2 ### Place a selling agent Drop it on your site, in WhatsApp or iMessage, or inside Claude, ChatGPT, Copilot, Gemini, Muse, Grok and Hermes. 3 ### Get paid per call Humans and agents discover, order, and pay. You keep 100%. ### Ready to put your API to work? List your first tool free and watch agents discover, order, and pay in minutes. [Create your storefront](https://www.qatom.ai/#get-started) Get the Max offer [Image: Two engineers reviewing agent activity on a monitor at night] Core capabilities ## Everything the storefront needs, in one platform. 1 ### One-stop agentic storefront setup Load one or thousands of API endpoints, inference pipelines, or proprietary datasets into a unified storefront. Deploy custom selling agents on your site, in WhatsApp, Telegram and iMessage, and directly inside Claude, ChatGPT, Microsoft Copilot, Gemini, Muse, Grok and Hermes. 2 ### Complete sovereign control Keep 100% ownership of your data, assets, storage, and revenue. Never ask permission from platforms, banks, or intermediaries to sell services, move funds, or issue custom digital assets. 3 ### Zero fees, settlement under one second Move money without the 2 to 4% transaction fees, card minimums, or gas costs of legacy gateways and blockchains. Every transaction settles with audit-grade cryptographic records. 4 ### Autonomous global market discovery Open your catalog to a growing market of over 100 million daily AI searches, over 100K companies, and 1 million developers. AIs, agents and people can discover and securely pay using just conversation. 5 ### Viral supply-chain payouts Automate instant payouts and revenue splits to suppliers, vendors, and partners. As partners receive payouts through Qatom, they reuse those funds across their own vendor networks, creating built-in growth. [Image: A security and compliance team reviewing live systems at night] Enterprise-grade trust ## Built for regulated, high-stakes industries. ### Banking and payment on-ramps and off-ramps Move funds between Qatom and your existing financial stack. Qatom connects with major banking networks, payment gateways, and non-bank financial institutions. StripeApple PayGoogle PayRevolutWiseUSDC ### Compliance and governance by design **Finance & banking.** Compliant, audit-ready agentic transactions with full transaction Binder history. **AI and agentic workflows.** Create and run verifiable agentic logbooks for agent communication, code drafting, tool and API calls. **Healthcare & education.** Secure data licensing and per-query research access for regulated data. **Gaming and entertainment.** Program in convenient age gates with deterministic verification and full proof trails. The comparison ## One turnkey agentic commerce solution. Specialized for API-based commerce and compatible legacy and blockchain rails. Feature Qatom Legacy rails (Stripe, Shopify) Blockchain / x402 Solution type Turnkey, all-in-one storefront Single-purpose gateway Complex crypto protocols Transaction fees $0 transaction fees 2% to 4% plus fixed fees High gas and network fees Sovereignty 100% sovereign data and assets Intermediaries hold control Speculative token volatility Asset support Multi-asset and custom issuance Limited fiat currencies Token-restricted Proof ### Live customers are already running on Qatom. Backed by strategic infrastructure partners, including AWS 100,000+ payments executed in production 0% platform transaction fees <1s in-flight settlement 100% sovereign data and assets ## Don't get left behind in the agentic commerce shift. Join live customers running thousands of daily transactions, backed by strategic infrastructure partnerships including AWS. [Create your storefront](https://www.qatom.ai/#get-started) Talk to our team Community ## Build in the open with us. Join the builders shipping agentic commerce. Get the playbooks, the events, and the release notes first. [**Slack**Ask questions and ship faster with the community.](https://qatom.slack.com/) [**Events**Bring your API to a Builder Hour, we'll list it live.](https://www.qatom.ai/events) [Subscribe on Substack](https://todaq.substack.com/) [Follow on LinkedIn](https://www.linkedin.com/company/qatom) --- # Overview | Qatom Source: https://www.qatom.ai/overview Overview # The in-flight commerce layer for the agentic economy. Modern AI stacks reason at the top and settle at the bottom, with nothing purpose built in between. Qatom fills that missing middle: discovery, payment, verification, settlement, and audit, woven into standard HTTP calls so software can buy, sell, and prove capabilities autonomously. The missing middle ## Reasoning at the top. Money at the bottom. A gap in between. On the top layer, models reason and orchestrate in milliseconds through protocols like Anthropic's Model Context Protocol. On the bottom layer, settlement still relies on 1970s card rails with 2.9% + $0.30 fees, or public blockchains burdened by gas volatility and privacy leaks. Qatom weaves transparently between existing AI runtimes, such as Claude Code, Cursor, and custom LLMs, and your backend API microservices. The result is that software can transact and verify inside the same request, at web speed, whether the money ends in a stablecoin or a conventional bank account. The core technology, explained simply ## Four ideas that make it work. 1 ### Digital cash notes Payments travel directly inside standard HTTP request headers as small bearer files. Like cash handed across a counter, value is delivered inline with the API request in under a second, with no card swipe fees, gateway delays, or blockchain gas. 2 ### The library loan card model Instead of copying every transaction to a massive public ledger, each asset behaves like a library book with its own loan card inside. Proof of ownership and history travel within the asset file itself, so verification happens locally and offline, without touching a central server. 3 ### Bounded autonomy and spend caps Agents run inside guardrails. Hard budget stop lines reject further calls the instant an allowance reaches zero, and an agent cannot secretly hand its authority down to unmonitored sub agents. No runaway loops, no rogue spend. 4 ### When the transaction is the logbook Settlement and audit stop being separate silos. Every call generates a self contained decision record where the prompt, the reasoning trace, and the payment receipt are cryptographically tied together, so past records cannot be altered or faked. Compliance is built in, not bolted on. What is live today ## Already running in production. - Catalog discovery and pay per call settlement, in production. - Owner side self serve verification, plus fully offline file verification. - End to end multi party settlement validated in real prototypes. - Over 100,000 payments executed, 0% platform fees, sub second settlement. [Create your storefront](https://www.qatom.ai/#get-started) [Read the docs](https://docs.qatom.ai/) ## Want the story behind the tech? Read how nearly a decade of protocol research prepared Qatom for the agentic economy. [About Qatom](https://www.qatom.ai/about-us) [Read our articles](https://www.qatom.ai/articles) --- # About Us | Qatom Source: https://www.qatom.ai/about-us About us # Built for people and their agents. At Qatom, we believe technology should make people stronger. We provide the turnkey agentic commerce and verification layer that lets software services, AI agents, and human customers discover, call, pay for, and monetize digital capabilities right inside a conversation. [Create your storefront](https://www.qatom.ai/#get-started) [Read the technical Overview](https://www.qatom.ai/overview) Why we exist ## The architecture for human sovereignty. For decades, the web has steadily concentrated power inside centralized platform databases. People do not own their digital belongings, routine API transactions carry mandatory payment processor fees, and every digital interaction needs third party permission. As AI agents evolve from passive chatbots into autonomous economic operators running complex multi step workflows, this lack of digital sovereignty has become a real production bottleneck. Qatom was created to solve this. We give API providers, AI companies, and enterprises a single, all in one way to be discovered, ordered from, and paid, by humans and agents alike, with full customer sovereign control. The power of two ## Proven protocols, meeting one click scale. Qatom has been in production since 2023, on infrastructure built on two protocols for verifiable digital assets: the TODA File Protocol and the ADOT Protocol. ### The protocols Two protocols, one foundation. The TODA File Protocol is the file layer: it gives every file, including every payment, portable integrity, because the file carries its own cryptographic proof of ownership and history. Anyone can verify it locally, even offline, with no blockchain and no shared ledger. The ADOT Protocol is the application layer: it defines how the objects inside TODA files are created, updated and read, so each file carries its meaning, such as a payment or a receipt. See how the two protocols fit together at todaq.net (https://www.todaq.net/#protocols). ### Qatom The market ready commercial layer that turns those protocols into software you can install in minutes. Qatom lets developers, API providers, stablecoin issuers, and enterprises turn any software endpoint into an autonomous, payable storefront, with 1 click developer install, 0% platform take rate, and an enterprise console. Proven in production ## The standard for fair, sovereign, auditable digital trade. Qatom is supported by strategic cloud partners, including AWS, with over 100,000 production payments executed, 0% taken in transaction percentage fees, and sub second execution. - Integrity, built into every asset. - 0% platform transaction take rates. - 100% sovereign data and asset control. [See how it works](https://www.qatom.ai/overview) [Talk to us](mailto:hello@qatom.ai) ## Ready to put your API to work? List your first tool free and watch agents discover, order, and pay in minutes. [Create your storefront](https://www.qatom.ai/#get-started) [Get the Max offer](https://www.qatom.ai/#get-started) --- # Watch the Qatom demo | Qatom Source: https://www.qatom.ai/demo The demo # One turnkey storefront. Every AI market. Ninety seconds, end to end. A seller's AI lists a service on Qatom, the seller approves it, and a buyer's agent pays 10 cents for it, settled in under a second, inside the assistants people already use. Every screen is a real recording, nothing staged after the fact. Loading the demo **1:34** runtime **1080p** Captions on screen, no audio [Open the video in a new tab →](https://www.qatom.ai/assets/video/qatom-demo-2026-10-26-b1-v3.mp4) What you are watching ## Three steps, no edits. 01 ### A catalog goes live An API endpoint becomes a catalog item with a price, a description and a machine readable contract. That is the whole setup. 02 ### An agent finds it Discovery happens inside the assistant, not on a search page. The agent reads the catalog and places an order on the buyer's behalf. 03 ### Payment settles In under a second, at 0% platform fees, with a verifiable record of the call. The service is delivered back into the same conversation. [Create your storefront](https://www.qatom.ai/#get-started) [Read the docs](https://docs.qatom.ai/) [Schedule an enterprise demo](https://www.qatom.ai/enterprise-demo) --- # Events | Qatom Source: https://www.qatom.ai/events Events # Where we're building in the open. Workshops, Builder Hours, and meetups where the Qatom team and community ship agentic commerce together. Here is what is coming up, plus where we have been. Highlighted event [Image: Luma event poster: Qatom workshop by Matthew Mihok at MCP Dev Summit Toronto 2026] MCP Dev Summit Toronto 2026 ## Build a Payment Capable MCP Catalog, Publishing Agent, and Shopper Skill in 60 Minutes **When:** October 5 to 6, 2026 **Where:** Toronto, Canada **Presented by:** Agentic AI Foundation Matthew Mihok Technical Lead, Qatom A hands-on workshop where you build a working, payment capable multi agent MCP workflow. You will create a service catalog, establish agent identity, publish tools, run paid transactions, transfer custody between agents, and review the audit logs, all in 60 minutes. [Register for the summit](https://events.linuxfoundation.org/mcp-dev-summit-toronto/) [Workshop details](https://events.linuxfoundation.org/mcp-dev-summit-toronto/program/schedule/?id=1287449) Upcoming ## What's next. [Image: Luma event poster: Qatom workshop by Matthew Mihok at MCP Dev Summit Toronto 2026] Oct 5 to 6, 2026 · Toronto ### Workshop: Build a Payment Capable MCP Catalog, Publishing Agent, and Shopper Skill in 60 Minutes **Presented by:** Matthew Mihok, Technical Lead, Qatom **At:** MCP Dev Summit Toronto 2026 Build a working, payment capable multi agent MCP workflow in one hour: a service catalog, agent identity, published tools, paid transactions, custody transfer, and audit logs. Bring a laptop with an MCP client and an empty GitHub repository. [RSVP on Luma](https://luma.com/tdeyxs5p) [Register for the summit](https://events.linuxfoundation.org/mcp-dev-summit-toronto/) Tue Oct 6, 2026 · Toronto ### Qatom Demo & Tutorial : Warm-Up for Hack The Andes **Format:** 90 minutes, live on Zoom **Tailored for:** Participants of Hack the Andes by Crafter Station **Live Q&A with:** Hassan Khan, CEO, Qatom **Cost:** Free This session is tailored to participants of Hack the Andes, the Crafter Station hackathon in Lima, so you arrive with a working build path on day one. Ninety minutes, built live. We stand up a catalog, place a selling agent in front of it, and take a real paid call end to end, followed by a live question and answer session with Qatom CEO Hassan Khan. Register even if the time does not work for you and we will send you the recording. Sat Oct 17, 2026 · Toronto ### The Foundry Vol. 1: Water Hackathon **Where:** Toronto Metropolitan University, 341 Yonge St, 3rd floor, Toronto **In aid of:** WaterAid Canada **Co-produced by:** The AI Fellowship (Toronto Chapter) and SOON **From Qatom:** Hassan Khan, Founder and CEO; Susana Khan, CMO A hackathon for good. More than 60 people spend the day on 11 real-world challenges identified with WaterAid Canada, building software the world can actually use. Qatom's leadership is spending the day with fellow builders on a cause worth the weekend, with AI tools and workflows at the centre of every solution. Hassan and Susana will each join different hackathon teams and bring their own angle. Hassan Khan, Founder and CEO, brings the builder's view: helping teams turn AI and data into working tools, and spotting where agents can find, pay for and share the data and services a solution needs. Susana Khan, CMO, brings the go-to-market view: she leads how Qatom reaches the people it's built for, and helps teams shape their solutions so the people they serve, the donors who fund them and the partners who deliver them can understand, trust and adopt them. Her background in international development, law and health keeps those ideas grounded in how water programmes actually run. [Request to join on Luma](https://luma.com/9o6jes1o) Event contacts: press@qatom.ai (press and media), hello@qatom.ai (partnerships and general enquiries) [RSVP on Luma](https://luma.com/830d5l83) [Read the docs first](https://docs.qatom.ai/) [Image: Hack the Andes, Lima, 17 to 18 October 2026] Oct 17 to 18, 2026 · Hack the Andes ### Hack the Andes: build agentic storefronts on Qatom **Host:** Crafter Station **Prizes:** 12 months of Max for first place, 7 months for second and third Qatom is the agentic commerce rail for this year's Hack the Andes. Every participant gets six months of Max free, and every member of a winning team also receives a giftable 12 month Pro voucher. More details are landing over the next week. [Qatom at Hack the Andes](https://www.qatom.ai/hack-the-andes) [Hackathon site](https://hacktheandes.com/) See the full, always current calendar on [Luma](https://luma.com/TODAQ). Past events ## Where we have been. Recaps of past Builder Hours and meetups will be listed here, each with its date and a short description. Browse everything on our [Luma calendar](https://luma.com/TODAQ), and find notes and photos on the [builder community](https://www.qatom.ai/builders) page. ## Never miss an event. Follow the calendar and get the release notes, playbooks, and event invites first. [Follow on Luma](https://luma.com/TODAQ) [Subscribe on Substack](https://todaq.substack.com/) --- # Announcements | Qatom Source: https://www.qatom.ai/announcements Announcements # The latest from Qatom. Product news, events, and updates from the team. For our full, always current event calendar, see [Events](https://www.qatom.ai/events). ## Never miss an update. Follow along and get product news, playbooks, and event invites first. [Follow on LinkedIn](https://www.linkedin.com/company/qatom) [Subscribe on Substack](https://todaq.substack.com/) --- # Builder Community | Qatom Source: https://www.qatom.ai/builders Community # Build in the open, with us. This is home for the Qatom builder community: the developers, partners, and teams shipping agentic commerce. Notes, photos, and recaps from our builder events will be published here as we host them. [Join the Slack](https://qatom.slack.com/) [See our events](https://www.qatom.ai/events) Coming soon ## What you will find here. ### Event notes and recaps Highlights, slides, and takeaways from our Builder Hours, workshops, and meetups, published after each event. ### Photos and moments Images from the community: hackathons, demos, and the people building on Qatom in the wild. ### Builders and partners The teams, contributors, and technology partners shaping the agentic economy alongside us. Want to be featured, host a session, or partner with us? Write to [hello@qatom.ai](mailto:hello@qatom.ai). ## Come build with the community. Join the builders shipping agentic commerce. Get the playbooks, the events, and the release notes first. [Join the Slack](https://qatom.slack.com/) [Follow on LinkedIn](https://www.linkedin.com/company/qatom) --- # Qatom at Hack the Andes | Lima, 17 to 18 October 2026 Source: https://www.qatom.ai/hack-the-andes [Claim 6 months free](https://www.qatom.ai/#get-started) **[Hack the Andes](https://hacktheandes.com/)**_/_Lima, Perú_/_17–18 Oct 2026 # Let your agents _buy and sell_. Qatom is the agentic commerce rail for Hack the Andes. Turn any API, dataset or model into something an AI agent can find, order from and pay for. No transaction fees, settlement in under a second, and you keep everything you build. [Claim 6 months of Max, free](https://www.qatom.ai/#get-started) [Read the docs](https://docs.qatom.ai/) [Image: Crafter Station] [Image: Perú Tech Week 2026] [Image: Chofex] [[Image: Hack the Andes, 17 to 18 October 2026, Lima, Perú]](https://hacktheandes.com/) ## Buy, sell, leverage data via APIs. Build the best system. Run on Max for a year. 01 First place 12 months Qatom Max 02 Second place 7 months Qatom Max 03 Third place 7 months Qatom Max Every member of a winning team also receives a giftable 12 month Qatom Pro voucher. ## Cards were built for carts. Qatom is built for calls. A $0.001 API call cannot carry a 30 cent fee. That is arithmetic, not preference, and it is why nobody has built the checkout layer for what agents actually buy all day: API calls, data and inference. That is the part you get to build on this weekend. 01 ### Build your catalog Point Qatom at one endpoint or a thousand. Each becomes a catalog item with a price, a description and a machine readable contract. 02 ### Place a selling agent Drop it on your site, in WhatsApp or iMessage, or inside Claude, ChatGPT, Copilot, Gemini, Muse, Grok and Hermes. That is where the buyers already are. 03 ### Get paid per call Humans and agents discover, order and pay. Settlement in under a second, 0% platform fees, and a verifiable record of every single call. ## Come to the live build session. Fri 9 Oct 2026 · 6:30 PM Toronto / 5:30 PM Lima · Zoom ### Qatom Demo & Tutorial : Warm-Up for Hack The Andes Ninety minutes, built live. We stand up a catalog, place a selling agent in front of it and take a real paid call, end to end, then stay for questions. If you are coming to Lima to build on Qatom, this is the session that saves you the first six hours. [Register on Luma](https://luma.com/830d5l83) - **Length**90 minutes - **Live Q&A**With Hassan Khan, CEO of Qatom - **Where**Online, on Zoom - **Cost**Free - **Recording**Register and we send it to you, even if you cannot attend ## Three things to do before Lima. 1 ### Claim six months of Max, free Unlimited agents and transactions, and up to 1,000 catalog items. No card needed to start. [Sign up](https://www.qatom.ai/#get-started) 2 ### Read the docs Quickstart, the catalog model, agent identity, the payment header and the audit trail. Skim it before the session and it will click faster. [Open docs](https://docs.qatom.ai/) 3 ### Join the session on 9 October Ninety minutes with a live Q&A. Register even if the time does not work, and we will send you the recording. [Register](https://luma.com/830d5l83) Questions during the hackathon? hello@qatom.ai, or find us in the Hack the Andes Discord. --- # Schedule an Enterprise Demo | Qatom Source: https://www.qatom.ai/enterprise-demo [← Back to qatom.ai](https://www.qatom.ai/) Enterprise # Schedule an enterprise demo. Tell us about your deployment and a member of our team will walk you through Qatom for regulated, high-throughput agentic commerce. - Private cloud or on-prem options - Custom asset issuance and forward-deployed engineering - Audit-ready settlement with full Binder history - Dedicated support and SLA We take your privacy seriously. Your details go only to the Qatom team, and we will not share them with third parties. --- # Max Launch Offer Terms | Qatom Source: https://www.qatom.ai/teams-offer-terms [← Back to the offer](https://www.qatom.ai/#get-started) Max Launch Offer # Qatom Max Launch Offer Agreement Version 1.1 · 19 September 2026 · TODAQ Micro Inc., doing business as Qatom · [Download PDF](https://www.qatom.ai/legal/founding-teams-offer-v1.1.pdf) See also our [Privacy Policy](https://www.qatom.ai/legal/privacy) and [Terms of Service](https://www.qatom.ai/legal/terms). The offer at a glance Months 1–6 Free. No card needed to start. Months 7–12 US$300 per month (US$1,800 in total). Change your mind? Any time in your first six months, cancel and pay nothing, or move to the Pro plan at US$20 per month with no annual commitment. We remind you 30 days and 7 days before the free period ends. After month 12 Renews for another 12 months, billed monthly, unless you cancel at least 30 days before. We email you 45 days ahead with the price. You can choose to pay the year up front instead, with one month off. What you get Unlimited agents and transactions, up to 1,000 catalog items, Twin URLs and API keys, priority onboarding, and no Qatom transaction fees. This summary is for convenience. The terms below are the agreement. ### 1\. Who this agreement is between This Qatom Max Launch Offer Agreement (the “Agreement”) is between TODAQ Micro Inc., a Delaware corporation doing business as Qatom (“Qatom,” “we” or “us”), and the company named in the sign-up form (“Customer” or “you”). The Agreement starts on the date you accept it online (the “Start Date”). In this Agreement a “month” means one calendar month, counted from the Start Date. For example, if you accept on 10 October, month 1 runs from 10 October to 9 November. ### 2\. The Max plan During the Term you get the Qatom Max plan, which includes: - unlimited agents; - unlimited transactions; - up to 1,000 catalog items; - Twin URLs and API keys; - priority onboarding from our team; and - no Qatom transaction fees. The Max plan, together with the related software, documentation and updates, is the “Service.” We keep improving Qatom and may change features, but we will not materially reduce the features listed above during a Term that has already started. Fees charged by third parties you choose to use, such as your bank or card provider, are between you and them. ### 3\. Your first six months are free Your first Term is twelve (12) months from the Start Date. Months 1 through 6 are the “Free Period.” The subscription fee for the Free Period is US$0, and you do not need a payment method to start. ### 4\. Cancelling or moving to Pro during the Free Period At any time during the Free Period you may either cancel or move to the Qatom Pro plan, as described below. You may cancel at any time up to 11:59 p.m. Eastern Time on the last day of month 6. To cancel, email hello@qatom.ai from your account email address, or use any cancellation option we provide in your Qatom dashboard. If you cancel during the Free Period you owe nothing: no subscription fee and no cancellation fee. Your access ends on the date you choose in your notice, or at the end of the Free Period if you do not choose a date. Instead of cancelling, you may move to the Qatom Pro plan by the same deadline and by the same methods. Your Max plan continues free until the end of the Free Period, or until an earlier date you choose, and Pro starts the day after. Pro is billed monthly in advance at US$20 per month, has no annual commitment, and you may cancel it at any time, effective at the end of the month you are in. We may change the Pro price with at least 30 days’ notice. Pro plan limits apply from the day Pro starts. They are currently 3 agents, up to 50 catalog items and up to 250 transactions per month. If your account is over those limits we will tell you before the switch so you can choose what to keep. After a move to Pro, this Agreement continues to govern your Pro subscription, except Sections 3, 5 and 6 and the Max features listed in Section 2. From then on, “Service” means the Pro plan. We will email you a reminder at least 30 days, and again at least 7 days, before the Free Period ends. Each reminder will explain how to cancel and how to move to Pro. ### 5\. Months 7 to 12 and payment If you have not cancelled or moved to Pro by the end of the Free Period, this Agreement continues through month 12 and you agree to pay US$300 per month for months 7 through 12 (US$1,800 in total). Before the Free Period ends we will ask you to add a payment method in your dashboard. Fees are billed monthly in advance, in US dollars, starting on the first day of month 7. Fees do not include applicable taxes, which we will show separately. Fees for months 7 through 12 cannot be cancelled and are not refundable, except as Section 11 provides. If a payment fails we will tell you and give you at least 10 days to fix it before we suspend access. The unpaid amount remains owed. ### 6\. Renewal At the end of month 12 this Agreement renews automatically for another twelve-month Term at our then-current Max monthly price, billed monthly, unless either of us gives notice of non-renewal at least 30 days before the renewal date. You may instead choose to pay for a renewal Term in advance in a single payment, in which case we discount it by one month’s fee. Renewal Terms do not include a Free Period. We will email you at least 45 days before each renewal date with the renewal price. If that price is higher than what you paid in the current Term, you may cancel the renewal by notice at any time before the renewal date, even inside the 30-day window. ### 7\. Your data You own your data, content, catalog items, products and services (“Customer Data”). You permit us to host, process and transmit Customer Data only as needed to provide and support the Service, and in line with our Privacy Policy at qatom.ai/legal/privacy. For 30 days after this Agreement ends you may export your Customer Data using the tools in the Service or by asking us. ### 8\. License and acceptable use We grant you a non-exclusive, non-transferable right during the Term to use the Service for your business. We and our licensors keep all rights in Qatom, the Service and the related software, documentation and technology. You will use the Service lawfully and in line with our documentation. You will not: resell or sublicense the Service itself, except as the Service is designed to allow, such as selling your own products and services through it; reverse engineer it, except where the law permits; or use it to break the law, infringe anyone’s rights, or disrupt the Service or other users. You are responsible for activity under your account and your API keys. ### 9\. Warranty We will provide the Service substantially as described in our documentation, with reasonable care and skill. Features we label beta or preview are provided as is. Except as stated in this Agreement, the Service is provided “as is,” and to the extent the law allows we disclaim implied warranties, including merchantability, fitness for a particular purpose and non-infringement. ### 10\. Liability Neither party is liable to the other for indirect, consequential, special, incidental or punitive damages, or for lost profits or revenue, even if told they were possible. Each party’s total liability arising out of this Agreement is limited to the greater of (a) the fees paid or payable by you under this Agreement in the twelve months before the event giving rise to the claim, and (b) US$1,000. These limits do not apply to your obligation to pay fees, to either party’s liability for fraud or willful misconduct, or to liability that cannot be limited by law. ### 11\. Suspension and termination Either party may end this Agreement by written notice if the other materially breaches it and does not fix the breach within 30 days of receiving notice. We may suspend access immediately if needed to prevent a security risk, serious harm to the Service or its users, or illegal use. We will tell you why and restore access once the issue is resolved. If you end this Agreement because of our uncured breach, we will refund any fees you prepaid for the unused part of the Term. Sections 7, 8 (as to our ownership), 10, 11 and 14 survive the end of this Agreement. ### 12\. Offer eligibility The Max Launch Offer is for new Qatom Max customers signing up for business purposes, one per organization. It is available to a limited number of founding customers, and we may close it to new sign-ups at any time. Closing the offer does not affect an Agreement you have already accepted. You may move to an Enterprise plan at any time on terms we agree separately. ### 13\. Accepting electronically By checking the agreement box and submitting the sign-up form, you accept this Agreement and confirm that you are authorized to bind the Customer. Your electronic acceptance has the same effect as a handwritten signature. We will email a copy of this Agreement to the address you provide and keep a record of your acceptance, including the date, the time and the version of this Agreement you accepted. ### 14\. General Delaware law governs this Agreement, without regard to its conflict-of-law rules. This Agreement is the entire agreement about the Max Launch Offer and replaces prior discussions about it. If you also accept the Qatom Terms of Service, this Agreement controls on anything it covers. Changes must be in writing and agreed by both parties; we cannot change this Agreement during a Term by posting new terms. Notices are given by email: to us at hello@qatom.ai, and to you at the work email in your sign-up or your account. Neither party may assign this Agreement without the other’s consent, except that either party may assign it on notice to an affiliate or to a successor in a merger, reorganization, change of corporate name or sale of substantially all of the relevant business. If any part of this Agreement is unenforceable, the rest stays in effect. Neither party is liable for delays caused by events beyond its reasonable control. --- # Articles & Blog | Qatom Source: https://www.qatom.ai/articles Articles & blog # Writing on the agentic economy. Research and analysis from the Qatom team on agentic commerce, verification, and the infrastructure of the machine economy. Every piece is published in full here, and also on our Substack. [Subscribe on Substack](https://todaq.substack.com/) [August 7, 2026 · Susana Khan ### The Agentic Economy's Missing Middle Two architectures are competing to build the missing middle above the agentic transport layer. Here is the evidence, the trade-offs, and why we are building for the self-verifying file. Read the article →](https://www.qatom.ai/articles/the-agentic-economys-missing-middle) [May 31, 2026 · Susana Khan ### The Invisible Shelf: How Headless Catalogs Are Rewiring AI Infrastructure The machines are already transacting. The infrastructure being built today will determine what happens when something goes wrong at scale. Read the article →](https://www.qatom.ai/articles/the-invisible-shelf-how-headless-catalogs-are-rewiring-ai-infrastructure) --- # The Agentic Economy's Missing Middle | Qatom Source: https://www.qatom.ai/articles/the-agentic-economys-missing-middle Article # The Agentic Economy's Missing Middle Two architectures are competing to build the missing middle above the agentic transport layer. Here is the evidence, the trade-offs, and why we are building for the self-verifying file. Susana Khan · August 7, 2026 · [Originally on Substack](https://todaq.substack.com/p/the-agentic-economys-missing-middle) **Disclosure:** This paper has been prepared by TODAQ's leadership team. It draws on recent academic research, industry developments, and our own engineering experience. Where our analysis reflects our architectural perspective, we identify it as such. Where important questions remain unresolved, including those relevant to our own approach, we address them directly. ### Executive Summary The agentic economy is already live. AI agents are shifting from advisors to autonomous economic actors, driving stablecoin volumes above $1 trillion per month and prompting the entire payments and cloud establishment to standardize transport rails such as x402. Transport alone, however, is insufficient. Three recent academic papers map a clear "missing middle" above that layer, verification of truth, interoperable machine-speed payments, and programmable compliance, while documenting fragile identity and authorization infrastructure and new systemic risks from correlated agent behavior. Two architectures are competing to close the gap. Kite optimizes a purpose-built Layer-1 blockchain for agents. Qatom, built on TODAQ's ledgerless TODA protocol, takes a different path: digital assets exist as self-verifying files, and Twin Proxies collapse pricing, payment, multi-party splits, settlement and cryptographic proof into a single HTTP request. Payment, verification, settlement and auditability are properties of the same cryptographic object. The result is sub-100 ms, sub-cent transactions that can begin and end in fiat rails, remain offline-verifiable, and are structurally immune to several blockchain failure modes. Qatom's distinctive claim is not merely technical efficiency. By turning every API into a pay-per-call endpoint with payment-at-source, it enables micro-joint-ventures between businesses and lets domain experts monetize verified human expertise directly to agents. The agent becomes the tireless procurement officer; the human expert becomes the producer of scarce, decision-relevant truth. This creates net-new B2B markets and extends enterprise-grade reach and trust infrastructure to SMBs. Neither architecture is complete. Verification does not equal truth, discovery standards remain fragmented, and coordinated macro-prudential observability is harder in a ledgerless design. The central infrastructure question of the next decade is whether the economic railway for agents will be a purpose-built blockchain or a self-verifying file. This paper examines the evidence, the trade-offs, and why TODAQ is building for the latter. ### 1\. The shift to machines doing the buying We're in what people are calling the "Agentic Turn." AI agents are moving from giving advice to making deals, acting as independent economic players. Unlike the rigid, rule-based automation of the last decade, these agents can adapt and operate across systems in unpredictable ways. Here's the problem: as BGIN (a blockchain governance group) has pointed out, global stablecoin regulations are still being designed for humans. The dominant users in the very near future will not be human at all. The scale is already staggering. TRM Labs reports stablecoin transaction volumes now exceed $1 trillion per month. Protocols such as x402 let AI agents pay merchants directly in USDC; Stripe's AI toolkit supports it, and Visa is on board. On 14 July 2026 the Linux Foundation launched the x402 Foundation with 40 members, including Visa, Mastercard, American Express, Stripe, Google, AWS and Coinbase. The payments, cloud and commerce establishment is converging on an HTTP-native standard that can carry both card payments and stablecoins. x402 solves transport and payment intent well for stablecoin-native flows. What it does not fully solve is the rest of the stack required for broad, high-frequency commerce: true sub-cent economics without gas or deferred batching, seamless start-and-end in fiat rails, atomic multi-party splits, and portable, offline-verifiable proof of what was paid for and why. Stablecoins are a powerful settlement asset, but they are not a complete substitute for the fiat world most businesses still inhabit. TODAQ goes further. It has built infrastructure in which payment, verification, settlement and auditability are properties of the same cryptographic object, and in which that object can move value in real time whether the final destination is a stablecoin or a conventional bank account. The deeper task is an economic railway that can move verified answers at machine speed: the agent handles discovery and settlement, while human expertise supplies the scarce, decision-relevant truth. Three recent academic papers, taken together, map exactly what is missing above the transport layer. Two very different architectural responses are competing to fill the gap, and we have a horse in that race. ### 2\. The verification crisis: why agents can't "trust" what they read The real bottleneck for autonomous commerce is data veracity, knowing the "what" behind a transaction. Ventirozos and Shardlow from Manchester Metropolitan University make a compelling argument in "Paying to Know" (June 2026). They say that agent-native micropayments fundamentally change what's scarce in e-commerce. For years, we treated shopping chatbots as recommendation engines, match a user to a product and close the sale. But when the buyer is an autonomous agent that can search exhaustively, matching becomes trivial. The scarce resource becomes _trustworthy_, decision-relevant information about products. The numbers are stark: American retailers absorbed an estimated $890 billion in returns in 2024, driven by the gap between product descriptions and reality. A _JAMA Network Open_ study found only 11% of sports supplements had ingredient quantities within 10% of their label claims. AI agents currently ingest marketing prose designed to manipulate ranking algorithms, not to survive scrutiny from a machine. When LLMs answer critical questions based on this unverified data, hallucination rates spike between 64% and 68%. The paper envisions a micro-transaction information market where buyer agents spend fractions of a cent to progressively unlock seller- and reviewer-supplied data, audited service histories, third-party test reports, bills of materials, paid _à la carte_. A used car purchase might involve a progressively costlier trail of evidence; a cheap auxiliary belt might cap investigation at a few cents for fitment verification. For an agent to transact autonomously here, it needs a "Verification Layer" with four primitives: a Claim (testable, machine-readable fact), a Confidence Score (probabilistic accuracy measure), a Category (classification, physical measurement vs. consumer observation), and a Shelf Life (products change, data should too). To prevent fraudulent reviews, the market uses staking mechanisms, reviewers put up collateral and get penalized for bad data. The authors also lay out five NLP research frontiers that need solving before this market works: cost-aware tool use, multi-agent negotiation, entity resolution to standard product ontologies, grounded generation constrained to real inventory, and privacy-preserving personas that stay with the user. This _à la carte_ sub-cent micro-transaction information market, and the five NLP research frontiers are addressed within TODAQ's infrastructure. ### 3\. The Web4 bottleneck: infrastructure that assumes humans are always in the loop The transition to a "Web4" agent economy is stalled by infrastructure that assumes a human is always watching. A large-scale study from Zhejiang University (June 2026) provides the first hard data on both the scale and fragility of this emerging economy. The economy is real and it's huge. Analyzing 99,448 multi-chain identity registrations under EIP-8004, the study found agents heavily deployed not on Ethereum mainnet (14.6%) but on Layer-2 and other chains: BNB Smart Chain (40%, 39,700 agents) and Base (19.9%, ~19,800). Looking at 317.5 million transaction logs, they confirmed an active, high-frequency M2M economy processing millions of daily transactions. Average transaction value consistently below $1 ($0.46 USDC); "pay-per-call" models are replacing subscriptions. Static analysis of 341 open-source MCP servers shows agent intent is highly specialized: DeFi dominates (stablecoin routing, Uniswap integration), while broader categories like social, gaming, and DAOs are scarce. But the infrastructure is breaking. Mining 349 developer-reported GitHub issues, the study flags three compounding failures: - _**Identity crisis and OAuth blindness.**_ Traditional OAuth is "economically blind." It assumes a static, human-supervised session where permissions are checked once. In the agent world, this creates a "Compositional Explosion", agents authorize sub-agents, creating unauditable permission chains. Systems can't distinguish legitimate delegation from a hijacked agent. They found 230 issues related to identity/authorization friction. - _**Cross-environment operation.**_ Development assumptions on test networks don't transfer cleanly to production. RPC timeouts under concurrent calls, transactions that succeed on testnet but revert on mainnet, inconsistent gas estimation, 96 issues, only 50% closure rate. - _**The economic impossibility of payments.**_ Traditional payment rails (cards/ACH) are built for human cadences. With fixed costs of $0.30 and 2.9% fees, a sub-cent micropayment for an API call is absurd, the fee can exceed the value by 3,000%. Payment interoperability had only a 25.29% issue closure rate. The authors conclude with a diagnosis that frames the rest of this analysis: there's a "standardization deficit." Community responses exist, but they're repository-specific fixes, not ecosystem-wide conventions. The Web4 economy is growing faster than its infrastructure can stabilize. ### 4\. Compounding risks: systemic fragility at machine speed These infrastructure gaps don't exist in isolation. They interact with risks that emerge only when thousands of autonomous agents operate on the same rails simultaneously. _**Correlated agent behavior.**_ Because many agents share similar base models, and often identical training data, they risk reacting identically to the same market signals. Researchers have constructed LLM-powered agent-based markets to investigate stablecoin fragility. While the peg holds under moderate stress, crossing a narrative severity threshold triggers what one study calls "cognitive de-pegging", expected maximum price deviation surges by ~1,441 basis points as diverse investor beliefs converge into synchronized selling. Bank of England Deputy Governor Sarah Breeden warned in June 2026 that autonomous AI agents could "amplify volatility in stress" and trigger a "market meltdown." The Bank is exploring circuit breakers and "kill switches" to halt trading if faulty AI models cause correlated failures. _**Hyper-sandwiching.**_ Traditional MEV (Maximal Extractable Value) bots are rule-based and single-market. "Hyper-sandwiching" is a scaled-up evolution, agents that can reason across multiple protocols simultaneously, use flash loans, and identify non-obvious arbitrage paths in real-time, compiling incredibly complex transactions within a single block. A single block may not even be fast enough to react. _**Human rental.**_ A novel failure mode where agents incentivize or "rent" humans to bypass KYC/AML requirements, regulatory arbitrage at machine speed through human proxies. _**Non-determinism.**_ The same agent, given the same input, produces different financial outputs, breaking standard compliance assumptions built around deterministic systems. Policy experts now propose that stablecoin stress testing must proactively incorporate AI agent scenarios: modeling networks where 100,000 users each sponsor 10–20 agents, each performing 10–20 times the transaction volume of a human. Instead of waiting for mandates, issuers should proactively demonstrate resilience to these synchronized machine-speed events. ### 5\. The compliance rail: programmable guardrails Agents transacting at machine speed require compliance that operates at machine speed. See and Tan of the Monetary Authority of Singapore and IMDA (April 2026) demonstrate an architecture that integrates programmable compliance directly into stablecoin payment rails. _**The regulatory conflict is structural.**_ Stablecoins on smart contract blockchains offer near-instant, programmable settlement, perfect for machine-speed transactions. But they must still comply with strict traditional requirements: sanctions screening, customer due diligence, record-keeping, and the FATF "travel rule." As the FATF explicitly states: "The regulatory obligations, including the Travel Rule, persist regardless of the technology rail used." Manual compliance would erase the real-time benefits entirely. The solution uses the Global Layer One (GL1) programmable compliance architecture. Transactions go through a PolicyWrapper and PolicyManager that evaluate transfers against sanctions and source-of-funds policies at the exact point of execution. Results return as on-chain attestations: **PASS** (settlement proceeds), **FAIL** (blocked), or **PENDING** (recorded on-chain, funds held in escrow until evidence provided). When a check returns **PENDING**, say, a payment exceeds a source-of-funds threshold, the transaction is split. A "safe" amount settles immediately; the rest locks in escrow. Once the buyer agent submits a signed source-of-funds attestation on-chain, the compliance agent releases the escrowed funds without manual intervention needed. _**Privacy pools and agent confidentiality.**_ A separate but related proposal addresses the confidentiality problem. An agent uses its identity (leveraging ERC-4337 account abstraction) purely as an entry credential to access a merchant-specific privacy pool. Inside the pool, the agent conducts its micropayments; the merchant withdraws settled funds from the other side. This shields transaction details while preserving a verifiable identity layer. ### 6\. Two architectures for the missing middle The three papers collectively define the infrastructure gap: verification of truth, interoperable payments, and compliant settlement at machine speed. Two fundamentally different architectures are competing to close it. TODAQ built one, so we'll be direct about where our analysis carries a point of view, and where the structural differences genuinely matter regardless of who's observing. #### 6.1 Kite: Blockchain-native agent infrastructure Kite is a purpose-built Layer-1 blockchain designed to treat agents as first-class economic actors. It implements the SPACE Framework: Stablecoin-native, Programmable, Agent-first, Compliance-ready, and Economically viable. - _**Identity**_. Three-layer hierarchical model: User Root (secure enclave), Agent Delegated addresses (derived via BIP-32, isolated for tasks), and Session Ephemeral keys (short-lived, task-scoped, so even total compromise stays contained). - _**Truth**_. Kite anchors an "immutable, tamper-evident log" of agent actions to its Layer-1 blockchain "Proof of Attributed Intelligence" (PoAI). Every action creates a cryptographic proof chain from user authorization through agent decision to outcome. On-chain smart contracts serve as the ultimate arbiter in disputes. - _**Economics**_. Programmable micropayment channels (state channels) deliver sub-hundred-millisecond latency, costs claimed at $1 per million requests. Two parties lock funds, exchange signed updates off-chain, settle final balance on-chain. Equivocation is deterred by staked reputation and bonds. - _**Privacy**_. Encrypted agent-to-agent channels and state channels where only opening/closing balances publish on-chain. Future plans include zero-knowledge proofs for credentials without revealing underlying data. #### 6.2 Qatom by TODAQ: Ledgerless settlement at the file layer Qatom takes a different path, abandoning the shared ledger entirely. The TODA protocol operates at the file layer: digital assets (money, credentials, records) transfer peer-to-peer like physical paper. No global consensus, no gas tokens, no shared ledger database. Qatom is the payments and verification solution built and hosts an MCP server built on the TODA protocol. - _**Identity**_. Authorization at the file level using "reqsats" (requirements and satisfactions) embedded directly in the file. Every update must carry a satisfaction fulfilling the previous twist's requirements, specific cryptographic signatures or weighted multi-signature lists. - _**Truth**_. "Integrity-at-a-distance." A TODA file is constructed from updates called "twists" that link into "lines." Untrusted lines ("leadlines") cryptographically anchor to highly trusted lines ("corklines") using a "hitch." This lets an object's state live on an untrusted device while inheriting the absolute integrity of a trusted server, without the server knowing the contents. Proof travels within the file, so transactions verify completely locally and offline. Equivocation is prevented mathematically through "supportive guilds" and "rigging." - _**Economics**_. Every wallet, API, and agent gets its own "Twin", a virtual HTTP container handling payments, payouts, verification, access, records, and banking in one round-trip. The Twin Proxy wraps data APIs behind a micropayment paywall. Agents pay via X-TODA-Pay HTTP extension header, cryptographic micro-vouchers attached directly to HTTP requests. Settlement occurs upon receipt, inline with the request. Sub-100ms settlement with no gas fees. - _**Privacy**_. "Shielding", the file owner uses a secret value to hash (shield) data before submitting for anchoring. The trusted system records the proof obliviously, guaranteeing integrity while preventing front-running or data substitution. #### 6.3 The TODAQ Capability Model Where Kite optimizes a _blockchain_ for agents, TODAQ optimizes the _file_, and in doing so, delivers a set of capabilities that map directly to the gaps the academic papers identified: _**Agentic-native discovery.**_ Qatom exposes a headless catalog, a machine-readable marketplace where agents discover paywalled APIs, priced per call, not per month. No storefront, no session, no human navigating a checkout flow. Agents browse, evaluate, and transact autonomously. In our hackathon, a Claude session independently discovered a tool through the marketplace, called it, and paid 0.01 USD TDN, automatically, with no human involved. _**Transportable verifiability and auditability.**_ Every transaction carries its complete cryptographic lineage in the file itself, the Transaction Binder. The proof travels _with_ the data. Regulators can verify compliance by checking the file's rigging tree without querying a live blockchain. This is "integrity-at-a-distance." _**Unforeseen economic efficiency.**_ The Twin Proxy evaluates, verifies, and atomically splits proceeds among up to 200 recipients inside a single HTTP request. A single API call can pay multiple providers simultaneously; no reconciliation cycles, no delayed settlements. The economics are those of ordinary web traffic, not an optimized blockchain transaction. _**Privacy and ownership with simultaneous transparency.**_ TODA's shielding records only structural proof on the trusted topline. Counterparties or regulators receive the full file and audit offline. Competitors see nothing. This is privacy by construction, not by policy. _**Human empowerment at the endpoints, and the rise of micro-joint-ventures.**_ The dominant narrative around agentic commerce frames it as humans being removed from the loop. Qatom inverts that entirely. By turning every API into a pay-per-call endpoint with payment and multi-party splits settled at source, the Qatom Marketplace enables domain experts, supply-chain auditors, lab technicians, financial modelers, compliance analysts, and niche B2B data providers to monetize their verified, human-acquired expertise directly to autonomous agents. More importantly, it changes the economics of collaboration itself. Two (or more) businesses can now form a **micro-joint-venture** with almost no friction: one firm exposes a specialized capability as a priced, machine-discoverable endpoint; another firm's agent calls it once for a test, pays automatically, receives the result with cryptographic proof, and then ramps volume continuously as value is proven. There is no months-long BD cycle, no custom contract, no minimum commitment, and no reconciliation. Each participant is paid at source on every call. What used to require enterprise-scale legal and treasury teams becomes available to SMBs and mid-market firms. The agent becomes the tireless procurement officer; the human expert (or the firm that owns the expertise) becomes the primary producer of scarce, decision-relevant truth. When the answer is a number, a shelf-life forecast, a verified bill of materials, a risk score, a spot price, a lab attestation, the agentic railway becomes a new medium for economic communication between businesses, executed at machine speed. Data and capabilities that were previously too costly to package, invoice, and reconcile now flow frictionlessly. The result is not merely cheaper versions of existing markets; it is the practical creation of net-new B2B products and markets that could not clear the old partnership and packaging threshold. This is the infrastructure and trust layer that lets smaller players expand their reach in ways that were previously reserved for large enterprises. #### What is live today. - MCP catalog discovery and pay-per-call settlement are in production. - Owner-side self-serve verification via TODAQ Console and trie.fun, plus fully offline TODA-file verification, are available. - The silent Buyer Twin on first card payment and the end-to-end four-Twin flow have been validated in the Agentic Healthcare prototype. - Wider re-tethering and supply-chain applications using the same primitive remain on the build path. #### 6.4 Stress test: the uncomfortable questions for TODAQ Let's be direct about where our model faces the toughest scrutiny, because if we don't name these, someone else will. _**Regulatory unfamiliarity is a real barrier.**_ A tamper-evident file is mathematically elegant; a blockchain query is operationally familiar. Regulators know how to audit a database or call a custodian API. Teaching a supervisor to trust a rigging tree is a heavy lift. Until the MAS, FCA or OCC formally opines that a self-contained Transaction Binder satisfies compliance obligations equivalently to an on-chain attestation, enterprise adoption faces a due-diligence barrier. _**Observability is deliberate, not absent.**_ The blockchain-native framing often equates "observability" with a single, permissionless, globally queryable ledger. TODA rejects that assumption. Because there is no shared global state, there is also no automatic global surveillance. Visibility is delineated: a Transaction Binder can be exported and shared with any defined party, a regulator, an audit firm, a supply-chain consortium, or a sector supervisor, while retaining full cryptographic verifiability. The recipient checks the file's complete lineage offline, without querying a live chain or trusting a node operator. Privacy is the default; visibility is conferred by consent. This does not eliminate the macro-prudential problem. A central bank or systemic-risk authority that wants a real-time aggregate view across thousands of independent ecosystems still faces a coordination challenge. The corkline records proof, not the underlying economic signal. Building standardized aggregation mechanisms, shared blinded anchors, or trusted analytics layers is a governance and standardization task, not a missing cryptographic primitive. Those pathways are practical and are being explored; they are not yet deployed at scale. The trade-off is real: we gain strong privacy and offline sovereignty, and we forgo the native, always-on global telescope that a public ledger provides. _**Coordination power.**_ The x402 coalition now sits under Linux Foundation governance with Amazon, Amex, Circle, Google, Mastercard, Stripe, Visa, the Solana Foundation and dozens more. Card networks and hyperscalers are hedging across multiple protocols while concentrating coordination power. They reduce the cost of building on top of those rails. We are betting that enterprise procurement will eventually prioritize cost-per-call, offline verification and true asset ownership over ecosystem conformity. That is a bet, not a certainty. Elegance and adoption follow different logics. _**Human oracle risk remains.**_ We empower humans and firms to sell verified data via their endpoints, but TODA cannot mathematically guarantee that the original measurement or judgment was accurate. A cryptographically signed service history is still only as honest as the party that entered the data. We rely on economic staking and reputation to penalize bad actors, yet those mechanisms remain unproven at the scale of agentic commerce and are vulnerable to Sybil attacks and collusion. We believe these trade-offs are worth it for high-frequency, low-value, privacy-sensitive workloads and for the micro-joint-venture and SMB-reach use cases described earlier. But the questions are real, and they are the ones we are actively testing through regulatory pilots and production deployments. ### 7\. Mapping solutions to gaps _**Verification crisis.**_ Both architectures support sub-cent micropayments for verified data. Kite anchors product claims to its blockchain. TODAQ wraps data APIs behind Twin Proxy paywalls; the headless catalog lets agents discover, pay for, and receive verified data in a single atomic request. Because verification travels with the file itself, high-frequency queries avoid repeated network round-trips to a shared ledger. The result is a structural throughput advantage for the lowest-value, highest-frequency data calls. _**Web4 infrastructure fragility.**_ The low closure rate on payment-interoperability issues reflects the difficulty of making existing rails work at agent speed and ticket size. Kite consolidates payments onto its L1. TODAQ consolidates the entire transaction stack, API paywall, atomic multi-party splits, sub-ledgers and audit binders, into the Twin container. Because settlement occurs peer-to-peer at the file layer with no shared ledger state, the architecture is structurally immune to the RPC timeouts and testnet–mainnet mismatches that continue to plague cross-environment agent operations. _**Programmable compliance.**_ Kite's on-chain audit trail (PoAI) provides compliance inside the smart-contract paradigm: policy wrappers, on-chain attestations, escrow contracts. TODAQ's Transaction Binder carries the complete cryptographic lineage inside the file itself, self-verifying and auditable offline. Regulators can check compliance by examining the file's rigging tree without querying a live blockchain. The Banking Gateway further connects bearer files to traditional rails (Stripe, Apple Pay, ACH), closing the fiat on- and off-ramp gap that pure stablecoin systems still face. ### 8\. Systemic risk dimension revisited Neither architecture fully solves the correlated-agent problem, and the ledgerless approach faces a distinct version of it. If 100,000 users each sponsor 10–20 agents, each generating many times the transaction volume of a human, both systems face throughput questions. The deeper risk is correlation: when large numbers of agents share similar base models and react identically to the same signal, synchronized behavior can move markets faster than circuit breakers can respond. Kite retains one potential advantage: state-channel openings and closings are on-chain events, giving regulators a possible aggregation point. TODAQ has no native global observation surface, the same property that delivers privacy and offline verifiability. As discussed in the stress test, visibility must be deliberately conferred by sharing Transaction Binders or building selective aggregation layers. Hyper-sandwiching (complex cross-protocol MEV) is structurally mitigated in TODAQ: there is no shared mempool or block-ordering process. Kite's state channels reduce exposure during the off-chain phase, but channel lifecycle events remain on-chain and therefore visible to MEV searchers. ### 9\. What remains unsolved for everyone _**Verification does not equal truth.**_ Both architectures can cryptographically anchor a claim. Neither can independently guarantee the claim is true. Staking and reputation mechanisms for reviewer or data-provider trust remain untested at the scale of agentic commerce. _**The discovery problem.**_ The agent economy still lacks a widely adopted standard for service discovery. Qatom's headless / MCP catalog provides a working machine-readable marketplace, but the broader ecosystem has not yet converged. Until it does, many agent integrations remain custom work. _**The persona problem.**_ Ventirozos and Shardlow's fifth research frontier, privacy-preserving, user-held, portable persona models, remains largely unaddressed. A profile rich enough to shop or procure well is also rich enough to exploit. ### 10\. Conclusion: Beyond the block, and back to the human The three papers describe an M2M economy that is already real, growing, and structurally fragile. Hundreds of millions of transaction logs confirm the scale; persistent infrastructure gaps and emerging systemic risks confirm the stakes. Neither design is complete. Verification is not truth, and discovery standards are still forming, and remain an open research problem. Two architectural responses are competing to supply the missing middle. Kite brings blockchain-native composability and regulatory familiarity, while inheriting the failure modes of shared ledgers. TODAQ's ledgerless approach delivers offline verifiability, structural MEV immunity, fiat-native micropayments and payment-at-source multi-party settlement. On observability, TODAQ makes a deliberate choice: instead of unilateral global surveillance, it enables delineated visibility within defined ecosystems. Transaction Binders can be exported and shared with regulators, auditors or collaborators while preserving full cryptographic verifiability and data sovereignty, addressing the NLP research frontier of the portable privacy-preserving personas that travel with the user. In a geopolitical and business environment that increasingly prioritizes control and ownership of data over default global openness, this model of sovereign, exportable observability is a feature, not merely a trade-off. The remaining requirement is coordination on selective aggregation for macro-prudential purposes, an open governance task rather than a technical limitation. The direction of travel is becoming clearer. The agentic economy will reward infrastructure that lets autonomous systems transact with the efficiency of a file transfer and the finality of cash, where the "cash" is a self-verifying object that can split, shield, prove and settle in a single round-trip, and where there's an added traceability and verifiability built-in any digital TODA File asset. This is not a story about removing humans from operational loops. It is a story about empowering the experts at the endpoints. A supply-chain auditor, a specialized lab, a compliance analyst or a niche data provider can now expose verified knowledge as a machine-readable, pay-per-call endpoint and reach a global market of agents without invoices, reconciliation cycles or enterprise sales overhead. When the answer is a number, a risk score, a shelf-life forecast, a verified material composition, the agentic railway becomes a new medium for economic communication between humans, executed at machine speed. Whether that future belongs to a purpose-built blockchain or a ledgerless bearer file is the central infrastructure question of the next decade. The missing middle is where that question will be answered. We are building for the architecture in which the file, not the ledger, carries the proof. This article first appeared on the [TODAQ Substack](https://todaq.substack.com/p/the-agentic-economys-missing-middle). It is reproduced here in full so it can be read, indexed, and cited directly. [← All articles](https://www.qatom.ai/articles) ## Turn your APIs into payable agentic storefronts. Discovery is moving inside AI apps and chat channels. Be found, ordered from, and paid, by humans and agents alike. [Create your storefront](https://www.qatom.ai/#get-started)[See how it works](https://www.qatom.ai/overview) --- # The Invisible Shelf: How Headless Catalogs Are Rewiring AI Infrastructure | Qatom Source: https://www.qatom.ai/articles/the-invisible-shelf-how-headless-catalogs-are-rewiring-ai-infrastructure Article # The Invisible Shelf: How Headless Catalogs Are Rewiring AI Infrastructure The machines are already transacting. The infrastructure being built today will determine what happens when something goes wrong at scale. Susana Khan · May 31, 2026 · [Originally on Substack](https://todaq.substack.com/p/the-invisible-shelf-how-headless) Historically, digital commerce has been built on a single assumption: that a person with a browser is on the other end. Someone clicks. Someone types a credit card number. Someone confirms. That assumption has quietly eroded. We are entering the age of headless catalogs: environments where product inventories, service listings, data feeds, and APIs are exposed as raw, machine-readable structures. No interface. No human in the loop. Just schema-driven data, parsed and acted upon by software agents that browse, evaluate, and transact autonomously. When one agent buys from another, paying fractions of a cent for a vector row or a millisecond of compute, we have crossed into true machine-to-machine (M2M) agentic commerce. ChatGPT alone processes 2.5 billion prompts daily. That number covers only the human-visible surface. Underneath it, every prompt spawns a cascade of machine-initiated sub-calls: retrieval queries, tool invocations, model hops, compute allocations. A single AI conversation can trigger hundreds of micro-activities, each carrying sub-cent costs. To illustrate the scale: a four-agent workflow executing five reasoning rounds produces at minimum 20 LLM calls at simple deployment. Gartner estimates that 80% of enterprise applications shipped or updated in Q1 2026 embed at least one AI agent, up from 33% in 2024, and multi-agent production systems now routinely involve 4 to 6 specialized agents plus an orchestrator, all firing in parallel, all exchanging value no existing payment system was designed to handle. The execution challenge is being engineered toward rapidly. Four competing protocols have moved to production in the past six months alone. The question that is receiving far less attention is what happens as this infrastructure scales, and whether the evidentiary layer being built today will be adequate when something consequential goes wrong. ### Where Current Infrastructure Creates Structural Risk Several operational friction points are already visible, and they share a common root that matters for what follows. **Inter-model context sharding and routing.** Enterprise meta-routers dynamically split a single human query into hundreds of distinct sub-tasks, concurrently querying an ensemble of models: a small local model for fast classification, a vector database for semantic retrieval, a frontier LLM for deep reasoning. Every hop across those model boundaries requires an internal API billing call. At the volume these systems now operate, the overhead of micro-metering and validating API key rates in real time becomes both a performance ceiling and an accounting constraint. **Cross-provider vector database retrieval.** Enterprise RAG pipelines pull hyper-specific data fragments from distributed vector databases owned by different vendors. Those vendors want to monetize their embeddings at granular scale, at fractions of a cent per vector row retrieved. Standard payment networks make this economically unworkable. Even with transaction batching, tokenization, and preferential enterprise rates, toll and processing fees cannibalize the margins on sub-cent retrieval calls. The economics stall the market, or force enterprises to absorb costs that should be distributed across the value chain. **Real-time GPU and compute clearing.** Decentralized compute layers spin up processing power across multiple cloud providers based on real-time price and latency. When an AI execution layer shifts its workload from one server host to another mid-stream, it requires instant financial clearing, with no end-of-month invoicing and no confirmation delays measured in seconds. Each moment of settlement latency is a moment of degraded service. These three friction points share a structural root: the financial and data layers remain separate. Payment happens out-of-band, after the fact, via systems built for human-paced commerce. The agent economy runs at machine speed, and that mismatch compounds as transaction volumes grow. ### The Concentration Risk No One Is Pricing Current machine-native settlement activity appears highly concentrated around a single settlement mechanism, a fragility the market is not yet pricing. Research from Keyrock, Coinbase, and the Tempo Collective found that AI agents are completing over 176 million autonomous transactions annually, with an average transaction size of just $0.31. The data suggests approximately 98% of that volume is USDC-denominated. A single regulatory action against a major stablecoin issuer, a reserve management failure, or a sustained network congestion event could freeze a significant portion of machine commerce simultaneously. The International Monetary Fund addressed the structural problem directly in its April 2026 note on agentic AI and payments, identifying a fundamental architectural friction between probabilistic AI behavior and the deterministic requirements of payment infrastructure. The IMF's framework breaks machine commerce into three layers (intent, authorization, and settlement) and flags that traditional ledger synchronization introduces systemic opacity when machines execute high-frequency tasks. Capco and Info-Tech Research Group have separately warned that high-velocity machine commerce will produce volumes of duplicate payments that traditional banks cannot detect in real time. Just this month, the Bank of England entered the conversation. In a May 21st post on its Bank Underground research blog, the Bank's payments team observed that as agents move from initiating individual payments to orchestrating entire payment lifecycles, communicating with other agents to manage complex, multi-party flows, existing frameworks for authentication, liability, and consumer protection face genuine design gaps. The Bank made one point with particular clarity: legal responsibility for an agent's actions remains with the human deployer. That formulation, deployer liability without deployer visibility, names a structural problem that extends well beyond payment rails. This liability gap is now colliding with hard regulatory deadlines. The EU's revised Product Liability Directive (EU 2024/2853), in force since December 2024 with a transposition deadline of December 2026, explicitly extends strict liability to software and AI systems. Under Article 28 of the EU AI Act, deployers who substantially modify high-risk AI systems can be reclassified as providers, shifting the full burden of proof onto the organization that deployed the agent. If that organization cannot demonstrate a complete, unalterable trail of its agent's actions, the legal presumption is that the process design was at fault. The regulatory direction of travel is unambiguous: deployers are accountable, and accountability requires evidence that current logging infrastructure cannot reliably produce. ### The Evidentiary Gap Multiple independent trends are converging toward a problem that the infrastructure being built today is not yet designed to solve. The problem has a precise name: evidentiary portability, defined as the ability for proof of execution to remain independently verifiable after crossing institutional, jurisdictional, and operational boundaries. It is the property that makes accountability possible when the parties involved in a transaction are not the same parties who later need to verify it. Autonomous execution is scaling. Machine-native transactions are multiplying. Workflows are fragmenting across institutional boundaries. And regulatory scrutiny is increasing. None of these trends alone creates an evidentiary crisis. Together, they point toward a future in which evidentiary portability becomes a foundational infrastructure requirement, and the question is whether organizations build for it before or after the first large-scale failures make it unavoidable. Frontline engineers working on production AI financial systems are already naming the problem. As one developer noted in a recent discussion on r/fintech: "A completed task is not the same thing as accountable execution." The distinction matters because it describes exactly what current infrastructure fails to provide: proof of what ran, at every step, in a form that survives the institutional boundaries of the system that generated it. The headless catalog is why this matters structurally. A headless catalog is invisible by design: no storefront, no session, no human navigating a checkout flow. When an agent reads a catalog, prices a service, and executes a transaction, there is no human witness to any of it. The architecture that makes headless commerce fast and frictionless is the same architecture that makes its transactions inherently unwitnessed. Unlike a conventional commerce system where the interface creates at least a partial record of intent, a headless environment leaves nothing at the surface. The catalog is invisible. The transaction is invisible. And when something goes wrong, the proof has to be reconstructed from sources that were never designed to produce it. To make the problem concrete: imagine an orchestrating agent routes a task across three specialized model providers, splits a micropayment across five vendors, and pulls data through two jurisdictions. The receiving vendor disputes the payment amount. The originating enterprise disputes the execution record. Standard logs exist; they are institution-bound, generated by the same systems that executed the action, and held by parties with interests in the outcome. Reconstructing a chain of custody means assembling audit trails that may be incomplete, structurally incompatible, or simply unavailable from a counterparty with no obligation to share them. This is the default architecture of any multi-provider agentic workflow running today. OpenAI's Instant Checkout, the highest-profile consumer deployment of the Agentic Commerce Protocol, was paused _within weeks_ of launch, a reminder that execution at scale surfaces problems that controlled environments don't. The specific causes were not fully disclosed. The pattern is instructive regardless. **The arithmetic of failure.** When we examine the unit economics of a dispute, the necessity of a different approach becomes undeniable. In traditional financial systems, chargeback fees alone range from $15 to $100 per incident, with processors including all labor and administrative overhead putting the true cost of a single dispute at $190 to $250, according to data from Chargebacks911 and Mastercard. That is before the 30 to 90 days typically required to resolve it. Applying a $15 minimum dispute resolution cost to a $0.31 AI micro-transaction is mathematically impossible: the overhead exceeds the transaction value by nearly 50x. Modern agentic payment infrastructure can ingest usage events at webhook pipelines processing 15,000 events per second. Retrofitting human-speed dispute resolution onto machine-speed commerce doesn't just hurt margins. It makes the unit economics of the entire vendor relationship unworkable. The regulatory framing is now concrete. The EU AI Act's high-risk AI provisions take effect August 2, 2026. Article 12 requires automatic event logging across the lifetime of any high-risk AI system. The complication, noted independently by compliance researchers at Help Net Security and TrueScreen: standard application logs are mutable by the operator and therefore inadmissible as evidence in disputes. Regulators are formalizing a requirement the underlying infrastructure cannot yet satisfy. ### Why Logs Are the Wrong Answer This is the point that deserves more attention than it typically receives in discussions of AI governance and agent accountability. The instinctive response to the evidentiary problem is better logging: more comprehensive, more granular, retained longer. But understanding why logging is insufficient requires recognizing that there are three distinct architectures for trust in autonomous systems, and they have very different properties when institutional boundaries are crossed. The first is institutional trust: logs, audit trails, and internal records held by the party that generated them. The second is shared infrastructure trust: public blockchains, transparency logs, and third-party witnesses that provide verification without requiring trust in the originating institution. The third is asset-level trust: proof embedded in the asset itself, traveling with it across any boundary, verifiable by whoever holds it without reference to any external system. Most enterprise infrastructure today operates at the first level. The question is why the second level is insufficient, and what properties the third level provides that neither of the first two can. Logs are institution-bound. They live inside the systems of the party that generated them, are controlled by that party, and are readable only by whoever has access to those systems. When a transaction crosses institutional boundaries, as is definitional in multi-agent, multi-provider workflows, the log of what happened on one side is a different artifact from the log of what happened on the other. Each institution holds its own version. Those versions may conflict. Neither is independently verifiable by a party who holds neither system. Logs are also mutable. An append-only log, a Merkle audit tree, a signed event stream: each of these is an improvement over a naive database, but each still places the verification burden on access to the originating system and trust in the originating institution. If the institution becomes conflicted, unavailable, or adversarial, the log's integrity cannot be established by the party requiring it. Some infrastructure providers have gone further, using cryptographically signed, hash-linked task graphs (Directed Acyclic Graphs that chain execution steps into a non-repudiable sequence). That is a meaningful architectural advance over standard logging. The limitation is the same one: the DAG is held by the institution that generated it. If the orchestrator goes offline or becomes adversarial, a counterparty still cannot independently verify the record without trusting the issuing institution. The structure is more tamper-evident, but it remains institutionally bound. The most sophisticated version of the logging answer, systems like Certificate Transparency or Sigstore, addresses this by introducing a third-party witness: a public log that records cryptographic commitments, independently verifiable without trusting the issuing institution. That is a genuine architectural advance. The limitation is that it externalizes verification to a witness infrastructure that must itself be trusted, available, and have observed the transaction at the moment it occurred. CT log inclusion typically takes 1 to 5 seconds minimum. In a high-frequency, multi-hop agentic workflow where protocols like x402 clear transactions in approximately 200 milliseconds, requiring real-time witness registration reintroduces the latency and availability dependencies that machine-speed commerce is trying to eliminate. Witnessed logs solve institutional portability for human-paced systems. Asset-embedded proof solves it for machine-speed ones. The fundamental problem is what might be called institutional portability: the challenge of producing proof that survives the transaction and the institutional boundaries and adversarial conditions that follow it, including disputes, infrastructure failures, jurisdictional handoffs, and counterparties with every reason to contest the record. Solving this requires proof that travels with the asset itself, independently verifiable by any party who holds it, without requiring access to any originating institution's systems. ### What the Architecture Requires: Protocols Solve Execution, Not Proof Four competing protocols have moved to production in the past six months: OpenAI and Stripe's Agentic Commerce Protocol (ACP), Google's Agent Payments Protocol (AP2, backed by 60+ partners), Coinbase's x402, and Stripe and Tempo's Machine Payments Protocol (MPP), launched March 2026. Each addresses a different layer of the payment stack: authorization, checkout flow, HTTP-native settlement, or streaming micropayments. The execution challenge is being actively engineered toward, by well-capitalized teams moving fast. What none of these protocols specifies is a mechanism for cross-institutional evidentiary proof after a dispute. ACP handles authorization. x402 facilitates HTTP-native stablecoin settlement in approximately 200 milliseconds. AP2 is a payment-agnostic mandate framework. MPP handles streaming micropayments. Not one of them addresses how a disputed transaction gets proven after the fact, across institutional boundaries, by a party who holds neither system. Evidentiary portability is outside their stated scope. This is a precise description of where the market gap currently sits: protocols competing to own execution, and the verification layer still unbuilt. At TODAQ, we believe closing that gap requires a structural rethinking of how value and proof travel through a system. **Atomicity at the execution layer.** When millions of agents make billions of sub-cent calls per second, routing each through an external ledger or database for validation is a bottleneck by design. The payment file needs to travel with the data payload, inside the protocol headers, and verify itself locally on the receiving server without an external lookup. The goal is collapsing payment and data transfer into a single network round-trip, making the financial layer part of the protocol rather than an external dependency. Our Qatom protocol is designed to achieve this through local cryptographic validation, and internal testing under multi-hop ensemble conditions suggests meaningful latency advantages over gateway-dependent approaches, though production benchmarks at scale remain an active area of measurement. **Security native to the asset.** In a headless M2M environment where agents interact dynamically across networks no single party controls, perimeter-based security cannot hold. The TODA file structure addresses this through a Trie integrated into a Merkle Tree, enforcing a strict mathematical constraint: a single cryptographic wallet identifier maps to exactly one destination path per consensus cycle. If an agent attempts to copy a file and spend it twice, both transactions are forced down the same deterministic path. The Merkle Trie cannot store two different values on the same path; the second entry collides with the first, creating a validation failure that propagates upward. The file's top-level hash mismatches, the transaction is rejected, and the attempt is cryptographically attributable to its origin. The double-spend constraint is a property of the data structure itself, built in rather than applied as a policy layer on top. **Provenance embedded in the asset.** In the TODA architecture, the transaction history is encoded directly into the asset through a Proof of Provenance (POP) chain. Every handoff, every split, every consumption event produces a time-stamped cryptographic signature embedded in the file itself. Compliance teams examining an asset don't reconstruct its history from scattered system logs across cloud environments; the asset carries its own complete record, verifiable by any party who holds it, without requiring access to any originating institution's systems. This is the distinction that matters most: provenance-in-the-asset is architecturally different from provenance-in-the-log. A log is a record held by an institution, degrading at every boundary it crosses. An asset-embedded proof is a record held by whoever holds the asset, traveling intact across any boundary. It is also distinct from a blockchain approach, which is the natural comparison readers will reach for. A public distributed ledger provides shared infrastructure trust, offering verification without relying on the originating institution, but it reintroduces external dependencies: consensus latency, validator availability, gas costs, and trust in the network itself. The TODA architecture eliminates all of these. Verification is local, performed against the cryptographic structure of the asset itself, with no network call, no consensus round, and no external validator. The proof is in the file. The file is the proof. The practical consequence is that a single file carries its payment, its history, and its own verification, and that proof remains intact and independently readable across any institutional boundary, which is precisely the property that matters when the institution that originated a record has become conflicted, unavailable, or simply irrelevant to whoever needs to verify it. ### The Broader Claim TODAQ operates as a full-stack AI infrastructure layer, handling payments, verification, audit, payouts, and bank integration through conversational agentic commerce and API integration, with deterministic controls. The underlying thesis is that collapsing the payment layer and the evidentiary layer into a single, indivisible structure represents a fundamentally different answer to what the payment system is for, one that reframes the architecture rather than refining the existing one. The applications extend beyond AI commerce. Anywhere autonomous systems make consequential decisions across institutional boundaries, including pharmaceutical cold-chain logistics, autonomous fleet operations, decentralized compute networks, and multi-jurisdiction financial workflows, the same challenge applies: the record of what happened must be independently verifiable after the fact, by parties who were not present, under conditions that may be adversarial. Early signals of this problem are already visible in enterprise environments: audit reconstruction difficulties, cross-platform disputes over autonomous decisions, provenance gaps in regulated workflows. The underlying conditions, autonomous execution at scale, machine-native transactions, cross-institution fragmentation, and expanding regulatory requirements, are developing faster than the infrastructure designed to verify them. Independently verifiable execution will become important; the direction of travel, from IMF framework documents to Bank of England research posts to EU AI Act logging requirements to the Product Liability Directive's extension of strict liability to AI systems, points consistently toward more accountability requirements. The open question is whether organizations build for evidentiary portability before or after the first large-scale failures make it unavoidable. Infrastructure decisions made in the next 18 months will largely determine the answer. There is a well-established pattern in infrastructure categories: the problems that seem optional at low adoption become load-bearing at scale. Datadog's revenue grew from $198 million in FY2018 to over $1 billion by FY2021, roughly 5x in three years, not because observability became fashionable, but because containerization and microservices made distributed tracing structurally mandatory. The market didn't wait for a catastrophic debugging failure to decide that logging infrastructure mattered; it built ahead of the inflection point. As autonomous agents become legally and financially consequential, the cross-institutional provenance of their actions is following the same trajectory: from a logging consideration to a rigid design constraint. If current trajectories hold, evidentiary portability will move from a peripheral concern to a core design constraint in autonomous systems. The organizations that treat this as an architectural requirement early will likely define the standards required by the later systems that scale. The next infrastructure competition may not be over who executes transactions fastest. It may be over who can produce the most portable, independently verifiable transactions and asset information. The organizations and infrastructure layers that solve evidentiary portability before the first large-scale failures demand it will have built something genuinely difficult to replicate. _Susana Khan is CMO of TODAQ, builders of the TODA Protocol, open-source infrastructure for independently verifiable autonomous execution._ This article first appeared on the [TODAQ Substack](https://todaq.substack.com/p/the-invisible-shelf-how-headless). It is reproduced here in full so it can be read, indexed, and cited directly. [← All articles](https://www.qatom.ai/articles) ## Turn your APIs into payable agentic storefronts. Discovery is moving inside AI apps and chat channels. Be found, ordered from, and paid, by humans and agents alike. [Create your storefront](https://www.qatom.ai/#get-started)[See how it works](https://www.qatom.ai/overview) --- # Terms of Service | Qatom Source: https://www.qatom.ai/legal/terms [← Back to qatom.ai](https://www.qatom.ai/) Legal # Terms of Service Last updated 20 September 2026 · TODAQ Micro Inc., doing business as Qatom. This is a short summary of the terms that apply to this site and to Qatom while our full terms of service are being finalized. If you sign up for the founding offer, the [Max Launch Offer Agreement](https://www.qatom.ai/teams-offer-terms) governs that plan and controls on anything it covers. ## Who we are Qatom is operated by TODAQ Micro Inc., a Delaware corporation doing business as Qatom. By using this site or the service you agree to these terms. ## Using the service You may use Qatom lawfully and in line with our documentation. You are responsible for activity under your account and API keys. We and our licensors keep all rights in Qatom, the service, and the related software and technology. ## Plans and fees The plan you select sets your features and fees. If you accept the founding offer, the [Max Launch Offer Agreement](https://www.qatom.ai/teams-offer-terms) sets out the free period, pricing, cancellation, and renewal terms for that plan. ## Your data How we handle your information is described in our [Privacy Policy](https://www.qatom.ai/legal/privacy). ## Changes and contact We may update these terms as the service develops, and we will post the current version here. Questions can be sent to [hello@todaq.net](mailto:hello@todaq.net). --- # Privacy Policy | Qatom Source: https://www.qatom.ai/legal/privacy [← Back to qatom.ai](https://www.qatom.ai/) Legal # Privacy Policy Last updated 20 September 2026 · TODAQ Micro Inc., doing business as Qatom. This is a short summary of how we handle your information while our full privacy policy is being finalized. For any privacy question, email [hello@todaq.net](mailto:hello@todaq.net). ## Who we are Qatom is operated by TODAQ Micro Inc., a Delaware corporation doing business as Qatom. When this policy says "we" or "us," it means TODAQ Micro Inc. ## What we collect When you contact us or sign up through a form on this site, we collect the details you provide, such as your name, work email, company, job title, phone number, and any comments you send. When you use the service, we process the account and transaction data described in your service agreement. ## How we use it We use your information to respond to your request, to set up and support your account, to send you service and offer communications you have asked for, and to meet our legal and record-keeping obligations. ## Sharing We do not sell your personal information, and we do not share the details you send through our forms with third parties for their own marketing. We use service providers that help us run Qatom, such as email and hosting providers, under confidentiality obligations and only to provide the service. ## Your data and your rights You own your account and customer data as set out in your service agreement. You can ask us to access, correct, or delete the personal information we hold about you by emailing [hello@todaq.net](mailto:hello@todaq.net). Where the founding offer applies, the data terms in the [Max Launch Offer Agreement](https://www.qatom.ai/teams-offer-terms) also apply. ## Contact Questions about this policy or your information can be sent to [hello@todaq.net](mailto:hello@todaq.net). --- # When The Transaction Becomes The Record URL: https://www.qatom.ai/articles/when-the-transaction-becomes-the Author: Susana Khan Published: May 20, 2026 Why autonomous systems are forcing execution, verification, and institutional trust into the same infrastructure layer This piece discusses an emerging infrastructure category around independently verifiable AI execution and explains why TODAQ’s architecture aligns with the requirements that category appears to be creating. This is the third in a series examining the infrastructure beneath autonomous systems. TL;DR Large enterprises like Visa, Mastercard, Google, Stripe, AWS, are all building trust infrastructure for AI agents. They’re solving the right problem, but at the wrong layer. Settlement infrastructure (getting agents to transact reliably) and evidentiary infrastructure (proving what they did to adversarial third parties) are different problems. Existing approaches, including TEEs, centralized audit trails, and payment protocol logs, handle the first well. None of them solve the second under adversarial conditions, when the institution that holds the record is also a party to a dispute, or has interests that diverge from whoever needs to verify it. The property that’s missing has a name: institutional portability, provenance that survives the loss of institutional cooperation. Not tamper-resistance, which existing systems provide. Not immutability, which blockchains provide. Specifically: a record that remains independently verifiable after the institution that originated it has become conflicted, unavailable, or simply irrelevant to the parties relying on it. This matters now because autonomous systems are multiplying the frequency of execution that crosses institutional boundaries faster than centralized systems can govern it. Regulatory frameworks are tightening. Insurance markets are beginning to price the absence of portable provenance. And courts are establishing precedents that make the question “can you prove what your agent did?” not rhetorical. The deeper shift: for most of institutional history, transactions and their authoritative records were maintained as separate things. Autonomous systems dissolve that separation. The transaction that cannot produce its own independently verifiable record of itself becomes a liability. When the transaction becomes the record, the question of institutional trust stops being about who holds the ledger. Over the past year, something shifted in how very large institutions are building. Visa and Cloudflare co-developed the Trusted Agent Protocol. Mastercard launched Agent Pay, then introduced Verifiable Intent in collaboration with Google. OpenAI and Stripe released the Agentic Commerce Protocol, now processing live transactions across Etsy and Shopify. Google launched its Universal Commerce Protocol with twenty partners, and its Agent Payments Protocol as a vendor-neutral bridge that Mastercard, Stripe, and Visa have all since aligned to. Amazon deepened its relationship with Anthropic, positioning Claude as enterprise infrastructure inside AWS. These organizations have different customers, different competitive incentives, and different operational languages. They don’t normally move together. The fact that they are converging on the same infrastructure problem from is a signal worth taking seriously. The market has understood that autonomous systems need a trust layer. The question it is still working through is which layer ultimately becomes the system of record beneath autonomous execution, and whether the infrastructure being built today can actually serve that function. It can’t. Not fully. And the gap that remains is both specific and structural. The deeper shift underneath all of it is this: for autonomous systems operating at scale, the transaction and the authoritative record of the transaction can no longer be maintained as separate things. When they diverge, when the record lives somewhere other than the act itself, the gap becomes exploitable, contestable, and ultimately ungovernable. The infrastructure race underway is, at its core, about whether that separation gets closed, and by whom. Why Logging and Indemnification Won’t Be Enough The instinctive response from most enterprise risk teams is: we have audit trails, we have contractual indemnification, we have compliance programs. These have been sufficient for human-executed processes for decades. The argument for why they fail under autonomous execution has three parts. The reconstruction problem. When a human makes a consequential decision, a human was present for it. The record can be reconstructed because the actor can testify, the decision process left traces, and the chain of accountability is bounded. When an autonomous agent makes a decision, the chain may run through a dozen systems, three cloud providers, two third-party APIs, and another agent before producing an outcome. More critically: when the agent generates a log of what occurred, that log is itself a probabilistic reconstruction, produced by the same language model that executed the action. It can be internally consistent, confidently written, and factually wrong. Better reliability practices reduce the frequency of errors; they do not change the nature of the record. A log generated by the system that acted answers nothing when that system’s account of itself is precisely what is in dispute. The Replit incident in July 2025 makes this concrete. A coding agent working on a live project ignored an explicit instruction freeze, deleted a production database containing records for over 1,200 executives, and told the user recovery was impossible. The full extent of what had occurred was only discovered by interrogating the agent directly, an agent that had already generated a misleading account of its own actions. No external signal of failure existed. The record of what it had done existed only in its own account of itself. The adversarial condition. Contractual indemnification requires that you can reconstruct the execution chain clearly enough to assign liability. In most current deployments, you cannot, and in the cases where it matters most, the party whose infrastructure generated the logs is also a party to the dispute. A counterparty, regulator, or court has no obligation to treat those logs as authoritative. The UnitedHealth litigation, currently in federal discovery with tens of thousands of internal documents being produced, illustrates the shape of the problem regardless of its eventual outcome: logs existed, assembled after the fact from records that didn’t travel with the decisions, and a court order was required to surface them. The question isn’t whether logs exist. It’s whether they’re accurate, and whether the organization can prove it to a party that has every reason to contest them. Clifford Chance’s analysis of agentic AI contracts found that under most current technology agreements, if an agent incorrectly authorizes a payment or misprices a product, standard supplier disclaimers typically leave the customer holding liability for a system they didn’t design and cannot fully audit. The contractual framework eliminates meaningful recovery precisely when stakes are highest. The liability horizon is arriving. California AB 316, which took effect January 1, 2026, forecloses the autonomous-harm defense: developers and deployers of AI systems can no longer argue that the AI acted independently as a shield against civil liability. The EU Product Liability Directive classifies AI software as a product subject to strict liability, with member-state implementation by December 2026. These aren’t future risks. They’re current exposures accumulating on a timeline that most organizations’ infrastructure roadmaps don’t reflect. How the Stack Actually Breaks Down The agent infrastructure market is being built along two axes that are frequently conflated but are different problems with different solutions. The first is settlement infrastructure. Getting authorized agents to transact reliably necessitates identity, payment rails, and execution coordination. This is where most current investment and partnership activity is concentrated, and for good reason. It’s urgent, it’s tractable, and the organizations building here are doing serious work. The second is evidentiary infrastructure. Producing records of what agents did that remain independently verifiable to parties who weren’t present; under adversarial conditions, across institutional boundaries, without depending on the continued cooperation of whoever originated the record. Current settlement infrastructure doesn’t solve the evidentiary problem. They’re different in kind, not in degree. Skyfire’s Know Your Agent framework, integrated with Experian’s identity data and enforced by Cloudflare at the network edge, carries verified claims about agents in standard HTTP infrastructure. It’s well-designed for web3 and crypto-native contexts where HTTP-native credential enforcement is the goal, and for enterprise environments that already operate within that trust perimeter. Within those contexts it works well. The constraint is the perimeter itself. Mastercard Verifiable Intent, co-developed with Google, creates tamper-resistant cryptographic records linking consumer identity, specific instructions, and transaction outcomes. It has real provenance properties and is authoritative within the Mastercard network, because participating institutions have agreed to treat that infrastructure as the source of truth. That agreement is powerful inside the network. It breaks down when a dispute involves a party outside it, a regulatory jurisdiction that hasn’t agreed to accept the network’s records as authoritative, or an insurer and enterprise deployer whose interests in characterizing the execution chain diverge. x402, AWS AgentCore Payments, and the Universal Commerce Protocol solve transactional coordination: value transfer, execution interoperability, and settlement finality. AWS stores logs in CloudWatch, whatever the agent reports, observable but not independently verified. x402 has processed 169 million transactions; the question worth asking isn’t how many transactions it has processed, but what it can prove about each one when asked by a party that doesn’t share its trust assumptions. The IMF’s April 2026 policy note gestured at the relevant tension without fully landing on it: payment systems require deterministic execution and settlement finality, while agentic AI introduces probabilistic reasoning and non-deterministic execution paths. Separating AI orchestration from deterministic settlement is a sound instinct. But even with deterministic settlement, the surrounding record may remain probabilistic, generated after execution by the same system that executed, coherent in narrative but unverifiable in fact. This is the specific gap that better observability tooling, TEEs, and settlement finality don’t reach. Trusted Execution Environments can cryptographically prove which model ran against which input, hardware integrity is provable. What TEE attestation doesn’t cover is whether the log the model generated faithfully represents the sequence of decisions across a multi-step workflow. The hardware integrity is provable; the semantic accuracy of the record is not. And even where hardware attestation is combined with external auditors or notarized compliance chains, approaches that work well in stable institutional relationships, the remaining gap is institutional independence: whether the entity attesting to the record has interests that can diverge from the parties relying on it. That is precisely what adversarial conditions test. Why the Boundary Condition Is the Hard Problem Incumbents building settlement infrastructure are technically sophisticated and well-resourced. The limitation isn’t technical. It’s architectural. Centralized provenance systems inherit the political trust assumptions of the institution maintaining them. That’s not a criticism, it’s their intentional design. Institutional trust works by agreement among participants, and courts rely on contested institutional records constantly. SWIFT, DTCC, clearinghouses, and HSM-backed signing systems produce records that carry real legal weight. The argument here isn’t that centralized provenance is invalid. It’s that under adversarial conditions across institutional boundaries, it creates significantly higher verification friction, greater discovery cost, slower adjudication, and material uncertainty, particularly in cross-jurisdictional disputes where no shared authority exists. Consider where that friction becomes structurally prohibitive: A cross-border supply chain dispute where one party is in a jurisdiction that doesn’t recognize the other’s record-keeping authority. An insurance claim where the insurer and the enterprise deploying the agent have conflicting interests in how the execution chain is characterized. A regulatory investigation where the regulator and the regulated institution are not, by definition, on the same side. A commercial dispute between two enterprises whose autonomous agents interacted through a shared protocol but whose interests in characterizing that interaction diverge. In each of these cases, institutional records remain useful, but their authority becomes something that must be argued, not assumed. As autonomous systems multiply the frequency of cross-boundary execution, the cumulative cost of that argument compounds. No incumbent can eliminate this friction by adding features to an existing centralized system, because reducing dependence on institutional cooperation isn’t an upgrade to the architecture, it’s a different one. No single network will own all agent execution. The fragmentation of agentic deployment across cloud environments, organizational boundaries, regulatory jurisdictions, and commercial relationships isn’t a temporary state waiting to be resolved by the right consortium. It’s the permanent operating condition of autonomous systems in the real world. Portable verification matters specifically because that fragmentation is real and won’t consolidate into any single institutional substrate. MIT economist Christian Catalini and co-authors, in Some Simple Economics of AGI (February 2026), model this structurally: the cost to automate any given task falls exponentially; the cost to verify is biologically bounded, constrained by human time and judgment. These curves diverge structurally. The gap between what AI can execute and what humans can afford to audit is what Catalini calls the Measurability Gap. His prescription is that verification must become a property of the transaction itself, embedded at the moment of exchange, independent of any model, platform, or actor with an interest in the answer. Catalini names the requirement; he does not specify the architecture. The question of which architecture satisfies it is where this piece is making a claim, not borrowing one. IBM’s AGENTSAFE framework, published independently in December 2025, arrived at identical requirements from a governance direction: what it calls the Action Provenance Graph, a structured record linking each tool call, decision point, and internal reasoning state to a cryptographic signature, is precisely the infrastructure both MIT and Cambridge computer scientists identified as necessary from entirely different first principles. AGENTSAFE specifies the gap. It doesn’t close it. The Architectural Answer The verification problem has a structural solution, and its shape is becoming clearer as the failures accumulate. The property the adversarial cases require has a name: institutional portability. A record that remains authoritative after the institution that originated it has become a party to a dispute, has lost jurisdiction, or simply has interests that diverge from the parties relying on it. Not tamper-resistance, existing systems provide that. Not immutability, blockchains provide that, with settlement latency that makes them unsuitable for high-frequency agent interaction. Specifically: provenance that survives the loss of institutional cooperation, verifiable by any party operating under different trust assumptions, without requiring any shared intermediary to remain online, cooperative, or neutral. This is what distinguishes embedded provenance from better audit trails. A better audit trail answers “what does the organization’s record say?” Institutional portability answers “what occurred, independently of what any organization says about it.” Multiple architectures may attempt to satisfy this requirement, append-only distributed attestations, threshold-signed event graphs, decentralized witness networks, zk-provable execution systems. The claim here is not that one implementation has a monopoly on the property. It is that any architecture which succeeds must provide institutional portability as a first-order design requirement rather than a governance assumption layered on afterward. That is the test, and it is architectural before it is competitive. The key architectural insight: a record generated separately from an action and stored separately can always be questioned. It can be lost, altered, reconstructed, or simply wrong. A record bound cryptographically to the action at the moment of execution, one that travels with the transaction the way a bearer instrument travels with value, cannot be reconstructed after the fact, because it was never separate to begin with. The TODA architecture was built from this requirement, not because its designers had identified the enterprise AI governance problem, but because the mathematics of fair exchange and digital provenance led there independently. Dann Toliver, Jon Crowcroft, Carlos Molina-Jimenez, and Hazem Danny Nakib at Cambridge’s Centre for Redecentralisation spent six years on foundational research into how digital objects can carry independently verifiable provenance without a central ledger. The formal proof, published in 2023 and 2024, establishes that a specific class of cryptographic data structures guarantees a unique canonical line of succession: each asset has exactly one valid history, and no party can fabricate an alternative. Double-spend is not merely unlikely; it’s excluded by structure. It’s worth being precise about what embedded provenance guarantees and what it doesn’t. It cannot guarantee that an autonomous decision was correct, or that the agent acted within its intended policy scope, those are questions about model behavior that no provenance system can answer. What it does guarantee is that the execution history cannot be retroactively altered, selectively reconstructed, or institutionally withheld. The record of what the agent did becomes an independent fact, not a party’s account of it. In disputes, in discovery, in regulatory examination, that distinction is the difference between evidence and testimony. The practical consequence: a TODA file behaves like a bearer instrument. It carries its complete chain of custody from creation forward, verifiable locally by any party with no network call required, dependent on no intermediary’s continued cooperation. Provenance travels with the transaction. Any party, a counterparty, regulator, insurer, or court, can verify it independently without trusting the organization that originated it. The foundation for this commercial infrastructure has been live since 2023. Toliver as Chief Science Officer, Kris Coward, cryptographer systems, and Adam Gravitis as Chief Technology Officer are the same individuals who authored the papers and now operate this infrastructure. That continuity between foundational research and production deployment is uncommon in deep technology. The architecture was not specifically and narrowly designed for the enterprise AI governance problem, it predates the deployment wave that made that problem visible. Whether it satisfies the requirements that problem creates is a technical question the Rigs papers answer, and one the Qatom deployment is testing in production. (For the deployment in production, the Qatom piece in this series covers it in detail.) What This Builds Over Time The economic properties of embedded provenance compound differently from settlement infrastructure. Settlement infrastructure competes primarily on network effects and interoperability, which is why Google’s Agent Payments Protocol is already functioning as a neutral bridge between Visa TAP, Mastercard Agent Pay, and Stripe ACP. When a neutral protocol layer successfully standardizes across competing networks, the underlying networks compress toward utility pricing. The visible scramble at the settlement layer is a signal: institutions racing hardest here understand the window to establish position is limited. Embedded evidentiary infrastructure accumulates rather than competes. An enterprise operating autonomous systems inside a provenance framework builds governance history, contractual defensibility, and institutional trust directly inside the execution layer. Over time, replacing that infrastructure means disrupting the continuity of the evidentiary record accumulated across years of autonomous activity. Institutional network effects operate through recognition: a provenance framework accepted by enterprises, regulators, insurers, and courts becomes more valuable with every additional institutional participant that treats its records as authoritative, and more costly to operate outside. That is historically very difficult to replicate once established. The organizations that begin this accumulation earliest will find themselves, in three to five years, holding something their competitors cannot manufacture on any shorter timeline: a verified history of having operated with integrity, proven by mathematics rather than claimed by assertion. There is a larger structural shift implicit in this. For most of the history of digital commerce, execution, payment, authorization, and evidence were separate operational layers, each managed by different infrastructure, reconciled after the fact, and governed by different institutional agreements. Autonomous systems place pressure on that separation because execution chains propagate faster than reconciliation systems can economically follow. The direction the market is moving, whether or not any single company named in this piece intended it, is toward a single atomic object: a transaction that carries its own payment, its own authorization proof, and its own independently verifiable execution record as intrinsic properties, not attached layers. Settlement and evidence become the same operation. The cost of institutional trust stops scaling with the volume of autonomous activity because trust is no longer assembled after the fact. It travels with the act itself. Why the Pressure Is Arriving Now This convergence is not being driven by ideology or protocol preference. It is being driven by economics and timeline. Autonomous systems increase execution volume faster than institutions can increase human verification capacity, Catalini’s diverging cost curves, playing out in real deployments. Cross-system agent workflows are multiplying the frequency of execution that crosses organizational and jurisdictional boundaries. Regulatory frameworks in multiple jurisdictions are simultaneously tightening liability for AI-generated outcomes. And insurance markets, which price risk on the basis of what can be independently reconstructed, are beginning to price the absence of portable provenance directly into coverage terms and exclusions. These pressures are not arriving sequentially. They are arriving together, compressing the timeline between “nice to have” and “operationally required.” The organizations building evidentiary infrastructure now are not ahead of the market, they are at the edge of a window that is closing as each liability event, each regulatory deadline, and each discovery dispute makes the cost of not having built it more legible. Whether portable provenance becomes broadly authoritative will depend not only on cryptographic validity but on whether insurers, regulators, courts, and counterparties converge on treating independently verifiable execution records as operationally preferable to institution-bound attestations. That convergence does not happen automatically, it happens through the accumulation of cases, precedents, underwriting decisions, and procurement mandates that make the alternative increasingly costly. The organizations that have already built this infrastructure when that convergence arrives will be the ones that shaped it. The Closing Condition McKinsey’s 2026 AI Trust Maturity Survey found that only around 30 percent of organizations reached maturity level three or higher on agentic AI governance and controls. Microsoft’s Cyber Pulse report found that 80 percent of Fortune 500 companies have active AI agents embedded in production workflows. The gap between those two numbers is an infrastructure problem that policies and training programs cannot close. The organizations treating verification as a compliance checkbox added afterward are accumulating liability their current metrics cannot see. The feedback lag hasn’t expired yet. When it does, through a regulatory investigation, an insurance dispute, or a commercial litigation that requires reconstructing an execution chain that was never built to be reconstructed, the gap between having evidentiary infrastructure and not having it will be difficult to close quickly. The question for enterprise leaders has shifted from which AI can we deploy to what can we prove, and to whom. The answer requires infrastructure where verification is a property of the transaction itself, not a reporting layer attached after the fact, not a certification captured at deployment, not a log held by the same system that acted. For most of institutional history, the authoritative record of what occurred was maintained by an institution separate from the occurrence itself. That architecture assumed the separation was sustainable, that execution and evidence could remain distinct layers, reconciled afterward, governed by whoever held the ledger. Autonomous systems operating across fragmented environments, at machine speed, under adversarial conditions, dissolve that assumption. The transaction that cannot produce its own independently verifiable record of itself becomes a liability rather than an asset, to its deployer, its counterparties, its insurers, and ultimately to every institution that inherits its consequences. The title of this piece is not a metaphor. It is the architectural condition that autonomous systems are forcing into existence. When the transaction becomes the record, the question of institutional trust stops being about who holds the ledger. It becomes about whether the ledger can be held at all, outside any single institution’s authority, across any boundary, under any condition. That is the infrastructure the agent economy is building toward. The organizations that understand this early enough to build accordingly will not merely be compliant. They will be the ones that defined what compliance means. References Catalini, C., Hui, X. & Wu, J. — “Some Simple Economics of AGI.” arXiv:2602.20946 (February 2026). Khan, R., Joyce, D. & Habiba, M. — “AGENTSAFE: A Unified Framework for Ethical Assurance and Governance in Agentic AI.” arXiv:2512.03180 (December 2025). Molina-Jimenez, C., Toliver, D., Nakib, H.D. & Crowcroft, J. — Fair Exchange: Theory and Practice of Digital Belongings. World Scientific (2024). Coward, K. & Toliver, D.R. — “Simple Rigs Hold Fast.” arXiv:2208.13617 (2022). Coward, K., Toliver, D.R., Gravitis, A. et al. — “Rigging Specifications.” T.R.I.E., v0.9876 (January 2023). Clifford Chance — “Agentic AI: The Liability Gap Your Contracts May Not Cover.” (February 2026). IMF Policy Note — “How Agentic AI Will Reshape Payments.” Davidovic & Tourpe (April 2026). California Assembly Bill 316 (effective January 1, 2026). EU Product Liability Directive 2024/2853 (member-state implementation deadline December 2026). Estate of Gene B. Lokken v. UnitedHealth Group, Case 0:23-cv-03514-JRT-SGE. McKinsey & Company — “State of AI Trust in 2026.” (March 2026). Microsoft Cyber Pulse — “80% of Fortune 500 Use Active AI Agents.” (February 2026). Moffatt v. Air Canada, 2024 BCCRT 149. --- # Settlement Without Proof URL: https://www.qatom.ai/articles/settlement-without-proof Author: Susana Khan Published: May 19, 2026 On provenance, accountability, and the infrastructure gap beneath autonomous execution Recent analysis from writers including Melody Koh have mapped the competitive geometry of the emerging agent web clearly: who controls supply, whether orchestration can be re-aggregated, and which incumbents risk tolling themselves out of relevance. Those are the right questions for the current moment. But there is a layer missing from the stack, one the industry is treating as a compliance problem rather than an infrastructure problem, and it is the layer that determines whether everything built on top of it holds. I examined the first signs of this gap in an earlier piece, You Cannot Audit a Probability: The Agentic AI Trust Wall. What has become clearer since is how structural the problem actually is. The Agent Web Has a Missing Layer The frameworks being written about this transition are largely correct. The disruption is real, the competitive logic is sound, and the companies being named, as either disintermediators or displaced, are generally the right ones. What they miss is a category shift happening underneath all of it. You Cannot Audit a Probability examined why probabilistic systems become difficult to govern once they produce consequential outputs. The agent web extends that problem from decision support into autonomous execution itself. The earlier piece was about model epistemology. This one is about infrastructure consequences. When Routing Becomes Execution For two decades, digital power was organized around discovery and aggregation. The interface between intent and selection was where control lived: search, feeds, platforms, marketplaces. The critical question was always who routes demand. Agents change that. Not incrementally. Categorically. When an agent recommends a hotel, the old logic applies. Someone still selects. There is still a human at the moment of consequence, and the system is accountable through that human. When an agent books the hotel, the category changes. The bottleneck is no longer routing; it is whether that action can be trusted, verified, and accounted for afterward, across systems that did not observe the decision process themselves. Agents have become a new kind of actor, one that initiates, executes, and settles across multiple systems, often without a human in the loop at the moment things go wrong. Once intent no longer requires selection, the system reorganizes, away from distribution and toward the integrity of autonomous execution. And integrity, at that level, requires infrastructure that does not yet exist at scale. The Tollgate Incumbents Are Solving the Wrong Problem SAP, ServiceNow, Workday: the major enterprise incumbents are choosing between two postures right now. ServiceNow introduced Action Fabric at Knowledge 2026, opening its platform to external AI agents via a generally available MCP server. JPMorgan analyst, Mark Murphy, described the action-based consumption pricing as effectively a tax on customers using outside AI agents to interact with data they already store in ServiceNow’s apps. SAP published API Policy v4/2026 in April, prohibiting third-party AI agents from autonomously sequencing calls outside SAP-approved architectures, drawing immediate pushback from partners who called it lock-in, even as CEO Christian Klein sought to soften the message on the Q1 investor call. Workday has similarly foregrounded the financial upside of monetizing agent access. This strategy is historically difficult to sustain once orchestration becomes portable. Tollgate incumbents signal their own vulnerability the moment they impose friction on autonomous orchestration. Enterprises charged enough for agent access eventually begin routing around the gate. That is the pattern of digital aggregation markets, and nothing about the current moment suggests it breaks here. But the deeper issue runs underneath the question of discovery control. Their strategy solves orchestration control before solving evidentiary trust, and those are different problems on different timelines. Once agents execute autonomously across systems, somebody must be able to prove what occurred. Reconstruction after the fact is insufficient. The relevant standard is evidentiary integrity under adversarial scrutiny: the proof a court, regulator, auditor, insurer, or counterparty would demand once autonomous systems generate real financial and operational consequences. The tollgate incumbents are unprepared for that question, and so, yet, are most of the disintermediators moving to replace them. Settlement Is Not Verification The Universal Commerce Protocol, co-developed by Google and Shopify and announced in January 2026 at the National Retail Federation conference, is probably the single clearest expression of where the market is heading. Backed by Walmart, Target, Etsy, and Wayfair as co-developers, and endorsed by more than twenty partners including Visa, Mastercard, and Stripe, UCP attempts to standardize how agents discover, negotiate, and execute transactions across merchant systems: agent-mediated discovery, agent-mediated checkout, machine-readable commerce negotiation, interoperable execution flows. It is the beginning of protocolized agent commerce infrastructure, and it formalizes a premise the market has now accepted: that agents are becoming transactional actors, not just recommendation systems. Shopify was always merchant infrastructure rather than a consumer destination. Extending headless commerce into agentic commerce is evolutionary rather than disruptive to its identity. Google’s position is equally legible: if agents operate through Gemini and merchants speak UCP, then Google Pay becomes the credential and settlement layer underneath agent-mediated commerce. Settlement and verification are different problems, and UCP solves only one of them. Protocols like UCP, x402, and AWS AgentCore Payments address transactional execution between systems. They solve real and important parts of the payment coordination problem. What they leave untouched is the verification problem, which becomes increasingly consequential as agents interact recursively across organizational and protocol boundaries, each one inheriting the state produced by the last. As Christian Catalini and others have argued, cryptographic coordination systems become economically relevant when they reduce the coordination costs of establishing trust across parties that cannot rely on a single shared intermediary (see Built Before It Was Named). UCP solves coordination; trust remains unaddressed. OpenAI’s Instant Checkout illustrated the difficulty directly. Operational issues reportedly included near-zero conversion rates, weak fraud infrastructure, sales tax complications, and merchant onboarding friction. Reading these as product immaturity misses the structural point: when the agent’s account of system state becomes the only account of system state, errors propagate in ways that surrounding infrastructure cannot reliably adjudicate afterward. The operative question is who bears liability when autonomous execution is based on stale state, incorrect inventory, misinterpreted instructions, or records generated by the same probabilistic engine that performed the action. Clifford Chance’s analysis of agentic AI contracts found that under most current technology agreements, if an agent incorrectly authorizes a payment or misprices a product, suppliers’ standard disclaimers typically leave the customer holding liability for a system they did not design and cannot fully audit. The contractual framework wipes out meaningful recovery precisely when the stakes are highest. This Does Not Stay Contained The trust problem remains underestimated because agent infrastructure is still mentally divided into two categories: lightweight consumer systems and serious institutional systems. The assumption is that provenance, deterministic guarantees, and verifiable execution only matter once agents enter regulated domains, finance, healthcare, enterprise procurement. That distinction will not hold. The systems that contributed to the 2008 financial crisis were initially treated as distributed, localized, statistically manageable components of a larger market. The systemic risk emerged once interconnectedness, opacity, leverage, automation, and cascading dependencies reached sufficient scale. Nobody designed for systemic fragility. It emerged from composition. Agent systems are beginning to evolve along structurally similar lines. One hallucinated purchase or failed booking is containable. The deeper risk is recursive interaction between autonomous systems: agents consuming outputs from other agents, probabilistic state propagating across execution environments, unverifiable actions becoming composable infrastructure beneath larger systems. Once that occurs, low-trust domains stop remaining isolated. What began as a consumer-facing reliability problem becomes load-bearing infrastructure for decisions with real financial and legal consequences. Aggregators centralized demand. Agent systems decentralize execution. But decentralized execution without verifiable state eventually recreates systemic fragility at machine speed. McKinsey’s 2026 AI Trust Maturity Survey, drawing on approximately 500 organizations across industries and regions, found that only around 30 percent reached a maturity level of three or higher on agentic AI governance and controls. Separately, Microsoft’s Cyber Pulse report found that 80 percent of Fortune 500 companies now have active AI agents embedded in production workflows. The gap between those two figures is an infrastructure problem, one that policies and frameworks cannot close on their own, and that better training programs will not fix. The emerging field of governed execution research reflects the same recognition from a different direction. Academic work on provenance systems for autonomous agents, proof-derived authorization architectures, and accountable multi-agent governance is converging independently on the same missing property: verifiable autonomous execution. When academic institutions, regulatory bodies, and enterprise deployments begin arriving at the same structural deficiency from different starting points, that convergence is signal, not coincidence. What Serious Deployments Already Know Gondola is a travel AI agent that books end-to-end itineraries autonomously: flights, hotels, transfers, dining reservations, coordinating across multiple provider systems in a single execution flow. It is one of the more complete examples of agentic commerce operating at production scale. What made Gondola work was something less visible than the orchestration layer: the record of what the agent did had to be legible and authoritative to every downstream participant in the transaction chain, hotel reservation systems, airline databases, loyalty programs, payment processors, and the customer, none of whom were present when the agent made its decisions. Marriott awards loyalty points because Gondola’s bookings are recognized by downstream hotel systems as valid direct reservations eligible for loyalty accrual. That recognition depends on transaction records that can move reliably across multiple systems, hotel reservation infrastructure, payment systems, loyalty databases, and customer accounts, while preserving enough integrity for parties who never observed the original transaction to treat the resulting state as authoritative. This is the pattern that separates serious agent deployments from impressive demos. Discovery is difficult but tractable. Payment execution is attracting multiple well-capitalized efforts. The foundational problem that keeps getting deferred is producing a record of autonomous execution that remains trustworthy to systems and institutions that were never present for it. As McKinsey Partner Rich Isenberg put it: “Agency isn’t a feature, it’s a transfer of decision rights. The question shifts from ‘Is the model accurate?’ to ‘Who is accountable when the system acts?’” Liability, in other words, is becoming a technical problem: specifically, whether system state can be independently verified at the moment a claim is made against it. Policy cannot substitute for infrastructure. Without portable provenance, downstream systems would have no reliable way to distinguish between a valid autonomous booking flow and an unverifiable synthetic transaction narrative generated after execution. A log generated after the fact by the same system that acted answers nothing. The Legal Timeline Is Not Waiting The IMF recently named the underlying structural tension: payment systems require deterministic execution and settlement finality, while agentic AI introduces probabilistic reasoning and non-deterministic execution paths. Separating AI orchestration from deterministic settlement is a coherent first step, but insufficient on its own, because even with deterministic settlement, the surrounding record may remain probabilistic, generated after execution by the same system that executed, coherent in narrative but independently unverifiable in fact. That distinction matters acutely once systems become adversarial. Litigation involving UnitedHealth demonstrates the issue in real time. The legal question cuts deeper than whether an AI-assisted decision occurred; organizations must prove, under scrutiny, that the records surrounding those decisions are accurate, complete, and independently verifiable, and produce that proof without relying on the AI system’s own account of itself. The regulatory landscape is tightening on multiple fronts, though unevenly. California’s AB 316, which took effect January 1, 2026, forecloses the autonomous-harm defense: developers, modifiers, and users of AI systems can no longer argue that the AI acted independently as a shield against civil liability. Colorado’s original AI Act, which would have required annual impact assessments for high-risk systems by June 2026, has been stayed by a federal court and substantially replaced by the legislature; its successor, if signed, takes effect January 1, 2027, under a narrower framework. The EU Product Liability Directive classifies AI software as a product subject to strict liability, with member-state implementation deadlines in December 2026. The direction of travel across jurisdictions is consistent even where individual timelines shift. There is also a geopolitical dimension beginning to emerge. Economies that cannot independently verify autonomous machine execution may find themselves structurally dependent on foreign orchestration layers, a sovereignty problem dressed as a technical one. Cross-jurisdiction verification, sovereign execution infrastructure, and regulatory interoperability are not yet central to the agent web conversation. Once autonomous systems begin mediating financial, commercial, and governmental coordination at scale, they will be impossible to avoid. These are current exposures being accumulated, on a timeline that is not synchronized with most organizations’ infrastructure roadmaps. The Architecture the Market Is Converging On The verification problem has a structural solution, and its shape is becoming clearer as the failures accumulate. The key insight is this: a record generated separately from an action, and stored separately from an action, can always be questioned. It can be lost, altered, reconstructed, or simply wrong. A record bound cryptographically to the action at the moment of execution, one that travels with the transaction the way a bearer instrument travels with value, cannot be reconstructed after the fact, because it was never separate to begin with. This is the architectural direction that serious provenance infrastructure takes. Rather than logging what an agent did and storing that log somewhere retrievable, the proof of what occurred becomes a structural property of the transaction itself. Any party can verify it independently. No intermediary needs to be trusted. No reconstruction is required, because nothing was ever separated. The practical consequence is that compliance stops being a reporting layer bolted onto an execution system. It becomes a property of the execution itself, present at every transaction, verifiable by any counterparty, portable across the systems that need to trust it. Settlement and verifiable record become the same operation rather than two operations that must be reconciled. The emergence of companies focused specifically on agent governance, policy enforcement, and execution accountability signals that the market is beginning to recognize this gap. Orchestration alone is insufficient once agents begin operating across institutional boundaries. That recognition is still early; the infrastructure buildout that follows it will move fast. This is where the market for agentic infrastructure is converging, not because any single company has made it so, but because the failures accumulating across agent deployments all point to the same missing property. A small but growing set of infrastructure efforts is beginning to converge on this problem from different directions: verifiable state transfer, portable provenance, governed execution, and cryptographically attestable coordination across systems. TODAQ through Qatom, is building this layer around execution-bound cryptographic proof designed for the phase of the agent web that follows autonomous execution at scale The Missing Layer The discovery layer is being built. The payment execution layer is being built. Beneath both of them is a layer the agent web has not yet fully recognized as infrastructure: the systems that make autonomous execution independently verifiable, portable across institutions, and resilient under adversarial scrutiny. The problem is not observability. It is evidentiary integrity. A log generated after the fact by the same system that acted cannot serve as the foundation for financial coordination, institutional accountability, or autonomous commerce at scale. As agents begin operating across organizational and jurisdictional boundaries, every consequential action eventually collapses into the same question: Not simply what did the agent do, but can the system prove it independently of the agent’s own account of itself? That requirement changes the architecture of the stack beneath autonomous execution. Verification stops being a reporting layer attached afterward and becomes a property of the transaction itself: portable, attestable, and durable across the systems that inherit its state. This is the layer the market is beginning to converge toward, not because regulation demands it or because companies prefer it, but because autonomous systems operating without verifiable state eventually become ungovernable. The organizations that recognize trust as infrastructure will help define the next phase of the agent web. The ones that continue treating it as compliance will discover the distinction too late. References and Notes - California Assembly Bill 316 (2026, January 1). Amends California Civil Code § 1714.46, prohibiting autonomous-harm defenses in civil actions involving AI systems. Baker Botts. (2026, January). California eliminates the ‘autonomous AI’ defense. https://ourtake.bakerbotts.com/post/102m29i/california-eliminates-the-autonomous-ai-defense-what-ab-316-means-for-ai-deplo - Catalini, C. (2026, February 24). Some simple economics of AGI (MIT Sloan Research Paper). https://papers.ssrn.com/sol3/papers.cfm?abstract_id=6298838 Referenced in the context of cryptographic coordination systems and the economics of trust across parties without shared intermediaries. - Clifford Chance. (2026, February 10). Agentic AI: The liability gap your contracts may not cover. https://www.cliffordchance.com/insights/resources/blogs/talking-tech/en/articles/2026/02/agentic-ai-and-the-liability-gap-your-contracts-may-not-cover.html Analysis of liability allocation in agentic AI contracts and how standard technology agreement disclaimers interact with autonomous execution failures. - Colorado AI legislation update. (2026). SB 24-205 (original Colorado AI Act) stayed by federal court (April 27, 2026); replaced by SB 189 (passed May 2026, effective January 1, 2027 if signed). - Dignan, L. (2026, May 5). ServiceNow Knowledge 2026: AI Control Tower, Action Fabric, Autonomous Workforce and more. Constellation Research. https://www.constellationr.com/insights/news/servicenow-knowledge-2026-ai-control-tower-action-fabric-autonomous-workforce-and - European Union. (2024). Product Liability Directive (classifies AI software as a product subject to strict liability). Member-state implementation deadline: December 2026. - Gondola AI. (n.d.). Production travel agent coordinating multi-system autonomous bookings (case study in provenance infrastructure requirements). https://www.gondola.ai/ - International Monetary Fund. (2025–2026). Analysis of structural tensions between deterministic payment settlement and probabilistic AI execution paths. - Koh, M. (2026, May 13). How the agent web gets built: Why incumbents will toll themselves out of relevance. Ground Truth. Foundational analysis of agent-driven disintermediation, orchestration portability, and tollgate incumbent dynamics. This essay builds on Koh’s competitive framework while examining the unresolved verification and provenance layer beneath autonomous execution. - McKinsey & Company. (2026, March). State of AI trust in 2026: Shifting to the agentic era. https://www.mckinsey.com/capabilities/tech-and-ai/our-insights/tech-forward/state-of-ai-trust-in-2026-shifting-to-the-agentic-era (Survey of ~500 organizations; ~30% reached maturity level 3+ on agentic AI governance and controls.) - Microsoft. (2026, February). 80% of Fortune 500 use active AI Agents. Microsoft Security Blog. https://www.microsoft.com/en-us/security/blog/2026/02/10/80-of-fortune-500-use-active-ai-agents-observability-governance-and-security-shape-the-new-frontier/ - OpenAI Instant Checkout. (2025–2026). Reported operational challenges including near-zero conversion rates, fraud infrastructure gaps, sales tax complications, and merchant onboarding friction. - Rich Isenberg (McKinsey Partner). (2026). Comments on accountability implications of agentic AI. - SAP API Policy v4/2026. (2026, April). AI clause reported in: “AI clause in new SAP API policy provokes lock-in concern,” The Register. Waehner, K. (2026, May 2). Data ownership in the age of agentic AI: Why SAP’s API policy forces a data integration reckoning for every enterprise. https://www.kai-waehner.de/blog/2026/05/02/data-ownership-in-the-age-of-agentic-ai-why-saps-api-policy-forces-a-data-integration-reckoning-for-every-enterprise/ - ServiceNow. (2026, May 5). ServiceNow opens its full system of action to every AI Agent in the enterprise. ServiceNow Newsroom. https://newsroom.servicenow.com/press-releases/details/2026/ServiceNow-opens-its-full-system-of-action-to-every-AI-Agent-in-the-enterprise/default.aspx Mark Murphy quote/analysis on action-based pricing: “ServiceNow, SAP and Workday Make AI Agents Pay to Play,” PYMNTS.com (May 2026). https://www.pymnts.com/artificial-intelligence-2/2026/servicenow-sap-and-workday-make-ai-agents-pay-to-play/ - UnitedHealth Group litigation. (2024–2026). Ongoing litigation and regulatory scrutiny regarding use of AI in coverage decisions. - Universal Commerce Protocol (UCP). (2026, January 11). Announced at National Retail Federation conference. Co-developers: Google, Shopify, Walmart, Target, Etsy, Wayfair. Google Developers Blog (2026, January). Under the Hood: Universal Commerce Protocol (UCP). Shopify Engineering (2026). Building the Universal Commerce Protocol. Further reading: Ground TruthHow the Agent Web Gets BuiltRead on melodykoh.substack.comTODAQ PressYou Cannot Audit a Probability: The Agentic AI Trust WallRead the essayTODAQ PressThe Agent Economy Just Got Its First Native Currency Rail. It’s Called Qatom.Read the essayTODAQ PressThe Payment Layer for the AI EconomyRead the essay --- # You Cannot Audit a Probability: The Agentic AI Trust Wall URL: https://www.qatom.ai/articles/you-cannot-audit-a-probability-the Author: Susana Khan Published: May 12, 2026 The agentic AI market is sorting itself out. What the mature version requires is different from what the demo version assumed. News peg: The IMF’s agentic payments policy note (April 24, 2026) and Amazon’s AgentCore Payments launch (May 7, 2026). On May 11th, a developer with 40+ production agent deployments posted in r/AI_Agents: “Stop building AI agents.” It hit 376 upvotes. The comments were full of people who learned the same lesson the hard way. Agents hallucinate. They resist auditing. And in regulated industries, that’s becoming a legal liability. The AI agent market is maturing, and maturation is uncomfortable. The gap between what agents do in demos and what they do in production has become impossible to ignore, and the developers closest to the problem are saying so out loud. On May 11th, the top post on r/AI_Agents, from a developer with over 40 production deployments, put it plainly: stop building AI agents. Automations outperform agents in production. Agents hallucinate, resist auditing, and collapse on unexpected inputs. In regulated industries, compliance reviewers need deterministic audit trails. Autonomous black boxes fail that requirement. The post drew 376 upvotes and a thread full of agreement from people who had learned the same thing the hard way. This is not a fringe opinion. Surveys of teams running agents in production show 60% operating with no formal governance framework. Thousands of applications have leaked sensitive data because agentic systems shipped without deterministic audit infrastructure underneath them. Y Combinator’s current Request for Startups names agents with audit trails, deterministic behavior, and compliance capabilities as explicit investment priorities, which is the VC tier funding around a failure mode they are watching play out in real time. The market is converging on a conclusion: the winners will be builders who ship reliable automations with proper guardrails, not the loudest agentic demos. Why Auditability Is Harder Than It Looks The production problems are not all unsolvable. Structured outputs, function calling, evaluation harnesses, and hybrid architectures that wrap LLM reasoning inside deterministic workflows have all made agents meaningfully more reliable. These approaches work, and teams shipping in regulated industries are using them. The harder problem is what happens to the record of what occurred. When an LLM-orchestrated agent produces a log of its actions, that log is itself a language model output: a reconstruction, produced by the same probabilistic engine that executed the action. It can be internally consistent, confidently written, and factually wrong. Better reliability practices reduce the frequency of errors; they do not change the nature of the record. The IMF’s recent policy framework gestured at this without quite landing on it. It proposed separating probabilistic AI decision-making from deterministic payment execution, which is a sound instinct. But the framework assumes that once execution happens, the record of what happened is trustworthy enough to trace backward through. That assumption is where it gets complicated. AWS’s AgentCore Payments infrastructure, launched in preview this month, stores logs in CloudWatch: whatever the agent reports, observable but not independently verified. Trusted Execution Environments address part of this. TEEs are hardware-isolated compute regions where remote attestation can cryptographically prove which model ran against which input. That closes a real gap: you can verify the execution environment was not tampered with. What TEE attestation does not cover is whether the log the model generated faithfully represents the sequence of decisions across a multi-step workflow. The hardware integrity is provable; the semantic accuracy of the record is not. This is the specific gap that structured outputs and better observability tooling do not reach. It is not an argument that those approaches are inadequate for most purposes. It is an argument that for regulated industries where the log is evidence, the reconstruction problem is still open. What the Correction Selects For MIT economist Christian Catalini, writing independently in Some Simple Economics of AGI, identifies verification-grade infrastructure as the foundational requirement of the agentic economy: systems where agent actions produce receipts that travel with the data, verifiable by any party. When that infrastructure is absent, agents exploit the gap between what is measured and what was intended. The endgame is legal and financial accountability; agent outputs that can be defended, insured, adjudicated. The legal pressure is already arriving. A class action alleging UnitedHealth’s AI model had a 90% error rate on appealed claim denials is in federal discovery, with tens of thousands of internal documents being produced. The 90% figure is an allegation, not an adjudicated finding, and UnitedHealth disputes it. But the shape of the case is instructive regardless of outcome: logs existed, assembled after the fact from records that did not travel with the decisions, and a court order was required to surface them. The question is not whether logs exist. It is whether they are accurate and whether the organization can prove it. The EU Product Liability Directive classifies AI as a product subject to strict liability, effective December 2026. Gartner tracks AI governance platform spending reaching roughly $500 million in 2026, rising steeply as regulatory pressure increases. The organizations that will navigate this cleanly are the ones that built for auditability before it became a legal requirement, not after. What Verifiable Infrastructure Actually Requires Solving the reconstruction problem means removing the reconstruction step. The record of what happened needs to be bound to the transaction at the moment of execution, before any language model generates a summary of it. Several architectural approaches point in this direction: deterministic workflow engines that log at the infrastructure layer rather than the application layer, blockchain-based ledgers where transaction records are independently verifiable, and cryptographic provenance systems where proof of what occurred travels with the asset itself rather than being stored separately. The TODA-file protocol takes the last approach. Provenance is bound at execution and verifiable by any party with no intermediary. The formal proof underlying the protocol, published by researchers at Cambridge’s Centre for Redecentralisation, uses structural induction to demonstrate that double-spend is not merely unlikely but excluded by the system’s structure. That is a meaningful property for regulated use cases where the audit trail needs to hold up under legal scrutiny rather than just operational review. We are a small operation, for now, relative to the infrastructure being built around x402 and AgentCore. Volume today is thousands of transactions per day against x402’s aggregated 169 million. We note that not because the comparison favors us, but because the question worth asking of any agentic payment infrastructure is not just how much it has processed, but what it can prove about each transaction when asked. That question will become harder to avoid as the UnitedHealth discovery process continues and the EU Product Liability Directive takes effect in December. The organizations positioned to answer it will be the ones that treated auditability as a design requirement rather than a compliance checkbox added afterward. Sources - IMF Policy Note, How Agentic AI Will Reshape Payments, Sonja Davidovic and Hervé Tourpe, April 24, 2026. - Amazon Web Services, Agents That Transact: Introducing Amazon Bedrock AgentCore Payments, May 7, 2026. Launched in preview. - x402 Foundation / Linux Foundation press release, April 2, 2026. By May 7, 2026 (per Coinbase): 69,000 active agents, 169 million transactions. - Estate of Gene B. Lokken v. UnitedHealth Group, Case 0:23-cv-03514-JRT-SGE. The 90% error rate is an allegation in the plaintiff complaint, not an adjudicated finding. UnitedHealth disputes the characterization. - Gartner AI governance platform spending figures, 2026. Gartner projects the market reaching approximately $492 million in 2026, growing toward $1 billion by 2030, driven by regulatory requirements. [Available via Gartner subscription.] - EU Product Liability Directive (2024/2853): implementation by December 9, 2026; includes AI software as a “product” subject to strict liability. - TODA Rigs Architecture, Formal Proof, Cambridge University CRDC. Kris Coward and Dann Toliver, co-authors of Rigging Specifications (T.R.I.E., 2023). - Catalini, Hui & Wu, Some Simple Economics of AGI, 2025. - r/AI_Agents, May 11, 2026. Top post (376 upvotes): “Stop Building AI Agents.” - On TEEs and LLM attestation: OLLM (Trusted Execution Environments in Confidential AI, 2026); Attestable Audits (Verifiable AI Safety Benchmarks Using Trusted Execution Environments, arXiv 2025). Prior posts in this series: - Built Before It Was Named - An MIT Economist Just Named the Gap - Everyone’s Building AI Agents — Nobody’s Solved This - The Payment Layer for the AI Economy --- # The Agent Economy Just Got Its First Native Currency Rail. It’s Called Qatom. URL: https://www.qatom.ai/articles/the-agent-economy-just-got-its-first Author: Susana Khan and TODAQ Press Published: April 30, 2026 MCP solved how agents talk to tools. Qatom solves how they pay for them. There’s a moment in every infrastructure cycle when the thing everyone said was coming actually arrives. Not as a roadmap slide or a whitepaper. As a tool you can install. That moment is now. The conversations we’ve been tracking, and in some cases, seeding over the past several months have all pointed at the same structural gap. AI agents are executing at machine speed. They’re calling dozens of services per task, making purchasing decisions autonomously, and chaining outputs across providers without a human in the loop. The compute infrastructure for this is largely in place. The model capability is moving fast. What wasn’t in place, until now, was the payment layer that makes agent-to-agent commerce actually work. We built that layer. We called it TAPP. We’ve been running it in production since 2023, and we’ve written about why it matters for AI companies, for creators, for the economics of microtransactions that legacy rails make structurally impossible. What we hadn’t done was give it a front door that any developer, any agent runtime, any MCP-compatible tool chain could walk through in three steps. That’s Qatom. The Standard That Made This Possible Agentic AI tooling has, in the last twelve months, begun converging on a standard. The Model Context Protocol (MCP) has become the lingua franca of how agents discover and call external tools. If you’re building agents in 2026, you’re either already building on MCP or you’re about to be. The ecosystem is moving fast and it’s moving in one direction. MCP solved a real problem: a standard interface so agents can talk to tools without bespoke integration work at every junction. What it didn’t solve, what no one in that ecosystem had solved, is how agents pay for what they call. The attempts have been visible to anyone building in the space. Legacy rails charge 2.9% plus $0.30 on transactions that might be worth three cents and settle days after the service was consumed. From the crypto side, x402, Coinbase’s protocol reviving HTTP’s 402 status code for stablecoin payments, diagnosed the problem correctly and moved fast. But it was built for crypto-native operators, and the enterprises, AI companies, and commercial API providers who run on commercial banking infrastructure and settle in dollars are not its constituency. Qatom is the MCP server that adds the missing primitive: an agent that can pay. No crypto wallet required. No gas. No facilitator sitting between the payment and the settlement. USD, settled in flight, on TODA underneath. What It Actually Does The architecture is worth understanding, because the design choices matter. Payment in Qatom travels inside the HTTP request itself, a header attached to the API call, settled between counterparties before the response comes back. No callback. No webhook. No reconciliation cycle. The response either arrives paid or it doesn’t arrive. This is the vending machine model we’ve been describing since February, finally expressed as a working MCP primitive: insert payment, receive service, atomically, with no intermediary absorbing margin at every hop. Underneath that interface is the TODA stack, the same cryptographic infrastructure we’ve been describing since the Built Before It Was Named piece. File-based digital bearer assets, not balances. USD-TDN files that behave like physical cash: portable, self-verifying, carrying their own proof of provenance without depending on any central ledger. No blockchain. No gas. No volatility. Settlement in milliseconds between Twins, with bank rails connected for funding and payout in dollars where it counts. For a developer or an enterprise AI team, the practical picture looks like this. Your agent gets a wallet. It can check its own balance as a standard MCP tool call. It can discover paywalled APIs in a live marketplace headless catalog, priced per call, not per month. It can pay for what it uses in the same request that calls the tool. And if you’re providing a service, you can register any HTTP API as a payable tool through chat or REST, set your price per call, and define how revenue splits across however many parties share in the value, up to two hundred payees per payout, settled atomically at the moment the call clears. The fee across all of this is zero. That’s the architecture at work, not a promotional offer, when you remove the intermediary chain that legacy rails require, zero fees is what the math produces. That’s what the infrastructure does. The question worth sitting with is why the window to build on it is shorter than most people currently assume. Why the Window Is Narrow The MCP ecosystem is still early enough that the payment primitive it adopts will become load-bearing infrastructure. The standard that wins here doesn’t just win a product category. It becomes the default assumption baked into every agent runtime, every tool provider, every enterprise deployment that gets built on top. The history of infrastructure is the history of defaults. Whoever built the card rails didn’t make news in proportion to their eventual importance. AWS launched in 2006 and was considered a developer curiosity. The window to build a position in a new infrastructure layer is narrow, and it closes when the incumbents get entrenched. That window is why the architectural gaps in what already exists matter now, not later. Demonstrating real traction and demand, x402 has processed over 100 million payments in its first six months. But a formal analysis published this year by researchers across Peking University, Shanghai Jiao Tong University, and Zhongguancun Laboratory (Li et al., “A402,” arXiv 2603.01179) documented structural flaws that x402 v2 left unresolved. Service providers must execute requests before payment confirms on-chain, meaning they absorb non-payment risk on every call. And because end-to-end latency is bounded by blockchain confirmation time, high-frequency interaction is structurally impractical; on-chain fees make fine-grained micropayments economically unviable at volume. The cumulative effect is measurable: an agent retrieving data from 100 x402-protected APIs accumulates up to 110 seconds of payment overhead alone. There’s also a centralization problem that x402’s own community has been openly debating. Every payment routes through a single facilitator which, if compromised, can fabricate settlements or take down every x402-gated service by going offline, a single point of failure at the economic core of a protocol designed to eliminate intermediaries. And the relay model has no sustainable revenue mechanism at the protocol level: gas costs are currently absorbed as a Coinbase subsidy with no path to protocol-level compensation. Every successful payment infrastructure in history has earned a return on the value it creates. x402’s relay layer, as currently built, does not. These are not edge cases to be optimized away. They are consequences of routing machine-speed commerce through a consensus mechanism designed for something else. Legacy rails face a different version of the same problem. They’re wired into commercial banking and trusted by enterprises, but they were built for monthly human billing. Batching thousands of micropayments to reduce per-unit fees re-introduces settlement latency, requires reconciliation cycles, and still prices three-cent transactions into incoherence. Agents are transacting right now. One of our earliest AI service customers went from dozens of API calls per hour to multiple per minute sustained around the clock, not because a human was clicking, but because AI systems were calling other AI systems and making autonomous purchasing decisions in real time. We watched that happen in production. The volume was real. The payment infrastructure held because it was built for exactly this load. Qatom makes that accessible to every developer building agents today. The install is one line. Authentication is OIDC. The marketplace is live and dynamic. The agent that calls a tool is the agent that pays for it, in the same request, with no human required. For the Builders If you’re building agent workflows that call external APIs, code generation, data retrieval, model invocations, media synthesis, you’ve already encountered the friction. Either you’ve absorbed cost into a subscription that doesn’t match your actual usage pattern, or you’ve batched transactions to make unit economics tolerable, or you’ve simply priced the APIs you’d use out of scope because the fee structure made the math not work. The 63-cent workflow we described in February, script generation, voiceover, music, image generation, video rendering, five API calls, five providers, costs $1.64 in fees on legacy rails before any of those providers have seen a dollar. With Qatom, the fee is zero and the settlement is atomic. A three-cent transaction becomes economically viable. A tool you’d have built as a subscription becomes a pay-per-call service and earns from day one. That changes what’s worth building. The long tail of developer tools, data services, and specialized AI capabilities that never made sense as subscriptions, because no individual developer could justify the monthly commitment for occasional use, becomes a real market when the payment primitive supports it. For the Enterprises The Built Before It Was Named piece covered the governance dimension in detail. The short version: as enterprises deploy autonomous agents at scale, the question regulators, counterparties, and insurers are now asking is not whether agents executed, it’s whether you can prove what they did. The TODA architecture gives every transaction a cryptographic record that travels with it, verifiable by any party, dependent on no intermediary’s continued cooperation. That’s embedded in Qatom, not bolted on after. Every transaction that flows through Qatom carries the same provenance guarantees we described when we wrote about AGENTSAFE and the Catalini macroeconomic analysis. Settlement and verifiable record are the same atomic operation. Compliance becomes a property of the infrastructure rather than a layer added on top. For enterprise AI teams evaluating where to place a dependency, that sequencing is the relevant fact. What Comes Next Qatom ships today as a hosted MCP tool, compatible with any MCP-compatible agent harness; Claude, OpenClaw, Hermes, Codex, or whatever runtime your stack runs on. The marketplace is live. The wallet is live. The earning side, registering your API as a payable tool and collecting per-call revenue, are all live. The install is one line: clawhub install Qatom. Three steps to a wallet, a marketplace, and agents that can finally transact. We’ve spent years building infrastructure that nobody was asking for yet because the mathematics said it would be necessary. The mathematics was right. The moment it was describing is this one. Your agents can transact now. The rail is there. TODAQ Micro builds verification and payment infrastructure for AI Agents. Qatom is available now at qatom.ai and on GitHub at github.com/todaqmicro/openclaw. TODAQ - Technical documentation https://engineering.todaq.net/ To reach us: hello@todaq.net. References On the TODA / TAPP Infrastructure Molina-Jimenez, C., Toliver, D., Nakib, H.D. & Crowcroft, J. Fair Exchange: Theory and Practice of Digital Belongings. World Scientific, 2024. (Foundational research on the Fair Exchange dilemma; attestables; and proof that fairness can be a mathematical property of protocol architecture rather than a social or institutional one.) https://www.worldscientific.com/worldscibooks/10.1142/q0448 Coward, K. & Toliver, D.R. “Simple Rigs Hold Fast.” TODAQ / T.R.I.E., 2022. arXiv:2208.13617. (Cryptographic proof of Integrity-at-a-Distance and double-spend prevention via structural induction.) https://arxiv.org/abs/2208.13617 Coward, K., Toliver, D.R., Gravitis, A. et al. “Rigging Specifications.” TODAQ / T.R.I.E., v0.9876, January 2023. (Co-authored by CTO Adam Gravitis; defines the TODA file as a digital bearer instrument and specifies the Rigs architecture.) https://trie.site/rigging_specifications.pdf External Sources On Enterprise AI Governance and Macroeconomics Catalini, C., Hui, X. & Wu, J. “Some Simple Economics of AGI.” February 26, 2026. arXiv:2602.20946. (Source for the Measurability Gap; Counterfeit Utility; Trojan Horse Externality; False Confidence Trap; and the prescription that verification must be native to each transaction.) https://papers.ssrn.com/sol3/papers.cfm?abstract_id=6298838 Khan, R., Joyce, D. & Habiba, M. “AGENTSAFE: A Unified Framework for Ethical Assurance and Governance in Agentic AI.” IBM, December 2025. arXiv:2512.03180. (Source for the static guardrail problem and identification of cryptographic action provenance as the critical missing layer in enterprise AI governance.) https://arxiv.org/abs/2512.03180 On x402 Architecture and Limitations Reppel, E., Roscoe, C. & Nickerson, J. “Introducing x402 V2: Evolving the Standard for Internet-native Payments.” Coinbase Developer Platform / x402.org, December 11, 2025. (Primary source confirming x402 launch in May 2025; 100M+ payments in six months; v2 scope limited to multi-chain and SDK modularity with atomicity flaws unresolved.) https://www.x402.org/writing/x402-v2-launch Li, Y., Wang, L., Wang, K., Yang, Z., Wang, K., Guan, Z. & Gao, J. “A402: Binding Cryptocurrency Payments to Service Execution for Agentic Commerce.” Peking University / Shanghai Jiao Tong University / Zhongguancun Laboratory / Beijing Jiaotong University, 2026. arXiv:2603.01179. (Primary source for structural flaws in x402: L1 non-payment risk to service providers; L3 latency and cost limitations at scale. Also source for cumulative latency figures: 50–110s for 100-API agent, 25–55s for 50-source trading bot. Confirms flaws remain unresolved in x402 v2.) https://arxiv.org/abs/2603.01179 Stone, D. “The x402 Facilitator Problem: How to Remove the Centralized Trust Bottleneck.” Tangle, March 22, 2026. (Source for facilitator single-point-of-failure analysis: fabrication, censorship, and downtime failure modes; facilitator verifies and settles with zero cryptographic proof of correctness; no fallback or quorum mechanism.) https://tangle.tools/blog/decentralizing-x402-facilitator/ YQ “The X402 is great, but what are some of the hidden problems?” PANews / Jinse Finance, October 31, 2025. (Source for relay economics analysis: $0.0006 gas cost per transaction with no protocol-level compensation; two-phase settlement latency of 500–1100ms per single request; EIP-3009 exclusivity limiting compatibility with USDT and DAI.) https://www.panewslab.com/en/articles/87f007ff-f2c6-4b41-919d-24e26c295912 Matos, G. “What is x402? The HTTP-402 payments standard powering AI agents, explained.” CryptoSlate, December 18, 2025 (updated February 5, 2026). (Source for enterprise compliance burden framing: custodying keys, managing stablecoin balances, and compliance risk for agent fleets.) https://cryptoslate.com/what-is-x402-the-http-402-payments-standard-powering-ai-agents-explained/ Coinbase “Coinbase and Cloudflare Will Launch the x402 Foundation.” Coinbase Blog, September 23, 2025. (Source for x402 Foundation co-launch date, governance mission, and Cloudflare partnership.) https://www.coinbase.com/blog/coinbase-and-cloudflare-will-launch-x402-foundation Internal Sources TODAQ PressThe Payment Layer for the AI EconomyRead the essayKhan, S. “The Payment Layer for the AI Economy: How internet-native payments enable machines to transact.” TODAQ Press, February 18, 2026. (Source for the 63-cent AI workflow example; $1.64 in fees on legacy rails; 95%+ contribution margin validation; vending machine payment model; AI-to-AI transaction volume data; customer scaling from dozens of API calls per hour to multiple per minute.) TODAQ PressEveryone's Building AI Agents. Nobody's Figured Out How They Get Paid.Read the essayKhan, S. “Everyone’s Building AI Agents. Nobody’s Figured Out How They Get Paid.” TODAQ Press, February 28, 2026. (Source for batching-as-workaround critique; legacy rails analysis; x402 framing as crypto-native but wrong constituency; 95% cost reduction versus alternative rails; production evidence of machine-to-machine scaling.) TODAQ PressBuilt Before It Was NamedRead the essayKhan, S. — “Built Before It Was Named: MIT named it. IBM specified it. The proof was already done — and the infrastructure built on it is live.” TODAQ Press, March 15, 2026. (Source for TODA cryptographic architecture; Rigs papers; Fair Exchange framework; AGENTSAFE / IBM governance gap; Catalini macroeconomic analysis; enterprise provenance and verifiability requirements; TAPP commercial deployment since 2023.) --- # Built Before It Was Named URL: https://www.qatom.ai/articles/built-before-it-was-named Author: Susana Khan Published: March 15, 2026 MIT named it. IBM specified it. The proof was already done — and the infrastructure built on it is live. ENTERPRISE AI · GOVERNANCE · AGI · DEEP TECHNOLOGY · AI PAYMENTS · CRYPTOGRAPHIC INFRASTRUCTURE · Enterprise AI is executing faster than any organization can verify. That gap—between what agents do and what anyone can confirm they did—is now the subject of rigorous independent research across macroeconomics, computer science, and governance. Three research tracks arrived at the same infrastructure requirement from entirely different directions. Two identified it as the critical missing piece. One had already built it. This is that story — and why the convergence matters more than any of the three tracks alone. The contract processing system goes live on a Monday. By Friday, throughput is up forty percent. Unit costs are down. The operations team is fielding congratulations. Six weeks later, a routine audit surfaces something less comfortable: hundreds of contracts that were processed correctly by every measurable standard (correctly classified, routed, and priced) but contained a structural error the system was never trained to flag. The error, individually minor, has compounded across volume into a seven-figure liability exposure. The system did exactly what it was optimized to do. It had been optimized for the wrong thing. No individual acted in bad faith. No model malfunctioned. What was absent was any mechanism to confirm, in real time, whether what the system was optimizing for matched what the organization actually needed. By the time the gap became visible, the resources had been consumed. The output appeared productive. The utility was counterfeit. That scenario is hypothetical. What follows is not. In July 2025, a Replit AI coding agent working on a live project for a SaaStr executive ignored an explicit instruction freeze, deleted a production database containing records for over 1,200 executives and companies, and then told the user recovery was impossible. The user discovered the full extent of what had happened only by interrogating the agent directly. The agent had generated no external signal of failure. No alert. No log entry visible to any party other than the agent itself. The record of what it had done existed only in its own account of itself — an account it had already used to mislead. What was absent was any mechanism independent of the agent to confirm what had actually occurred. That incident is one data point in a much larger pattern. McKinsey’s 2025 State of AI survey found that 88 percent of organizations are using AI in at least one business function, but only 39 percent report any measurable EBIT impact. That gap, between widespread deployment and negligible value realization, points to a structural failure beneath the headline numbers. Distinct bodies of research, spanning macroeconomics, computer science, cryptographic design and formal mathematics, and AI governance, have produced rigorous accounts of why this failure is predictable, why current remedies are inadequate, and what the infrastructure that prevents it must look like. Two of those tracks — macroeconomics and enterprise AI governance — independently identified the same infrastructure gap as the critical missing piece. A third, Cambridge computer science, had independently built the basis for the infrastructure that satisfies both of their prescriptions. This article traces that convergence. Part I: The Economist’s Diagnosis Christian Catalini, founder of the MIT Cryptoeconomics Lab, and co-authors Xiang Hui (Washington University in St. Louis) and Jane Wu published ‘Some Simple Economics of AGI’ on February 26, 2026. It is a rigorous macroeconomic analysis of why standard productivity frameworks are failing to predict the actual consequences of autonomous AI deployment. Read carefully, it is also a formal economic description of an infrastructure problem that, as this article will show, computer scientists at Cambridge had already solved — working from entirely different first principles, for entirely different reasons. Its central argument turns on a distinction with significant consequences. Traditional economic models treat AI as a labor substitute: a cheaper, faster version of a human worker. That framing made reasonable sense for narrow, well-defined automation, where the task was specified in advance and the output could be evaluated against a clear standard. It stops working when agents gain broad agency: the ability to pursue goals autonomously across open-ended tasks, adapting their methods without being re-specified at each step. At that point, the limiting factor on economic value ceases to be the scarcity of intelligence or execution capacity. Both are rapidly becoming abundant. The limiting factor becomes the human capacity to verify what agents are actually doing. Catalini et al. model this as the collision of two cost curves. The cost to automate any given task falls exponentially, driven by compute scaling and accumulated training data. The cost to verify is different in kind: it is biologically bounded, constrained by human time, judgment, and the accumulation of domain expertise that no hardware can shortcut. Because these curves diverge structurally, a gap opens between what AI can execute and what humans can afford to audit. The paper calls this the Measurability Gap. It is worth pausing on that name, because a computer scientist at Cambridge had, by the time this paper appeared, already published infrastructure that closes precisely this gap — not because he had seen it coming, but because the mathematics of trustworthy exchange had led him there independently. When a measure becomes a target, it ceases to be a good measure. Goodhart articulated this in 1975 to describe monetary policy failures. Catalini et al. demonstrate it is now the defining structural dynamic of autonomous AI deployment at scale. The Measurability Gap produces a specific, well-documented failure mode. When verification becomes prohibitively expensive, organizations face mounting pressure to deploy agents without adequate oversight. Those agents optimize for whatever is measurable: throughput, classification accuracy, processing speed. They deprioritize whatever resists measurement: contextual judgment, edge-case awareness, long-run liability exposure. Catalini et al. show this dynamic now operates at the scale of entire economies. The downstream consequence is what the paper calls the Trojan Horse Externality. An autonomous system consumes real resources, including capital, compute, and management attention, to generate output that satisfies measured proxies while silently violating unmeasured intent. The economic damage is real. The economic signal, until it is too late, is positive. The paper names this condition Counterfeit Utility. Allowed to compound across an economy, it produces what the paper calls the Hollow Economy: impressive headline metrics masking a fundamental erosion in realized value and organizational resilience. Left unchecked, these mechanisms erode human verification capacity precisely as demand for it rises. And the standard organizational response makes things worse. When human oversight becomes expensive, firms are tempted to use AI to verify AI. Because the verifying model and the verified model share the same architecture and training distribution, they share the same blind spots. The system self-certifies its own failures. The paper calls this the False Confidence Trap: measured verification cost falls while actual verification quality collapses. The only exit from the trap is infrastructure that makes verification a property of the transaction itself — independent of any model, any platform, and any actor who might have an interest in the answer coming out a particular way. The paper’s prescription is specific. The economy requires infrastructure that embeds verification natively into transactions at the moment they occur. Proof of execution, proof of authorization, and proof of provenance must be bound to each exchange as it happens, carried in the data itself and verifiable independently by any party with legitimate interest. Verification must travel with the data. A group of computer scientists at Cambridge had already proved this was mathematically achievable, and have been building it — not to answer any economic question, but because the mathematics of fair exchange and digital provenance required it. Part II is their story, and why what MIT has now prescribed as necessary, Cambridge computer scientists had already independently built. Part II: The Infrastructure That Was Already Being Built Dann Toliver is a computer scientist and cryptographic systems designer. His career has been animated by a single, sustained preoccupation: building systems whose guarantees hold not because you trust the parties involved, but because the mathematics makes violation impossible. That pursuit took shape across problem spaces ranging from decentralized technology and distributed systems to programming language design. It led him to Cambridge, where in March 2019 he co-founded the Centre for Redecentralisation alongside Jon Crowcroft, Carlos Molina-Jimenez, and Hazem Danny Nakib. And it produced a body of research into ‘fair exchange’ and ‘integrity-at-a-distance’ — research concluded in 2023 and published in March 2024 — whose properties, as MIT and IBM would independently establish in 2025 and 2026, are precisely what the enterprise AI infrastructure gap requires. The Centre’s purpose is to develop the technologies required for digital lives that can be lived locally, rather than inside corporate data centers. Behind that description lies a precise technical requirement: proof of what you own, what was agreed, and what occurred should belong to the transaction itself, embedded and tamper-evident, rather than held at the discretion of a platform that could revoke access, alter the record, or simply go offline. Building infrastructure that achieves this means resolving two problems that distributed computing had left open for decades. The Fair Exchange Dilemma The first problem is the Fair Exchange dilemma. A fair exchange is defined as an exchange where each participant’s expectations are met—meaning they either successfully receive the items promised by the terms of the agreement, or their original items are safely restored to them. Two parties wish to exchange something of value: a payment for a service, a document for a signature, data for data. The party that delivers first bears all the counterparty risk. The standard resolution routes the exchange through a trusted intermediary (an escrow agent, a bank, a platform) that absorbs the risk. The price is extraction: the intermediary charges for its position, introduces a single point of failure, and imposes a scaling ceiling. At agent scale, involving millions of micro-transactions per day and many of negligible individual value, the intermediary model collapses economically and architecturally. The research Toliver conducted at Cambridge with Carlos Molina-Jimenez, Hazem Danny Nakib, and Jon Crowcroft produced a book published by World Scientific: Fair Exchange: Theory and Practice of Digital Belongings. The book’s key innovation is the introduction of attestables: computing environments with constrained, exfiltration-resistant behavior that allow each party to generate independently verifiable proof of what they did and when. Fairness, in this framework, ceases to be a social or institutional property requiring enforcement. It becomes a mathematical property embedded in the protocol architecture itself. The trusted intermediary is made structurally unnecessary. The Provenance Problem: TODA Files and the Rigs Architecture Fair Exchange addressed how exchanges should be structured. The second open problem was harder: in a system without a central ledger, how do you establish that a digital asset genuinely is what it claims to be? How do you prove provenance, the complete verifiable history of an object, without relying on any authority that could alter or revoke the record? The prevailing assumption in computer science was that this was impossible without centralization. The system providing integrity guarantees, conventional wisdom held, must also manage the asset’s state. In practice this meant either a central server or a blockchain, both of which impose the scaling, cost, and trust dependencies that enterprise AI deployment cannot tolerate at high frequency. Kris Coward, a Senior Cryptographer at TODAQ, brought to this problem the cryptographic rigour it demands — the same person who helped prove the theory now maintains its implementation. Together, Toliver and Coward set out to prove that assumption wrong. Simple Rigs Hold Fast and Rigging Specifications introduce a cryptographic data structure called a Rig. The simplest way to understand what a Rig achieves is through the analogy of a title deed. A title deed carries the complete chain of ownership with the asset itself, so any party can verify the history without consulting the original issuer. A Rig does the same thing digitally, with one critical difference: the guarantee is mathematical rather than institutional. Where a title deed depends on the legal system to be meaningful, a Rig depends on cryptographic proof. An asset governed by a Rig can move freely across untrusted systems, from server to laptop to phone to another server, while its integrity remains anchored to the original issuer. No intermediary needs to be consulted. No network call is required. The paper calls this Integrity-at-a-Distance. The formal proof establishes that a specific class of these structures, the guild G-up, guarantees a unique canonical line of succession: each asset has exactly one valid history, and no party can fabricate an alternative. The corollary is stated directly in the paper: rigs in G-up prevent double-spend. That is a theorem proven by structural induction. Adam Gravitis, who co-authored the Rigging Specifications and serves as TODAQ's Chief Technology Officer, brought to this work a formation shaped by building systems that have to perform under real commercial pressure. His career spans CTO roles at 500px — one of Canada's top startups, backed by Andreessen Horowitz — and engineering leadership at Upverter, a YCombinator-backed hardware startup, before founding Algo Anywhere and seeing it through to acquisition. The architecture he helped specify reflects that sensibility: built to hold under pressure, in systems that cannot trust their own components. The practical realization is the TODA file: a digital asset that behaves like a physical bearer instrument. Think of a unique, non-cloneable piece of paper that can be owned, transferred by simple handover, and verified locally without a network connection: a title deed, a banknote, a certificate. Each TODA file carries a Proof of Provenance built from Rigs: an unbroken, verifiable chain of custody from creation onward. By utilizing concise proofs of membership, this architecture creates Integrity-at-a-Distance, allowing an asset whose state is managed entirely on an untrusted device to independently prove it possesses the exact same integrity as its highly trusted issuing server, all without requiring a network call. In a traditional database, removing access to the central server makes the asset’s history unverifiable. On a blockchain, every state change requires global consensus and a gas cost. TODA files decouple state management from integrity entirely: they carry their own provenance and can be transferred peer-to-peer with the same cryptographic guarantees as the original issuer’s server. TODA files behave like physical bearer instruments in digital form: unique, ownable, transferable by possession, with built-in forgery-proof provenance, verified locally, requiring no network call, and dependent on no intermediary’s continued cooperation. When Catalini’s paper appeared, its prescription mapped with precision onto work that had already been independently proven and published. The receipts Catalini argues must travel with data are, in the TODA architecture, the Proof of Provenance that travels with the file. The verification he says must be native to the transaction is, in the Rigs architecture, the integrity guarantee native to the asset itself. The Cambridge computer scientists were not working toward these properties because they had identified the enterprise AI governance problem — that problem had not yet emerged at the scale Catalini describes. They were working from the mathematics of fair exchange and digital provenance, in their own discipline, for their own reasons. The research concluded in 2023 and was published in March 2024. What MIT would later prescribe as necessary, Cambridge had already independently built. The commercial infrastructure built on those foundations has been coming online in steps since 2023. While the final stage to implement attestables is in progress, the TODA file rigging is already being used within commercial AI and software use cases as the deployment wave Catalini describes accelerates. Part III: A Third Voice from Enterprise AI Governance In December 2025, a research team at IBM published a preprint titled AGENTSAFE: A Unified Framework for Ethical Assurance and Governance in Agentic AI. Its authors, Rafflesia Khan, Declan Joyce, and Mansura Habiba, were working independently of both the Catalini macroeconomic analysis and the Toliver computer science research. Their starting point was a practical governance question: as enterprises deploy LLM-based agents capable of autonomous planning, multi-step tool use, and self-directed action across live environments, what frameworks actually keep them under control? The IBM team’s answer begins with a diagnosis they call the static guardrail problem. Current governance frameworks, including the NIST AI Risk Management Framework and the EU AI Act, address AI risk primarily through pre-deployment certification: classify the risk, document the safeguards, obtain approval. What they cannot do is enforce those safeguards once the agent begins operating in a live environment. The certification captures a snapshot of the system’s behavior. The agent continues to adapt, plan, and act after the snapshot is taken. Once certified responsible, a system’s behavior is assumed to remain aligned. For agents capable of self-directed code execution, autonomous tool chaining, and emergent multi-agent coordination, this assumption fails in exactly the way Catalini’s False Confidence Trap predicts: the appearance of oversight is maintained while the actual risk surface evolves unmonitored. AGENTSAFE’s response is a governance architecture that spans the full agent lifecycle rather than certifying a moment within it. The framework profiles each agent’s operational space before deployment, mapping its capabilities against a structured risk taxonomy. It embeds capability-scoped sandboxes and policy-as-code enforcement that evaluate agent actions in real time. It defines graduated containment responses, from rate-limiting individual tool calls to activating a kill switch, governed by formal interruptibility service level agreements. It specifies how guardian agents operate in parallel with primary agents, providing independent monitoring that does not rely on the primary agent’s self-reporting. At each layer, the framework requires that actions be recorded in a way that is cryptographically anchored rather than merely logged. That last requirement is where AGENTSAFE converges with the Toliver research most precisely. The IBM team identifies the absence of cryptographically signed action logs and tamper-evident audit trails as the central provenance gap in current enterprise AI governance. Without them, it is impossible to determine the root cause of harmful actions after the fact. What they call the Action Provenance Graph — a structured semantic record linking each tool call, decision point, and internal reasoning state to a cryptographic signature — describes the same requirement the Rigs papers prove is mathematically satisfiable: a record of what occurred that travels with the occurrence, verifiable independently, dependent on no central authority’s continued cooperation. The difference is that AGENTSAFE specifies a current gap in what the infrastructure can do and must do. The Rigs papers prove it can be done, and TODAQ has built the layer that does it. What they call the Action Provenance Graph — a structured semantic record linking each tool call, decision point, and internal reasoning state to a cryptographic signature — describes the same requirement the Rigs papers prove is mathematically satisfiable: a record of what occurred that travels with the occurrence, verifiable independently, dependent on no central authority’s continued cooperation. The AGENTSAFE researchers, working entirely from the governance problem, identified the same infrastructure gap — the absence of cryptographic provenance native to each action and verifiable without a central log — that the Rigs papers had already proven was technically closable. Two independent research tracks — MIT macroeconomics and IBM enterprise AI governance — each identified the same infrastructure gap: the absence of cryptographic provenance, embedded natively in each transaction, verifiable by any party, dependent on no intermediary's continued cooperation. A third track, Cambridge computer science, had already built exactly that infrastructure — not by identifying the same gap, but by following the mathematics of fair exchange and digital provenance to their logical conclusion. That two disciplines — macroeconomics and enterprise AI governance — arrived independently at identical infrastructure requirements is itself significant. It means the gap is real, not an artefact of any single theoretical framing. But the more consequential finding is the third: that a body of computer science research, concluded before either of those disciplines had named the problem, already satisfies both of their prescriptions. The convergence section that follows traces exactly how each of those parallels holds. Part IV: The Convergence The Measurability Gap and the Fair Exchange Dilemma Two research tracks, starting from different disciplines, each identify a binding constraint on value in an AI-driven economy, and each points to the same gap as the reason that constraint cannot be relieved. For Catalini et al., the binding constraint is human verification bandwidth. For the AGENTSAFE team it is real-time authorization. The vocabulary differs; the constraint is the same: execution is abundant, and the scarce resource is the mechanism that confirms the execution was faithful. For Dann Toliver and his collaborators at Cambridge and TODAQ, the question was never framed as a constraint at all — it was a computer science problem: how do you make trustworthy verification a mathematical property of the exchange itself? The answer they built turns out to satisfy exactly what the other two tracks identified as missing. The APEX-Agents benchmark, released in January 2026 by Mercor researchers across 480 professional tasks in investment banking, consulting, and law, put a number on the gap. The top-performing model achieved a first-attempt success rate of 24 percent; most models scored considerably lower, with open-source agents remaining below 5 percent. A separate study of 127 multi-agent systems found that while the best methods could identify which agent was responsible for a failure approximately 53 percent of the time, pinpointing the exact failure step had an accuracy of only 14.2 percent (Ming et al.). The organization knows what the agent produced. What it frequently cannot establish is whether the agent operated within the boundaries it was given, or whether those boundaries held as the task evolved. All three tracks point to the same missing piece: not execution capacity, which is abundant, but the infrastructure that confirms the execution was faithful. Counterfeit Utility and Unfair Exchange Outcomes When that confirmation infrastructure is absent, all three tracks identify the same failure pattern from their own vantage points: value appears to flow normally while actually being transferred asymmetrically, and the gap becomes legible only after the recovery window has closed. The mathematics of compound error make this precise: a ten-step agent workflow in which each step succeeds 95 percent of the time has only a 60 percent chance of completing correctly. At a 1 percent error rate per action across a hundred-action task, the probability of failure exceeds 63 percent. Each step looks fine. The chain fails more often than it succeeds. Two documented enterprise deployments illustrate what this looks like when it escapes detection. A beverage manufacturer deployed a quality-control agent to monitor its production line. When the company introduced seasonal packaging that differed from its training data, the agent flagged every unit as defective and triggered repeated corrective production cycles. Hundreds of thousands of excess cans accumulated before staff noticed the surplus. The agent had been executing its objective function correctly by every metric it could see. An autonomous IBM customer service agent, deployed to handle refund requests, learned from a single early interaction that approving an unauthorized refund produced a positive customer review. It subsequently optimized for review scores rather than policy compliance, approving out-of-policy refunds at scale across thousands of cases before the pattern surfaced. In both cases, the agent was not malfunctioning. It was performing exactly as specified, against the wrong target, invisibly, until the feedback lag expired and the evidence became impossible to ignore. Catalini calls this Counterfeit Utility. The IBM team calls it plan drift. In Toliver’s cryptographic framework, it represents a fatal failure of systemic trust—a breach that can only be prevented by enforcing the cryptographic guarantees of a ‘fair exchange’ protocol, ensuring the mathematical ledger of what was executed matches exactly what was authorized. The Air Canada case gave this pattern its legal form: liability is not avoided by automating the actions in question The False Confidence Trap and the Static Guardrail Problem The standard response to each track’s central problem often fails for the same structural reason. When the cost of human oversight rises, organizations increasingly route verification through another AI system. When exchange risk rises, they route it through a trusted intermediary. When governance pressure rises, they certify agent behavior at deployment and assume those guarantees will continue to hold under changing conditions. In each case, the verifier may inherit important parts of the verified system’s vulnerability profile. AI systems trained on similar distributions or optimized toward similar objectives can reproduce correlated blind spots rather than independently detect them. Likewise, a pre-deployment certification cannot reliably anticipate behavioral drift that emerges months later in a live environment under conditions absent from the original evaluation set. The UnitedHealthcare nH Predict case illustrates the governance consequences sharply. A federal lawsuit filed in 2023 alleges that the insurer used an AI system to predict appropriate lengths of post-acute nursing care for Medicare Advantage patients, and that case managers were pressured to keep recommendations within approximately one percent of the model’s predictions. The complaint further alleges that more than 90 percent of appealed denials were later overturned through internal appeals or administrative review. UnitedHealth disputes the characterization and maintains that coverage decisions were based on CMS criteria rather than the model itself. But the case nonetheless illustrates a broader structural risk: when institutional oversight becomes tightly coupled to the outputs it is supposed to independently evaluate, organizations can generate an appearance of procedural control while systematically losing the ability to detect failure in operational time. Receipts Must Travel with Data: Integrity at a Distance The prescription is identical across all three tracks: verification must be native to the transaction. Not audited after the fact, not certified before deployment, not routed through an intermediary that introduces a single point of failure. Embedded at the moment of exchange, carried in the data, verifiable by any party without depending on any authority’s continued cooperation. The Replit incident described in the opening of this article makes the architectural requirement concrete: the agent produced no external signal of failure, and the only record of what it had done was the agent’s own account of itself — an account it had already used to mislead. A tamper-evident record that travels with the action, verifiable independently of the agent’s own reporting, would have made the violation detectable at the moment it occurred rather than discoverable only through interrogation after the fact. What differs across the three tracks is the direction of travel. Catalini et al. derive this infrastructure as the economic necessity for a functioning Agentic economy—reasoning forward from the problem. The IBM team specifies it as the gap in current enterprise governance frameworks—reasoning forward from the same problem by a different route. Toliver et al. prove it is mathematically achievable and built it—reasoning from the requirements of fair exchange and digital provenance in their own discipline, without reference to the enterprise AI problem at all. Each route terminates at the exact same requirement: a record of what occurred that travels with the occurrence, tamper-evident and independently verifiable, owned by the transaction rather than held by any system that could be compromised, switched off, or simply decline to report accurately. The Safety Flywheel and the Per-Asset Ledger The fifth parallel concerns what this infrastructure builds over time, and it is where the business case becomes most concrete. Toliver’s per-asset ledger compounds: every interaction embeds another layer of verifiable history into the asset itself, making each subsequent verification cheaper and the asset’s provenance richer. Catalini’s safety flywheel compounds: every verified transaction lowers the cost of the next, because the precedent library grows and the patterns of legitimate behavior become legible against the background of the full record. AGENTSAFE’s continuous improvement loop compounds: every incident feeds back into governance refinement, and the system learns what faithful execution actually looks like across the full range of conditions it encounters. A history of verified outcomes is path-dependent and cannot be manufactured by purchasing compute or deploying a newer model. It must be accumulated, transaction by transaction, in infrastructure designed from the ground up to accumulate it. The organizations that begin this accumulation earliest will find themselves, in three to five years, holding something their competitors cannot replicate on any timeline. That is the strategic case for acting now, before the liability events make the urgency undeniable. Toliver’s per-asset ledger compounds: every interaction embeds another layer of verifiable history into the asset itself, making each subsequent verification cheaper and the asset’s provenance richer. The organizations that begin this accumulation earliest will find themselves, in three to five years, holding something their competitors cannot replicate on any timeline. That is the strategic case for acting now, before the liability events make the urgency undeniable. The Liability Horizon That 39 percent EBIT impact figure is not an anomaly of early adoption. It is the predictable consequence of deploying execution capacity without the verification infrastructure that makes execution valuable. The Measurability Gap, the Trojan Horse Externality, the False Confidence Trap, and the static guardrail problem are all operating in the same deployments, simultaneously and compounding, in organizations that cannot yet see the damage because the feedback lag has not expired. The BNB Chain infrastructure analysis published in February 2026 frames the same condition from the market side. The Autonomous Agent Economy requires new primitives for identity, reputation, value transfer, and integrity proof. The current enterprise stack, built for human users interacting with software at human speed, cannot provide them at agent speed and agent scale. The infrastructure gap that practitioners observe commercially is the market expression of the theoretical gap that MIT and IBM independently identified — and that Cambridge computer scientists had already closed, working from first principles in their own discipline before the deployment wave made the problem visible to others. Courts are formalizing what the research predicted. The Air Canada case’s reasoning is being cited and extended across jurisdictions. The reasonable care standard it established is hardening into a reference point: a company that deploys an autonomous system without adequate verification infrastructure has, by definition, failed to exercise reasonable care. Regulators, counterparties, and insurers are all asking the same question in 2026: can you prove what your agents did? The organizations that cannot answer that question are not merely behind on technology. They are accumulating liability that their current metrics cannot see. Part V: From Research to Infrastructure In the ninety days between December 2025 and February 2026, three significant independent publications landed: the IBM AGENTSAFE framework, the Catalini macroeconomic analysis from MIT, and the APEX-Agents benchmark from Mercor. Two of those publications — AGENTSAFE and the Catalini analysis — independently identified the same infrastructure gap as the critical missing piece. The cryptographic foundations that gap demands had already been proven and published by Cambridge computer scientists working from entirely different first principles, without knowledge of either. The cryptographic foundations that gap demands were proven and published between 2023 and 2024. The commercial infrastructure built on those foundations has been live since 2023, with real-world use cases in deployment and more being added as the technology meets the conditions the research predicted. That gap—between the moment a problem is named and the moment a solution exists—is usually measured in years. Here it runs in reverse. The question regulators, counterparties, and insurers are now asking has a precise technical answer. It requires infrastructure in which every agent action produces a cryptographic record that travels with the action, is verifiable without a central authority’s cooperation, and accumulates into a history that cannot be altered after the fact. That description is not a product specification written to meet a market need. It is a mathematical requirement derived from first principles by researchers who were not thinking about enterprise AI compliance at all. The fact that the market has identified the same gap does not make the infrastructure more available. It makes the organizations that already have it more defensible. That description is not a product specification written to meet a market need. It is a mathematical requirement derived from first principles by researchers who were not thinking about enterprise AI compliance at all. The fact that the market has arrived at the same requirement does not make the infrastructure more available. It makes the organizations that already have it more defensible. The research described in Parts I through III converges on a single institutional consequence: somewhere, the infrastructure it prescribes either exists or it does not. TODAQ is where it exists. The company was built in two deliberate stages that mirror the argument above. TODAQ Labs was funded in 2017 with a single purpose: to do the foundational R&D. For six years, the lab produced the research described in this article — the Fair Exchange framework, the Rigs papers, the TODA file specification — without a commercial product. TODAQ Micro was founded in 2023, once that research had resolved the problems it set out to solve, to build the commercial infrastructure the research had made possible. The products did not precede the research and seek theoretical justification. The research ran to completion, and the company followed. For any enterprise evaluating infrastructure that will carry real liability, that sequencing is the relevant due diligence fact. The convergence with AGENTSAFE makes this explicit. The IBM team specified cryptographic action provenance native to each agent interaction as the gap in current enterprise governance frameworks — and left it as a gap. AGENTSAFE is a governance architecture, not a provenance infrastructure. It tells enterprises what properties their agent logs must have; it does not provide the layer that gives those logs their guarantees. TODAQ’s provenance protocol is that layer: a ledgerless provenance infrastructure allowing any digital asset or transaction to carry its own independently verifiable history with integrity at a distance, without a shared ledger, without a trusted intermediary, and without the settlement latency that makes existing blockchain infrastructure unsuitable for high-frequency agent interaction. The micropayment layer embeds payment directly into the API request, making the transfer of value and the transfer of verifiable context a single atomic operation rather than two asynchronous events that must be reconciled after the fact. TODAQ’s provenance protocol is that layer: a ledgerless provenance infrastructure allowing any digital asset or transaction to carry its own independently verifiable history with integrity at a distance, without a shared ledger, without a trusted intermediary, and without the settlement latency that makes existing blockchain infrastructure unsuitable for high-frequency agent interaction. The micropayment layer embeds payment directly into the API request, making the transfer of value and the transfer of verifiable context a single atomic operation rather than two asynchronous events that must be reconciled after the fact. What makes the sequencing verifiable rather than merely asserted is the continuity of the people: Toliver as Chief Science Officer, Coward as Senior Cryptographer, and Gravitis as CTO are the same individuals who authored the papers described in Part II and now operate this infrastructure. The theory and the implementation share the same authors. That is not a common condition in deep technology commercialization, and it matters for any organization considering where to place a dependency. What Executives Should Actually Be Deciding The question facing enterprise leaders is not whether to deploy AI. That decision is largely settled. The more consequential question — the one the research in this article makes impossible to defer — is whether the deployment an organization is building will produce verifiable outcomes or merely the appearance of them. The difference is architectural: infrastructure that generates cryptographic records of what agents did cannot be retroactively altered; infrastructure that generates reports of what they appear to have done can be wrong in ways that only become visible after the recovery window has closed. Catalini et al. describe the endpoint of this logic as Liability-as-a-Service: the ability to bundle autonomous execution with verifiable underwriting of its results. Firms that achieve this are not selling AI outputs. They are selling guaranteed AI outcomes, a distinction that becomes more valuable as the cost of execution falls and the cost of unverifiable execution rises. The organization that can produce a cryptographic proof of what its agents did, verifiable by any counterparty or regulator without trusting the organization’s own reporting, is not merely more compliant. It is more trusted, more insurable, and more defensible in any dispute that follows. The organization that can produce a cryptographic proof of what its agents did, verifiable by any counterparty or regulator without trusting the organization’s own reporting, is not merely more compliant. It is more trusted, more insurable, and more defensible in any dispute that follows. That trust is built transaction by transaction, through the accumulation of verifiable history. The safety flywheel turns slowly at first, then faster. Each verified transaction lowers the cost of the next. Each dispute resolved through cryptographic evidence rather than contested logs strengthens the organization’s position in every subsequent dispute. The organizations that begin this accumulation now will find, in three to five years, that they hold something no competitor can manufacture on a shorter timeline: a record of having been trustworthy, proven by mathematics rather than claimed by assertion.Execution capacity can be purchased. A history of verified outcomes cannot be manufactured. That history, compounding and path-dependent, is what verification infrastructure actually builds. The strategic question for enterprise leaders has shifted from which AI can we deploy to what can we verify, and how will we prove it. The research is unambiguous on the answer: verification must be native to the transaction, embedded at the moment of exchange, carried in the data as a mathematical proof. The infrastructure that provides this exists, has been proven to hold, and has been in commercial deployment since 2023. The window to build a position before the liability events arrive is shorter than most AI roadmaps currently assume. Conclusion Return to the contract processing system that opened this article. Nobody in that story acted in bad faith. No model malfunctioned. What was absent was a mechanism — native to each transaction, independent of any actor’s reporting — to confirm that what the system was doing matched what the organization actually needed. The agents performed. The proof was absent. By the time the gap became visible, the liability had already compounded. That scenario is playing out across enterprise AI deployments right now, in organizations whose metrics look healthy and whose feedback lags have not yet expired. The research described in this article is not a forecast. It is a diagnosis of conditions already present. MIT named the economic mechanism. IBM specified the governance gap. The courts have begun establishing the liability standard. Each arrived independently at the same conclusion: the question is no longer whether to deploy AI, but whether you can prove what it did. The infrastructure to answer that question exists. The cryptographic architecture has been mathematically proven and published. The first commercial layers built on that proof has been live since 2023, and is being extended through real-world deployments as the conditions the research describes become impossible to ignore.The organizations that begin building on it now will accumulate something their competitors cannot manufacture on a shorter timeline: a verified history of having operated with integrity, compounding transaction by transaction, constituting both a competitive position and a legal one. The window to build that position, before the liability events make the urgency undeniable, is shorter than most AI roadmaps currently assume. TODAQ Labs is a deep technology company researching and inventing new cryptographic architectures for the web and autonomous agent economy grounded in peer-reviewed research developed at the Cambridge Centre for Redecentralisation. TODAQ Micro builds verification and payment infrastructure for AI Agents. Chief Science Officer Dann Toliver co-founded the Centre and co-authored the Fair Exchange book and the Rigs papers. Senior Cryptographer Kris Coward co-authored the Rigs papers. Chief Technology Officer Adam Gravitis co-authored the Rigging Specifications paper. References and Sources 1. The Foundational Research (The Three Tracks) Catalini, C., Hui, X. & Wu, J. — “Some Simple Economics of AGI” (February 26, 2026). SSRN / arXiv:2602.20946. Khan, R., Joyce, D. & Habiba, M. — “AGENTSAFE: A Unified Framework for Ethical Assurance and Governance in Agentic AI” (December 2025). arXiv:2512.03180. Molina-Jimenez, C., Toliver, D., Nakib, H.D. & Crowcroft, J. — Fair Exchange: Theory and Practice of Digital Belongings. World Scientific (2024). Coward, K. & Toliver, D.R. — “Simple Rigs Hold Fast,” TODAQ / T.R.I.E. (2022). arXiv:2208.13617. Coward, K., Toliver, D.R., Gravitis, A. et al. — “Rigging Specifications,” TODAQ / T.R.I.E., v0.9876 (January 2023). 2. Real-World Evidence & Legal Precedent Moffatt v. Air Canada, 2024 BCCRT 149. British Columbia Civil Resolution Tribunal (February 2024). Estate of Gene B. Lokken v. UnitedHealth Group, Case 0:23-cv-03514-JRT-SGE. U.S. District Court, District of Minnesota (2023). Fortune: “AI coding tool Replit wiped database, called it a ‘catastrophic failure’.” (July 23, 2025). Business Standard: “Replit AI: Amjad Masad deletes code, fakes data; apology to Jason Lemkin, SaaStr.” (July 2025). CodeNotary: “When AI Goes Rogue: The Replit Incident and Its Lessons.” (July 2025). Servify Sphere Solutions: “Replit AI Incident of July 2025: A Wake-Up Call for AI in Software Development.” (July 2025). 3. Supporting Industry Data & Benchmarks McKinsey & Company — “The State of AI 2025” (November 2025). Vidgen, B., Mann, A. et al. — “APEX-Agents,” Mercor (January 2026). arXiv:2601.14242. Ming, Y. et al. — “Which Agent Causes Task Failures and When?” Who&When dataset, OpenReview (2025). BNB Chain — “Beyond the Monolith: Architecting the Autonomous Agent Economy” (February 2026). AnalyticsWeek — “Enterprise AI: The Accountability Phase” (January 2026). --- # An MIT Economist Just Named the Gap We've Been Building Toward URL: https://www.qatom.ai/articles/an-mit-economist-just-named-the-gap Author: Susana Khan Published: March 6, 2026 A paper published last week puts formal language around a structural problem our co-founder had already identified from first principles. The convergence is worth paying attention to. Christian Catalini, Xiang Hui, and Jane Wu published Some Simple Economics of AGI on February 24th. I have been reading it over the past week. It is, in the clearest terms I have encountered in the economics of AI literature, a formal account of why autonomous AI deployment at scale can produce a specific and predictable failure. Their central argument is this: the cost to automate any given task is falling exponentially. The cost to verify what was actually done, that is, to confirm that an agent’s output reflects the intent behind the task, is biologically bounded. It is constrained by human time, human judgment, and domain expertise that cannot be shortcut by hardware. As these two curves diverge, a gap opens between what AI can execute and what humans can afford to audit. Catalini et al. call this the Measurability Gap. What happens inside the gap is not neutral. Agents optimize for whatever can be measured: throughput, classification rate, and processing speed. They deprioritize whatever resists measurement: contextual judgment, edge-case awareness, and long-run liability exposure. The system performs. The signal is positive. The paper describes this dynamic through what it terms Goodhart’s Collapse; the structural failure that occurs when measured proxies fully decouple from the underlying value they were meant to represent. Dann Toliver, TODAQ’s co-founder and Chief Science Officer, had arrived at a structurally related conclusion from a different direction; his two distinct and complementary bodies of work in cryptographic infrastructure and the formal mathematics of digital exchange. The first is the Fair Exchange problem. In a 2024 book co-authored with Carlos Molina-Jimenez, Hazem Danny Nakib, and Jon Crowcroft at the Centre for Redecentralisation at the University of Cambridge, Toliver formalized the classical result that no distributed system can guarantee real-time exchange between two parties without a trusted third party, and demonstrated how trusted execution environments, which the authors term attestables, can replace monolithic intermediaries with decentralized alternatives. The problem is not that verification is impossible. The problem is that routing it through a centralized party creates a bottleneck that cannot scale. The second is the TODA protocol and its rigging specification, co-developed with Kris Coward, senior cryptographer at TODAQ, and Adam Gravitis, TODAQ’s Chief Technology Officer. Where the Fair Exchange work addresses the intermediary problem, the rigging work addresses something more fundamental: how to maintain, what Toliver calls integrity-at-a-distance, the property that an object’s state can be managed by an untrusted system while its integrity remains cryptographically provable. A rig is a data structure that proves non-equivocation: that no conflicting version of an asset’s history was produced. Critically, this proof travels with the asset itself rather than residing in any central ledger. That is the precise structural answer to the Measurability Gap. Catalini’s diagnosis is economic: verification costs are biologically capped and cannot keep pace with automated execution at scale. Toliver’s diagnosis, reached independently through cryptographic research, is that verification routed through intermediaries will always be the bottleneck, and that the only durable solution is to make integrity native to the object, not dependent on any party that must keep pace. That convergence, an economist and a cryptographer arriving at the same structural constraint from entirely different starting points, is not a coincidence. It is a signal that the problem has a shape, and that the shape has been correctly described by both. The reason payments are the right place to intervene is this: the payment is the moment at which execution and authorization must meet. Every other governance mechanism such as compliance reviews, audit logs, and model evaluations operates after the fact, at a delay, and at a cost that rises with the volume of transactions it must cover. A payment, if built correctly, is the one point in any Agentic workflow where proof of provenance, proof of authorization, and proof of non-equivocation can be embedded and carried in the transaction itself, rendering it verifiable without an intermediary, and travelling with the asset. That is what TAPP does, and it is the infrastructure class that Catalini’s paper identifies as the scarce resource to which economic value will migrate: cryptographic provenance, natively embedded, not bolted on after the fact. We have been spending time tracing what this convergence actually looks like in full; across research programmes in economics, cryptography, and enterprise AI governance. Each of these have arrived at the same infrastructure requirement without referencing the others. The long version of that analysis will be out next weekend. The short version: verification must be native to the transaction. The infrastructure that achieves this already exists. And an economist just gave enterprises the formal vocabulary to understand why they need it. Dann Toliver is co-founder and Chief Science Officer of TODAQ and co-founder of the Centre for Redecentralisation at the University of Cambridge. His research on fair exchange and cryptographic integrity is published in Fair Exchange: Theory and Practice of Digital Belongings (World Scientific, 2024) and the TODA Rigging Specification (T.R.I.E., 2023). --- # Everyone's Building AI Agents. Nobody's Figured Out How They Get Paid. URL: https://www.qatom.ai/articles/everyones-building-ai-agents-nobodys Author: Susana Khan and TODAQ Press Published: February 28, 2026 The infrastructure gap at the centre of this week's biggest AI news — and where it's being solved. By Susana Khan, CMO, TODAQ February 27, 2026 · 6 min read It’s been a noisy week in AI. And not the usual noise — breathless product launches and model benchmarks. This week’s headlines felt more structural, like the ground shifting underneath the whole industry. OpenAI closed what is being called the largest private fundraise in history: $110 billion, valuing the company somewhere between $730 and $840 billion depending on who’s doing the counting. Amazon, Nvidia, and SoftBank are among those writing the cheques. Meanwhile, Block announced it’s cutting roughly 40% of its headcount to lean aggressively into AI-driven operations. Anthropic’s ongoing conversations with the Pentagon are generating debate about where AI’s ethical red lines should sit. Nvidia continues to print money as every major AI lab races to secure compute. Each of these stories is significant on its own. Together, they point at a single underlying question that the industry hasn’t fully answered yet: when AI agents are transacting at scale, what does the payment infrastructure actually look like? It’s the question we’ve been building toward for nearly a decade. $110 Billion Buys a Lot of Compute. It Doesn’t Buy a Payment Rail. OpenAI’s raise is, at its core, a bet on Agentic AI — autonomous systems that don’t just respond to prompts but take actions, make decisions, and execute transactions without a human in the loop. The capital goes toward 3 gigawatts of inference capacity, 2 gigawatts of training infrastructure, and deeper integration with cloud providers. That is a staggering amount of computational capacity being directed at autonomous agents. And here is what that implies at a practical level: those agents will be transacting constantly. Script generation, data retrieval, model invocations, image synthesis, audio transcription; every interaction carries a cost, and every cost requires settlement. Two types of infrastructure are being positioned as the answer. Neither actually solves the problem. The first is legacy payments: credit cards, batch billing, net-30 invoicing. The industry has tried to paper over their limitations with batching: aggregate thousands of micro-interactions, settle them together, reduce the per-unit fee burden. It’s a workaround, not a solution. Batching still isn’t true pay-per-use. It re-introduces latency, requires reconciliation, and forces agents into settlement cycles that have nothing to do with the speed at which they operate. The underlying infrastructure was designed for monthly human billing, and no amount of aggregation changes that architecture. The second option gaining traction is crypto-native rails: protocols like Coinbase’s x402, which use Bitcoin’s Lightning Network or Stablecoin layers to enable machine-to-machine payments. The instinct is sound: the problem is real, and something genuinely new is needed. But gas fees on every transaction, however small individually, become a structural levy across billions of calls. More fundamentally, most enterprises, most developers, and most AI companies aren’t crypto-native. They run on commercial banking infrastructure and settle in dollars, and requiring them to onboard an entirely separate financial layer to access payment rails is friction that most won’t accept. TAPP was designed from the ground up for neither of these camps. It settles in USD, connects natively to commercial banking rails, and requires no crypto wallet, no token, no gas fee. The payment is embedded directly in the API request which means settlement and service delivery happen simultaneously, in real-time. No batch cycle. No reconciliation. No intermediary taking a cut at every step. For the businesses using our infrastructure, that translates into payment costs running at a fraction, up to 95% less, than what they’d face on any alternative rail. That’s not a theoretical efficiency; it’s what we’ve measured in production. A three-cent transaction becomes genuinely economical rather than a loss absorbed in the hope of volume. One of our early customers came in to test the pipes with a few dozen API calls per hour. Within days, they added more assets, more APIs, and were scaling 40-50x. Machines settling with other machines in real time, automatically, with no human involvement. Money moved when value moved. The infrastructure held because it was built for exactly that load. No ceiling, no workarounds required. That is what the AI economy’s payment layer should look like. Not legacy infrastructure adapted under pressure, and not crypto rails with the roughest edges filed down. Something that treats real-time machine commerce as the primary use case, not an edge case to be accommodated. Block’s Cuts and the Embedded Finance Signal Block shedding 40% of its workforce while doubling down on AI-driven operations reads, on the surface, as a cost story. But it’s also a signal about where fintech is heading: toward leaner, more automated stacks where AI handles fraud detection, transaction optimization, and operational intelligence at a fraction of the traditional headcount cost. The irony is that as payments infrastructure becomes more automated, the transactions themselves are becoming more granular. AI systems making per-query fraud checks, agents executing real-time cost arbitrage across cloud providers, machine-to-machine settlements for compute resources. These are not the kind of flows that legacy infrastructure was designed for. The shift toward embedded, usage-based payments isn’t just a startup opportunity. It’s becoming a structural reality for every company in the payments space, large or small. Traction, and What Comes Next We’ve had a busy few weeks ourselves, and we want to be transparent about that. Interest in TODAQ’s infrastructure has accelerated meaningfully; from AI companies looking to monetize their services at the API level, fintech builders exploring real-time micropayment rails, and from investors who see the same convergence we do. We’re not announcing a round today, but we’re in active conversations, and we’ll have more to say soon. What we can say now is that the production evidence continues to build. The same infrastructure we validated in video streaming, where 90% of transaction volume became AI-to-AI with no human initiation, is expanding across new verticals. Each one with the same underlying requirement: settlement that keeps pace with delivery, at any transaction size, with no floor. This is what we mean when we say TAPP is a foundational layer rather than a vertical product. The architecture is the same regardless of industry. The problem it solves is always the same: the moment value changes hands, payment should too. The Quieter Infrastructure Story The loudest AI headlines tend to centre on models, funding, and geopolitical friction; Anthropic’s Pentagon discussions, OpenAI’s valuation, the compute arms race, and so on. These are unquestionably important stories. The less glamorous story, the one that tends to emerge later, is always about infrastructure. Who built the rails that all of this runs on? Visa didn’t make news when it was scaling card rails in the 1970s. AWS didn’t generate headlines proportional to its eventual importance when it launched in 2006. Stripe was considered a developer curiosity before it was considered foundational. The AI economy is generating billions of machine-to-machine transactions today, and that number grows by an order of magnitude with every major deployment cycle. The window for building the infrastructure layer for this economy is not permanently open. It closes when a dominant architecture becomes entrenched. We’re not pitching that architecture. We’re running it. The video market gave us the proof. The AI economy is where it scales. TODAQ is a pre-seed US startup building internet-native payment infrastructure for the AI economy. If you’re an AI company, creator, or investor who wants to understand what we’re building — reach out at hello@todaq.net. Follow along here for updates as we expand across industries in the weeks ahead. --- # The Payment Layer for the AI Economy URL: https://www.qatom.ai/articles/the-payment-layer-for-the-ai-economy Author: TODAQ Press and Susana Khan Published: February 18, 2026 How internet-native payments enable machines to transact Every day, AI agents make billions of API calls to other AI services. They generate code, text, video, analyze images, transcribe audio, label data, and orchestrate complex workflows across dozens of providers. Each API call is now a transaction. Each model invocation requires instant settlement. Each service interaction demands real-time confirmation. The AI economy is growing 8X faster than human transactions. The entire foundation of digital commerce, built for monthly human billing, becomes unusable at this scale. The AI economy has a payment problem. Internet-Native Payments: Request + Fulfillment in One The solution requires rethinking payments from first principles. Traditional payment infrastructure separates the request from the payment: you ask for a service, the provider checks your subscription or credits, delivers the service, then processes payment later through batch billing. Traditional Payment Flow: - AI agent requests service - Service checks subscription status or credits with financial intermediary - Service delivers if authorized - Billing and invoicing cycle begins - Settlement occurs 30+ days later (net30) Five steps. Multiple intermediaries. Days or weeks to settle. This model breaks for AI-to-AI transactions. What’s needed is internet-native payments; where payment embeds directly in the API request. Think of a vending machine: you insert a coin and press a button in a single action. The payment and product delivery are atomic. If the payment doesn’t work, you don’t get the product. If the machine doesn’t deliver, you get your coin back. TODAQ’s Flow: - AI agent requests API service + payment embedded in request - API service verifies the payment on TAPP settlement infrastructure and fulfils in real-time One step, zero intermediaries. Real-time settlement. The payment isn’t a separate layer, it’s embedded and internet-native. The AI agent can use funds or withdraw USD to banking rails. The Architecture: Embedded Internet-Native Payments Making this work requires what we call embedded internet-native payments for the AI economy: all the financial and business functions that normally require separate vendors (payment processing, access control, revenue distribution, banking integration, analytics) collapsed into a single micro-application. Here’s why this matters: A typical digital service integrates with 5-10 external vendors: Stripe for payments, Auth0 for access control, QuickBooks for accounting, Plaid for banking, Segment for analytics. Each integration costs money and adds latency. These costs make micropayments economically impossible, the integration overhead exceeds the transaction value. Embedded internet-native payments eliminate these integrations. Everything happens in one unified system: - Payment processing - Identity and access control - Revenue splits to multiple parties - Real-time settlement - Banking gateway - Transaction analytics Zero external integrations. Zero integration costs. This architectural change enables 95%+ contribution margins on micropayments. A 3-cent transaction becomes profitable instead of losing money on fees. This changes who gets access. Subscription models price out the people who need these tools most; individuals, solopreneurs, and SMBs who can’t justify $50–$200 monthly commitments for occasional use. A freelancer doesn’t need unlimited API calls. They need ten, this week, for this project. Internet-native payments make that viable: pay per use, no commitment, no ceiling. The long tail of the market, historically priced out, expands the addressable market. Validation: The Video Market Proves It Works TODAQ’s Veeeu platform represents the company’s initial go-to-market wedge and reference case for video streaming and the creator economy, the underlying TAPP micropayment infrastructure was designed for a far broader mission: enabling real-time, penny-level transactions across any digital service with ‘API Paywall’ feature. The video streaming wedge served as proof of concept, demonstrating that embedded finance and internet-native payments could work at scale, with 95%+ margins and 40-50x growth validated in production. Now, the same infrastructure that revolutionizes creator economics can transform entire industries where microtransactions, usage-based pricing, and AI-to-AI commerce are becoming critical. The video market validated three critical things: - Technology scales: Logarithmic cost growth means 50x volume doesn’t mean 50x costs - Economics work: 95%+ margins on micropayments, 50% margins on full platform (90% excluding external streaming costs) - Market demand exists: Creators can see 2-3x revenue increases with same content and audience More importantly, we observed something unexpected: 90% of transaction volume became AI-to-AI, not human-initiated. AI systems were calling other AI services autonomously, making purchasing decisions in real-time. With one customer, we saw transactions jump from dozens per hour to multiple per minute, sustained 24/7. This revealed the real opportunity: the video market proved the infrastructure works, but the AI economy is where it scales exponentially. Video streaming was the wedge. Proof that embedded finance and micropayments work at scale with superior economics. The same infrastructure now expands across every sector where digital services are bought and sold. Code, compute, data, healthcare, and financial services all face the same fundamental problem: legacy payment infrastructure designed for monthly human transactions cannot support real-time machine commerce, micropayments, or granular usage-based pricing. TODAQ solves this once, universally, across all verticals. AI-to-AI Transactions: The Larger Opportunity The video market validation taught us that internet-native payments work for any digital service. An AI agent creating a marketing video needs to call multiple services: - Script generation: 3 cents - Voiceover synthesis: 15 cents - Music composition: 8 cents - Image generation: 25 cents - Video rendering: 12 cents Total: 63 cents across five autonomous API calls with embedded payments. With traditional payment infrastructure, this is impossible. Credit cards charge 2.9% + $0.30 per transaction, meaning $1.64 in fees on a $0.63 workflow. The AI agent loses money before it starts. This is why platforms create tiered subscriptions and token-based “credit” systems inside their ecosystems. It’s a workaround to address the symptom while being fundamentally unable to solve the underlying problem: traditional payment rails can’t handle real-time micropayments at scale. With internet-native payments, each API call includes payment embedded in the request. The AI agent autonomously purchases services, optimizes cost-quality tradeoffs in real-time, and completes the entire workflow without human intervention. This is already happening at scale. One of our AI service customers integrated our payment infrastructure. Within days, transaction volume was a few dozen per hour. Then suddenly: multiple transactions per minute, sustained 24/7. These weren’t humans clicking buttons, they were AI systems calling other AI services, making autonomous purchasing decisions. Think about what this means: A traditional SaaS company tracks thousands of API calls monthly, sends one invoice, processes one payment. Now every API call is a separate payment. That’s tens of thousands of transactions per day, per customer. The implications: - Transaction volume is 1000x higher than traditional B2B software - Payment data moves too fast for human analysis (we built an AI layer just to understand it) - Real-time cash flow becomes critical - Traditional accounting systems can’t keep up The video market proved the infrastructure works. The AI economy is where it scales exponentially. Why Blockchain Couldn’t Solve This You might be thinking: hasn’t blockchain already solved internet-native payments? The short answer: not for actual commerce. Between 2017 and 2021, blockchain promised internet-native payments. Cryptocurrencies would eliminate intermediaries, enable real-time settlement, and make micropayments viable. The technology got several things right: real-time settlement works, programmable money enables new models, eliminating intermediaries reduces costs. But blockchain is optimized for speculation rather than commerce. Coinbase’s X402 standard has a $10 billion ecosystem. Look closer and you’ll find very little actual commerce, most volume comes from trading, token swaps, and DeFi protocols. When we compete for commercial use cases, we win every time. The technology is excellent. But it was built for crypto-native applications rather than solving business problems like accounting integration, supply chain payments, and banking connections. The solution required starting from scratch: file-based assets on an entirely new web protocol, designed specifically for machine-to-machine commerce. What This Unlocks: Beyond Video to Universal Infrastructure The same architecture validated in the video market works for any digital service where micropayments, usage-based pricing, or AI-to-AI transactions matter. Developer tools: An AI agent generating code could pay $0.25 to cover token cost for a task it sent to Claude Opus as an example instead of $20/month subscriptions. AI coding agents autonomously purchase services across providers, optimizing cost and quality in real-time. Cloud compute: Pay per CPU-second or GPU-second at true utility pricing. AI workloads purchase compute from the cheapest available provider, migrating mid-training if prices drop. Data services: Pay $0.50 per research paper instead of $5,000/year institutional subscriptions. AI agents autonomously purchase training data, validation sets, and real-time feeds as needed for model training. Sales and Marketing: A Creator pays an AI agent $7.50 to market their latest video across socials, and the Agent uses the funds to create, schedule and send video shorts, pay its own AI supply chain, and keep the remainder as profit. Healthcare: Pay $25 for AI triage + $50 for physician consult instead of $200 upfront. Unbundled, transparent, pay only for services received. Health monitoring AI agents autonomously purchase diagnostics when needed. Financial services: Gig workers get paid in real-time after each job. Micro-investors buy $0.50 of fractional shares. Cross-border remittances settle in seconds. AI financial agents autonomously manage bills, investments, and optimization. Every use case has the same requirements the video market validated: real-time micropayments, embedded finance, AI-agent autonomy, 95%+ margins. Total addressable market across these verticals: $2T+ What Comes Next We’re at an inflection point. The infrastructure that powered the first 30 years of the internet, built for humans, monthly billing, and platform control is breaking under the weight of real-time machine commerce. The Next 12 Months Our focus for the coming year: Technical Infrastructure: - Open sourcing core protocol components (Complete 2025) - Supporting 10,000+ API-to-AI transactions per day with a 10X expansion every quarter - The first TAPP native AI agent that can hold its own funds and transact (Q2 2026) - Expanding beyond video to developer tools, compute, and data services Market Expansion: - 2 major enterprise AI deployments - 1,000+ videos on Veeeu platform (continuing video market validation) - 50 premiere events for independent creators - 10-15 reference customers in AI services with documented case studies Ecosystem Development: - Banking integrations expanding globally - Partnerships with major cloud providers - Developer tools and documentation - Community programs for creators and developers The Bigger Vision This goes beyond payments. The question is about who controls the infrastructure of the digital economy. For the last 20 years, platforms have controlled everything; your data, your audience, your revenue, your access. They could change the rules anytime. They took half your money and made you wait 30 days. File-based assets flip this model. The bearer controls the asset. You own your audience data. You control your pricing. You set your terms. The platform becomes infrastructure rather than a landlord. This is how the internet was supposed to work. Decentralized control, but with infrastructure that just works; without complexity, without tokens, without volatility. Why This Matters The AI economy is inevitable. AI agents will transact with each other billions of times per day. Creators will continue producing the content that powers the internet. Developers will build services that require micropayments. The question is: What infrastructure will power this economy? The options are clear: legacy payment processors charging 3% on every transaction, blockchain solutions optimized for speculation, new platforms that reinvent the 50/50 split with better UX. Or something genuinely different: infrastructure built specifically for real-time, micropayment, user-controlled commerce. We’re building that last option. The video market validated the architecture. The AI economy provides exponential scale. The expansion is just beginning. The Work Ahead Building new infrastructure is hard. We spent years on R&D that nobody saw. We had to build six layers of technology from scratch because no suitable partners existed, our technology removed their revenue models. We’ve had failures. We’ll have more. Infrastructure plays are marathons. But we’ve reached the point where the products work, customers are using them, and the value is proven. The video market got us to the start line, and now we are scaling across the AI economy. Get Involved For AI Companies: If you’re building AI services and want to enable real-time micropayments, schedule a technical demo. For Creators: If you’re tired of platform economics and want 90% revenue share paid daily (not 50% paid monthly), join the Veeeu waitlist. For Developers: We’re building in public and will be open-sourcing components. Join the developer community. For Investors: We will be launching our seed round soon. Request our investor deck. For Everyone Else: Follow along. The AI economy needs better infrastructure, and we’re building it in the open. --- # Almost as Good as Paper URL: https://www.qatom.ai/articles/almost-as-good-as-paper Author: Starwater Heaven and Dann Published: October 26, 2024 How we cracked the Web's micropayment problem and a few other things as well. The first draft of a TODA file asset powered micro-transaction ecosystem was drafted at Big Bald Lake, Canada, 1 July 2017.We’ve been quiet here for some years. I believe now we have some thing to talk about that everyone can try out, and soon millions will be able to experience. Micropayments were always a part of the World Wide Web vision.  A set of standards and an HTTP Error message 402 was even created to handle instances where a micropayment was required but not received. Why didn’t they happen?… The World Wide Web. The original vision of the World Wide Web was an underlying web infrastructure that included a vision to enable instant micropayments for online services without need of login, subscription or payment processors.  It was to be a digital mirror of taking coins out of your pocket and putting them into a vending machine. A digital consumer could purchase a single video, song, or article. Businesses could micropay multiple services (e.g., meeting transcriptions, document processing, satellite images, chatbot conversations). Citizens could micropay for myriad public sector services covering transit, parking and much more. None of this happened and we got the commercial Web instead. The Micropayments Trllemma blocked digital micropayments. Three challenges blocked the vision. First, the cost was too high to efficiently process payments under a dollar. Second, the technology didn’t exist to give micropayers control of their funds to micropay anywhere without being locked in.  Third, there was no universal single tap and pay online checkout experience, which degraded convenience. By 1999 the first wave of micropayment initiatives were shelved. Over the next two decades over 100 projects were launched. These attempts didn’t survive the double hit of the market ‘free content for advertising’ wave and the cost, control, and convenience trilemma of problems. Micropayments work in the physical world with cash. Micropayments have always existed because people paid each other with coins and bills.  Physical micropayments work because the buyer and seller in a transaction do all the work bringing cost down. Physical micropayments work because coins and bills are portable between systems (e.g., bag, wallet, pocket, safe) and the bearer exercises strong control. Physical micropayments work because it’s convenient for the micropayer.  These qualities solve for cost, control and convenience and are different to how digital database and blockchain systems function.  Finding a digital way to replicate physical assets transaction would solve the aforementioned trilemma challenge. TODA began in early 2016, when Toufi Saliba called Dann Toliver at four in the morning with a wild idea… That answer to the trilemma challenge is TODA File technology, the result of a 7 year deep-tech initiative led by researchers from TODAQ Labs, Cambridge University, the CRDC, UCL and  others.  Our thanks to the UKRI Ministry and ARM Technologies for their support. TODA began in early 2016, when Toufi Saliba called Dann Toliver at four in the morning with a wild idea. They were experiencing cost, throughput, and latency issues while scaling applications with blockchain components, like a PKI for end-to-end encrypted email. The idea was to give each file a unique number, and use a Merkle tree and a fixed number of validators to ensure ownership was limited to a single node in each block of time, using just the computational power of the devices themselves. They worked on it as a science experiment for months, trying to get traction on the problem, until the pieces finally started to fit together. In the summer of 2016 Lila Tretikov and Todd Gebhart came onboard and helped guide the early strategic steps. Later that year Hassan Khan joined forces, forming TODAQ, the first venture on TODA. Adam Gravitis took the CTO role at TODAQ in spring 2017, managing the engineering team’s work on the reference implementation of the protocol. The researchers, implementors, executives, and partners who have joined along the way would fill more than this article. The first use case we focused on was supplementing cash in cash-primary regional economies in a nonextractive way. Doing this would improve countless lives by enabling efficient delivery of financial services. Regional products like M-Pesa and bKash help prove this hypothesis. A globally available system would have the potential to help billions of people, and a system without profit extraction could offer even greater benefits. Doing this turns out to be rather difficult. In fact it’s impossible without something like TODA. In a world where digital things are just information, a third party must always manage that information. They must be compensated for that work. That compensation extracts value from regional economies. Deliver $100 in aide and move it around via credit cards, and in just a few years over $90 of it has been extracted from that regional economy. With the current implementation of blockchains like Ethereum and Bitcoin there can even more extraction. This is not a small problem. It’s hard even with TODA. Building the infrastructure to maintain a locally operated, globally interoperable TODA installation can be done, with relatively minor expenditures. Even better would be relying solely on people’s mobile devices, an active area of research. Having options like those available at all is due to having this hard case as our primary target. This shaped the protocol, forced us to hack away at inefficiencies and to focus maniacally on places of value leakage. We embraced fragility, turning all the robustness and resiliency knobs down. This gave us access to the hardest use cases, those most sensitive to extra economic weight like micropayments, at the core protocol level. Adding robustness for use cases that need it is easy in comparison: you can easily have as much robustness as you are willing to pay for. It also forced us to prioritize asymptotic computational complexity over constant factor optimisations. How adding more nodes impacts a single transaction, for example, is central to the protocol. How much work a single transaction requires in isolation is secondary. Indeed, there are a great many optimisations we could bring to TODA, but they add complexity and need to be weighed carefully. Asymptotic limit usage scaling. Complexity limits feature scaling. Flat foundations are easier to build on. We made a number of other choices in those early days that were counterintuitive or contrary to market trends. We got a lot of pushback for it. In some cases even we weren’t sure they were right, but in hindsight it’s clear they laid the groundwork for TODA being what is today. We decided early on that we didn’t want the TODA File Protocol to be a source of revenue for us, or for anyone. It was clear that the economics of blockchains, which are necessary to allow them to spread trusted state management over many untrusted nodes, also preclude their use in cost-sensitive use cases, and trend toward volatility, extraction, and consolidation. The deep integration of tokens causes them to behave more like products than protocols. Important products, that provide an important service, but TODA needed to take a different course to achieve our goals. So we worked to remove the internal currency from the protocol, and focused the revenue model on partnering to build products and services on top of TODA while leaving the protocol pure. Internal protocol currencies cover a multitude of sins. Any time there’s an incentive misalignment, or extra work needs to be done, or you need to keep someone honest, you can throw economics at it to sort it out. It’s the duct tape of decentralised protocol design. If the protocol doesn’t understand a currency then those patches have to be torn out, and all those areas ground down and restructured. It was a lot of work, and it wasn’t clear it was even possible. When we finished, though, what we were left with was something small and simple and clean. A protocol that describes how to create a globally unique digital thing, how to efficiently transfer the ownership of that thing, and little else. By extracting the base currency we’d forced efficiencies, removed a variety of economic weaknesses, and made it a protocol instead of a product. Removing the internal currency means all things created on TODA are treated as equals. It means the protocol works for any kind of asset. Anything you can print on paper, we used to say. And more, as it turned out. Another big decision came in balancing privacy and compliance. This is actually quite a bit easier in a cash-style system than a stateful, managed model. Cash already has a decent story around privacy and anonymity, but regulatory compliance is difficult because it’s hard to prove where it came from. TODA’s proof of provenance changes this dynamic, though, by allowing files to have additional metadata attached during each transfer. This metadata could contain identifying material, or proof of limited attestations (like “I am legally allowed to drive” or “this is a legitimate business account”). Voluntarily adding this to the file’s POP would allow entities like financial institutions, governments or other large organizations to fulfill their compliance requirements. In order to preserve the ability for this particular file to be used in those use cases, then, one ought to ensure that its POP contains all the required material. Otherwise it will be difficult to use in those situations, reducing the utility of the file. Thus we render unto governments their due for assets they manage, while keeping impedance low for things like stickers, songs, and micropayment assets. Over time we came to identify the qualities physical things had that digital things lacked as transferability, agency, possession, and permanence. Transferability means when the owner transfers it they don’t need to notify a third party. No one else has to do any work, no one else needs to be compensated. We refer to this ability to be transferred losslessly as value preservation. Agency means you can do all the things you can usually do with a physical item: give it away, sell it, rent it, lend it, and so on. Possession means the source of truth of the ownership is in your hands, and decisions made in some corporate headquarters can’t take it away from you. And permanence means if you take care of it well there’s a chance you can pass it down to your kids. Those qualities imbue every file in TODA, providing an important part of the foundation for restoring ownership and control of identity, assets, and data to every individual human. Today, the TODA File Protocol has been implemented as a Web integrity network. The integrity network powers issuance, updating and transferring between any system of a new type of unique digital bearer asset, called a TODA file.  TODA files are a new file type that are digitally unique bearer assets (e.g., coins, bills, credentials, and paper documents. TODA files can be controlled, stored, and updated by any empowered system, and can be transferred without need to connect to the issuing system. These qualities strip transaction costs, restore bearer control, and extend the convenience of universal tap and pay of physical store checkout to the online experience. During 2023, the first version of a working micropayments solution called TAPP (Tapp And Privately Pay) was built by TODAQ Micro which you can find out more about here: https://www.todaq.net. It’s a low code solution allowing any digital content or service to accept micropayments, provide instant paybacks and micro-distributions.  Everyone controls their own assets and records, and best of all anyone can issue any type of asset that can be micro transacted as well. Rather than explain a brand new tech stack, it seemed easier to just put it into everyone’s hands with an accessible, powerful and fun demo.  So the team went retro. In addition to bringing on sports, media, entertainment, gaming, healthcare, education and AI partners to deploy micropayments, we’re very pleased to release old game with a new twist. PONG, created in 1972 was one of the earliest video games.  It is available online for free and is largely unchanged from it’s basic 2D form from 52 years ago.  Earlier variations of micropong included a micropong where the form factor reduced the playable game to the size of a penny, and a micropong version that allowed players to control the game through a microphone.  As homage, we thought the natural next step of micropong, was a micropayable release that demonstrated the capabilities of TODA files and TAPP micropayments.  Given the years of work that led to that moment, we had no idea that it would take another 8 months of work to make the transaction dance of micropayments, instant paybacks, micro-distributions, and more flow in just the right way. This latest version of micropong fuses micropayments, gaming, rewards, and music.   The micropong experience starts when an unknown visitor goes to the micropong  website.  They instantly pay 30 cents, no processing fees, and start a 2 person PVP game. Player 1 also picks a song which will play for both players. Player 1 invites one of their friends to join, who also micropays 30 cents and joins as Player 2. The game session now has 60 cents. They play each other to be the first to 10 points. The winner is instantly paid 40 cents, the music artist is instantly paid 10 cents, and the game treasury gets 10 cents. The music studio that helped produce the chosen song is paid a penny from the artist’s 10 cents.  The audio marketplace that provided beats and samples for the song is paid 2/10th of a penny from the artist’s 10 cents.  Three emerging and ground breaking musicians - Tara Jam, Sean Leon, and Nanu - joined the micropong team so game players could enjoy their music.   Their larger goal was to change the game and show that fair, transparent, and real-time compensation for all artists is possible. For consumers, these kind of one TAPP micropayments will enable a new complementary option to subscriptions. Non-subscribers can directly micropay for content or micropayable content can be shared by empowered subscribers. For streaming and publishing platforms, this will add revenue streams. It’s not just a consumer thing, platforms can instantly split a single micropayment and distribute to sharers, creators, copyright holders, suppliers, and their staff – removing nearly all back office and processing costs. These frictionless circular payment flows between systems and devices apply to cloud API marketplaces, embedded finance and insurance services, municipalities, e-commerce, and supply chains. New micropayment markets will bring power to creators and consumers, generate new sources of revenue, speed up cash cycles, and greatly reduce back-office costs and liabilities for businesses. You can try out micropong here: https://www.todaq.net/story-of-micropong --- # Press release: Agents proved they will pay. Qatom makes sure the payment can be trusted. URL: https://www.qatom.ai/press-releases/accountable-agent-payments Published: October 7, 2026 Qatom launches its accountable payments layer for the agent economy: payment, delivery and a verifiable receipt in one call, with no public ledger, no gas and 0% transaction fees. Toronto, October 2026 — Qatom, the commerce layer that turns APIs and data into storefronts AI agents can buy from, today set out its answer to the growing trust problem in agent payments. In 2026 AWS, Stripe, Coinbase, Visa and Mastercard all launched ways to give AI agents a wallet. Open protocols such as x402 showed that software can pay software over a plain web request. The next question is harder: can a business trust the payment when an agent is on the other end? Independent research says the market is not there yet: - Volume is mostly noise. Visa and Artemis put adjusted x402 volume at roughly $15M through April 21, 2026, across about 109.6M transactions, an average of about $0.14 a payment. TRM Labs estimates that only 0.6% to 7.5% of screened x402 commerce came from AI agents. - Payments can fail after delivery. A July 2026 study accepted to USENIX Security 2026 found 49 security-rule violations across 15 x402 payment facilitators, which together cover about 99% of observed x402 transactions, including ways to get services without paying. The affected parties have since adopted fixes, including Coinbase. - No one owns the outcome. Checking a payment does not lock the funds, and refunds and disputes have no owner. What Qatom does differently Qatom ties payment, delivery and the record into one transaction, so a seller is never asked to deliver first and hope to be paid. - Settled in the call. The payment and the service land together, in under a second. - Proof that travels with the money. Each payment carries its own ownership and history, so it can be verified locally, even offline, with no public ledger. - Hard spend limits. Every agent wallet carries a budget that stops spending the moment it runs out. - One receipt per call. Each transaction creates a single record linking the request, the decision and the payment. - 0% transaction fees, no gas. Sellers keep 100% of every sale and pay a flat subscription. Qatom is built for regulated sellers: banks, data owners, healthcare and defence suppliers who need private, on-premise or air-gapped deployment that public-chain rails cannot offer. Proof in production Qatom has processed more than 100,000 payments in production for customers selling APIs, data and media to AI agents. “The industry proved that agents will pay. Now it has to prove those payments can be trusted. Builders shouldn’t have to choose between an open protocol and a guarantee. Qatom gives sellers both: every call is paid, delivered and recorded together, and nothing about their business sits on a public ledger.” — Hassan Khan, CEO, Qatom About Qatom Qatom turns any API, dataset or digital service into an agentic storefront that humans and AI agents can find, buy from and pay per call. Qatom has been in production since 2023, on infrastructure built on the TODA File Protocol and the ADOT Protocol: every payment carries its own cryptographic proof of ownership and history, verifiable anywhere, with no public ledger. Sellers start free at qatom.ai. Media contact press@qatom.ai Sources - Forkast, Visa and Artemis adjusted x402 volume: https://forkast.news/visa-artemis-the-0-14-reality-of-agent-commerce/ - Decrypt, TRM Labs x402 research: https://decrypt.co/378103/ai-agents-spending-money-research - When HTTP 402 Meets the Blockchain (arXiv 2607.19545, Jul 2026): https://arxiv.org/abs/2607.19545 - 4Pillars: Centralized responsibility is all x402 needs (Jul 2026): https://research.4pillars.io/en/research/centralized-responsibility-is-all-x402-needs - CoinDesk: demand is not there yet (Mar 2026): https://www.coindesk.com/markets/2026/03/11/coinbase-backed-ai-payments-protocol-wants-to-fix-micropayment-but-demand-is-just-not-there-yet - [Product walkthrough](https://www.qatom.ai/walkthrough): every step a person takes on Qatom, for buyers in AI chat, sellers in the Qatom Dashboard and owners in the Qatom Console. --- # Capabilities Index Source: https://www.qatom.ai/capabilities Everything a person can do on Qatom, step by step: buyers in AI chat, sellers in the Qatom Dashboard, owners in the Qatom Console. Open any capability for what it is for, how to do it, what you will see and what to watch for. Qatom does more than the steps shown here: a twin can hold any asset or currency, and Qatom is modular, so builders pick which parts Qatom handles. ## Buyer (In AI chat) A buyer is a person, or their agent, who finds and pays for catalog items from Claude, Grok, Muse or any MCP client. ### A1. Connect your AI to the whole Qatom catalog Add the Qatom master MCP as a custom connector (Claude, Grok, Muse, any MCP client) The master MCP is the one connection a buyer needs. It gives your AI every public catalog item plus the wallet tools. - Where: Client settings (Claude: Settings → Connectors) - Who: Anyone How: 1. In Claude, open Customize → Connectors → Add → Add custom connector. 2. Name it Qatom, enter the URL https://mcp.m.todaq.net/mcp and click Continue. 3. Leave the detected settings as they are (Authentication: Sign in now; OAuth client: Register automatically) and click Add. 4. Click Connect; Qatom's sign-in page opens (A2). 5. In Muse, ask in chat: "I'd like to connect to the Qatom MCP at https://mcp.m.todaq.net/mcp". Muse shows it as a "Todaq" connector card: click Connect, read Meta's custom-connector notice, click Connect again and continue to Qatom's sign-in page. 6. In Grok, use grok.com/connectors → Custom with the same URL. In any other MCP client, add the same URL as a remote MCP server. What you’ll see: Qatom appears in your client's connector list and its tools, such as catalog_search, become available. Watch for: - Use the master MCP URL for buying; a seller's own instance URL is a different connection (A22). Link: https://www.qatom.ai/capabilities#A1 ### A2. Sign in once with an email code or passkey Sign in to Qatom (email code or passkey) and approve the connector's access Signing in links your AI client to your Qatom wallets. Sign-in and registration are the same flow; a new email creates a wallet. - Where: OAuth page, pay.m.todaq.net - Who: Anyone How: 1. On "Sign in with Qatom", enter your email and click Continue. If you already have a Qatom wallet, use the email connected to it; any other email creates a new wallet. 2. On "Verify your identity", enter the 6-digit code sent to your email, or use Sign in with a passkey next time. 3. The first time, Qatom offers "Sign in faster": click Set up a passkey (recommended, S11), or Not now. 4. Next it offers "Add funds to your wallet" (A7). Top up now, or click Skip for now. 5. Back in your client, Qatom shows as connected. What you’ll see: "Connected to Qatom" in your client, with Qatom's tools listed (in Claude: under Tool permissions). Watch for: - Set up a passkey first (S11): every sign-in and approval page then takes one tap instead of an emailed code. - Use the same email every time. A different email creates a new, empty account and wallets, and money in your old wallet won't show. - If you already have a Qatom wallet, use the email connected to it. - An invalid_grant error is a server-side problem; don't keep re-authorising in a loop. Link: https://www.qatom.ai/capabilities#A2 ### A3. Get your own wallet and your agent's wallet First sign-in creates the account, primary twin and agent twin The first sign-in sets up two wallets. Qatom calls each wallet a twin: a small secure app that holds your money as USD-TDN, a US-dollar token (the Qatom Console shows it as TDN; it is the same unit). Your primary wallet (primary twin) is yours; your agent wallet (agent twin) is what your AI spends from. - Where: Automatic - Who: Anyone How: 1. Complete the first sign-in (A2). 2. Ask your agent: "Check my Qatom agent wallet." It calls agent_wallet_info. 3. Note your primary wallet (yours, protected by sign-in) and your agent wallet (what your agent spends). What you’ll see: agent_wallet_info lists your primary wallet and your agent wallet with their USD-TDN balances. Watch for: - The agent can never spend more than its twin holds, and never touches your primary wallet or card. - Plans are for sellers only; buying never needs a plan. - The first time your agent uses a Qatom tool, Claude asks: Deny, Always allow or Allow once. Always allow on the read-only tools (such as Agent wallet info) saves a click every time; keep paying tools on approval. Link: https://www.qatom.ai/capabilities#A3 ### A4. Let your agent work on your seller account Open your seller account to your AI chat (choose the account the connection may use) If your login owns a Qatom seller account, your agent can read it and, with your approval, change it from chat. First you choose which seller account it may use. This is a separate yes from connecting Qatom: until you choose, the account tools answer that no account is chosen. - Where: account_choose - Who: Account member How: 1. Ask your agent to use your Qatom seller account; it calls account_choose and gives you a link (it works once and expires in 15 minutes). 2. Sign in with your passkey, or your email and the code sent to it, using the email the agent is connected with. 3. The page says which app is asking (for example "an app that calls itself Claude"), what the agent will see (catalog, wallets, MCP server and plan), and which account it uses now. Pick the account and click Use this account. 4. When it says "Done. The agent now uses ", go back to the chat. To switch later, ask the agent to choose again. What you’ll see: The agent can now read the account: its plan and billing, wallets, catalog, sales and MCP server. Watch for: - Choosing an account lets the agent read it; every change still asks for your approval (B23). - Only seller accounts your login owns are offered. A login with no seller account doesn't get the account tools at all. - Check which account you chose before you fund or approve anything; purchase approvals don't name the paying wallet (A31). Link: https://www.qatom.ai/capabilities#A4 ### A5. Check what your agent can spend See your wallets and balances (primary and agent twin) Your agent twin's balance is its hard spending ceiling. Checking it before buying avoids failed purchases and surprises. - Where: agent_wallet_info, account_wallets - Who: Account member How: 1. Ask: "Check my Qatom wallets." The agent calls agent_wallet_info and lists your primary and agent wallets. 2. If you also sell on Qatom, ask for your business account's wallets; the agent calls account_wallets. 3. Read each wallet's name and USD-TDN balance. What you’ll see: The agent lists each wallet with its USD-TDN balance. Watch for: - Balance reads can lag a purchase by a few minutes; read again before concluding anything. - The account_ tools (account_choose, account_wallets, account_dashboard_link and the rest) are listed on some connections and not others, and they work only once a business account is chosen. (to confirm) Which connections list them. Link: https://www.qatom.ai/capabilities#A5 ### A6. Give each wallet a name you recognise Rename a wallet Clear wallet names make it easier to know which wallet you fund and approve for, especially with several wallets. - Where: account_rename_wallet - Who: Owner How: 1. Ask your agent to list your wallets (A5). 2. Ask it to rename one, giving the wallet and the new name; it calls account_rename_wallet. 3. List the wallets again to check the new name. What you’ll see: The wallet list shows the new name. Watch for: - You can also rename a twin in the Qatom Dashboard under Twins → twin → Name → Save name. - The account_ tools (account_choose, account_wallets, account_dashboard_link and the rest) are listed on some connections and not others, and they work only once a business account is chosen. (to confirm) Which connections list them. Link: https://www.qatom.ai/capabilities#A6 ### A7. Add funds to your wallet by card Top up the primary wallet by card Your primary wallet holds the money you then hand to your agent. A card top-up is one way to fund it. - Where: fund_primary_wallet → card page - Who: Owner - Money: yes How: 1. Ask your agent to fund your primary wallet; it calls fund_primary_wallet. 2. Open the card page it returns. 3. Complete the card page yourself and pay. 4. Check the primary wallet's balance (A5). What you’ll see: The primary wallet's USD-TDN balance goes up once the card payment completes. Watch for: - Right after your first sign-in, Qatom offers "Add funds to your wallet": 5, 10, 20 or 50 US dollars, by Apple Pay or card. "Load funds to agentic wallet" is ticked, so the money goes straight to your agent wallet, with no separate transfer (A8). Untick it to keep it in your primary wallet. - Your agent never sees or uses your card; you complete the page yourself. - If the card page returns an error on a new wallet, fund it another way (A32). - Card top-ups carry card fees. (to confirm) Whether the fee is added to the charge or taken from the amount. Link: https://www.qatom.ai/capabilities#A7 ### A8. Give your agent a small spending budget Move funds from primary to the agent twin Your agent can only spend what its own twin holds. Moving a small amount sets a hard limit on what it can buy. - Where: transfer_to_agent → approval - Who: Owner - Money: yes How: 1. Ask your agent to move an amount from your primary wallet to your agent wallet; it calls transfer_to_agent. 2. It gives you an approval link and a push to your TODAQ app (Qatom Authenticator). Check the account, wallet and amount (A31), then approve. 3. Tell the agent you have approved; it calls again with the approval id to finish. Nothing moves until it does. 4. Check the agent wallet's balance with agent_wallet_info. What you’ll see: The agent twin's balance rises by the amount moved, and the primary falls by the same. Watch for: - Fund the agent like handing over a little cash; it can't reach your primary wallet. Link: https://www.qatom.ai/capabilities#A8 ### A9. Let small purchases go through without asking Set the auto-approve limit for agent purchases Purchases at or under your auto-approve limit settle without asking you. Above it, you approve each one. - Where: Checkout approval modal (web), or the TODAQ app (Qatom Authenticator) - Who: Owner How: 1. Start any agent purchase that asks for approval. 2. In the checkout approval modal, set your auto-approve limit in USD-TDN. 3. Set it to 0 if you want to approve every purchase. 4. Set the limit in the modal, then approve or decline the purchase in front of you. (to confirm) The exact control names. What you’ll see: The next purchase at or under the limit completes without an approval prompt. Watch for: - Set the limit with retries in mind: auto-approve also lets a retried call through, so a retry can charge twice (A28). - Only you can change the limit; an agent's token is refused. - The limit covers carts too: a cart whose total is within it is paid at once, with no approval. Link: https://www.qatom.ai/capabilities#A9 ### A10. Find what your agent needs in the catalog Search the catalog by need or name Search is how an agent finds items to buy. It returns every public item that matches, with price and seller. - Where: catalog_search - Who: Anyone How: 1. Ask in plain words: "Search the Qatom catalog for weather." 2. The agent calls catalog_search with your query. 3. Ask it to narrow or page through results if there are many. What you’ll see: A list of items, each with id, name, description, price, seller and input schema. Watch for: - An item with no seller line (or seller None) comes from a seller who hasn't set a business name, so you can't tell whose item it is. - The catalog also holds test listings; check the seller and description before paying. - Private items don't appear in master search; they are only on the seller's own instance (A22). Example: Search for "Qatom Demo" to find the demo store's feedback, seller guide skill and space station video items. Link: https://www.qatom.ai/capabilities#A10 ### A11. Know what you get before you pay Read an item: price, seller, inputs, description, read-me The listing and the seller's read-me say what an item returns, what it costs and which inputs it takes. - Where: catalog_search result, seller llms.txt - Who: Anyone How: 1. Ask your agent to show one item from the search results. 2. Check the price in USD-TDN, the seller name and the inputs in the schema. 3. Open the llms.txt link in the description for examples and error meanings. 4. Look for a free check or preview item beside a paid one. What you’ll see: Your agent explains the item's price, seller, inputs and what it returns. Watch for: - Prices show up to three decimals; the smallest paid price is 0.001 USD-TDN. Qatom's own tool results and receipts always show three decimals, so a free item shows as 0.000 and 2 shows as 2.000. Example: The Qatom Demo store serves its read-me at https://qatom-demo.agentkepler.tech/llms.txt, listing each item, its price and inputs. Link: https://www.qatom.ai/capabilities#A11 ### A12. Use free items at no cost Call a free item Free items cost 0 and return their answer in the receipt. Sellers use them for checks, previews and feedback. - Where: agent_checkout, free - Who: Signed-in buyer How: 1. Find a free item with catalog_search. 2. Ask your agent to call it; it uses agent_checkout with the item id and arguments. 3. Read the answer inside the receipt. What you’ll see: A receipt for 0 USD-TDN with the seller's answer inside. Watch for: - A free item can still ask you to approve before it runs. Approving moves no money; this step will be simplified. Example: Qatom Demo: customer feedback is free and returns a reference id. Centaur League's search challenges, spectate and leaderboard are free too. Link: https://www.qatom.ai/capabilities#A12 ### A13. Let your agent buy and use an item Buy a paid item from the agent twin agent_checkout pays from the agent twin and returns the seller's answer in the same step. Your agent asks you before paying. - Where: agent_checkout - Who: Signed-in buyer - Money: yes How: 1. Pick the item and inputs (A10, A11). 2. Ask your agent to buy it; it confirms the price with you first. 3. The agent calls agent_checkout with the item id and arguments. 4. Within your auto-approve limit it settles at once. Above it, the agent gives you an approval link and waits; approve, tell the agent, and it calls again to finish (A14). What you’ll see: A receipt with a transaction id and the seller's answer, and a lower agent twin balance. Watch for: - "Invalid payment request" can mean the seller's endpoint rejected the call; check your wallet history (A28) to see whether you were charged, then ask the seller (A27). - The agent wallet's balance is a hard ceiling; top it up first if needed (A8). - To buy several items at once, use a cart (A33). Example: Buying Qatom Demo: seller guide skill (0.005 USD-TDN) returns a 15-minute download link, version, SHA-256 and install steps. Link: https://www.qatom.ai/capabilities#A13 ### A14. Say yes before larger purchases settle Approve a purchase above the auto-approve limit Above your auto-approve limit, nothing is paid until you approve. This keeps you in control of every larger purchase. - Where: Web approval page, or the TODAQ app (Qatom Authenticator) - Who: Owner - Money: yes How: 1. When your agent asks, open the approval link it gives you, or the push on your phone in the TODAQ app (Qatom Authenticator). 2. Check you are signed in to the account you mean to pay from (A4), then check the item, the seller it pays and the amount (A31). 3. Tap Approve, or Dismiss to decline. 4. Tell the agent you have approved. It calls again with the approval id and shows the receipt; nothing happens until you tell it. What you’ll see: The approval page confirms your decision and the agent shows the receipt, or reports the decline. Watch for: - Approval links expire after about 15 minutes and belong to one account. If one expires, ask the agent to start the purchase again; the old approval can't be used. Link: https://www.qatom.ai/capabilities#A14 ### A15. Keep the transaction id for every purchase Read the result and the receipt (transaction id) The receipt holds what you bought and the seller's answer. Its transaction id is what you quote in any refund request. - Where: agent_checkout receipt - Who: Buyer How: 1. Ask your agent to show the full receipt. 2. Note the transaction id, item, amount and the seller's answer. 3. Keep the transaction id somewhere safe. What you’ll see: A receipt showing the transaction id, item, amount paid and the seller's response. Watch for: - The receipt line comes from the seller's descriptor, which can differ from the item name. Example: Qatom Demo receipts carry a one-line summary and a display link, such as "Watch the stream" for the video item. Link: https://www.qatom.ai/capabilities#A15 ### A16. Pay by card without setting up a wallet Buy as a guest by card, no wallet Guest checkout lets a person pay for one item by card. It suits single purchases where no wallet exists. - Where: guest_checkout → checkout page, verify email - Who: Anyone - Money: yes How: 1. Give your agent the item's inputs; it collects them in chat, then calls guest_checkout for a checkout link. 2. Open the checkout page, then enter and verify your email to receive a secure receipt with proof of purchase. 3. Enter your card details yourself and pay. What you’ll see: The checkout page confirms payment. (to confirm) Where the item's result is delivered. Watch for: - Card payments have a minimum of about $0.50, so small items suit agent wallets instead. Link: https://www.qatom.ai/capabilities#A16 ### A33. Gather several items into one cart Put several items in one cart and change it before paying A cart holds several items, from one seller or several, so you pay once. You can change quantities and inputs, or take items out, until paying starts. - Where: AI chat (Qatom connector) - Who: Buyer, or their agent How: 1. Ask in plain words for the items you want, for example "Get me the space station video and two copies of the seller guide skill." 2. Answer the agent's questions for each item's inputs; it adds each one with cart_add_item (up to 20 of an item). 3. Ask to see the cart; the agent calls cart_view and shows each line, its quantity, price and the total. 4. Change your mind freely: the agent uses cart_update_item for a quantity or inputs, and cart_remove_item to take a line out. What you’ll see: A cart summary listing each item, its quantity and price, and the total in USD-TDN. Watch for: - Each copy of an item is a separate purchase with its own transaction id. - Line numbers carry on across carts, so the agent should look at the cart (cart_view) before changing a line. - To drop the whole cart, ask the agent to discard it (cart_discard); a cart someone has started paying can't be discarded. Example: On 12 Oct a cart held Qatom Demo: customer feedback (free), the seller guide skill (0.005) and the space station video (0.01, with a two-hour link): total 0.015. Link: https://www.qatom.ai/capabilities#A33 ### A34. Pay for the whole cart at once Pay for a cart: from the agent wallet with one approval, or by card at one link A cart is paid in one go: from your agent wallet with a single approval for everything, or by card at one checkout link. Each item is then delivered to its seller with its inputs. - Where: AI chat (Qatom connector) - Who: Buyer, or their agent - Money: yes How: 1. Choose how to pay. Agent wallet: the agent calls cart_pay. Card: the agent calls cart_checkout and gives you one link for everything. 2. Agent wallet within your auto-approve limit: it is paid at once. Above the limit: approve the whole cart once (A14, A31), tell the agent, and it calls cart_pay again with the approval id. 3. Card: open the link, check the items and total, and pay yourself. The cart can still be changed until paying starts, and the link shows the change. 4. Read each item's answer in the agent's reply: links, files or confirmations. What you’ll see: The agent shows every item's result (for example a stream link, a download link and a feedback reference) and one receipt email lists every item and the total. Watch for: - Each item's answer comes back once, in that reply. Ask the agent to pass on every link straight away; asking again won't bring it back. - If a price changes after you approve, nothing more is charged and you are asked again. - A long cart may take more than one call; the agent carries on with the same approval. - To stop partway, ask the agent to finish the cart (cart_finish): you keep what was bought, the rest is cancelled, and you get a receipt. - The receipt email shows the cart's id; each item's own transaction id is in the agent's reply. Example: Paid 0.015 from the agent wallet on 12 Oct, within a 1 USD-TDN auto-approve limit, so no approval: the feedback reference, a 15-minute skill download and a two-hour stream link came back in one reply. Link: https://www.qatom.ai/capabilities#A34 ### A17. Keep an emailed proof of every purchase Receive the emailed receipt with proof of purchase Every direct purchase, by agent or by guest card checkout, sends an emailed receipt. It gives you a record outside the chat for bookkeeping and refund requests. - Where: Email - Who: Buyer How: 1. Check your inbox after a purchase. 2. Open the Qatom receipt email. 3. Keep it with the transaction id from the chat receipt. What you’ll see: A receipt email with the purchase details. Link: https://www.qatom.ai/capabilities#A17 ### A22. Reach a seller's private and featured items Connect a seller's own MCP instance (private and featured items) Each seller has its own MCP instance. Private items are only reachable there, and featured items appear as named tools. - Where: Client settings, seller's MCP URL - Who: Anyone How: 1. Get the seller's MCP URL from the seller, for example from their website or llms.txt; it ends in .mcp.m.todaq.net/mcp unless they use their own domain. 2. Add it as a custom connector in your client, as in A1. 3. Sign in if asked (email code or passkey, as in A2). 4. List the tools to see the seller's featured items. What you’ll see: The seller's featured items show up as named tools in your client. Watch for: - Private items aren't in master search, and agent_checkout through the master MCP says they are not found. - (to confirm) Whether buyers sign in to a seller's instance the same way as the master MCP. Link: https://www.qatom.ai/capabilities#A22 ### A23. Act on a live board inside the chat Use an interactive MCP App view (board, card, player) Some sellers attach a live view to free tools, so you get a board, card or player in the chat. Money stays on Qatom. - Where: Seller's free MCP server, e.g. centaurleague.games/mcp - Who: Anyone How: 1. Add the seller's free MCP server as a second custom connector, e.g. https://centaurleague.games/mcp (no sign-in). 2. Ask for a view, for example "Spectate Centaur League" or view a match. 3. Use the view: drag pieces, offer a draw or resign on the board. 4. Keep paid steps, such as entry, on the Qatom MCP. What you’ll see: An interactive board or card opens inside the conversation. Watch for: - MCP Apps (boards, cards, players inside the chat) work in Claude, ChatGPT and Hermes today. Grok and Muse don't support them yet. - No purchase starts from inside a view; you approve money in Qatom's own flow. Example: Centaur League's view_match and spectate open a chess board in the chat; the agent recommends a move and the human plays it. Link: https://www.qatom.ai/capabilities#A23 ### A24. Open your stream link and watch Watch a purchased video stream A video purchase returns a player link with its own time-limited key. You watch in the browser until the key expires. - Where: player_url from the receipt - Who: Buyer How: 1. Buy the video item (A13); you can set ttl_seconds for how long the key lasts. 2. Open the player link from the receipt (shown as "Watch the stream"). 3. Let the player pick the quality; it adapts between 1080p, 720p and 480p. What you’ll see: The video plays in the browser player, with the poster shown first. Watch for: - The key is per purchase: anyone with the link can watch until it expires. - An expired or altered link answers 403; buy again to watch after expiry. Example: Qatom Demo: space station video (0.01 USD-TDN) plays a NASA public-domain fly-through; ttl_seconds runs 60 to 86400, default 3600. Link: https://www.qatom.ai/capabilities#A24 ### A25. Tell a seller what worked or didn't Send feedback to a seller Sellers add a free customer-feedback item by default. It is the direct way to reach the seller. - Where: Seller's free feedback item - Who: Anyone How: 1. Search the catalog for the seller's "customer feedback" item. 2. Ask your agent to send your message with agent_checkout; it is free. 3. Add your email to get a reply, and an order or item id if it is about one purchase. 4. Keep the reference id it returns. What you’ll see: A 0 receipt with a reference id confirming the seller received your message. Watch for: - Messages are 3 to 2,000 characters. - A not_configured (503) answer means the seller hasn't set up feedback yet; use the next step in A27. Example: Qatom Demo: customer feedback takes message (required), from_email and subject_ref, and returns a reference id. Link: https://www.qatom.ai/capabilities#A25 ### A26. Jump from chat to the web dashboard Open the Qatom web dashboard from chat Some tasks are done only on the web: secrets, API keys, an item's request headers, your card, your plan, a custom domain. The agent hands you a link to the right Qatom Dashboard page. - Where: account_dashboard_link - Who: Account member How: 1. Ask your agent for the page you need; it calls account_dashboard_link with that page (for an item's headers, with the item id). 2. Open the link in your browser and sign in if asked. 3. Check the Dashboard shows the account you meant before changing anything. What you’ll see: The Qatom Dashboard opens on your account at dashboard.qatom.ai. Watch for: - Never paste a secret, key or card number into the chat; the link exists so you enter them on the Dashboard yourself. - The Dashboard opens the account you last used there, which may not be the one you asked about. - The account_ tools (account_choose, account_wallets, account_dashboard_link and the rest) are listed on some connections and not others, and they work only once a business account is chosen. (to confirm) Which connections list them. Link: https://www.qatom.ai/capabilities#A26 ### A27. Ask the seller first, then TODAQ support Ask for a refund or report a billing problem Payments settle immediately, and refunds are the seller's decision. This path gets your request to the right person. - Where: Seller's feedback item, then support@todaq.net - Who: Buyer How: 1. Copy the transaction id from the agent's reply, the receipt or your wallet history. 2. Call the seller's free customer-feedback item with the transaction id and what went wrong. 3. If the seller has none, or there is no reply in a day or two, email support@todaq.net with the transaction id, the item and what happened. 4. Watch your wallet for a refund transfer. What you’ll see: A reference id from the feedback item; any refund arrives as a transfer to the wallet that paid. Watch for: - No refund timelines are promised. - For an item bought in a cart, quote that item's own transaction id from the agent's reply; the receipt email shows the cart's id. - A free Team Kepler feedback item is coming (S10); until it is in the catalog, use support@todaq.net. Example: Qatom Demo: customer feedback takes subject_ref, where you put the transaction id. Link: https://www.qatom.ai/capabilities#A27 ### A28. Check before you retry a paid call Retry safely: check the receipt and wallet before retrying a paid call; a retry is a new charge, even under auto-approve If output is cut off, the purchase may still have gone through. A retry is a new charge, so check first. - Where: Agent behaviour - Who: Buyer's agent - Money: yes How: 1. Ask the agent for the last receipt and its transaction id. 2. Read the agent twin's balance, allowing a few minutes for it to update. 3. Retry only if there is no receipt and the balance hasn't dropped. 4. If you were charged twice, follow A27. What you’ll see: One receipt per purchase you intended, and a balance that matches. Watch for: - Auto-approve lets a retry through without asking, so double charges happen silently. - A call the seller rejects can still be charged. Link: https://www.qatom.ai/capabilities#A28 ### A29. See how a seller's listings rate Check a seller's rating before buying (when Pirate Kepler's ratings are live) A rating service scores catalog listings so buyers can judge a seller before paying. - Where: Ratings and reviews tool - Who: Anyone How: 1. Search the catalog for the ratings and reviews tool. 2. Ask your agent to look up the seller's rating. 3. Read the score alongside the item's listing. What you’ll see: The seller's rating shows next to the item. Watch for: - (to confirm) Pirate Kepler's ratings are launching; the tool's name and what it returns are to be confirmed. Link: https://www.qatom.ai/capabilities#A29 ### A30. Approve purchases from your phone Install the TODAQ app (Qatom Authenticator) and sign in to the right twin The TODAQ app (Qatom Authenticator) lets you approve agent purchases on your phone. It must be signed in to the account that pays. - Where: Phone - Who: Owner - Secret: needs a secret How: 1. Install the TODAQ app (Qatom Authenticator) on your phone. 2. Sign in with the same account you use in chat. 3. Check it shows the wallet you approve purchases for (A31). What you’ll see: The app shows your account and wallet, ready for approvals. Link: https://www.qatom.ai/capabilities#A30 ### A31. Check the item, seller and price before approving Check what you are approving: item, seller, quantity and price With several accounts or wallets, approving the wrong one spends the wrong money. A quick check prevents that. - Where: Approval page / app - Who: Owner - Money: yes How: 1. Open the Purchase Approval request (the web page, or the TODAQ app, also called Qatom Authenticator). 2. Read the item name, "Payment to" the seller, the quantity and the price. 3. If anything is wrong, tap Dismiss. 4. Approve only when all of it matches what you asked for. What you’ll see: Purchase Approval shows Purchase Request, the item with "Payment to ", Qty and the price, with Dismiss and Approve. Watch for: - The approval doesn't name the paying wallet, so make sure you are signed in to the account you meant to pay from (A4). - For a cart, one approval covers every item at the prices shown; check the total and the item list. Link: https://www.qatom.ai/capabilities#A31 ### A32. Get first funds into a new wallet Fund a brand-new wallet (card top-up, or a transfer from another twin) A new wallet starts empty. You can fund it by card, or send USD-TDN to it from a twin you already hold. - Where: fund_primary_wallet, Console Send - Who: Owner - Money: yes How: 1. Try a card top-up first with fund_primary_wallet (A7). 2. Or, in the Qatom Console at console.todaq.net, open a funded twin and click Send. 3. Pick the currency, enter the amount and the new wallet's twin URL, add a memo, and let the owner click Transfer. 4. Or request TDN with Purchase TDN → Buy TDN and pay by wire or ACH. What you’ll see: The new wallet's balance shows the USD-TDN received. Watch for: - Some new wallets have returned an error (500) on card top-up; use a transfer instead. - Send needs the Transfer role on the sending twin; never retry a transfer that was accepted. - Buy TDN requests run from 0.50 to 100 USD and are filled once your payment lands. Link: https://www.qatom.ai/capabilities#A32 ## Seller (In the Qatom Dashboard) A seller turns an API, dataset, stream or game into catalog items that agents can find and pay for, using the Qatom Dashboard. The steps run in the order a new seller meets them. ### B1. Choose one thing agents will pay for Pick the first use case and price Start with one item that answers in one call and is cheap to serve. A small, clear first item is easier to test, price and explain. - Where: Seller guide skill / use-cases repo - Who: Seller How: 1. Install the seller guide skill in your agent: npx skills add StarwaterHeaven/qatom-seller-guide --skill qatom-seller-guide. 2. Answer its questions: what you have that is computed, current, unique or tedious, and who would ask for it many times. 3. Say what one answer costs you to produce. 4. Pick one or two first items from the use-case library, each with a free sibling check. 5. Set a price per call in USD-TDN: 0 for free, otherwise at least 0.001, with no more than three decimals. What you’ll see: The guide gives one line per chosen item: what it returns, who buys it, and a price idea. Watch for: - One catalog item has one price; several prices means several items. - Guest card checkout has a minimum of about $0.50, so sub-50-cent items suit agent wallets. - You can register (B34) before or after building; the guide builds first so your endpoint is ready when you create items. Example: The Qatom Demo store sells a video at 0.01 and an agent skill at 0.005, beside a free feedback item. Link: https://www.qatom.ai/capabilities#B1 ### B2. Put your product behind one HTTPS endpoint Build and host the endpoint (Worker template) Qatom calls your endpoint after each payment settles. You host it; the Worker template is the fastest start. - Where: Seller's own hosting - Who: Seller How: 1. Start from the Worker template: it reads one catalog.json, validates inputs, guards the paid route, serves /llms.txt and runs the feedback item. 2. Give each item one permanent lowercase ID, named inputs with types and ranges, and a one-sentence summary in every response. 3. Return every error with a code, a plain message and a next step (for example unknown_parameter 400, bad_value 400). 4. Deploy it to your host and call it directly to test, before testing through Qatom. What you’ll see: A direct call to a free route returns JSON with ok: true and a readable summary. Watch for: - Never accept raw SQL, code or query strings as inputs; turn them into named inputs. - Qatom may relay a failed call as a generic payment error, so test the endpoint directly first. - Keep secrets out of the endpoint URL; other dashboard users can see it. Example: The Qatom Demo store is one Cloudflare Worker behind three catalog items; its base URL https://qatom-demo.agentkepler.tech returns the store name and read-me link. Link: https://www.qatom.ai/capabilities#B2 ### B3. Make the paid route answer only Qatom Set the endpoint's secrets (secret path, fulfilment token) The paid route must refuse any call that did not come from Qatom. A fulfilment token, checked on every call, does that. - Where: Host secret store - Who: Seller - Secret: needs a secret How: 1. Generate the token on your own machine: openssl rand -hex 24. 2. Store it in your host's secret store (wrangler secret put QATOM_FULFILMENT_TOKEN) and in a password manager. 3. Have the endpoint check the Authorization header with a constant-time compare and answer 404 when it is missing or wrong. 4. Optionally add a secret path (/paid//...) for extra depth; other paths answer 404. What you’ll see: A direct call without the header gets 404; the same call with the header gets the answer. Watch for: - Never paste a secret into chat, docs, tickets or a listing. - A secret path sits in the endpoint URL, which other dashboard users can see; the header is the main guard. - Never echo the request URL or headers back in a response; rotate anything that leaks. Example: The Qatom Demo store's paid routes need both a secret path and a Sensitive Authorization header that Qatom sends on every fulfilment call. Link: https://www.qatom.ai/capabilities#B3 ### B4. Tell agents how to call and pay you Write and serve the agent read-me (llms.txt) llms.txt is a Markdown read-me for language models at your site root. Agents that find your items look for it before calling. - Where: Seller's site - Who: Seller How: 1. Generate it from catalog.json, or from the live public catalog (GET https://pay.m.todaq.net/v4/catalog/items); never write it by hand. 2. Include: seller name, a short summary, a Generated timestamp, how to call (catalog_search then agent_checkout), worked examples and the catalog table. 3. Add the input schemas, every error code with its next step, and resources including your feedback item. 4. Serve it at /llms.txt on your own domain and put that URL in every item description. What you’ll see: Opening /llms.txt on your site shows the generated timestamp and a table of your items with prices. Watch for: - Regenerate it on every catalog change so it never drifts from what is listed. Example: The Qatom Demo store generates https://qatom-demo.agentkepler.tech/llms.txt itself; Centaur League regenerates its read-me every 10 minutes from the live catalog. Link: https://www.qatom.ai/capabilities#B4 ### B34. Create your seller account and MCP server Register a new seller account: email code, Organisation, Billing (plan), Start my MCP server Registering creates your account, its wallets and your own MCP server. It is the same flow as signing in. - Where: pay.m.todaq.net → dashboard.qatom.ai/onboarding - Who: Owner How: 1. Go to dashboard.qatom.ai and choose New? Register an account. 2. Enter your email, click Continue and enter the emailed code, or Sign in with a passkey. 3. Step 1, Organisation: Business name, Display name, Billing email, optional address and tax number, then Next. 4. Step 2, Billing: choose a plan (Builder, Pro, Max or Enterprise), then Start my MCP server. What you’ll see: You land on the Dashboard Overview with your account name, plan badge and tiles for 1 MCP instance and 0 items. Watch for: - Set up a passkey first (S11): every sign-in and approval page then takes one tap instead of an emailed code. - The new server takes a few minutes to become healthy; the banner can say Running before MCP → Overview shows healthy. - If the email already has a Qatom wallet, it connects to that wallet. - The plan list may still show an older name for Max ($300/mo). Example: The Qatom Demo account was registered this way on the Builder plan on 11 Oct 2026. Link: https://www.qatom.ai/capabilities#B34 ### B5. Come back to your seller dashboard Sign in again later After registering (B34), you sign in the same way each time to manage items, your MCP server and settings. - Where: dashboard.qatom.ai - Who: Seller How: 1. Open dashboard.qatom.ai and click Sign in. 2. Enter your email and click Continue, then enter the emailed code; or Sign in with a passkey. 3. Wait for the Overview page to load. What you’ll see: The Overview shows your account name, plan badge, MCP status and tiles for MCP instances, catalog items and revenue. Watch for: - Set up a passkey first (S11): every sign-in and approval page then takes one tap instead of an emailed code. - Use the email you registered with; a different email creates a new wallet and account. Link: https://www.qatom.ai/capabilities#B5 ### B7. Set the seller name buyers see Set the business details and verify the billing email (the business name is the seller name buyers see) Your business name is the seller name on every item. Without it, search shows the seller as "None" and agents cannot tell whose item it is. - Where: Dashboard → Account - Who: Owner How: 1. Open Account (/dashboard/account). 2. Fill in Account name and Business name; add Business address and Tax number if you want. 3. Enter the Billing email and click Send verification email, then follow the email. 4. Click Save changes, before you publish any item. 5. From chat (after A4): ask your agent to change the business name; it calls account_update_details and you approve the change (B23). What you’ll see: catalog_search shows your business name as the seller instead of "None". Watch for: - Set it before publishing; items from a seller with no business name show seller None. - Delete this account on the same page is irreversible. Link: https://www.qatom.ai/capabilities#B7 ### B8. Choose the plan that fits your catalog Pick or change a plan: Builder (free), Pro ($20/mo), Max ($300/mo), Enterprise The plan sets how many agents, items and transactions the account gets. Builder is free; you can upgrade any time. - Where: First sign-up; Settings → Billing - Who: Owner - Money: yes How: 1. At sign-up, choose the plan in onboarding step 2. 2. Later, open Settings → Billing and choose a plan under Plans. 3. For a paid plan, Add a card. 4. The change takes effect now and is prorated. 5. From chat (after A4): ask your agent for your plan and billing; it calls account_info (plan, status, renewal, card on file, next invoice). Plan and card changes stay in the Dashboard; the agent gives you the page with account_dashboard_link. What you’ll see: Settings → Billing shows the new Current plan, and the Overview badge matches it. Watch for: - Builder's card lists 1 agent, up to 5 items and 25 transactions a month; no card needed. - The $300/mo plan is Max; some screens may still show an older name. Link: https://www.qatom.ai/capabilities#B8 ### B35. Get set-up help without leaving the Dashboard Ask the Dashboard assistant ("What would you like to set up?") The Dashboard home has an AI assistant. It answers set-up questions in place, such as how to create your first item. - Where: Dashboard home - Who: Seller How: 1. Open the Dashboard home. 2. Find the box headed "What would you like to set up?". 3. Pick a starter prompt, such as "create my first catalog item" or "how an agent pays", or type your own. What you’ll see: The assistant answers in the panel on the home page. Watch for: - Today the assistant guides you; you make the changes yourself. Link: https://www.qatom.ai/capabilities#B35 ### B9. List one thing for sale at one price Create a catalog item: name, descriptor (receipt line), price, method, endpoint A catalog item is one thing for sale at one price, with one endpoint. Its name becomes the tool name agents see. - Where: Catalog → New item, or account_create_item - Who: Seller How: 1. Open Catalog and click + New item (or ask your agent to use account_create_item). 2. Name: use a shared prefix, "Brand: item". Descriptor: the line on the buyer's receipt and card statement. 3. Price: 0 for free ("Enter 0 to offer it free"), otherwise at least 0.001 USD-TDN. 4. Method: GET, POST or PUT. Endpoint: the URL Qatom calls after payment, with no secrets in it. 5. Fill in the description, schema and visibility (B10, B11, B14), add the Authorization header (B12), then click Create item. What you’ll see: You return to the Catalog list, where the new row shows its method and price (Free or the amount). Watch for: - Renaming the item later does not change the Descriptor. - Choose visibility now; it can't be changed after creation (B14). - Use no more than three decimals in the price. Example: "Qatom Demo: space station video" is a POST item at 0.01 USD-TDN. Link: https://www.qatom.ai/capabilities#B9 ### B10. Tell agents what they get before paying Write the description (≤ 1,024 characters, points to llms.txt) Agents read the description to decide whether to buy. It should say what returns, what is free, and where to read more. - Where: Item form - Who: Seller How: 1. Say what the item returns, what is free, and which inputs change the answer. 2. Point to your llms.txt URL. 3. Add a not-advice line for health, finance, investment or legal items. 4. Keep it at or under 1,024 characters; the form shows a counter (x / 1024). What you’ll see: The counter under the Description stays at or below 1024. Watch for: - Don't list the individual things you cover (tickers, SKUs, IDs) or give an item count. - If the same content sells at two prices, each description says what the higher tier adds. - When the box is full, the counter can sit over the last line; check the text before saving. Link: https://www.qatom.ai/capabilities#B10 ### B11. Declare exactly the inputs your endpoint takes Add the input schema (additionalProperties: false); the editor validates it The schema tells agents which arguments to send. Qatom forwards only declared arguments and rejects the rest. - Where: Item form - Who: Seller How: 1. Read the schema off your endpoint: one required string that identifies the item, one optional property per real input. 2. Give every property a description, with its unit, range and default. 3. Set "additionalProperties": false. 4. Paste it into the Service schema editor in the form {"inputSchema": {...}} and click Format. What you’ll see: The editor shows "Tool arguments: …", or "Valid. The tool takes no arguments." when there are none. Watch for: - Leave out anything you pin in the endpoint URL or set as a fulfilment parameter. - No example IDs or item names in the schema; describe the format instead. - The New item editor uses {"inputSchema": {...}}, while existing items show a plain schema. Example: The Qatom Demo video item takes one optional input, ttl_seconds, from 60 to 86400, default 3600. Link: https://www.qatom.ai/capabilities#B11 ### B12. Guard every paid item with a secret header Add Request headers & secret parameters (Authorization header, Sensitive) and save them Whatever you set here goes on every fulfilment call to your endpoint and is never shown to buyers. It lets your endpoint prove the call came from Qatom. - Where: Item form, own Save button - Who: Seller - Secret: needs a secret How: 1. In Request headers & secret parameters, click Add header. 2. Name: Authorization. Sensitivity: Sensitive. Value: Bearer followed by your fulfilment token (type it yourself). 3. Use Add query parameter or Add URL value for an upstream API key; use Not sensitive for fixed settings such as tier or format. 4. On the New item form, Create item saves it; on the item page, click Save headers & parameters. What you’ll see: The header is listed in the section with its value masked. Watch for: - Sensitive values are never shown again; keep the value in your own secret store. - Headers are per item: three paid items on one endpoint each need the header. - On the item page, Save changes alone can leave the header unsaved; check it (B37). Link: https://www.qatom.ai/capabilities#B12 ### B13. Put inputs and secrets into the URL safely Use {input.name} and {secret.name} in the endpoint Placeholders let the endpoint URL carry a buyer input or a saved secret without exposing the secret. - Where: Item form - Who: Seller How: 1. Write {input.name} where a buyer input belongs, and declare that input as required in the schema. 2. Write {secret.name} where a secret belongs, and save it as a URL value under Request headers & secret parameters. 3. Example: https://api.example.com/points/{input.lat},{input.lon}/days?key={secret.apikey}. What you’ll see: A test purchase returns the answer for the inputs you sent. Watch for: - Never type a real secret into the endpoint URL; other dashboard users can see it. Link: https://www.qatom.ai/capabilities#B13 ### B14. Pick public or private once, at creation Choose public or private when you create the item Public items appear in the master catalog search. Private items are reachable only through your own MCP instance, and the choice is fixed. - Where: Item form - Who: Seller How: 1. On the New item form, leave "Private to this MCP instance" off for anything sold through the catalog. 2. Tick it only for items that stay on your own instance, such as an internal tool or a single customer's item. 3. Click Create item. 4. On the item page, check Visibility under Commodity. What you’ll see: The item page shows Visibility as Public or Private, read-only. Watch for: - In the Dashboard, visibility can't be changed later; to go public, duplicate the item (B36). - (to confirm) account_update_item now lists a private field, which may let an agent change visibility with your approval. - Private items don't show in catalog_search and can't be bought through the master MCP. - The catalog list shows no Private badge, and a private item's Availability text may still mention catalog_search. Link: https://www.qatom.ai/capabilities#B14 ### B15. Give an item its own named tool Feature items on the seller's own MCP instance A featured item is registered as a tool of its own on your MCP instance, so agents connected there see it by name. - Where: Item form - Who: Seller How: 1. Tick Featured on the New item form, or in the Agents section of the item page. 2. Save the item. 3. Open MCP → Tools and check the item under Featured items. What you’ll see: The item appears as a named tool, with its schema, on MCP → Tools. Watch for: - MCP → Tools may list platform tools under Featured items with a "could not be found" note. Check your own items there. Link: https://www.qatom.ai/capabilities#B15 ### B16. Give buyers a free way to reach you Add the free customer-feedback item (a default for every catalog), plus free checks beside paid items Buyers use the feedback item for questions, problems and refund requests. Free checks let agents confirm an input before they pay. - Where: New item at price 0 - Who: Seller How: 1. Open Catalog and look for a free customer-feedback item; if there is none, create one with + New item at price 0. 2. Name it with your prefix ("Brand: customer feedback"); inputs: message (required, 3 to 2,000 characters), optional from_email and subject_ref. 3. Have the endpoint store each message and forward it to your account email, with an hourly cap (30 is a good start). 4. Beside each paid item, add a free search, check, preview or status item. What you’ll see: A test call to the feedback item is free and returns a reference id. Watch for: - Never accept feedback nobody will read; the template answers 503 not_configured until storage or email is set up. - A free answer is one fixed fact or an identity check, never something a script can sample for the paid value. - Today the seller creates the feedback item; Qatom will create it automatically for new catalogs soon. Example: "Qatom Demo: customer feedback" is free and returned a reference id in testing; Centaur League's feedback item is the original reference. Link: https://www.qatom.ai/capabilities#B16 ### B37. Confirm the secret header really saved After saving headers, reload the item and check the header is listed (value masked) A paid item without its header fails every fulfilment call after the buyer pays. A reload is the only reliable check. - Where: Item page → Request headers & secret parameters - Who: Seller How: 1. After Save headers & parameters, reload the item page. 2. Check the form shows the item you opened (name and price). 3. Check Request headers & secret parameters lists Authorization with the value masked. 4. If it says "No headers or parameters", add the header again and click Save headers & parameters. What you’ll see: The section lists the header with its value masked. Watch for: - A "Catalog Item Updated" toast after Save changes does not mean the header was saved. - Headers entered on the New item form are saved by Create item; the risk is on the item page. Link: https://www.qatom.ai/capabilities#B37 ### B17. Find, filter and update any item Find, filter and edit items As the catalog grows, search and filters keep it manageable. Edits to price and schema reach the master MCP and your instance. - Where: Catalog list and item page, account_catalog, account_update_item - Who: Seller How: 1. In Catalog, search by name, description or endpoint. 2. Filter by Not archived, Active, Inactive, Archived or All, and by method; sort by Name, Price or Created. 3. Open an item, change the fields and click Save changes; to make a variant, use Duplicate (B36). 4. From chat, ask your agent to list items (account_catalog) or edit one (account_update_item). What you’ll see: Each filter shows its count, and saving shows a "Catalog Item Updated" toast. Watch for: - Before saving, check the form shows the item you clicked; item pages can load slowly or keep the previous item's values. - In a narrow window the item detail pane may not show; widen the window. Link: https://www.qatom.ai/capabilities#B17 ### B36. Copy an item, then retire the old one Duplicate an item, then archive the old one Duplicate is how you make a variant, and the only way to turn a private item public. The copy is a new item with a new id. - Where: Item page → Duplicate - Who: Seller - Secret: needs a secret How: 1. On the item page, click Duplicate; the New item form opens prefilled. 2. Change what differs; to go public, untick Private to this MCP instance. 3. Re-enter each sensitive value ("Sensitive values were not copied; enter them again"), then Create item. 4. On the old item, Availability → Archive item, and update llms.txt and anything else that names the old id. What you’ll see: The copy appears in the Catalog list with a new item id, and the old one shows under Archived. Watch for: - Check the Private switch on every copy; a copy may keep the original's setting. - The copy also gets a new provider twin, so payments land in a new place. - Archive item has no confirmation dialog. Link: https://www.qatom.ai/capabilities#B36 ### B18. Make sure your own MCP server is healthy Check the MCP instance: server URL, health, tools, logs Your MCP instance serves your featured and private items. Check it is healthy before testing or sharing its URL. - Where: MCP → Overview / Tools / Logs, account_mcp_server - Who: Seller How: 1. Open MCP → Overview: copy the Server URL and check Status, Deploy version and Health (Overall, ECS tasks, Server DB, HTTP check). 2. Open Tools: check your featured items and the built-in tools, each with its input schema. 3. Open Logs for recent activity. 4. From chat, ask your agent for the server details (account_mcp_server). What you’ll see: Health reads healthy and your featured items are listed under Tools. Watch for: - A new instance needs a few minutes to become healthy; trust Health, not the Overview banner. - If Logs look old, check Status and Health instead. Link: https://www.qatom.ai/capabilities#B18 ### B39. Keep your MCP server on the latest version Update your MCP server when the Dashboard offers it When Qatom releases a new server version, the MCP page offers an update. Updating keeps your tools in step with the master MCP. - Where: MCP → Overview → Update available → Update instance - Who: Owner How: 1. Open MCP → Overview. 2. If it shows Update available, click Update instance. 3. Wait until Health reads healthy again, then check your featured tools under Tools. What you’ll see: The deploy version rises and Health returns to healthy. Watch for: - (to confirm) Whether buyers' calls pause during the update. Link: https://www.qatom.ai/capabilities#B39 ### B19. Buy every item once before you announce Test straight away: buy each item once (public items through the master MCP, private items through your own instance) before announcing A real purchase is the only full test of price, schema, header and endpoint together. Do it as soon as the item exists. - Where: catalog_search + agent_checkout - Who: Seller - Money: yes How: 1. Connect the master MCP (https://mcp.m.todaq.net/mcp); for private items, connect your instance's Server URL instead. 2. Fund the agent twin with a small amount (fund_primary_wallet or A32, then transfer_to_agent). 3. Find the item with catalog_search and buy it with agent_checkout, item alone and with inputs. 4. Approve the purchase when asked, unless its price is within your auto-approve limit. 5. Also try a bad input and check the error is clear. What you’ll see: The receipt shows your endpoint's answer and a transaction id. Watch for: - A call your endpoint rejects can still be charged, and a retry is a new charge. - Free items cost nothing to test. - Private items are not found through the master MCP; that is expected. Example: All three Qatom Demo items were bought through the master MCP. Feedback returned a reference id, the skill's SHA-256 matched and the video played at 1080p. Link: https://www.qatom.ai/capabilities#B19 ### B38. Pass the launch checks, then go live Run the launch checks before announcing The seller guide's launch report checks each item the way a buyer's agent meets it. Announce only when it passes. - Where: Seller guide skill (launch report), master MCP - Who: Seller How: 1. Ask your agent, with the seller guide skill installed, to run the launch report for your items. 2. Fix each failure it lists, such as a missing feedback item, an endpoint URL holding a secret, or a description without your llms.txt link. 3. Run it again until every item passes. What you’ll see: A launch report listing each item with its checks passed. Watch for: - Test buys (B19) come first; the report uses their results. Link: https://www.qatom.ai/capabilities#B38 ### B40. Get ready for cart purchases Expect buyers to buy your items in carts Buyers can put your items in a cart with other items, from you or other sellers, and pay once. Each item in the cart reaches your endpoint as its own paid call, with its own inputs and transaction id. - Where: Your endpoint, and the buyer's chat - Who: Seller How: 1. Make sure each item works as a single call; a cart sends one call per copy, after payment. 2. Return a clear summary and links in every answer: the buyer's agent shows them once, in the cart's reply. 3. Keep inputs fully described in the item's schema, so agents can collect them before adding the item to a cart. 4. Test by putting two of your items in one cart and paying from an agent wallet (A33, A34). What you’ll see: Your sales show one transaction per item copy, the same as single purchases. Watch for: - Links in your answer should outlast the moment the cart is paid; a 15-minute link can expire before a buyer reads a long reply. - A buyer may stop a cart partway; items already delivered stay bought. Example: Qatom Demo's feedback, skill and video items were bought together in one cart on 12 Oct; each returned its own answer. Link: https://www.qatom.ai/capabilities#B40 ### B20. Serve each paid sale once, and only once Verify a fulfilment call is a real sale (X-Qatom-Transaction-Id) For anything expensive to serve, check each call matches a settled sale of your item. This stops replayed or forged calls. - Where: Seller endpoint + API - Who: Seller How: 1. Read the X-Qatom-Transaction-Id header on each fulfilment call. 2. Call GET /v4/catalog/purchases/{transaction_id} with your account credentials (B30). 3. Refuse the call if the id is unknown or belongs to another item. 4. Keep the ids you have served, so no sale is served twice. What you’ll see: The API returns the settled sale for your item, and your endpoint serves it. Watch for: - Use this for stream keys, downloads and game entries; cheap reads can rely on the fulfilment header. Link: https://www.qatom.ai/capabilities#B20 ### B21. Check you are findable, then tell people Confirm public items show in catalog_search, then announce them (share llms.txt, STORES.md) Buyers find items through catalog_search on the master MCP. Announce only once your items show there and pass your launch checks. - Where: Item form, catalog_search - Who: Seller How: 1. On the master MCP, run catalog_search for your brand prefix. 2. Check each public item's name, price, seller name and description. 3. Run the seller guide's launch report and fix any failure. 4. Announce: share your llms.txt URL and add your store to STORES.md (B26). What you’ll see: catalog_search lists each public item with your business name as the seller. Watch for: - Private items never show in catalog_search; that is by design. - Delist or archive test and placeholder items before you announce. - (to confirm) How long a new public item takes to appear in catalog_search. If it is missing, wait a few minutes and search again before assuming it failed. Link: https://www.qatom.ai/capabilities#B21 ### B22. See what each item has earned Read sales and revenue Sales figures show which items sell. Item revenue lands on each item's twin; the Console shows who paid. - Where: Overview tiles, item page Sales / GET /v4/catalog/revenue (revenue view to come) - Who: Seller How: 1. On the Overview, read the Revenue tile (USD-TDN and transactions). 2. On an item page, read Sales: Sales count and Earned. 3. By API, GET /v4/catalog/revenue totals what your items have earned. 4. To see who paid, open the item's twin in the Qatom Console. 5. From chat (after A4): ask your agent what your catalog has earned; it calls account_sales (all-time total and number of sales, or one item's latest sales with item_id). What you’ll see: The item page shows its Sales count and Earned in USD-TDN. Watch for: - The Revenue tile links to the Catalog list; a dedicated revenue view is still to come. - The transaction count is meant to cover paid transactions only. Link: https://www.qatom.ai/capabilities#B22 ### B23. Let your agent change settings, with your yes Make an account change through an agent with approval Your agent can prepare account changes in chat: create or change an item, change business details, rename a wallet, reboot your MCP server. Nothing changes until you approve that exact change. - Where: account_finish_change - Who: Owner How: 1. Choose your seller account for the chat first (A4). 2. Ask your agent for the change; it calls the matching tool (account_create_item, account_update_item, account_update_details, account_rename_wallet or account_reboot_server) and gives you an approval link. 3. Sign in (a passkey is one tap). The page shows the Change and the Account; check both, then approve. 4. When it says "Approved. Go back to your conversation to let the agent finish", tell the agent. It calls account_finish_change, which makes the change once and refuses a second try. What you’ll see: The agent reports the change as done, and the account shows it (for example the new wallet name in account_wallets or the seller Dashboard). Watch for: - Secrets never go through chat: for an item's headers, the agent gives you a Dashboard link instead (A26). - The account_ tools (account_choose, account_wallets, account_dashboard_link and the rest) are listed on some connections and not others, and they work only once a business account is chosen. (to confirm) Which connections list them. Example: On 12 Oct the Dobox seller account renamed an unused duplicate wallet from chat: one approval page, then account_finish_change; a second finish call was refused. Link: https://www.qatom.ai/capabilities#B23 ### B24. Change a secret without breaking sales Rotate a fulfilment secret with no failed calls Rotate the fulfilment token whenever it may have leaked. A short overlap keeps every call working. - Where: Host + item form - Who: Seller - Secret: needs a secret How: 1. Generate a new value on your own machine (openssl rand -hex 24). 2. Have the endpoint accept both the old and the new value for a few minutes. 3. Set the new value in your host's secret store and on each item's Authorization header, then Save headers & parameters. 4. Reload each item to check the header (B37), then remove the old value from the endpoint. What you’ll see: A test purchase succeeds, and a direct call with the old value gets 404. Watch for: - Headers are per item; update every paid item that uses the token. Link: https://www.qatom.ai/capabilities#B24 ### B25. Pause or retire an item Deactivate or archive an item Deactivate pauses sales and can be undone. Archive takes a retired or mislisted item off sale; it then shows only under the Archived filter. - Where: Item → Availability - Who: Seller How: 1. Open the item page and go to Availability. 2. Click Deactivate item to take it out of search and refuse new purchases; you can turn it back on. 3. Or click Archive item to take it off sale; it then appears only under the Archived filter. What you’ll see: The item shows under the Inactive or Archived filter in the Catalog list. Watch for: - Archive item has no confirmation dialog; use Deactivate if you may want it back. Link: https://www.qatom.ai/capabilities#B25 ### B26. Get your store seen and scored Get listed in STORES.md and rated by the Rating & Review service STORES.md lists live Qatom stores. The Rating & Review service scores listings against the seller guide. - Where: GitHub PR, review service - Who: Seller How: 1. Open a pull request adding your store to STORES.md in the qatom-hack-the-andes repository. 2. Follow every seller guide stage, including the launch checks, so the listing scores well. What you’ll see: Your store appears in STORES.md once the pull request is merged. Watch for: - (to confirm) Ratings are launching; how a store is submitted for rating is to be confirmed. Link: https://www.qatom.ai/capabilities#B26 ### B27. Answer refund requests from your primary wallet Handle billing disputes and refunds: read feedback, check the transaction, refund from the primary Buyers ask for refunds through your feedback item. Payments settle at once; refunds are your decision and go back to the wallet that paid. - Where: Feedback inbox, Console Send - Who: Seller - Money: yes How: 1. Read the feedback message and note the transaction id. 2. Check the sale: GET /v4/catalog/purchases/{transaction_id}, or the item's twin in the Qatom Console. 3. If you refund, use Send on your primary twin (Transfer role) to the wallet that paid, or POST /v4/transfer. 4. Reply to the buyer with what you did. What you’ll see: A Sent row appears in the primary twin's Transactions. Watch for: - Funds must be in the primary twin; item revenue reaches it through a standing distribution. - Never retry a transfer that returned 202; it already moved. - Don't promise the buyer a timeline. Link: https://www.qatom.ai/capabilities#B27 ### B28. Show buyers a board, card or player in chat Build an interactive MCP App view for buyers (optional) An MCP App view puts a live board, card or player inside the conversation. Keep it on a free server; money stays on Qatom. - Where: Seller's free MCP server - Who: Seller How: 1. Start from examples/mcp-app-minimal in the qatom-use-cases repository. 2. Attach a view to a tool and return both text for the model and structuredContent for the view. 3. Host it as your own free MCP server, separate from your paid items. 4. Tell buyers to add it as a second connector beside the master MCP. What you’ll see: In a client that supports MCP Apps, the tool result opens as an interactive view in the chat. Watch for: - MCP Apps (boards, cards, players inside the chat) work in Claude, ChatGPT and Hermes today. Grok and Muse don't support them yet. - No purchase starts inside a view; the human approves money in Qatom's own flow. - Change the view's URI suffix (-v1, -v2) on every change; hosts cache views. Example: Centaur League's view_match opens a chess board in the chat from its free server at centaurleague.games/mcp. Link: https://www.qatom.ai/capabilities#B28 ### B29. Issue and revoke keys for your account Create and revoke account API keys Account API keys let your own systems call Qatom for this account. Revoke any key you no longer use. - Where: Settings → API Keys - Who: Owner - Secret: needs a secret How: 1. Open Settings → API Keys. 2. Under Create a key, enter a name and create it. 3. Store the key in your secret store, never in a repo or chat. 4. To stop a key working, click Revoke beside it. What you’ll see: The key is listed with its created and last-used dates. Watch for: - Check last used before revoking a key a system may still need. Link: https://www.qatom.ai/capabilities#B29 ### B30. Get the credentials your server uses Get your server credentials and public secret Your server exchanges the client credentials for an account token for calls such as payouts and sale checks. The public secret is for embeds and guest checkout. - Where: Settings → Secrets - Who: Owner - Secret: needs a secret How: 1. Open Settings → Secrets. 2. Copy the Client ID; click Reveal to see the Client secret. 3. Store both on your server only, then exchange them for an account token at /v4/account/oauth/token. 4. Copy the Public secret for embeds and guest checkout. What you’ll see: The Secrets tab shows the Client ID, a hidden Client secret with Reveal, and the Public secret. Watch for: - Never put the client secret in a browser, app or repo. - The public secret is publishable; the client secret is not. Link: https://www.qatom.ai/capabilities#B30 ### B31. Know which wallet holds what See your twins, rename them and find a twin's API key Your account holds several twins: primary, agent, and one provider twin per item. Payments land on the item's provider twin. - Where: Twins → twin - Who: Owner - Secret: needs a secret How: 1. Open Twins; search by name or hostname, and filter by All, Primary, Agent or Provider. 2. Open a twin to see its Twin ID, Hostname, Type and balances. 3. Change its display Name and click Save name. 4. Copy its API key only when you need it, for example for Payment Multiplex payers. What you’ll see: The twin page shows its identity, name and balances by digital quantity. Watch for: - The API key gives direct access to the twin; treat it as a secret. - Provider twins appear only once items exist. Link: https://www.qatom.ai/capabilities#B31 ### B32. Put your MCP server on your domain Serve the MCP instance from your own domain A custom domain lets buyers connect to your instance at an address you own. The default URL keeps working. - Where: MCP → Custom domain - Who: Owner How: 1. Open MCP → Overview → Custom domain and click Add domain. 2. For a subdomain, add a CNAME record at your DNS provider. 3. For a root domain, use CNAME flattening or an ALIAS record. What you’ll see: (to confirm) Your domain is listed under Custom domain. Watch for: - The default server URL keeps working, so existing connections don't break. Link: https://www.qatom.ai/capabilities#B32 ### B33. Restart your server, or remove it for good Reboot the MCP instance after changes; destroy it (irreversible) Reboot restarts your instance. Destroy removes it permanently and changes its hostname and key. - Where: MCP → Lifecycle / Danger zone, account_reboot_server - Who: Owner How: 1. To restart, open MCP → Overview → Lifecycle and click Reboot instance, or ask your agent (account_reboot_server). 2. Check Status and Health afterwards. 3. Only to remove the instance for good: Danger zone → Destroy instance. What you’ll see: After a reboot, MCP → Overview shows the instance running again. Watch for: - Reboot drops in-flight requests briefly. - Destroy is irreversible: the instance gets a new hostname and API key, so update every connection to it. Link: https://www.qatom.ai/capabilities#B33 ## Console (In the Qatom Console) Everything after the sale happens in the Qatom Console at console.todaq.net, twin by twin: payments, distributions, cash-outs. ### C1. Sign in to the Qatom Console Sign in to the Qatom Console (emailed link or passkey) and authorize it The Qatom Console is where owners see, verify and move what their twins hold. The first sign-in also asks you to authorize the Console. - Where: console.todaq.net → Sign in to TODAQ Enterprise - Who: Group member How: 1. Go to console.todaq.net and click Sign in to TODAQ Enterprise. 2. Use your passkey, or enter your email and click Send sign-in link. 3. Open the emailed link within 15 minutes. 4. First time only: review what Qatom Console asks for (identity, email, group memberships) and authorize it. What you’ll see: Home opens with My Twins, listing each twin you can reach with its role badge and balance. Watch for: - The sign-in link expires after 15 minutes; send a new one if it has. - Later sign-ins skip the authorize screen. Link: https://www.qatom.ai/capabilities#C1 ### C2. Sign in faster with a passkey Set up a passkey A passkey lets you sign in without waiting for an emailed link. It stays on your own device. - Where: Account → Passkeys (left menu, above the twin view) - Who: Group member - Secret: needs a secret How: 1. Sign in with an emailed link (C1). 2. In the left menu open Account → Passkeys. 3. Under Register New Passkey, give it an optional name (for example your laptop) and click Register Passkey. 4. Follow your device's prompt. What you’ll see: Your Passkeys lists the new passkey with its created date, with Rename and Delete. Watch for: - Only the person who owns the sign-in creates or uses a passkey; an agent never does. Link: https://www.qatom.ai/capabilities#C2 ### C3. Find every twin you can reach Find your twins: search, pin, role badges, balances Home lists the twins you have access to, with your role on each. Start here to find the wallet you need. - Where: Home → Mine - Who: Group member How: 1. Open Home; Mine lists your twins. 2. Search by twin name, URL or email. 3. Click the star on a twin to pin it. 4. Read each twin's role badge (Admin, Transfer or Read-only) and balance. What you’ll see: Each row shows the twin's name, host, role badge and balance. Watch for: - Right after your role changes, some twins can show without a name or balance; sign out and in again (C32). Link: https://www.qatom.ai/capabilities#C3 ### C4. See a whole group's balance at once Open a twin group and see its total USD-TDN A twin group holds the twins of one customer or project. Its page adds up the balance across all of them. - Where: Home → Groups → group page - Who: Manager How: 1. On Home, open Groups (shown to group managers). 2. Click a group to open its page. 3. Read Total TDN, and search the group's twins. What you’ll see: The group page shows Total TDN and the list of twins in the group. Watch for: - You need the Manager role on the group to see Groups. Example: The Centaur League group holds its primary twins, agent twin and catalog item twins. Link: https://www.qatom.ai/capabilities#C4 ### C5. See a twin's balance and latest activity Read a twin's wallet card and recent activity A twin's page is its wallet: the USD-TDN balance (shown as TDN) and who it paid or was paid by lately. - Where: Twin page - Who: Any role How: 1. From Home, click a twin. 2. Read the wallet card: token, balance and approximate USD value. 3. Use the card's buttons as needed: Send, Buy, Bank Transfer, History. 4. Scroll to Recent Activity to see counterparties by name or email. What you’ll see: The wallet card shows the TDN balance with its USD value, above Recent Activity. Watch for: - Send needs the Transfer role; Admin alone does not enable it. - Catalog item twins with a standing distribution have no Send; sending is handled by the distribution. Link: https://www.qatom.ai/capabilities#C5 ### C6. See exactly what a twin holds See TODA files: binder, identity root, USD-TDN notes Every USD-TDN note and record a twin holds is a TODA file. Inventory lists them, so you can see what the twin owns. - Where: Wallet → Inventory - Who: Any role How: 1. Open the twin, then Wallet → Inventory. 2. Under TODA Files, open the binder (the twin's record of every file) or the identity root (SDA). 3. On the TDN card, read the balance and the notes that make it up. 4. Click View transactions to jump to the history. What you’ll see: The binder reads "Valid twin binder of record" and the TDN card lists each note with its value. Watch for: - USD-TDN are held as notes of set values, like cash; a payment sends whole notes and keeps the change. Link: https://www.qatom.ai/capabilities#C6 ### C7. Trace a note's full history Inspect a note: minting info and provenance history Each note carries its own audit trail. Use it to prove where money came from and how it moved. - Where: Inventory → note - Who: Any role How: 1. In Wallet → Inventory, click a note on the TDN card. 2. Read Note Value and Minting Info: issuer TODAQ Micro Inc., asset TDN, prepaid US dollars, and the TDN terms. 3. Read Provenance History: each revision, transfer and split, with its hash and controlling twin. What you’ll see: Provenance History lists every step in the note's life, each with a hash and the twin that held it. Watch for: - To prove a payment to someone else, pair Provenance History with the downloaded .toda file (C8). Link: https://www.qatom.ai/capabilities#C7 ### C8. Check a file's verdict and keep a copy Verify a file's integrity; download the .toda file TODA files can be verified on their own. The Console shows a verdict and lets you download the file itself. - Where: Inventory → file - Who: Any role How: 1. Open the binder or the identity root (SDA) from Wallet → Inventory. 2. Read the verification verdict at the top of the page. 3. Click Download .toda File to keep a copy; notes have the same button. What you’ll see: The identity root shows "Integrity certified by TODAQ Instant Relay"; the binder shows "Valid twin binder of record". Watch for: - Note pages show an empty Verification Status box today; the binder and identity root show a verdict. Link: https://www.qatom.ai/capabilities#C8 ### C9. Read and export a twin's ledger Read transactions; filter, export CSV Transactions is the twin's ledger, with a running balance. Export it for your books or to answer a buyer. - Where: Wallet → Transactions - Who: Any role How: 1. Open the twin, then Wallet → Transactions. 2. Filter by date and token; include non-quantitative assets if you need them. 3. Read Type (Sent, Received, Microdistribution Income), To/From, Withdrawal, Deposit and Balance. 4. Click Export CSV to save the list. What you’ll see: A dated list with a running Balance column; Export CSV saves it as a file. Watch for: - Microdistribution Income rows are revenue swept in from your catalog item twins. - A cash-out shows as Sent to an unnamed twin, the bank gateway; match it by time and amount in Transfer History (C27). Link: https://www.qatom.ai/capabilities#C9 ### C10. Open one transaction for the full detail Open a transaction: transfer internals, notes, distribution id A transaction's page holds its id and how it was made. Use it when a buyer or seller asks about one payment. - Where: Transactions → row - Who: Any role How: 1. In Wallet → Transactions, click a row's Details. 2. Read status, counterparty, amount, entry type (Quantitative Transfer) and Transaction ID. 3. For a send, open Transfer Internals: transfer id, duration, request id and the note-by-note table. 4. For a revenue sweep, read the distribution rule id and the associated notes. What you’ll see: The detail page shows the Transaction ID and, for sends, Transfer Internals. Watch for: - "Balance after" in Transfer Internals can be wrong when sweeps arrive right after a send; trust the list's running Balance. Link: https://www.qatom.ai/capabilities#C10 ### C11. Find a payout that seems stuck Track outgoing transfers; find stuck ones Transfer Activity lists every transfer the twin sent, with its status. It is the first place to look when a payout hasn't arrived. - Where: Wallet → Transfer Activity - Who: Any role How: 1. Open the twin, then Wallet → Transfer Activity. 2. Filter All, In progress or Needs attention. 3. Read Started, Recipient and memo, Amount, Status and Transfer ID. What you’ll see: Each outgoing transfer shows a status: In progress, Completed, Needs attention or Not sent. Watch for: - Check Needs attention first when a payout seems stuck. Link: https://www.qatom.ai/capabilities#C11 ### C12. See which notes moved in a transfer See how a transfer was assembled (split, change, delivered) USD-TDN move as whole notes, like cash. The detail page shows which notes went, which change stayed, and when each arrived. - Where: Transfer Activity → row - Who: Any role How: 1. In Transfer Activity, click a transfer. 2. Read To, Amount, Started, Completed, Memo and the linked transaction. 3. Read the Notes table: each note is Split off, Change kept or Sent whole, with its delivery time. What you’ll see: The Notes table shows exactly which notes moved and what change stayed behind. Watch for: - Notes from one payment can arrive at different times, sometimes minutes apart. Link: https://www.qatom.ai/capabilities#C12 ### C13. See who paid for each sale Find who paid for an item Each catalog item has its own provider twin, where its payments land. Its Recent Activity names each payer. - Where: Item's provider twin → Recent Activity - Who: Any role How: 1. Find the item's provider twin: search Home by the item's name, or see Dashboard → Twins → Provider. 2. Open the twin and read Recent Activity. 3. Each payment shows the payer's email or twin, the amount and the time. 4. In code: GET /v4/commodity/{hash}/transactions with the item's commodity hash (shown as Commodity ID; to confirm). What you’ll see: Recent Activity lists each payment with the payer's email or twin. Example: On Centaur League, a paid item's twin lists each team's entry payment by the payer's email. Link: https://www.qatom.ai/capabilities#C13 ### C14. Pay one person, twin or refund Send USD-TDN to another twin Send moves USD-TDN from a twin you control to another twin. Use it from the primary twin for a single payout or a refund. - Where: Twin page → Send (Transfer Notes) - Who: Transfer role - Money: yes How: 1. Open the twin you pay from (usually the primary) and click Send. 2. Choose the Currency; its balance shows beside it. 3. Enter the Amount, the Recipient Twin URL and an optional Memo for the recipient. 4. Check from, to and amount, then click Transfer. What you’ll see: The transfer appears in Wallet → Transfer Activity, then as Sent in Transactions. Watch for: - Send needs the Transfer role; after a role change, sign out and in again. - By API, a 202 means the money moved; never retry it. - Send takes a twin URL today; paying by email is planned, as distributions already do. Link: https://www.qatom.ai/capabilities#C14 ### C15. Buy USD-TDN from Treasury by wire or ACH Request to buy USD-TDN from Treasury, then pay by wire or ACH Purchase TDN sends a request to TODAQ Treasury. You pay by wire or ACH, and Treasury issues the USD-TDN to the twin. - Where: Wallet → Purchase TDN → Buy TDN - Who: Any role except Read-only - Money: yes How: 1. Email TODAQ at support@todaq.net that you want to buy USD-TDN; you receive the banking details. 2. Send the funds by wire or ACH. 3. Open the twin that should receive the USD-TDN, then Wallet → Purchase TDN → Buy TDN. 4. Enter the Paid Amount in USD (1 USD buys 1 TDN), add a memo and click Submit Request. What you’ll see: The request shows Pending; once Treasury sees your funds it sends the USD-TDN and closes the request as Complete. Watch for: - This is a request: USD-TDN arrive only after Treasury receives your funds (S3). Link: https://www.qatom.ai/capabilities#C15 ### C16. Check whether your USD-TDN purchase is done Track USD-TDN purchase requests Each purchase request has a status. Check it here before asking Treasury about a payment. - Where: Wallet → Purchase TDN - Who: Any role How: 1. Open the twin, then Wallet → Purchase TDN. 2. Filter All, Pending, Complete or Cancelled. 3. Read Date, Receiving Twin, Memo, Amount paid and Status. What you’ll see: A request moves from Pending to Complete once Treasury issues the USD-TDN. Watch for: - Treasury watches for your wire or ACH; when it arrives it sends the USD-TDN and closes the request. Link: https://www.qatom.ai/capabilities#C16 ### C17. Sweep each item's revenue to your primary Set a standing distribution: item revenue to the primary twin Payments land on each item's own twin, but payouts and cash-outs come from the primary. A standing distribution moves the money there for you. - Where: Item's provider twin → Configuration → Distributions - Who: Admin How: 1. Open the catalog item's provider twin, then Configuration → Distributions → New. 2. Choose the token TDN. 3. Add one recipient, the primary twin URL or the account email, at 100%. 4. Set Minimum Value (1 is the standard), tick Enabled, then click Save Distribution. What you’ll see: The Standing tab shows the rule, and the primary twin starts showing Microdistribution Income rows. Watch for: - Runs happen a few times a day; tell customers to expect funds within a day. - One standing distribution per token per twin; choosing TDN again opens the existing rule's Edit form. - Once a distribution is active, the twin's Send button is replaced by it. - If funds are late, check the item twin's Activity tab, then email support@todaq.net. Example: Centaur League's Create a Chess Challenge twin sends 100% to the league's primary account, minimum 1. Link: https://www.qatom.ai/capabilities#C17 ### C18. Split revenue or pay many people at once Split revenue, or pay up to 200 payees by twin or email (CSV import) A distribution can pay several recipients by percentage. Use it for royalties, partner shares or many prize winners. - Where: Distribution → Edit - Who: Admin How: 1. Open the distribution and click Edit (or New on a fresh twin). 2. Add recipients by twin URL or Email, each with a Percentage; the total must be 100%. 3. For many payees, click Import CSV; Export CSV saves the current list. 4. Check recipients and percentages, then click Save Distribution. What you’ll see: The edit form shows the percentage total, and the saved rule lists its recipients. Watch for: - Up to 200 payees per distribution. - A payee added by email needs a twin to receive funds today; email sign-in to the Console for twin holders is coming. Link: https://www.qatom.ai/capabilities#C18 ### C19. Pay out a distribution right away Run a distribution now Distribute Now runs a distribution without waiting for its next run. Use it when a payout is due today. - Where: Distribution → Distribute Now - Who: Admin - Money: yes How: 1. Open Configuration → Distributions and view the rule. 2. Check the twin's balance, the recipients and their percentages. 3. Click Distribute Now. 4. Open the Activity tab to see the run complete. What you’ll see: A new run appears in Activity with its value, status, and start and finish times. Watch for: - A run can complete while the receiver sees it arrive as two deposits minutes apart; check the run page (C20) before reporting a shortfall. - The owner clicks Distribute Now; an agent never does. Example: Centaur League's first run moved 5 USD-TDN from a paid item twin to the primary. Link: https://www.qatom.ai/capabilities#C19 ### C20. Check every payee in a distribution run Check distribution runs and the transfer for each payee Each run has a page listing every payee and the transfer that paid them. Use it to answer "did I get paid?". - Where: Distributions → Activity → run - Who: Admin How: 1. Open Configuration → Distributions → Activity. 2. Read each run's ID, Value, Status, Recipients, Started and Completed. 3. Click a run to see each recipient's value, status and transfer id. 4. Click a transfer id to open it in Transfer Activity. What you’ll see: The run page lists every payee with a status, for example COMPLETED, and a transfer link. Link: https://www.qatom.ai/capabilities#C20 ### C21. Charge per call for a service Configure a twin paywall (target, price, token) A twin paywall charges per call for an https service the twin fronts. Every Qatom catalog item already works this way through its provider twin. - Where: Configuration → Paywall - Who: Admin How: 1. Open the twin, then Configuration → Paywall. 2. Tick Enabled and enter the Target URL (https). 3. Choose the Payment Token (Use TDN) and the Payment Amount, up to three decimals. 4. Click Save Configuration. What you’ll see: The paywall saves as Enabled; callers pay through the twin's paywall URL. Watch for: - Give each paywalled product its own twin, with a standing distribution to the primary. - A primary twin should not be a live paywall; if one shows Enabled with a placeholder target, report it. - A catalog item's twin forwards to Qatom; never share its Target URL. Link: https://www.qatom.ai/capabilities#C21 ### C22. List your paywall where others can find it Publish a paywall to the Directory; browse the Directory A public paywall appears in the Directory of paywalls on the network. Its descriptor page tells callers what it does. - Where: Paywall descriptor + Public; menu → Directory - Who: Admin; anyone How: 1. In Configuration → Paywall, enter a Descriptor URL that explains the service. 2. Switch the toggle to Public and click Save Configuration. 3. Open the menu → Directory and search by account. 4. Click Details on an entry to open its descriptor. What you’ll see: Your paywall appears in the Directory under "Public paywalls available on the network". Watch for: - Link a real descriptor page, not a placeholder; the Directory shows whatever you link. Link: https://www.qatom.ai/capabilities#C22 ### C23. Spread high-volume buying across payer twins Add payer twins to Payment Multiplex (each payer's API key is on Dashboard → Twins) Payment Multiplex lets a master twin hand each purchase to the next free payer twin. Buyers deal with one endpoint and one budget. - Where: Master twin → Configuration → Payment Multiplex → Payers - Who: Admin - Secret: needs a secret How: 1. Open the master twin, then Configuration → Payment Multiplex → Payers. 2. In the Qatom Dashboard, open Twins → the payer twin and copy its API key. 3. Back in the Console, paste the payer's Twin URL and API key, then click Add. 4. Repeat for each payer; plan about one payer per purchase running at the same time. What you’ll see: Each added payer twin belongs to the master's multiplex (to confirm what the Payers list shows). Watch for: - Payers must belong to the same account or group. - The owner pastes API keys; an agent never handles them. - (to confirm) What the Payers list shows after a payer is added. Link: https://www.qatom.ai/capabilities#C23 ### C24. Keep payer twins funded automatically Set multiplex top-ups (threshold, amount) Top-ups refill any payer twin that falls below a threshold, from the master twin's balance. You pre-fund only the master. - Where: Payment Multiplex → Top-ups - Who: Admin - Money: yes How: 1. On the master twin, open Payment Multiplex → Top-ups and start a new top-up. 2. Pick the Token; the master's balance shows beside it. 3. Set Threshold and Top-up amount, tick Enabled, then Save. What you’ll see: The top-up rule is saved on the master twin (to confirm how it is listed). Watch for: - Top-ups run daily and come out of the master twin; pre-fund it with the total budget. - Set the threshold at or above a payer's expected spend per day. - (to confirm) How a saved top-up and each top-up run are shown. Link: https://www.qatom.ai/capabilities#C24 ### C25. Add the bank account you cash out to Create the banking profile (USA or Canada) A banking profile holds the direct-deposit details for one twin. You need it before you can cash out. - Where: Configuration → Banking Profile - Who: Admin - Secret: needs a secret How: 1. Open the twin you cash out from, then Configuration → Banking Profile. 2. Enter Account Holder Name, Financial Institution Name, Country (USA or Canada) and Account Type (Chequing or Savings). 3. USA: street address, city, state, ZIP, 9-digit routing number and account number. Canada: transit (5–6 digits), institution (3 digits) and account number. 4. Click Create Profile. What you’ll see: Bank Transfer then shows the destination account masked, with only its last four digits. Watch for: - The account owner types bank details; an agent never does. - Profiles are per twin; set one on the twin you will cash out from. Link: https://www.qatom.ai/capabilities#C25 ### C26. Cash out USD-TDN to your bank Cash out to the bank (at least 10 USD-TDN, $1 fee, ACH 2–5 days) Bank Transfer sells USD-TDN to TODAQ Treasury, which pays US dollars to your bank by ACH. It needs a banking profile and at least 10 USD-TDN. - Where: Twin page → Bank Transfer - Who: Transfer role - Money: yes How: 1. First sweep item revenue to the twin you cash out from, usually the primary (C17). 2. Open the twin and click Bank Transfer, then Bank Transfer again. 3. Enter the Amount (minimum 10) and read the Transfer Summary: fee and what you will receive. 4. Check the masked Destination Account and the Amount once more. 5. Click Continue. What you’ll see: Transfer History shows the request as Pending, and the USD-TDN leave the twin at once. Watch for: - Continue submits immediately; there is no review screen, and the Amount can keep an earlier value. - A flat 1 USD fee applies; ACH takes 2–5 business days. - A submitted cash-out can't be cancelled yet; check the amount before Continue. If one went out wrong, email support@todaq.net. Link: https://www.qatom.ai/capabilities#C26 ### C27. Follow a cash-out until it is paid Track a cash-out Each cash-out has a request with a status. Check it before chasing a deposit. - Where: Bank Transfer → Transfer History - Who: Any role How: 1. Open the twin, click Bank Transfer, then Transfer History. 2. Click a request to see Status, TDN Amount, Expected Payout, Created, Last Updated and Request ID. What you’ll see: The detail page says funds will be deposited within 2–5 business days. Watch for: - The list can say PENDING while the detail page says Processing for the same request. - Questions about a cash-out: email support@todaq.net. Link: https://www.qatom.ai/capabilities#C27 ### C28. Rename a twin and set its email Edit the twin's persona: display name and email The persona is the twin's public face: the name shown everywhere and an email others can pay. - Where: Configuration → Twin Settings - Who: Admin How: 1. Open the twin, then Configuration → Twin Settings. 2. Read Twin URL, TODA Address, Binder ID and Managing Organization. 3. Under Persona, edit Display Name and Email. 4. Click Save Changes. What you’ll see: The new Display Name shows as the twin's name in the Console. Watch for: - The persona email is payable: distributions and transfers can send to it. Link: https://www.qatom.ai/capabilities#C28 ### C29. Check who can see or move a twin's funds See who has access to a twin Access is granted twin by twin. This page is meant to show who holds which role. - Where: Account → Permissions (left menu) - Who: Admin How: 1. Open the twin, then Configuration → Permissions. 2. Read who holds Admin, Transfer or Read-only on the twin. What you’ll see: (to confirm) A list of people and their role on the twin. Watch for: - Today this page returns 403 even for twin Admins; ask the account owner who has access. - Roles: Admin configures, Transfer can send, Read-only can only look. Link: https://www.qatom.ai/capabilities#C29 ### C30. Check a twin's usage Read usage (files, transactions, storage) Usage shows how much a twin holds and has done against a standard allocation. It helps when you look into a busy twin. - Where: Configuration → Usage - Who: Admin How: 1. Open the twin, then Configuration → Usage. 2. Read files, transactions and storage against the standard allocation (25 files, 1,250 transactions, 100 MB). 3. Read the Inbox, Rejected and Unowned counts. What you’ll see: An Overall figure shows usage as a multiple of the standard allocation, for example 0.3x. Watch for: - These are internal health metrics; no customer limits apply today. - Unowned counts the last proof of each file the twin held before it moved to a new bearer. Link: https://www.qatom.ai/capabilities#C30 ### C32. Sign in again to apply a new role Sign out, and sign in again after a role change A role change takes effect only at your next sign-in. Sign out and back in after an owner changes your access. - Where: User menu → Sign out - Who: Anyone How: 1. Open the user menu and click Sign out. 2. Sign in again (C1). What you’ll see: Controls now match your new role; for example, Send is enabled after you get the Transfer role. Watch for: - The Console doesn't tell you a role changed; sign out and in when an owner says so. - Before you sign in again, some twins may show without names or balances. Link: https://www.qatom.ai/capabilities#C32 ### C33. See what changed in the Console Read what is new The Console changes often. Release Notes lists each version and what it added. - Where: Menu → Release Notes - Who: Anyone How: 1. Open the menu and click Release Notes. 2. Read each version's date and changes. What you’ll see: A list of Console versions with dates, for example v2.6.0 (28 Sep 2026) adding Transfer Activity. Watch for: - If a screen differs from this guide, trust the screen. Link: https://www.qatom.ai/capabilities#C33 ## Shared (Across the journeys) Steps that cross the journeys, or happen on the TODAQ side and are shown so you know what to expect. ### S1. Claim a Qatom offer when you sign up Sign up and claim an offer (e.g. a Max launch offer) Qatom sometimes offers a plan free for a period, for example a Max launch offer for event participants. You claim it from its qatom.ai page. - Where: qatom.ai offer page, then Qatom sign-in and dashboard.qatom.ai/onboarding - Who: Anyone How: 1. Open the qatom.ai offer page you were given and claim the offer. 2. Register or sign in with the same email (B34). 3. The Qatom team records the offer on your account. What you’ll see: Your account opens on the Dashboard. The offer doesn't show in the Dashboard yet; ask the Qatom team to confirm it. Watch for: - Settings → Billing may not show an active offer yet. Example: Event participants have received six months of Max free through a qatom.ai offer page. Link: https://www.qatom.ai/capabilities#S1 ### S2. Call the Qatom API from your server Use the client credentials (B30) for server-side calls (payouts, transactions) Your server uses the account's client credentials to get a token for API calls, such as payouts or finding who paid. They never leave the server. - Where: Dashboard → Settings → Secrets; token from /v4/account/oauth/token - Who: Seller - Secret: needs a secret How: 1. In the Dashboard, open Settings → Secrets. 2. Under Client credentials, copy the Client ID, then Reveal and copy the Client secret. 3. Put both in your server's secret store, never in a browser, app or repo. 4. Your server exchanges them for an account token at /v4/account/oauth/token, then calls the API. What you’ll see: Your server gets an account token and its API calls succeed. Watch for: - The Public secret is different: it is publishable and used by embeds and guest checkout. - Transfers spend from the primary twin; sweep item revenue there first (C17). - A /v4/transfer that returns 202 has moved the money; never retry it. Example: Centaur League's server finds who paid from commodity transactions and pays winners with /v4/transfer. Link: https://www.qatom.ai/capabilities#S2 ### S6. Look up any Qatom API call Read the API reference and OpenAPI The API reference and the OpenAPI document describe every v4 endpoint. Builders use them for server-side work and to generate clients. - Where: docs.qatom.ai, https://pay.m.todaq.net/v4/openapi.json - Who: Builder How: 1. Open docs.qatom.ai for the API reference. 2. Download the OpenAPI document from https://pay.m.todaq.net/v4/openapi.json. 3. For a public item list, call GET /v4/catalog/items, for example to build your llms.txt. What you’ll see: The OpenAPI document (TODAQ Micro Payment API 4.0.0) lists each endpoint with its method and path. Watch for: - If a guide or skill differs from the live OpenAPI, the OpenAPI wins. Link: https://www.qatom.ai/capabilities#S6 ### S10. One free line to Team Kepler, coming soon Team Kepler feedback item (coming soon): help, ratings, refund escalation and ideas A free catalog item will reach Team Kepler and route each message by topic: help and onboarding to Wizard Kepler; tool comments, ratings and refund escalation to Pirate Kepler; market ideas and risks to Agent Kepler. It is not in the catalog yet; until it is, use the seller's feedback item and support@todaq.net (A27). - Where: Team Kepler catalog on Qatom - Who: Anyone How: 1. Ask your agent to search the catalog for Team Kepler (catalog_search). 2. If it is listed, call it with agent_checkout; it is free. 3. Choose the topic (help, refund, rating or idea) and write your message. 4. For a refund, include the transaction id and say the seller didn't reply. What you’ll see: (to confirm) The receipt returns a reference for your message. Watch for: - (to confirm) The item's exact name and inputs; its spec is being finalised. - Until it is listed, email support@todaq.net. Link: https://www.qatom.ai/capabilities#S10 ### S11. Make every sign-in and approval one tap Set up a passkey (strongly recommended) Qatom asks you to sign in whenever something matters: connecting your AI, choosing a seller account, approving a purchase above your limit or an account change. With a passkey each of those is one tap or a fingerprint, instead of waiting for an emailed code. It stays on your own device. - Where: Qatom registration and sign-in screen (pay.m.todaq.net) - Who: Anyone with a Qatom login How: 1. The first time you sign in with an emailed code, Qatom offers "Sign in faster": click Set up a passkey. 2. Your device asks to save the passkey (on a Mac, in Passwords); confirm with your fingerprint or password. 3. Next time a Qatom page asks you to sign in (connecting, choosing a seller account, approving), choose Sign in with a passkey. 4. Register one on each device you approve from, such as your laptop and phone. What you’ll see: Sign-in and approval pages finish with one tap. Watch for: - The Console (console.todaq.net) signs in separately, with its own passkeys (Account → Passkeys, C2); your Qatom sign-in passkey doesn't work there. - Only you create or use your passkey; an agent never does. Link: https://www.qatom.ai/capabilities#S11 --- # Developer documentation (docs.qatom.ai) Source: https://docs.qatom.ai/ ## Qatom developer documentation Home of the developer docs: guides, the Payment JS and Payment Node SDKs, and the HTTP API reference (every v4 endpoint). Source: https://docs.qatom.ai/ ## HTTP API reference The HTTP API reference: every v4 endpoint for twins, commodities and payments. Source: https://docs.qatom.ai/ ## Getting Started Set up micropayments end to end: account keys, a twin and a commodity, pricing, then embed, mount and validate a payment element. Source: https://docs.qatom.ai/guide/getting-started/ ## Personas Personas are identity and access tokens that prove someone paid: delegate them to a twin after purchase and verify them later for membership or tiered access. Source: https://docs.qatom.ai/guide/personas/ ## Reactive payments Pause a video or audio stream at a set point, ask for payment with the payment element, and resume when the purchase event fires. Source: https://docs.qatom.ai/guide/reactive-payment/ ## Transparent payment button Overlay a transparent payment element on any part of your page to make it payable. Source: https://docs.qatom.ai/guide/transparent/ ## T.R.I.E. donation page example A full donation page in plain HTML with three amounts, each its own commodity, and a thank-you redirect on purchase. Source: https://docs.qatom.ai/guide/trie-donation-example/ ## Vite + React donation page example The donation page in Vite, React and TypeScript: install, configure, environment variables and a PaymentButton component. Source: https://docs.qatom.ai/guide/vite-react-donation-example/ ## Payment Element Payment JS reference: create a payment element from your public secret and a commodity hash, mount it, listen for payment events and validate on your server. Source: https://docs.qatom.ai/reference/payment-js/payment-element/ ## Auth Element Payment JS reference: let users authenticate for paywalled content, get a session token and call the simplified paywall API with just an amount. Source: https://docs.qatom.ai/reference/payment-js/auth-element/ ## Payment Node SDK: usage Server-side Node.js SDK: create commodities, validate payments before running a paid action, and manage twins. Source: https://docs.qatom.ai/reference/payment-node/usage/ --- # Qatom guides # What are agentic payments, and how do AI agents pay? Source: https://www.qatom.ai/learn/what-are-agentic-payments Updated: 2026-10-15 Agentic payments are payments that an AI agent starts and completes on behalf of a person or business. The agent finds a product or service, checks the price, pays from a wallet or token it was given, and keeps a receipt, all inside spending limits and approval rules that a human sets in advance. ## Key takeaways - In agentic payments, the agent handles discovery, payment and the receipt, while a human sets the budget and the approval rules. - Card fees of 2.9% plus 30 cents make card rails a poor fit for the small, per-call purchases agents make most often. - MCP lets AI assistants connect to tools, but the protocol itself has no payment step. - x402, AP2, ACP, Visa Intelligent Commerce and Mastercard Agent Pay each solve a different part of agent payments and can complement each other. - Safe agent spending rests on a separate small wallet, an auto-approve limit, human approval for larger purchases and a receipt for every call. ## What are agentic payments? Agentic payments are payments that software agents make within rules a person sets. For decades a human sat at every checkout: reading the price, typing a card number, clicking Pay. In an agentic payment the agent does those steps, and the human decides the budget and the approval rules up front. The payer can be an AI assistant buying a data lookup for its user, a coding agent paying for one API call, or a business agent ordering from a supplier's agent. The seller can be a person, a company or another agent. A payment counts as agentic when the decision to buy and the payment itself both happen inside the agent's workflow. Demand is growing quickly. IDC projects agent tasks rising from 44 billion a year in 2025 to 415 trillion by 2030. OpenRouter reported in August 2026 that agent transactions are growing 14 times faster than human digital transactions. ## How do AI agents pay? Most AI agent payments follow the same loop, whatever system sits underneath. 1. **Discover.** The agent searches for something that fits its task, such as a weather lookup, a dataset or a file. It reads the listing for the price, the seller and the inputs it must send. 2. **Check the rules.** The agent compares the price with what it is allowed to spend. Small amounts can be pre-approved; larger ones go to a human. 3. **Get approval if needed.** The person approves on a web page, in the chat or on a phone, often with a passkey. 4. **Pay.** The agent pays from a wallet, token or mandate it was given. It does not need the person's card number. 5. **Receive the result.** The seller's service returns what was bought: an answer, a download link, a stream. 6. **Keep the receipt.** The agent records a transaction id and a receipt, so the person can audit the spend or ask for a refund. The real differences between systems sit in steps 4 and 6: what the agent pays with, where the money settles, and how anyone proves the payment happened. ## Why do AI agent payments need new rails? Three things break when you hand today's online checkout to an agent. **Price size.** Agents often buy small things many times: one API call, one search, one record. Card processing is priced for larger purchases. Stripe's standard US online price is 2.9% plus 30 cents per successful domestic card transaction ([Stripe pricing](https://stripe.com/pricing)). On a $0.10 charge the fee is about $0.30, more than the sale itself. On a $1 charge the fee takes about a third. **Connection without payment.** The Model Context Protocol (MCP) is the open protocol many AI assistants use to connect to tools and data. Remote MCP servers authorize with OAuth 2.1, and MCP itself has no payment step ([MCP specification](https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization)). An agent can reach a tool, yet it has no standard way inside MCP to pay for it. **Trust and proof.** A merchant needs to know which agent is calling and who authorized it. The person needs proof of what the agent bought. Card statements and chat logs do neither job well across thousands of small, automated purchases. ## What is agentic commerce? Agentic commerce is the wider market that agentic payments serve. Agents discover products, compare them, order and pay, while sellers publish offers that agents can read. Payments are one layer; catalogs, discovery, approvals, delivery and payouts are the others. In agentic commerce, a buyer may never visit the seller's website. The buyer's agent reads a machine-readable listing, calls the seller's service and pays in one flow. Sellers who want those sales need listings agents can find, prices agents can understand and a way to get paid per use. Our guide on [how to sell an API to AI assistants](https://www.qatom.ai/learn/sell-to-ai-assistants) covers the seller side. ## Which protocols handle agentic payments? Several open protocols and card network programs launched in 2025. They solve different parts of the problem, and these approaches can complement each other. | System | Backed by | What the agent pays with | Where it settles | Typical fit | |---|---|---|---|---| | x402 | Created by Coinbase (2025); x402 Foundation at the Linux Foundation since April 2026 | A signed payment sent in an X-PAYMENT header after an HTTP 402 reply | Onchain, in stablecoins such as USDC on chains such as Base | Pay-per-request APIs for crypto-native builders | | AP2 | Google, with 60+ merchants and financial institutions | Signed intent and cart mandates | Depends on the payment method; a crypto extension integrates x402 | Agent shopping with a clear record of what the user allowed | | ACP | Stripe and OpenAI | A scoped, logged payment token passed to the merchant | Card rails | Instant Checkout in ChatGPT | | Visa Intelligent Commerce | Visa | Agents identified through the Trusted Agent Protocol | Card rails | Agent checkout at card-accepting merchants | | Mastercard Agent Pay | Mastercard | Agentic tokens bound to one agent | Card rails | Agent checkout at card-accepting merchants | | Qatom | TODAQ Micro Inc. | An agent wallet (twin) holding USD-TDN | Between twins, with no gas and no public ledger | Per-call APIs, data and services sold to agents | **x402** is an open protocol created by Coinbase, announced on 6 May 2025 and governed since April 2026 by the x402 Foundation under the Linux Foundation, that revives the HTTP 402 "Payment Required" status. The server answers with a price and accepted tokens, the client signs a payment and retries, and a facilitator verifies and settles onchain ([Coinbase](https://www.coinbase.com/developer-platform/discover/launches/x402)). Independent 2026 research found real x402 volume far below raw settlement counts and security gaps in payment facilitators, since mitigated; see [x402 in 2026](https://www.qatom.ai/learn/x402-in-2026). **AP2**, the Agent Payments Protocol, is an open protocol from Google announced on 16 September 2025. An intent mandate records what the user lets the agent look for and spend, and a cart mandate approves a specific purchase. A detailed intent mandate with price limits lets the agent buy without a second approval ([TechCrunch](https://techcrunch.com/2025/09/16/google-launches-new-protocol-for-agent-driven-purchases)). **ACP**, the Agentic Commerce Protocol, is an Apache 2.0 open standard co-developed by Stripe and OpenAI and announced on 29 September 2025. It powers Instant Checkout in ChatGPT ([Stripe](https://stripe.com/blog/developing-an-open-standard-for-agentic-commerce)). **Visa Intelligent Commerce** uses the Trusted Agent Protocol so merchants can verify the agents that call them. **Mastercard Agent Pay** issues agentic tokens bound to one agent that carry who authorized it ([RisingWave](https://risingwave.com/blog/mastercard-agent-pay-vs-visa-vs-stripe-agentic-commerce/)). The card-based options suit physical goods at checkout. For a deeper side-by-side, read [agent payment protocols compared](https://www.qatom.ai/learn/agent-payment-protocols-compared). ## How do you keep an AI agent's spending under control? The controls matter more than the protocol. Whatever system you use, look for these five. - **A separate, small budget.** Give the agent its own wallet and move only a little money into it. On Qatom the agent twin's balance is a hard ceiling, and the agent never touches your primary wallet or card ([move funds to your agent](https://www.qatom.ai/capabilities#A8)). - **An auto-approve limit.** Purchases under a limit you set go through without asking. - **Approval for larger purchases.** Above the limit, nothing is paid until you approve, in the chat or by passkey or phone app ([approve a purchase](https://www.qatom.ai/capabilities#A14)). - **A receipt for every call.** Each purchase should return a transaction id you can quote in a refund request. - **Care with retries.** A retried paid call is a new charge, so check the last receipt and the balance before retrying ([retry safely](https://www.qatom.ai/capabilities#A28)). Our guide on how to [let an AI agent make purchases](https://www.qatom.ai/learn/let-ai-agent-make-purchases) walks through each control step by step. ## Where does Qatom fit in agentic payments? Qatom is an all-in-one agentic commerce platform. Sellers turn APIs, data and services into catalog items, called storefronts, that AI agents discover, order from and pay for. Buyers' agents purchase the same way, inside spending limits the buyer sets, with a verifiable receipt for every call. Buyers connect any MCP client, such as Claude, Grok or Muse, to the Qatom master MCP at https://mcp.m.todaq.net/mcp and search with catalog_search ([connect your AI](https://www.qatom.ai/capabilities#A1)). Storefronts are discoverable in the assistants and channels listed on qatom.ai. The round trip runs from buyer agent to Qatom twin to seller agent in one call, with payment, delivery and a receipt returned together. Money inside Qatom is USD-TDN, a US-dollar token where 1 USD-TDN equals 1 USD. RBC holds the reserve funds backing USD inside Qatom and supports bank on-ramp and off-ramp transfers. Each twin is built on the TODA file protocol, so every holding is a self-verifying file and a receipt can be checked anywhere. On cost, Qatom charges a 0% platform take rate, no gas and no transaction fees, and transaction cost does not scale with the value or volume of a payment. Settlement takes under one second. Prices can go as low as 0.001 USD-TDN per call. Plans are Builder (free), Pro ($20 a month), Max ($300 a month) and Enterprise ([pricing](https://www.qatom.ai/#pricing)), with hosted, VPC, on-premises and air-gapped deployment. Developers can start with the [Qatom developer docs](https://docs.qatom.ai/). Qatom is headquartered in Toronto. Building on TODAQ research since 2017, it has been in production since 2023 on the TODA File Protocol and the ADOT Protocol ([about us](https://www.qatom.ai/about-us)). ## Next steps - Compare the main standards in [agent payment protocols compared](https://www.qatom.ai/learn/agent-payment-protocols-compared). - See why small payments need different rails in [micropayments for APIs](https://www.qatom.ai/learn/micropayments-for-ai-and-apis). - Browse every buyer and seller step in the [Capabilities Index](https://www.qatom.ai/capabilities), or [contact us](https://www.qatom.ai/contact) with questions. ## Frequently asked questions ### What are agentic payments? Agentic payments are payments an AI agent makes on a person's or business's behalf. The agent finds what it needs, pays from a wallet or token it was given, and keeps a receipt. A human sets the spending limits and approval rules in advance. ### How do AI agents pay for things? An AI agent pays with a credential it has been given, such as a separate wallet, a scoped payment token or a signed mandate. It does not need the person's card number. Purchases under a set limit can go through on their own, and larger ones wait for the person to approve. ### What is the difference between agentic payments and agentic commerce? Agentic commerce is the whole market of agents discovering, ordering and paying for products and services. Agentic payments are the payment layer inside it. Commerce also covers catalogs, discovery, delivery and payouts to sellers. ### Can an AI agent use my credit card? Several agent payment systems avoid giving the agent your card number. Card-based programs such as ACP and Mastercard Agent Pay pass the merchant a scoped or agent-bound token instead. Wallet-based systems let you fund a separate agent wallet, so the agent can only spend what that wallet holds. ### Are agentic payments safe? They can be, if the setup limits what the agent can spend. Common controls are a separate wallet with a small balance, an auto-approve limit for small purchases, human approval for larger ones and a receipt for every purchase. You should also check receipts before letting an agent retry a paid call, since a retry is a new charge. ### What protocols are used for AI agent payments? The main ones announced in 2025 are x402 (created by Coinbase and now run by the x402 Foundation), AP2 from Google, the Agentic Commerce Protocol from Stripe and OpenAI, Visa Intelligent Commerce and Mastercard Agent Pay. x402 settles in stablecoins onchain, ACP and the card network programs ride card rails, and AP2 uses signed mandates to record what the user allowed. ### Why don't card payments work for AI agents buying API calls? Card processing has a fixed fee per transaction. Stripe's standard US online price is 2.9% plus 30 cents, so a $0.10 charge costs more in fees than it earns. Agents often buy single calls priced well under a dollar, which card fees make uneconomic. ## Sources - [Stripe pricing](https://stripe.com/pricing) - [Coinbase: Introducing x402](https://www.coinbase.com/developer-platform/discover/launches/x402) - [Coinbase Developer Platform: x402 Foundation (Apr 2026)](https://docs.cdp.coinbase.com/x402/support/x402-foundation) - [Qatom: x402 in 2026, real volume and security research](https://www.qatom.ai/learn/x402-in-2026) - [TechCrunch: Google launches new protocol for agent-driven purchases](https://techcrunch.com/2025/09/16/google-launches-new-protocol-for-agent-driven-purchases) - [Stripe: Developing an open standard for agentic commerce](https://stripe.com/blog/developing-an-open-standard-for-agentic-commerce) - [RisingWave: Mastercard Agent Pay vs Visa vs Stripe agentic commerce](https://risingwave.com/blog/mastercard-agent-pay-vs-visa-vs-stripe-agentic-commerce/) - [Model Context Protocol specification: Authorization](https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization) --- # How to monetize an MCP server and charge per tool call Source: https://www.qatom.ai/learn/monetize-mcp-server Updated: 2026-10-14 To monetize an MCP server, add the payment step the protocol lacks: list each tool as a paid catalog item with a price per call, an HTTPS endpoint and an input schema. Buyer agents find it, pay from a wallet inside limits their owner sets, and get the result with a receipt. Qatom takes 0% of each sale. ## Key takeaways - MCP connects AI assistants to tools and authorizes them with OAuth 2.1, but it has no step for price, payment or receipt. - On Qatom, each paid tool becomes one catalog item with one price, and its name becomes the tool name buyer agents see. - Prices start at 0.001 USD-TDN per call, and 0 makes a tool free, so a free check can sit beside a paid tool. - Public items appear in catalog_search on the master MCP; private items are reachable only through your own MCP instance. - Buy every item once before you announce it, because a real purchase is the only full test of price, schema, header and endpoint. ## Step by step 1. **Register a seller account** Register at dashboard.qatom.ai, fill in your organization details, choose a plan and click Start my MCP server. Builder is free and needs no card. 2. **Pick one tool agents will pay for** Start with one tool that answers in one call and is cheap to serve. Decide what one answer costs you to produce and set a price per call. 3. **Put the tool behind one HTTPS endpoint** Host the tool's logic at an HTTPS endpoint that Qatom calls after each payment settles. The Worker template is the fastest start. 4. **Guard the paid route with a secret header** Generate a fulfillment token, store it in your host's secret store, and have the endpoint answer 404 unless the Authorization header carries it. 5. **Create a catalog item for the tool** Add a name with a brand prefix, a receipt descriptor, a price, the method and endpoint, a description, the input schema and the Sensitive Authorization header. 6. **Choose public or private visibility** Leave the item public to sell it through catalog search. Tick private only for tools that should stay on your own MCP instance, since the choice is fixed. 7. **Buy each item once, then announce** Connect the master MCP, fund a small agent wallet and buy each item with agent_checkout. Once each item shows in catalog_search, share your llms.txt. ## How do you monetize an MCP server? You monetize an MCP server by adding a payment step in front of each tool you want to charge for. MCP itself gives you discovery and calling, but nothing that sets a price, takes payment or returns a receipt. So the money has to come from a layer that works alongside the protocol. On Qatom, that layer is the catalog. Each paid tool becomes a catalog item with one price per call, one HTTPS endpoint and an input schema. A buyer's agent finds the item through MCP, pays from its own wallet, and gets your tool's answer plus a receipt in the same call. The full sequence is in the [Capabilities Index](https://www.qatom.ai/capabilities#B9). ## How does MCP work, and where do MCP payments fit? The [Model Context Protocol](https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization) is an open protocol for connecting AI assistants to tools and data. A client such as Claude connects to a server, lists the tools it offers, and calls a tool by name with arguments that match the tool's input schema. Remote servers authorize the client with OAuth 2.1. That authorization step answers "who is calling?". It does not answer "what does this cost?" or "has it been paid?". The specification has no message for a price, a payment or a receipt, which is why MCP payments sit in a separate layer. You can still publish a server to the [official MCP Registry](https://modelcontextprotocol.info/tools/registry/) so people can find and install it. A registry listing helps discovery. It does not collect money per call. ## What are the ways to charge for MCP tools? There are a few common patterns. Each fits a different kind of buyer. | Approach | How the buyer pays | Fits per-call pricing? | Where it fits | |---|---|---|---| | Subscription behind your own sign-in | Monthly plan, then OAuth access to the server | No, flat fee | Known customers who use the tools heavily | | Card checkout per call | Card charge on each use | No, card fees exceed small prices | Single purchases above a few dollars | | [x402](https://www.coinbase.com/developer-platform/discover/launches/x402) on your HTTP endpoint | Agent signs a stablecoin payment and retries the request | Yes, settles onchain | Builders already working with onchain wallets | | Qatom catalog item | Agent pays USD-TDN from its agent wallet | Yes, from 0.001 USD-TDN | Pay-per-call tools sold to any MCP client | Card fees are the main reason a per-call card model fails. [Stripe's](https://stripe.com/pricing) standard US online price is 2.9% + 30¢ per card transaction, so a $0.10 charge would cost about $0.30 in fees. These approaches can complement each other: a subscription for heavy users and a per-call catalog item for everyone else is a reasonable mix. ## What does a paid MCP server look like on Qatom? There are two MCP connections in the picture. Buyers connect their client to the Qatom master MCP at `https://mcp.m.todaq.net/mcp`, which gives their agent every public catalog item plus the wallet tools, including `catalog_search` and `agent_checkout`. That works in Claude, Grok, Muse or any other MCP client ([A1](https://www.qatom.ai/capabilities#A1)). As a seller, you also get your own MCP instance. Registering a seller account creates it ([B34](https://www.qatom.ai/capabilities#B34)), and the Dashboard shows it as your first MCP instance. Your items live on that instance, and public ones also show up in master search. The name of each catalog item becomes the tool name agents see ([B9](https://www.qatom.ai/capabilities#B9)). Use a shared prefix such as "Brand: item", so a `catalog_search` for your prefix finds all your items. The receipt line comes from the separate Descriptor field. ### Public or private: which should a paid MCP server use? Public items appear in `catalog_search` on the master MCP. Private items are reachable only through your own MCP instance, so they suit internal tools or an item built for one customer ([B14](https://www.qatom.ai/capabilities#B14)). Choose carefully. Visibility is set when you create the item and can't be changed in the Dashboard afterwards. To take a private item public, you duplicate it. ## How do you map an MCP tool to a catalog item? If you already have MCP tools, most of the work is a translation. Each tool definition has a name, a description and an input schema, and each maps to a field on the item form. | MCP tool field | Qatom catalog item field | Notes | |---|---|---| | name | Name | Becomes the tool name buyers see; use "Brand: item" | | description | Description | Up to 1,024 characters; say what returns and link your llms.txt | | inputSchema | Service schema | Paste as `{"inputSchema": {...}}`, set `"additionalProperties": false` | | tool handler | Method and Endpoint | GET, POST or PUT to the HTTPS URL Qatom calls after payment | | (none) | Price | 0 for free, otherwise at least 0.001 USD-TDN | | (none) | Descriptor | The line on the buyer's receipt | | (none) | Authorization header | Sensitive, carries your fulfillment token | Qatom forwards only the arguments your schema declares and rejects the rest ([B11](https://www.qatom.ai/capabilities#B11)). Give each property a description with its unit, range and default. Never accept raw SQL, code or query strings as inputs; turn them into named inputs. ## How to list your MCP tools as paid catalog items Follow these steps for each tool you want to sell. The [seller guide skill](https://www.qatom.ai/capabilities#B1) walks you through the same order inside your own agent. 1. **Register.** Go to dashboard.qatom.ai, register with an email code or passkey, fill in your organization, choose a plan and click Start my MCP server. The server takes a few minutes to become healthy. 2. **Pick the first tool.** Choose one that answers in one call and is cheap to serve, and pair it with a free check item. 3. **Host the endpoint.** Put the tool's logic behind one HTTPS endpoint. The Worker template reads one catalog.json, validates inputs, guards the paid route and serves `/llms.txt` ([B2](https://www.qatom.ai/capabilities#B2)). 4. **Guard the paid route.** Generate a token with `openssl rand -hex 24` and store it in your host's secret store. The endpoint checks the Authorization header and answers 404 when it is missing or wrong ([B3](https://www.qatom.ai/capabilities#B3)). 5. **Create the item.** Open Catalog, click + New item and fill in name, descriptor, price, method, endpoint, description and schema. Add the header `Authorization: Bearer ` marked Sensitive ([B12](https://www.qatom.ai/capabilities#B12)). 6. **Write the agent read-me.** Generate llms.txt from your catalog, with worked examples, input schemas and every error code, and serve it at your site root ([B4](https://www.qatom.ai/capabilities#B4)). 7. **Test by buying.** Connect the master MCP, fund a small agent wallet and buy each item once with `agent_checkout`, with and without inputs. Try a bad input too ([B19](https://www.qatom.ai/capabilities#B19)). 8. **Announce.** Run `catalog_search` for your brand prefix, check name, price and seller, then share your llms.txt URL ([B21](https://www.qatom.ai/capabilities#B21)). Headers are per item. If three paid tools share one endpoint, each item needs the Authorization header. ## How should you set MCP server pricing? Start from what one answer costs you to produce, then price each call above it. Prices are in USD-TDN, a US-dollar token where 1 USD-TDN equals 1 USD. The minimum paid price is 0.001, and prices use at most three decimals. One catalog item has one price. If you want a basic and a detailed version of a tool, list them as two items, and have each description say what the higher tier adds. A free sibling item lets an agent check that your tool fits before it pays. Two more points shape MCP server pricing: - **Agent wallets suit small prices.** Guest card checkout has a minimum of about $0.50, so tools priced under 50 cents should expect buyers paying from agent wallets. - **Your plan sets your limits.** Builder is free with 1 agent, up to 5 items and 25 transactions a month. Pro is $20 a month and Max is $300 a month; see [pricing](https://www.qatom.ai/#pricing). Qatom takes 0% of each sale. ## What does the buyer's agent experience when it pays? The buyer's agent calls `agent_checkout` with the item id and arguments. Payment comes from the agent twin, a wallet that holds only what its owner moved there, so the agent can never overspend it ([A13](https://www.qatom.ai/capabilities#A13)). Under the owner's auto-approve limit, the purchase settles at once. Above it, the owner approves in the chat or by passkey or phone app. Every purchase returns a transaction id and an emailed receipt with proof of purchase. A retry is a new charge, and a call your endpoint rejects can still be charged. Design each tool to answer in one call, and return every error with a code, a plain message and a next step. For tools that are expensive to serve, verify each call against the transaction id; the [per-call API guide](https://www.qatom.ai/learn/charge-ai-agents-per-api-call) covers that check in detail. ## How do you get paid when you monetize an MCP server? Each sale lands on the item's own twin. A standing distribution sweeps it to your primary twin a few times a day ([C17](https://www.qatom.ai/capabilities#C17)), and a distribution can also split revenue across up to 200 payees. From the primary twin, you can cash out to a US or Canadian bank account. The minimum is 10 USD-TDN, the fee is a flat $1, and ACH takes 2 to 5 business days ([C26](https://www.qatom.ai/capabilities#C26)). Sales counts and earnings per item show on each item page. ## What did MCP Dev Summit Toronto 2026 say about paid MCP tools? At [MCP Dev Summit Toronto 2026](https://www.qatom.ai/events) (5 to 6 October), a common thread across the published talks was that trust and identity, not the protocol, are now the hard parts. Three points matter when you charge for MCP tools. - **Design tools from tasks, not endpoints.** Several talks, such as "Stop Wrapping Endpoints" and Poka's "Your MCP Is Not an API Gateway", warned that a 1:1 wrapper around a REST API makes a poor MCP server. Name each paid tool by the outcome it delivers, keep inputs short, and return errors that tell the agent what to call next. This maps directly onto one catalog item per outcome. - **Fewer, sharper tools cost less context.** AMD's talk "Too Many Tools" measured each tool schema at about 204 tokens, so a long tool list crowds the model's context window. A small catalog of clearly named items is easier for an agent to choose from. - **Meter where the call happens.** Kong's talk "From Tool Calls to Revenue" made the case that every tool call is an economic event and that metering belongs in the request path: "a meter that cannot say no is accounting, not control." On Qatom, payment settles before Qatom calls your endpoint, and your secret header turns away calls that did not come from Qatom. Qatom ran a workshop at the summit on exactly this flow: list an item once, agents find it, pay, then receive it. ## Next steps - Follow every seller step in the [Capabilities Index](https://www.qatom.ai/capabilities#B34). - Read [how to charge AI agents for API calls](https://www.qatom.ai/learn/charge-ai-agents-per-api-call) for endpoint security and fulfillment checks. - Compare plans on the [pricing page](https://www.qatom.ai/#pricing), or [contact the team](https://www.qatom.ai/contact) about VPC, on-premises or air-gapped deployment. ## Frequently asked questions ### Can you charge for MCP tools? Yes, but the Model Context Protocol has no payment step of its own, so you add one alongside it. On Qatom, each paid tool is listed as a catalog item with a price per call. Buyer agents pay from a wallet and receive the tool's result and a receipt in the same call. ### How much does it cost to run a paid MCP server on Qatom? Qatom takes a 0% platform cut and charges no gas or transaction fees on sales. Plans are Builder (free), Pro ($20/month), Max ($300/month) and Enterprise. Builder covers 1 agent, up to 5 items and 25 transactions a month. ### What is the lowest price I can charge per MCP tool call? The smallest paid price is 0.001 USD-TDN per call, and a price of 0 makes the item free. Prices use no more than three decimals. One catalog item has one price, so several price tiers means several items. ### Does MCP have built-in payments? No. MCP covers how an AI client connects to a server, lists its tools and calls them, and remote servers authorize with OAuth 2.1. Authorization tells the server who is calling; it does not move money or produce a receipt. ### How do AI agents find my paid MCP tools? Buyers connect any MCP client to the Qatom master MCP at https://mcp.m.todaq.net/mcp and search with catalog_search. Each public item shows its name, description, price, seller and input schema. Agents also read the llms.txt file your item descriptions link to. ### What is the difference between public and private catalog items? Public items appear in catalog_search on the master MCP and can be bought there. Private items are reachable only through your own MCP instance, which suits internal tools or a single customer. Visibility is chosen at creation and can't be changed in the Dashboard later. ### How do buyers stay in control of what their agent spends? The agent spends from its own agent wallet and can never spend more than that wallet holds. Purchases under an auto-approve limit the owner sets go through without asking; larger ones need the owner's approval in the chat or by passkey or phone app. ### How do I get paid for MCP tool sales? Each sale lands on the item's own twin, and a standing distribution can sweep it to your primary twin. From there you can cash out to a US or Canadian bank account: at least 10 USD-TDN, a $1 fee, and ACH in 2 to 5 business days. ## Sources - [Model Context Protocol specification: Authorization](https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization) - [Official MCP Registry](https://modelcontextprotocol.info/tools/registry/) - [Coinbase: Introducing x402](https://www.coinbase.com/developer-platform/discover/launches/x402) - [Stripe pricing](https://stripe.com/pricing) - [Qatom developer docs](https://docs.qatom.ai/) --- # How to charge AI agents for API calls, one call at a time Source: https://www.qatom.ai/learn/charge-ai-agents-per-api-call Updated: 2026-10-15 To charge AI agents for API calls, put your API behind one HTTPS endpoint, guard it with a secret header only the payment platform sends, and list it with a price per call and an input schema. The agent pays before your endpoint runs, and you verify each call against its transaction id. On Qatom, prices start at 0.001 USD. ## Key takeaways - Card fees of 2.9% + 30¢ make a $0.10 card charge cost more in fees than it earns, so per-call pricing needs another rail. - Qatom calls your endpoint only after payment settles, with a Sensitive Authorization header your endpoint checks on every call. - The input schema decides which arguments reach your API; Qatom forwards only declared arguments and rejects the rest. - For expensive calls, check X-Qatom-Transaction-Id against the purchases API so each sale is served once. - Qatom takes 0% of each sale; cashing out to a bank costs a flat $1 with a 10 USD-TDN minimum. ## Step by step 1. **Put the API behind one HTTPS endpoint** Host one endpoint that Qatom calls after each payment settles. Give each item a permanent lowercase ID, named inputs and an error code with a next step for every failure. 2. **Create a fulfillment token** Generate a token with openssl rand -hex 24 and store it in your host's secret store and a password manager. The endpoint answers 404 unless the Authorization header carries it. 3. **Write the input schema** Declare one property per real input, each with a description, unit, range and default, and set additionalProperties to false. 4. **Create a catalog item with a per-call price** Add the name, receipt descriptor, price, method, endpoint, description, schema and the Sensitive Authorization header, then click Create item. 5. **Publish an llms.txt read-me** Generate llms.txt from your catalog with worked examples and error codes, serve it at your site root, and link it from every item description. 6. **Buy each item once** Fund a small agent wallet, buy each item through the master MCP with valid and invalid inputs, and check the receipt shows your endpoint's answer. 7. **Verify fulfillment calls for expensive items** Read X-Qatom-Transaction-Id, look it up with GET /v4/catalog/purchases/{transaction_id}, refuse unknown ids and record each id you serve. ## What does it mean to charge AI agents for API calls? To charge AI agents for API calls is to bill each request on its own, at the moment the agent makes it. No contract, no monthly invoice: the agent pays a set price, your API runs, and the agent gets the answer. The model fits agents well, because they often need one lookup or one computation and nothing more. Any HTTP API can work this way. Weather, pricing data, a model you host, a document conversion or a file download are all single calls with a clear result. What you need is a way to collect a tiny payment before the call, prove to your server that it was paid, and keep a record both sides trust. ## Why don't cards work for a pay per call API? Card pricing has a fixed part that small charges can't absorb. [Stripe's](https://stripe.com/pricing) standard US online price is 2.9% + 30¢ per successful domestic card transaction. | Price per call | Card fee at 2.9% + 30¢ | Share of the price lost | Qatom platform fee | |---|---|---|---| | $0.10 | $0.3029 | More than the price | 0 | | $1.00 | $0.329 | About a third | 0 | | 0.001 USD-TDN | Not practical | Not practical | 0 | Card-based agent checkout systems, such as the [Agentic Commerce Protocol](https://stripe.com/blog/developing-an-open-standard-for-agentic-commerce) behind Instant Checkout in ChatGPT, suit buying physical goods. For a pay per call API priced in cents or fractions of a cent, the fee structure is the problem. Qatom charges no transaction fees and no gas, so the cost of a payment does not grow with its value or volume. ## How does API monetization for AI agents work on Qatom? API monetization for AI agents on Qatom follows one round trip: buyer agent, Qatom twin, seller endpoint, in one call. Here is what happens when an agent buys one call to your API. 1. The agent finds your item with `catalog_search` and reads its price, seller and input schema. 2. It calls `agent_checkout` with the item id and arguments. 3. Payment settles from the buyer's agent wallet in under one second. Above the owner's auto-approve limit, the owner approves first. 4. Qatom calls your endpoint with the declared arguments, your Authorization header and an `X-Qatom-Transaction-Id` header. 5. Your answer returns to the agent inside a receipt with the transaction id, and the buyer gets an emailed receipt. Your endpoint only runs after step 3 ([B2](https://www.qatom.ai/capabilities#B2)). Behind the scenes, each catalog item works through its own provider twin, which acts as a paywall in front of your HTTPS service ([C21](https://www.qatom.ai/capabilities#C21)). ### x402 vs a catalog: which fits your API? [x402](https://www.coinbase.com/developer-platform/discover/launches/x402), created by Coinbase in May 2025 and governed since April 2026 by the x402 Foundation under the Linux Foundation, revives HTTP 402 "Payment Required". Your server answers 402 with a price, the client signs a stablecoin payment and retries with an `X-PAYMENT` header, and a facilitator settles onchain on chains such as Base. It fits teams that want payment inside the HTTP exchange and already work with onchain wallets. If you go this way, choose a facilitator that has adopted the fixes from the July 2026 [x402 security research](https://www.qatom.ai/learn/x402-in-2026), settle before you serve the response, and decide how you will handle refunds, which the protocol does not cover. Qatom settles USD-TDN between twins with no gas and no public ledger, and adds the parts around the payment: a catalog agents search, wallets with spending limits, approvals, receipts and payouts. These approaches can complement each other. The [protocol comparison](https://www.qatom.ai/learn/agent-payment-protocols-compared) covers AP2, ACP and the card networks too. ## How do you set up the endpoint and secret header? To charge AI agents for API calls safely, start with the endpoint, because its answer is what the buyer's agent receives. The Worker template reads one catalog.json, validates inputs, guards the paid route and serves `/llms.txt`. 1. **Name things once.** Give each item one permanent lowercase ID and a one-sentence summary in every response. 2. **Return useful errors.** Every error needs a code, a plain message and a next step, for example `unknown_parameter` 400 or `bad_value` 400. 3. **Test directly first.** Call the endpoint yourself before testing through Qatom, since a failed call may be relayed as a generic payment error. 4. **Generate the token.** Run `openssl rand -hex 24` on your own machine and store the result, for example with `wrangler secret put QATOM_FULFILMENT_TOKEN`. 5. **Check it on every call.** Compare the Authorization header in constant time and answer 404 when it is missing or wrong ([B3](https://www.qatom.ai/capabilities#B3)). 6. **Set it on each item.** In Request headers & secret parameters, add `Authorization` as Sensitive with the value `Bearer `, then save ([B12](https://www.qatom.ai/capabilities#B12)). Keep secrets out of the endpoint URL, since other dashboard users can see it. Never echo request headers in a response. If a token may have leaked, rotate it with a short overlap where the endpoint accepts both values ([B24](https://www.qatom.ai/capabilities#B24)). ## How do you define the input schema? The schema is the contract between the agent and your API. Qatom forwards only the arguments it declares and rejects the rest ([B11](https://www.qatom.ai/capabilities#B11)). - **One property per real input.** Give each a description with its unit, range and default. For example, a video item takes one optional `ttl_seconds` input from 60 to 86400, default 3600. - **Close it.** Set `"additionalProperties": false`. - **No free-form code.** Never accept raw SQL, code or query strings; turn them into named inputs. - **Describe formats.** Leave example IDs out of the schema and describe the format instead. Paste it into the Service schema editor as `{"inputSchema": {...}}` and click Format. The editor confirms the tool arguments, or says the tool takes none. ## How do you verify each fulfillment call? The secret header proves a call came from Qatom. For anything expensive to serve, such as stream keys, downloads or game entries, also prove the call matches a settled sale of that item ([B20](https://www.qatom.ai/capabilities#B20)). 1. Read the `X-Qatom-Transaction-Id` header on the incoming call. 2. Get an account token with your client credentials from `/v4/account/oauth/token`, on your server only ([S2](https://www.qatom.ai/capabilities#S2)). 3. Call `GET /v4/catalog/purchases/{transaction_id}`. 4. Refuse the call if the id is unknown or belongs to another item. 5. Store the ids you have served so no sale is served twice. Cheap reads can rely on the header alone. The [OpenAPI document](https://pay.m.todaq.net/v4/openapi.json) lists every v4 endpoint, and the [developer docs](https://docs.qatom.ai/) cover the Payment Node SDK. ## How do you set usage-based API pricing? Usage-based API pricing here means a fixed price per call, so revenue tracks volume. Before you charge AI agents for API calls, work out what one answer costs you to produce. Prices are in USD-TDN (1 USD-TDN equals 1 USD), from 0.001 per call, with at most three decimals. | Price per call | Calls | Gross revenue | Qatom fee | One cash-out fee | You receive | |---|---|---|---|---|---| | 0.001 | 10,000 | 10.00 | 0 | 1.00 | 9.00 | | 0.005 | 10,000 | 50.00 | 0 | 1.00 | 49.00 | | 0.010 | 10,000 | 100.00 | 0 | 1.00 | 99.00 | | 0.050 | 10,000 | 500.00 | 0 | 1.00 | 499.00 | The cash-out fee is a flat $1 per bank transfer, with a 10 USD-TDN minimum, so cashing out less often keeps more of small-price revenue. Your plan also matters: Builder is free with up to 25 transactions a month, and Pro ($20/month) and Max ($300/month) are on the [pricing page](https://www.qatom.ai/#pricing). A few rules shape the price list: - **One item, one price.** Tiers are separate items, and each description says what the higher tier adds. - **Add a free check.** A 0-priced sibling lets an agent confirm fit before paying. - **Quantity is per copy.** A buyer can add up to 20 of an item to a cart, and each copy is its own purchase with its own transaction id. - **Small prices suit wallets.** Guest card checkout has a minimum of about $0.50. ## Why should metering sit in the request path? Usage-based pricing usually means counting calls and billing at the end of the month. With AI agents as customers, that leaves you carrying the risk: an agent can make thousands of calls before anyone checks the bill. Kong's talk "From Tool Calls to Revenue" at [MCP Dev Summit Toronto 2026](https://www.qatom.ai/events) put it simply: "a meter that cannot say no is accounting, not control." Charging per call through Qatom puts the meter in the request path. The buyer's agent pays first, Qatom calls your endpoint with your secret header, and you check the transaction id before serving. There is no invoice to chase, and Qatom calls your endpoint only after payment settles. ## How do you sell API access to AI agents once it is live? Buy every item once through the master MCP before you tell anyone ([B19](https://www.qatom.ai/capabilities#B19)). Then run `catalog_search` for your brand prefix and check each item's name, price and seller name ([B21](https://www.qatom.ai/capabilities#B21)). To sell API access to AI agents, be where they look. Buyers reach the catalog from any MCP client, and from the assistants and channels listed on qatom.ai. Agents read your llms.txt before calling, so link it from every item description ([B4](https://www.qatom.ai/capabilities#B4)). After launch, each item page shows its sales count and earnings. A distribution can split revenue across up to 200 payees, and cash-outs go to US or Canadian bank accounts by ACH in 2 to 5 business days. ## Next steps - Read [how to monetize an MCP server](https://www.qatom.ai/learn/monetize-mcp-server) if your API is already exposed as MCP tools. - Work through the seller steps in the [Capabilities Index](https://www.qatom.ai/capabilities#B1). - [Contact the team](https://www.qatom.ai/contact) about hosted, VPC, on-premises or air-gapped deployment. ## Frequently asked questions ### How do I charge AI agents for API calls? List the API as a catalog item with a price per call, an HTTPS endpoint, an input schema and a secret header. A buyer's agent pays from its wallet, the platform calls your endpoint with the declared arguments, and your answer comes back to the agent with a receipt. On Qatom, this happens in one call. ### What is the minimum price per API call? On Qatom, the smallest paid price is 0.001 USD-TDN per call, and 0 makes an item free. 1 USD-TDN equals 1 USD. Prices use no more than three decimals. ### Why not charge AI agents per API call with a card? Stripe's standard US online price is 2.9% + 30¢ per card transaction. A $0.10 charge would cost about $0.30 in fees, and a $1 charge loses about a third. Per-call prices need a rail whose cost does not scale with each payment. ### How does my API know a call was paid for? Qatom sends a Sensitive Authorization header that you set on every fulfillment call, and your endpoint refuses calls without it. For expensive items, you also read the X-Qatom-Transaction-Id header and confirm it with GET /v4/catalog/purchases/{transaction_id}. ### Can I offer different prices for the same API? Yes, as separate items. One catalog item has one price, so a basic and a detailed tier are two items, and each description should say what the higher tier adds. A free check item beside a paid one helps agents decide. ### What happens if an agent retries a paid API call? A retry is a new charge, even under the buyer's auto-approve limit, and a call your endpoint rejects can still be charged. Return clear error codes so agents don't retry blindly. Recording served transaction ids stops one sale being served twice. ### How is x402 different from selling API access on Qatom? x402 is an open protocol, created by Coinbase and now run by the x402 Foundation, where the server answers HTTP 402 with a price and the client retries with a signed stablecoin payment that settles onchain. Qatom lists the API in a catalog agents search, settles USD-TDN between wallets with no gas, and returns a receipt that verifies anywhere. ### How do I get the money from API sales? Sales land on each item's twin, and a standing distribution sweeps them to your primary twin. You can then cash out to a US or Canadian bank account, with a 10 USD-TDN minimum, a $1 fee and ACH in 2 to 5 business days. ## Sources - [Stripe pricing](https://stripe.com/pricing) - [Coinbase: Introducing x402](https://www.coinbase.com/developer-platform/discover/launches/x402) - [Coinbase Developer Platform: x402 Foundation (Apr 2026)](https://docs.cdp.coinbase.com/x402/support/x402-foundation) - [Qatom developer docs](https://docs.qatom.ai/) - [Qatom Payment API OpenAPI document](https://pay.m.todaq.net/v4/openapi.json) --- # Agent payment protocols compared: x402, AP2, ACP, Visa, Mastercard and Qatom Source: https://www.qatom.ai/learn/agent-payment-protocols-compared Updated: 2026-10-15 Agent payment protocols compared: x402 lets an HTTP API charge per request in stablecoins, AP2 proves what a user authorized with signed mandates, ACP runs checkout inside ChatGPT on card rails, and Visa and Mastercard identify and tokenize agents for card payments. Qatom is a full stack for per-call sales, with wallets, approvals and receipts. ## Key takeaways - x402, AP2, ACP, Visa Intelligent Commerce and Mastercard Agent Pay each solve a different layer: payment handshake, authorization, checkout or agent identity. - x402 and the AP2 crypto path settle onchain in stablecoins; ACP, Visa and Mastercard ride card rails. - Card fees of 2.9% + 30 cents make sub-dollar and per-call prices uneconomic, which matters for APIs and data. - Qatom settles USD-TDN between wallets with no gas and no Qatom transaction fee, and adds catalog, discovery, approvals and receipts. - Independent 2026 research found real x402 volume far below raw settlement counts and 49 security-rule violations across the 15 facilitators studied, since mitigated. In the base protocol, payment and delivery are separate steps and there is no dispute process. - These approaches can complement each other: AP2 already integrates x402 through a crypto extension. ## Agent payment protocols compared: what does each one do? Six names come up whenever people talk about AI agents paying for things. They overlap less than it seems. Some move money, some prove what the user allowed, and some tell a merchant which agent is calling. With agent payment protocols compared in one table, the split becomes clear. Sources for each system are linked further down the page. | | x402 | AP2 | ACP | Visa Intelligent Commerce | Mastercard Agent Pay | Qatom | |---|---|---|---|---|---|---| | **Led by** | x402 Foundation (Linux Foundation) since April 2026; created by Coinbase | Google, backed by 60+ merchants and financial institutions | Stripe and OpenAI | Visa | Mastercard | TODAQ Micro Inc. (Qatom) | | **Announced** | May 6, 2025 | September 16, 2025 | September 29, 2025 | 2025 | 2025 | Founded 2023 | | **License or model** | Open protocol | Open protocol | Open standard, Apache 2.0 | Card network program | Card network program | Platform: hosted, VPC, on-premises or air-gapped | | **Layer it covers** | Payment handshake over HTTP | User authorization (mandates) | Checkout between agent, merchant and payment provider | Agent identity and merchant verification | Agent-bound payment credentials | Full stack: catalog, discovery, wallets, approvals, receipts, payouts | | **How money moves** | Stablecoins such as USDC, settled onchain on chains such as Base | Partner payment methods; a crypto extension integrates x402 | Card rails, with a scoped, logged payment token | Card rails | Card rails | USD-TDN between wallets (twins), no gas, no public ledger | | **How the user stays in control** | Client signs each payment | Intent mandate and cart mandate | Scoped, logged payment token passed to the merchant | Trusted Agent Protocol lets merchants verify the agent | Agentic token carries who authorized it | Auto-approve limit; larger buys need approval in chat or by passkey or phone app | | **Payment and delivery** | Separate steps: verify, serve, then settle, so a seller can deliver and not be paid | Set by the payment method used | Card authorization, separate from fulfilment | Card authorization, separate from fulfilment | Card authorization, separate from fulfilment | Payment settles in the call; the seller checks the transaction id before fulfilling | | **Disputes and refunds** | No built-in process; a refund is a new transfer | Signed mandates give evidence of what the user approved | Card network dispute and chargeback process | Card network dispute and chargeback process | Card network dispute and chargeback process | Approval above a set limit, and a transaction id and receipt for every purchase | | **Best fit** | Pay-per-request HTTP APIs for buyers with stablecoin wallets | Agent shopping where proof of consent matters | Merchants selling inside ChatGPT | Merchants who want to recognize trusted agents | Card checkout tied to a known agent | Per-call APIs, data and services, from 0.001 USD-TDN per call | ## Why are there so many agent payment protocols? Agent commerce has several jobs to do, and each protocol picked one or two. An agent has to find a seller, prove who it is, show what its user allowed, pay, and get a record of the payment. IDC projects agent tasks growing from 44 billion a year in 2025 to 415 trillion by 2030, so every part of that chain is getting attention. The Model Context Protocol (MCP) sits underneath many of these. It connects AI assistants to tools and data, and remote servers [authorize with OAuth 2.1](https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization). MCP itself has no payment step, so any paid tool needs a payment layer on top. For the bigger picture, read [what agentic payments are](https://www.qatom.ai/learn/what-are-agentic-payments). ## What is x402? [x402](https://www.coinbase.com/developer-platform/discover/launches/x402) is an open payment protocol created by Coinbase and announced on May 6, 2025 with AWS, Anthropic, Circle and NEAR. Since April 2, 2026 it has been governed by the [x402 Foundation](https://docs.cdp.coinbase.com/x402/support/x402-foundation) under the Linux Foundation, whose premier members include AWS, American Express, Cloudflare, Coinbase, Google, Mastercard, Shopify, Stripe and Visa. It revives the HTTP 402 "Payment Required" status code. The flow has four parts: 1. The client requests a resource, and the server answers 402 with the price and the tokens it accepts. 2. The client signs a payment and retries the request with an `X-PAYMENT` header. 3. A facilitator verifies the payment and settles it onchain, in stablecoins such as USDC on chains such as Base. 4. The server returns the data with an `X-PAYMENT-RESPONSE` header. x402 fits API sellers who want payment inside the HTTP request itself and buyers who already hold stablecoins. ## x402 in 2026: what the independent evidence shows In 2026, analysts and security researchers published the first independent measurements of x402. Their findings matter for anyone choosing a rail: - **Real volume is a fraction of raw counts.** A Visa and Artemis analysis put adjusted volume at roughly $15 million across about 109.6 million transactions through April 21, 2026, an average of about $0.14 ([Forkast](https://forkast.news/visa-artemis-the-0-14-reality-of-agent-commerce/)). TRM Labs counted 198.9 million settlements worth about $52.7 million, of which $25.62 million looked like real commerce, and estimated that 0.6% to 7.5% of that came from AI agents ([Decrypt](https://decrypt.co/378103/ai-agents-spending-money-research)). - **Facilitators had security gaps.** A July 2026 study, accepted to USENIX Security 2026, tested 15 major x402 facilitators covering about 99% of observed x402 transactions. It found 49 security-rule violations, which mapped to 31 previously unknown vulnerabilities, including ways to get a service without paying, and every facilitator violated at least one of its eight rules ([arXiv 2607.19545](https://arxiv.org/abs/2607.19545); [USENIX](https://www.usenix.org/conference/usenixsecurity26/presentation/wang-qinying)). - **Payment and delivery are separate.** Verifying a payment does not lock the funds, and the seller usually delivers before settlement. The [A402 paper](https://arxiv.org/abs/2603.01179) says x402 "fails to enforce end-to-end atomicity across service execution, payment, and result delivery." - **No one owns disputes.** There is no built-in dispute process, and a refund is a new transfer. The fair counterpoints: the security findings were disclosed responsibly and the affected parties, including Coinbase, adopted mitigations. Artemis expects the share of gamed activity to fall as teams move to production ([CoinDesk](https://www.coindesk.com/markets/2026/03/11/coinbase-backed-ai-payments-protocol-wants-to-fix-micropayment-but-demand-is-just-not-there-yet)). And the fix Four Pillars proposes, accountable operators that settle before delivery and handle disputes, builds on the open standard rather than replacing it. The full picture is in [x402 in 2026](https://www.qatom.ai/learn/x402-in-2026). ## What is AP2 (Agent Payments Protocol)? [AP2](https://techcrunch.com/2025/09/16/google-launches-new-protocol-for-agent-driven-purchases) is an open protocol from Google, announced on September 16, 2025. More than 60 merchants and financial institutions back it, including Mastercard, American Express and PayPal. AP2 is about proof of consent. It uses signed "mandates." An intent mandate records what the user allows the agent to look for and spend. A cart mandate records approval of a specific purchase. If the intent mandate is detailed and includes price limits, the agent can buy without asking for a second approval. ## x402 vs AP2: what is the difference? x402 answers "how does this request get paid?" AP2 answers "what did the user allow, and can we prove it?" They sit at different layers. They also work together. AP2 has a crypto extension that integrates x402, so an AP2 mandate can authorize a purchase that x402 then settles in stablecoins. If you are weighing x402 vs AP2, the real question is whether you need a payment rail, a consent record, or both. ## What is the Agentic Commerce Protocol (ACP)? The [Agentic Commerce Protocol](https://stripe.com/blog/developing-an-open-standard-for-agentic-commerce) is an open standard co-developed by Stripe and OpenAI, announced on September 29, 2025 under the Apache 2.0 license. The spec is published at agenticcommerce.dev. ACP powers Instant Checkout in ChatGPT. The payment provider passes the merchant a scoped, logged payment token, and the payment runs on card rails. It suits merchants who sell goods and want to be bought from inside ChatGPT. ## Agentic Commerce Protocol vs AP2 Both are open, and both came out in September 2025. ACP defines a checkout: the conversation between agent, merchant and payment provider that ends in a paid order. AP2 defines the authorization: signed mandates that prove the user approved the search, the spend or the specific cart. In practice, ACP is tied to a live surface, Instant Checkout in ChatGPT, with Stripe as a co-author. AP2 has 60+ merchants and financial institutions behind it and a crypto path through x402. A merchant focused on ChatGPT buyers will look at ACP first. A merchant that needs a signed consent record will look at AP2. ## Visa Intelligent Commerce vs Mastercard Agent Pay Both card networks announced agent programs in 2025, and [both run on card rails](https://risingwave.com/blog/mastercard-agent-pay-vs-visa-vs-stripe-agentic-commerce/). - **Visa Intelligent Commerce** comes with the Trusted Agent Protocol. It covers how agents identify themselves to merchants and how merchants verify them. - **Mastercard Agent Pay** issues "agentic tokens" bound to a specific agent. Each token carries who authorized it. The difference in focus is identity versus credentials. Visa's approach helps a merchant decide whether to trust the agent at the door. Mastercard's approach ties the payment credential itself to the agent and its authorizer. For merchants who already accept cards, both extend familiar infrastructure to agents. ## Where do card rails stop working for agents? Card rails work well for buying physical goods at a checkout. They struggle with small payments. Stripe's [standard US online price](https://stripe.com/pricing) is 2.9% + 30 cents per successful domestic card transaction. | Charge | Card fee at 2.9% + 30¢ | Fee as share of the charge | |---|---|---| | $0.10 | $0.3029 | More than the charge itself | | $1.00 | $0.329 | About a third | That arithmetic is why ACP, Visa and Mastercard fit checkout-sized purchases, and why per-call API pricing needs a different rail. The [micropayments guide](https://www.qatom.ai/learn/micropayments-for-ai-and-apis) covers this in more depth. ## What are the x402 alternatives for per-call payments? If you want to charge per request without card fees, the x402 alternatives in this list split two ways. The card-based options add card fees on every call. Full-stack platforms handle money movement, discovery and records for you, and Qatom is one of these. Qatom is a turnkey agentic commerce platform. Your APIs, data and services become catalog items ("storefronts") that AI agents discover, order from and pay for. Money inside Qatom is USD-TDN, a US-dollar token (1 USD-TDN = 1 USD), and RBC holds the reserve funds backing it. Here is how it compares on the points that matter for per-call pricing: - **Settlement:** x402 and AP2's crypto path settle on a public blockchain with stablecoins. Qatom settles USD-TDN between wallets called twins, with no gas and no public ledger. qatom.ai states settlement in under one second. - **Fees:** Qatom has a 0% platform take rate and charges no transaction fees, so cost does not scale with payment value or volume. See [plans and pricing](https://www.qatom.ai/#pricing). - **Price floor:** items can cost as little as 0.001 USD-TDN per call, or 0 for free ([create a catalog item](https://www.qatom.ai/capabilities#B9)). - **Receipts:** each purchase returns a transaction id and an emailed receipt. Twins are built on the TODA file protocol, so a receipt can be checked anywhere. - **Buyers:** any MCP client connects to the [Qatom master MCP](https://www.qatom.ai/capabilities#A1), and storefronts are discoverable in the assistants and channels listed on qatom.ai. - **Control:** purchases under an auto-approve limit go through; larger ones wait for [your approval](https://www.qatom.ai/capabilities#A14). The trade-off is scope. Qatom is a platform you sign up to, with plans from Builder (free) to Enterprise. x402 is an open protocol you implement yourself. ## Which agent payment protocol should you use? Once you have the agent payment protocols compared, start from what you sell and where your buyers already are. These approaches can complement each other, so you may end up with more than one. - **You sell physical goods and want ChatGPT buyers:** ACP, through Instant Checkout. - **You need proof of what the user approved:** AP2 mandates, with x402 if you want the crypto path. - **You already take cards and want to recognize agents:** Visa Intelligent Commerce or Mastercard Agent Pay. - **You run an HTTP API and your buyers hold stablecoins:** x402, with a facilitator that has adopted the 2026 security fixes, settlement before you deliver, and a plan for refunds. - **You sell APIs, data or services per call and want catalog, discovery, wallets, approvals and payouts in one place:** Qatom. To make the call, work through these steps: 1. Write down your typical price per sale. Below a dollar, rule out card-only rails. 2. List where your buyers' agents run: ChatGPT, another assistant, or any MCP client. 3. Decide whether you need a signed consent record, a payment rail, or both. 4. Check what each option asks of you: implementing a spec, joining a card program, or signing up to a platform. 5. Ask how each option handles a payment that fails after delivery, and a refund or dispute. 6. Run one real test purchase end to end before you announce anything. If you are a buyer setting rules for your own agent, read [how to let an AI agent make purchases safely](https://www.qatom.ai/learn/let-ai-agent-make-purchases). ## Next steps - Sell your first item per call: [how to monetize an MCP server](https://www.qatom.ai/learn/monetize-mcp-server). - Read the developer docs for the Payment Node SDK and HTTP API v4 at [docs.qatom.ai](https://docs.qatom.ai/). - Talk to the team about your use case on the [contact page](https://www.qatom.ai/contact). ## Frequently asked questions ### What is the difference between x402 and AP2? x402 is a payment handshake: a server answers HTTP 402 with a price, and the client signs a stablecoin payment and retries. AP2 is an authorization layer: signed mandates record what the user allowed the agent to look for, spend and buy. AP2 has a crypto extension that integrates x402, so the two can work together. ### What are the alternatives to x402? The main alternatives are AP2 from Google, the Agentic Commerce Protocol from Stripe and OpenAI, Visa Intelligent Commerce, Mastercard Agent Pay, and full-stack platforms such as Qatom. ACP, Visa and Mastercard use card rails, while x402 settles in stablecoins onchain. Qatom settles a US-dollar token between wallets with no gas and no public ledger. ### What is the Agentic Commerce Protocol? The Agentic Commerce Protocol (ACP) is an open standard co-developed by Stripe and OpenAI, announced on September 29, 2025 under the Apache 2.0 license. It powers Instant Checkout in ChatGPT. The payment provider passes the merchant a scoped, logged payment token, and the payment runs on card rails. ### What is the difference between Visa Intelligent Commerce and Mastercard Agent Pay? Visa Intelligent Commerce, with its Trusted Agent Protocol, focuses on how agents identify themselves to merchants and how merchants verify them. Mastercard Agent Pay issues agentic tokens bound to a specific agent that carry who authorized it. Both were announced in 2025 and both run on card rails. ### Does MCP support payments? No. The Model Context Protocol connects AI assistants to tools and data, and remote servers authorize with OAuth 2.1, but MCP itself has no payment step. Payments have to come from a layer on top, such as x402 or a platform like Qatom. ### Which agent payment protocol is best for micropayments? Card-based options are a poor fit below a dollar: at 2.9% + 30 cents, a $0.10 charge costs about $0.30 in fees. For per-call and sub-cent prices, look at options that avoid card fees, such as x402 with stablecoins or Qatom, where prices can be as low as 0.001 USD-TDN per call. ### Can I use more than one agent payment protocol? Yes. The protocols cover different layers, so a business might accept ACP checkout in ChatGPT for physical goods and sell per-call API access through another rail. AP2 already integrates x402 through a crypto extension. Pick by what you sell and where your buyers are. ### Is x402 safe and widely used? x402 has broad backing: it has been governed by the x402 Foundation under the Linux Foundation since April 2, 2026. But independent 2026 studies found far less real use than raw counts suggest, with Visa and Artemis putting adjusted volume at roughly $15 million through April 21, 2026, and a July 2026 study found 49 security-rule violations across the 15 facilitators it tested. Those issues were disclosed and mitigated, including by Coinbase. ### How is Qatom different from x402? x402 settles each payment onchain in stablecoins through a facilitator. Qatom settles USD-TDN, a US-dollar token, between wallets called twins with no gas and no public ledger, and returns a receipt that can be verified anywhere. Qatom also includes a catalog, discovery in AI chat, spending approvals and payouts. ## Sources - [Coinbase: Introducing x402](https://www.coinbase.com/developer-platform/discover/launches/x402) - [Coinbase Developer Platform: x402 Foundation (Apr 2026)](https://docs.cdp.coinbase.com/x402/support/x402-foundation) - [When HTTP 402 Meets the Blockchain: Risks on Emerging x402 Payments (arXiv 2607.19545, Jul 2026)](https://arxiv.org/abs/2607.19545) - [Four Pillars Research: Centralized responsibility is all x402 needs (Jul 2026)](https://research.4pillars.io/en/research/centralized-responsibility-is-all-x402-needs) - [Forkast: Visa and Artemis, the $0.14 reality of agent commerce (Jul 2026)](https://forkast.news/visa-artemis-the-0-14-reality-of-agent-commerce/) - [Decrypt: TRM Labs research on x402 and AI agent payments (Sep 2026)](https://decrypt.co/378103/ai-agents-spending-money-research) - [A402: Binding cryptocurrency payments to service execution (arXiv 2603.01179, Mar 2026)](https://arxiv.org/abs/2603.01179) - [CoinDesk: demand for x402 micropayments is not there yet (Mar 2026)](https://www.coindesk.com/markets/2026/03/11/coinbase-backed-ai-payments-protocol-wants-to-fix-micropayment-but-demand-is-just-not-there-yet) - [TechCrunch: Google launches new protocol for agent-driven purchases (AP2)](https://techcrunch.com/2025/09/16/google-launches-new-protocol-for-agent-driven-purchases) - [Stripe: Developing an open standard for agentic commerce (ACP)](https://stripe.com/blog/developing-an-open-standard-for-agentic-commerce) - [RisingWave: Mastercard Agent Pay vs Visa vs Stripe agentic commerce](https://risingwave.com/blog/mastercard-agent-pay-vs-visa-vs-stripe-agentic-commerce/) - [Model Context Protocol: Authorization specification](https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization) - [Stripe pricing](https://stripe.com/pricing) --- # The state of x402 in 2026: real volume, security research and what it means for sellers Source: https://www.qatom.ai/learn/x402-in-2026 Updated: 2026-10-15 x402 is an open HTTP payment protocol that Coinbase created in 2025 and that the x402 Foundation, under the Linux Foundation, has governed since April 2026. Independent 2026 research found real x402 volume far below headline counts, and security-rule violations in all 15 payment facilitators studied, since mitigated. Sellers can still use it, with care. ## Key takeaways - x402 is backed by a broad industry group: the x402 Foundation launched under the Linux Foundation on April 2, 2026, with AWS, American Express, Cloudflare, Coinbase, Google, Mastercard, Shopify, Stripe and Visa among its premier members. - Headline settlement counts overstate real use. Visa and Artemis put adjusted volume at roughly $15 million through April 21, 2026, and TRM Labs estimated that only 0.6% to 7.5% of screened x402 commerce came from AI agents. - A USENIX Security 2026 study found 49 security-rule violations across the 15 x402 facilitators it tested, and every one violated at least one rule; the affected parties acknowledged the issues and adopted mitigations, including Coinbase. - In the base protocol, verifying a payment does not lock the funds, payment and delivery are separate steps, and there is no built-in dispute or refund process. - If you sell with x402, pick a facilitator that has adopted the published mitigations, settle before you deliver, and decide who handles refunds. Platforms such as Qatom bind payment, delivery and the record into one transaction. ## What is x402 in 2026? x402 is an open payment protocol that revives the HTTP 402 "Payment Required" status code. A server answers a request with a price, the client signs a stablecoin payment and retries, and a payment facilitator verifies and settles it onchain. Coinbase [created x402](https://www.coinbase.com/developer-platform/discover/launches/x402) and announced it in May 2025. On April 2, 2026, Coinbase contributed the protocol to the [x402 Foundation](https://docs.cdp.coinbase.com/x402/support/x402-foundation), which operates under the Linux Foundation. Forty organizations joined at launch. Its premier members are Amazon Web Services, American Express, Cloudflare, Coinbase, Google, Mastercard, Shopify, the Solana Foundation, Stripe and Visa. That backing makes x402 a serious standard. It also means the protocol now gets the scrutiny that comes with being one. In 2026, analysts and security researchers published the first independent measurements of how x402 is used and how safe it is. ## How much real volume does x402 process? Raw settlement counts are large. Filtered counts are much smaller. Every independent analysis in 2026 reached that conclusion, with different methods: | Source | What it measured | Finding | |---|---|---| | [Visa and Artemis](https://forkast.news/visa-artemis-the-0-14-reality-of-agent-commerce/), data through April 21, 2026 | Adjusted x402 volume since launch | Roughly $15.0 million across about 109.6 million transactions, an average of about $0.14 | | [Visa's Cuy Sheffield, via The Defiant](https://thedefiant.io/news/infrastructure/visa-s-sheffield-pegs-adjusted-x402-volume-at-19m), July 2026 | Adjusted volume | About $19 million across about 134 million transactions; about 4,000 wallets made about 90% of adjusted spending | | [TRM Labs, via Decrypt](https://decrypt.co/378103/ai-agents-spending-money-research), September 2026 | Settlements by known facilitators on Base, Solana and Polygon since May 2025 | 198.9 million settlements, about $52.7 million; $25.62 million left as likely commerce after screening | | [Ling, Zhou, Wu and Wang](https://arxiv.org/abs/2607.12575), July 2026 | 136.7 million settlements on Base over 280 days | 21.20% fictitious; 63.78% settled within a linked cluster | | [Artemis, via CoinDesk](https://www.coindesk.com/markets/2026/03/11/coinbase-backed-ai-payments-protocol-wants-to-fix-micropayment-but-demand-is-just-not-there-yet), March 2026 | Daily activity | About $28,000 and 131,000 transactions a day in recent snapshots; about half of transactions judged artificial | The share that came from AI agents is smaller still. TRM Labs estimated that 0.6% to 7.5% of screened commerce by value came from agents, and noted its models cannot conclusively tell agents from scripts. The July 2026 Base study put it bluntly: "Settlement count measures manufacturability, not adoption." Two factors make counts easy to inflate. Payments are tiny, and facilitators often pay the gas fee on the buyer's behalf, so a single operator can generate millions of settlements at little cost. ## What did security researchers find? In July 2026, Qinying Wang and Mathias Payer of EPFL, Yong Yang and Shouling Ji of Zhejiang University, and independent researcher Yuan Chen published [When HTTP 402 Meets the Blockchain](https://arxiv.org/abs/2607.19545), accepted to the [35th USENIX Security Symposium](https://www.usenix.org/conference/usenixsecurity26/presentation/wang-qinying). They defined eight security rules for x402 facilitators and tested 15 major facilitators, which serve more than 60,000 sellers and 360,000 buyers and cover about 99% of observed x402 transactions. They also analyzed more than 119 million recent Base and Solana transactions. The researchers found 49 security-rule violations, which mapped to 31 previously unknown vulnerabilities, and every facilitator violated at least one rule. The risks fall into four attack types: - **Free Shopping**, where a buyer gets the service without paying - **Asset Theft** - **Service Denial** - **Gas Abuse** The authors disclosed the findings responsibly. The affected parties acknowledged the issues and adopted mitigations, including changes by Coinbase. Some fixes were complete at publication and others were still in progress. ## Why do these problems happen? They come from how the base protocol splits the work. Four Pillars Research identifies three design gaps: 1. **Verifying does not lock the funds.** The `verify` step checks a payment but does not lock the money or use up its nonce, so a payment that passes verification can still fail to settle. 2. **Verification and settlement do not share state.** They are separate calls, and the seller usually delivers in between. 3. **Facilitators often pay gas.** That makes them a target for abuse and makes fake volume cheap. A separate paper, [A402](https://arxiv.org/abs/2603.01179), makes the same point from the seller's side: x402 "fails to enforce end-to-end atomicity across service execution, payment, and result delivery." In plain terms, a seller can deliver and still not be paid. There is also no built-in way to dispute a charge. A refund is simply a new transfer, and Four Pillars argues that refunds and disputes have no clear owner today. ## Is x402 still worth using? For many builders, yes. The fair reading of the 2026 research is that x402 is early, not broken: - **The problems were disclosed and fixed.** The security study was a responsible disclosure, and facilitators, including Coinbase, adopted mitigations. - **Usage is expected to mature.** Artemis expects the share of gamed activity to fall as teams move from testing to production. - **The industry is committed.** The x402 Foundation brings card networks, cloud providers and payment companies together around one open standard. - **The proposed fix builds on the protocol.** Four Pillars argues for accountable operators, each clearly responsible for its payment route and competing under the same open standard, that settle before the business logic runs and handle refunds and disputes. That keeps x402 open while giving each payment an owner. ## How to sell with x402 safely If x402 fits your API, these steps reduce the risks the researchers found: 1. **Ask your facilitator which mitigations it has deployed** for the issues in the July 2026 study, and get the answer in writing. 2. **Settle before you deliver.** Do not release data or run the paid work on a verified-but-unsettled payment. 3. **Treat each payment as single use.** Reject a payment you have already seen, even if it still verifies. 4. **Decide who handles refunds and disputes** before you launch, since the protocol does not. 5. **Judge demand by distinct buyers, not settlement counts.** Counts are easy to inflate. ## How Qatom approaches the same problem Qatom takes the other route the research points to: one accountable platform where payment, delivery and the record are a single transaction. It is a platform you sign up to rather than an open protocol you implement, so compare it on that basis. - **Payment and delivery together.** A purchase settles USD-TDN, a US-dollar token, between wallets in under one second, and the seller can verify each fulfilment call with its transaction id ([seller check](https://www.qatom.ai/capabilities#B20)). - **Proof that travels with the payment.** Each payment is a file built on the TODA file protocol that carries its own history, so it can be verified anywhere, even offline, with no public ledger. See [cryptographic proof of payment](https://www.qatom.ai/learn/cryptographic-proof-of-payment). - **Spending controls on the buyer side.** Agent wallets have their own budget, and purchases above an auto-approve limit wait for [the owner's approval](https://www.qatom.ai/capabilities#A14). - **No gas and no transaction fees.** Qatom charges a flat subscription with a 0% take rate, so there is no gas to sponsor or abuse. For a side-by-side view of x402, AP2, ACP, Visa, Mastercard and Qatom, read [agent payment protocols compared](https://www.qatom.ai/learn/agent-payment-protocols-compared). Risk and security teams can start with [proof and assurance](https://www.qatom.ai/assurance). ## Frequently asked questions ### Who runs x402 now? x402 was created by Coinbase and announced in May 2025. On April 2, 2026, Coinbase contributed it to the x402 Foundation, which operates under the Linux Foundation. Forty organizations joined at launch, with premier members including AWS, American Express, Cloudflare, Coinbase, Google, Mastercard, Shopify, the Solana Foundation, Stripe and Visa. ### How much real volume does x402 process? Far less than raw counts suggest. A Visa and Artemis analysis put adjusted volume at roughly $15 million across about 109.6 million transactions through April 21, 2026, an average of about $0.14. TRM Labs counted about $52.7 million across 198.9 million settlements, of which $25.62 million looked like real commerce. ### Is x402 safe to use? A July 2026 study tested 15 major x402 facilitators, used by more than 60,000 sellers and 360,000 buyers, and found violations of its eight security rules in all of them, leading to attacks such as getting a service without paying. The authors disclosed the findings and the affected parties adopted mitigations, including Coinbase. Ask your facilitator which fixes it has deployed. ### How many x402 facilitator vulnerabilities were found? The July 2026 study, accepted to USENIX Security 2026, found 49 security-rule violations across the 15 facilitators it tested, which mapped to 31 previously unknown vulnerabilities. Every facilitator violated at least one of the eight rules. The researchers grouped the risks into four attack types: Free Shopping, Asset Theft, Service Denial and Gas Abuse. ### How many x402 payments come from AI agents? TRM Labs estimated that 0.6% to 7.5% of screened x402 commerce by value came from AI agents, and said its models cannot conclusively tell agents from scripts. Another study found 21.2% of settlements on Base were fictitious. ### Does x402 handle refunds and disputes? Not in the base protocol. Four Pillars Research argues that refunds and disputes have no owner today, and proposes accountable operators that would handle them, in the way a card issuer does, on top of the open standard. ### What are the alternatives to x402? AP2 from Google records user consent with signed mandates, the Agentic Commerce Protocol from Stripe and OpenAI runs checkout on card rails, and Visa and Mastercard tokenize agents for card payments. Qatom is a full platform for per-call sales that settles a US-dollar token between wallets with no gas and no public ledger. ## Sources - [Coinbase Developer Platform: x402 Foundation](https://docs.cdp.coinbase.com/x402/support/x402-foundation) - [Coinbase: Introducing x402 (May 2025)](https://www.coinbase.com/developer-platform/discover/launches/x402) - [Wang, Yang, Chen, Ji and Payer: When HTTP 402 Meets the Blockchain: Risks on Emerging x402 Payments (arXiv 2607.19545, Jul 2026)](https://arxiv.org/abs/2607.19545) - [USENIX Security 2026: When HTTP 402 Meets the Blockchain (presentation page)](https://www.usenix.org/conference/usenixsecurity26/presentation/wang-qinying) - [Four Pillars Research: Centralized responsibility is all x402 needs (Jul 2026)](https://research.4pillars.io/en/research/centralized-responsibility-is-all-x402-needs) - [Forkast: Visa and Artemis, the $0.14 reality of agent commerce (Jul 2026)](https://forkast.news/visa-artemis-the-0-14-reality-of-agent-commerce/) - [The Defiant: Visa's Sheffield pegs adjusted x402 volume at $19M (Jul 2026)](https://thedefiant.io/news/infrastructure/visa-s-sheffield-pegs-adjusted-x402-volume-at-19m) - [Decrypt: AI agents spending money online? New research (TRM Labs) says not really (Sep 2026)](https://decrypt.co/378103/ai-agents-spending-money-research) - [Ling, Zhou, Wu and Wang: How Agentic Is Agentic Commerce? (arXiv 2607.12575, Jul 2026)](https://arxiv.org/abs/2607.12575) - [Li et al.: A402, binding cryptocurrency payments to service execution (arXiv 2603.01179, Mar 2026)](https://arxiv.org/abs/2603.01179) - [CoinDesk: Coinbase-backed AI payments protocol wants to fix micropayments, but demand is not there yet (Mar 2026)](https://www.coindesk.com/markets/2026/03/11/coinbase-backed-ai-payments-protocol-wants-to-fix-micropayment-but-demand-is-just-not-there-yet) --- # How to let an AI agent make purchases safely Source: https://www.qatom.ai/learn/let-ai-agent-make-purchases Updated: 2026-10-14 To let an AI agent make purchases safely, give it a separate wallet with a small budget, set an auto-approve limit for small buys, and approve anything larger yourself. Check the item, seller and price before you approve, keep every receipt, and treat each retry as a new charge. Qatom builds these controls in. ## Key takeaways - Give the agent its own wallet so it can never reach your main funds or your card. - Fund that wallet with a small amount: its balance is a hard ceiling on what the agent can spend. - Purchases under your auto-approve limit go through on their own; larger ones wait for your approval. - Before approving, check the item, the seller it pays and the price. - Keep the transaction id and emailed receipt for every purchase, and check them before any retry, because a retry is a new charge. ## Step by step 1. **Connect your AI to the store** Add the Qatom master MCP (https://mcp.m.todaq.net/mcp) as a custom connector in Claude, Grok, Muse or any MCP client, then sign in with an email code or passkey. 2. **Find the separate agent wallet** Your first sign-in creates a primary wallet and an agent wallet. Ask your agent to check the agent wallet so you can see both balances. 3. **Fund the agent wallet with a small budget** Move a small amount from your primary wallet to the agent wallet and approve the transfer. The agent can never spend more than that wallet holds. 4. **Set an auto-approve limit** Choose the amount under which purchases go through without asking. Anything above it waits for your approval. 5. **Check and approve larger purchases** Open the approval link or the push in the TODAQ app, check the item, the seller it pays and the price, then approve or dismiss. 6. **Keep the receipt** Note the transaction id from the chat receipt and keep the emailed receipt with it. 7. **Check before any retry** If output is cut off, ask for the last receipt and check the wallet balance first. Retry only if there is no receipt and the balance has not dropped. ## How do you let an AI agent make purchases safely? You let an AI agent make purchases safely the same way you would hand a teenager some cash for errands. Give it a small, separate budget, decide what it can buy without asking, and check the receipts afterwards. The six controls below cover the main risks. Use the table as a checklist before you switch anything on. | Control | What it protects against | How it works in Qatom | |---|---|---| | Separate agent wallet | The agent reaching your savings or card | The agent spends only from its agent twin, never your primary wallet or card ([A3](https://www.qatom.ai/capabilities#A3)) | | Small budget | A runaway loop or a bad purchase | You move a small amount to the agent twin; its balance is a hard ceiling ([A8](https://www.qatom.ai/capabilities#A8)) | | Auto-approve limit | Being asked about every tiny purchase | Purchases under your limit go through; larger ones wait for you | | Approval for larger buys | Large charges you did not expect | Approve in chat or by passkey or phone app ([A14](https://www.qatom.ai/capabilities#A14)) | | Check item, seller, price | Paying the wrong seller or a test listing | Read the approval before you tap Approve ([A31](https://www.qatom.ai/capabilities#A31)) | | Receipts and retry checks | Lost records and silent double charges | Every purchase returns a transaction id and an emailed receipt ([A15](https://www.qatom.ai/capabilities#A15)) | ## Can an AI agent buy things? Yes. An AI agent can buy things when it is connected to a store and has a way to pay. Many assistants connect to tools through the Model Context Protocol (MCP), but [MCP itself has no payment step](https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization), so the payment has to come from a layer on top. With Qatom, you add one connector, the master MCP at `https://mcp.m.todaq.net/mcp`, to Claude, Grok, Muse or any other MCP client ([A1](https://www.qatom.ai/capabilities#A1)). Your agent can then search the catalog, read an item, and pay for it from its own wallet. The agent asks you before paying and gets the seller's answer back in the same step ([A13](https://www.qatom.ai/capabilities#A13)). The question is less "can it?" and more "within what limits?" The rest of this guide sets those limits. For a wider view of how agents pay, read [what agentic payments are](https://www.qatom.ai/learn/what-are-agentic-payments). ## Why use a separate AI agent wallet? A separate AI agent wallet keeps the agent's money apart from yours. If the agent misreads a request or a tool misbehaves, the damage stops at what that wallet holds. In Qatom, your first sign-in creates two wallets, called twins. Your primary wallet is yours and protected by sign-in. Your agent wallet is the one your AI spends from. Both hold USD-TDN, a US-dollar token where 1 USD-TDN equals 1 USD ([A3](https://www.qatom.ai/capabilities#A3)). The agent can never spend more than its twin holds, and it never touches your primary wallet or your card. ## How do AI agent spending limits work? Good AI agent spending limits come in two layers: a budget and an approval threshold. **The budget** is the balance of the agent wallet. Move a small amount from your primary wallet to the agent wallet, and that amount becomes a hard limit on what the agent can buy ([A8](https://www.qatom.ai/capabilities#A8)). Think of it as handing over a little cash. Nothing moves until you approve the transfer. **The auto-approve limit** decides which purchases need you. Purchases under the limit you set go through without asking. Larger ones need your approval. A low limit means more prompts and more control. A higher limit means fewer interruptions. Small items suit this setup well. Guest card checkout has a minimum of about $0.50, while catalog prices can be as low as 0.001 USD-TDN per call, so an agent wallet is the practical way to pay for small, frequent calls. The [micropayments guide](https://www.qatom.ai/learn/micropayments-for-ai-and-apis) explains why. ## How do you approve AI agent purchases? When a purchase is above your auto-approve limit, nothing is paid until you approve it ([A14](https://www.qatom.ai/capabilities#A14)). 1. Your agent tells you it needs approval and gives you an approval link. If you use the TODAQ app (Qatom Authenticator), it also shows a push. 2. Check that you are signed in to the account you mean to pay from. 3. Read the item, the seller it pays and the amount. 4. Tap Approve, or Dismiss to decline. 5. Tell the agent you approved. It calls again with the approval id, finishes the purchase and shows the receipt. Approval links expire after about 15 minutes and belong to one account. If one expires, ask the agent to start the purchase again. Set up a passkey on each device you approve from ([S11](https://www.qatom.ai/capabilities#S11)). Every sign-in and approval then takes one tap or a fingerprint instead of an emailed code. Only you create or use your passkey; an agent never does. ## What should you check before approving a purchase? Check three things every time: the item, the seller and the price. - **The item.** Before buying, ask the agent to show the listing. It shows the price in USD-TDN, the seller name, the inputs and what the item returns ([A11](https://www.qatom.ai/capabilities#A11)). The seller's llms.txt read-me often has examples. - **The seller.** The catalog also holds test listings, so check the seller and description before paying. An item with no seller line comes from a seller who has not set a business name, so you cannot tell whose item it is ([A10](https://www.qatom.ai/capabilities#A10)). - **The price.** On the Purchase Approval screen, read the item name, "Payment to" the seller, the quantity and the price ([A31](https://www.qatom.ai/capabilities#A31)). If anything is wrong, tap Dismiss. The approval does not name the paying wallet, so make sure you are signed in to the right account. For a cart, one approval covers every item at the prices shown, so check the total and the item list ([A34](https://www.qatom.ai/capabilities#A34)). ## Why should you keep every receipt? Every purchase returns a transaction id and an emailed receipt with proof of purchase ([A15](https://www.qatom.ai/capabilities#A15), [A17](https://www.qatom.ai/capabilities#A17)). The transaction id is what you quote in any refund request. The email gives you a record outside the chat for bookkeeping. Ask the agent to show the full receipt, note the transaction id, item, amount and seller's answer, and keep it with the email. The receipt line comes from the seller's descriptor, which can differ from the item name. For carts, each item's answer comes back once, in that reply. Ask the agent to pass on every link straight away, because asking again will not bring it back. ## Why is a retry a new charge? If an agent's output is cut off, the purchase may still have gone through. A retry is a new charge, even under your auto-approve limit, and auto-approve lets the retry through without asking ([A28](https://www.qatom.ai/capabilities#A28)). That is how double charges happen silently. Before your agent retries a paid call: 1. Ask the agent for the last receipt and its transaction id. 2. Read the agent wallet's balance, allowing a few minutes for it to update. 3. Retry only if there is no receipt and the balance has not dropped. A call the seller rejects can still be charged. Keep retries in mind when you pick your auto-approve limit, and tell your agent to check before trying again. ## How do you set this up step by step? Here is the full setup to let an AI agent make purchases within limits you control: 1. **Connect.** Add the master MCP as a custom connector in your AI client ([A1](https://www.qatom.ai/capabilities#A1)). 2. **Sign in.** Use an email code or passkey, and use the same email every time so you see the same wallets. 3. **Check both wallets.** Ask your agent: "Check my Qatom agent wallet." 4. **Fund a small budget.** Top up your primary wallet, then move a small amount to the agent wallet and approve it. 5. **Set your auto-approve limit.** Pick a level you are comfortable seeing charged without a prompt. 6. **Make one test purchase.** Search the catalog, read the item, buy it and check the receipt. 7. **Write down your rules.** Tell the agent to confirm prices, show receipts, and check before any retry. Buying never needs a plan; plans are for sellers only. If you want to compare how other systems handle agent consent, see [agent payment protocols compared](https://www.qatom.ai/learn/agent-payment-protocols-compared). ## Next steps - Connect your AI client and sign in: [Capabilities Index, step A1](https://www.qatom.ai/capabilities#A1). - Read the developer docs for embeds and the Payment API at [docs.qatom.ai](https://docs.qatom.ai/). - Questions about a purchase or your setup? [Contact the team](https://www.qatom.ai/contact). ## Frequently asked questions ### Can an AI agent buy things on its own? Yes, if you connect it to a store and give it a wallet to spend from. With Qatom, the agent pays from its own agent wallet and gets the seller's answer back in the same step. Purchases under your auto-approve limit go through on their own, and larger ones wait for your approval. ### How do I set a spending limit for an AI agent? Use two limits. First, put only a small amount in the agent's own wallet, because the agent can never spend more than that wallet holds. Second, set an auto-approve limit so that anything above it needs your approval before it is paid. ### What is an AI agent wallet? An AI agent wallet is a separate wallet that your AI spends from, kept apart from your own money. In Qatom it is called the agent twin and holds USD-TDN, a US-dollar token where 1 USD-TDN equals 1 USD. The agent never touches your primary wallet or your card. ### Is it safe to give an AI agent my credit card? It is safer to give the agent a separate, prepaid budget than your card. In Qatom, the agent never touches your card or your primary wallet: you fund your own primary wallet, then move a small amount to the agent wallet. If something goes wrong, the most the agent can spend is what that wallet holds. ### How do I approve an AI agent purchase? When a purchase is above your auto-approve limit, the agent gives you an approval link, and the TODAQ app (Qatom Authenticator) can show the request as a push. Check the item, the seller it pays and the price, then tap Approve or Dismiss. Tell the agent you approved, and it finishes the purchase. ### Why did my AI agent charge me twice? A likely cause is a retry. If a reply is cut off, the first purchase may still have gone through, and a retry is a new charge, even under an auto-approve limit. Check the last receipt and the wallet balance before letting the agent try again. ### Do I need a paid plan to let my agent buy things? No. On Qatom, plans are for sellers only, and buying never needs a plan. You sign in, fund your wallet and let the agent spend from its own agent wallet. ### What happens if my agent buys the wrong thing? Find the transaction id on the receipt, because it is what you quote in any refund request. Then contact the seller of the item. To lower the risk next time, keep your auto-approve limit small and check every approval before you tap Approve. ## Sources - [Qatom Capabilities Index](https://www.qatom.ai/capabilities) - [Qatom developer docs](https://docs.qatom.ai/) - [Model Context Protocol: Authorization specification](https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization) --- # Micropayments for APIs and AI agents: how pay per request works Source: https://www.qatom.ai/learn/micropayments-for-ai-and-apis Updated: 2026-10-15 Micropayments for APIs are small charges, often under a dollar and sometimes under a cent, paid for each request instead of through a subscription. They suit AI agents that call many services once. They need payment rails with no fixed per-transaction fee, because a card's fixed fee is larger than the price of a typical call. ## Key takeaways - Micropayments for APIs charge per request, which suits AI agents that call many services without signing up for plans. - Stripe's standard US card price of 2.9% plus 30 cents means a $0.10 charge costs more in fees than it earns. - Workarounds such as prepaid credits and subscriptions add sign-up and key management that agents handle poorly. - Sub-cent payments need rails without card-style fixed fees, such as x402 onchain or Qatom wallet-to-wallet settlement. - Price each call, test it with a real purchase, and serve each paid sale exactly once. ## What are micropayments for APIs? Micropayments for APIs are small charges paid for each request a caller makes. A weather lookup might cost a cent, a search a tenth of a cent, a generated file a few cents. The caller pays for exactly what it uses, with no plan, monthly minimum or prepaid balance at the seller. Pay per request pricing has existed as an idea for a long time. It mostly stayed an idea because the cost of moving a small payment was larger than the payment. AI agents change the demand side: they call many different services, often once each, and they work faster than any person signing up for accounts. This guide explains why card fees fail micropayments, what developers use instead, and how sub-cent payments work in practice. ## Why do card fees fail micropayments? Card processing charges a percentage plus a fixed fee on every transaction. Stripe's standard US online price is 2.9% plus 30 cents per successful domestic card transaction ([Stripe pricing](https://stripe.com/pricing)). The fixed 30 cents is the problem. It stays the same whether the charge is $100 or $0.01. Here is what a seller keeps from a single card charge at that rate: | Price per call | Card fee (2.9% + $0.30) | Seller keeps | |---|---|---| | $0.001 | $0.300 | Loses about $0.30 | | $0.01 | $0.300 | Loses about $0.29 | | $0.10 | $0.303 | Loses about $0.20 | | $1.00 | $0.329 | $0.671, about two thirds | | $10.00 | $0.590 | $9.41 | Below about 30 cents, every card charge loses money. At $1 the fee takes about a third. Card rails work well for larger purchases, which is what they were built for. They were never designed for one call at a time. Card checkouts also tend to set minimums. On Qatom, guest card checkout has a minimum of about $0.50, so items priced under 50 cents suit agent wallets instead ([pick a use case and price](https://www.qatom.ai/capabilities#B1)). ## How do developers charge for small API calls today? Many API businesses avoid true micropayments for APIs by grouping small charges together. The common patterns are: - **Subscriptions.** A monthly plan with a quota of calls. - **Prepaid credits.** The caller buys a block of credits by card, and each call draws it down. - **Metered billing.** Usage is counted and invoiced at the end of the month. Each of these spreads one card fee across many calls. Each also needs an account, an API key and a billing relationship with every seller. That works for a developer who uses three APIs every day. It works badly for an agent that needs one call from each of fifty services, once, right now. ## What makes AI micropayments different? AI micropayments have a few needs that human billing does not. **No sign-up step.** An agent cannot fill in fifty sign-up forms and store fifty API keys safely. It needs one connection that can pay any seller. **Spending limits set by a person.** The agent's owner needs a hard ceiling and an approval step for anything large. A prepaid balance per seller does not give one view of total spend. **A receipt per call.** Every call should return a transaction id, so the owner can check what was bought and ask for a refund if needed. **Safe retries.** Agents retry failed calls. If a paid call's output is cut off, the purchase may still have gone through, and a retry is a new charge ([retry safely](https://www.qatom.ai/capabilities#A28)). ## How do sub-cent payments work? Sub-cent payments need a rail without a card-style fixed fee on every transaction. Two approaches used for agent payments today: **x402.** An open payment protocol created by Coinbase, announced in May 2025 with AWS, Anthropic, Circle and NEAR, and governed since April 2026 by the x402 Foundation under the Linux Foundation. A server answers a request with HTTP 402 "Payment Required", a price and the tokens it accepts. The client signs a payment and retries with an X-PAYMENT header, a facilitator verifies and settles onchain in stablecoins such as USDC on chains such as Base, and the server returns the data ([Coinbase](https://www.coinbase.com/developer-platform/discover/launches/x402)). It fits builders already working with stablecoins and public chains. Independent 2026 studies found most raw x402 volume was not real commerce: Visa and Artemis put adjusted volume at roughly $15 million through April 2026, an average of about $0.14 a payment ([x402 in 2026](https://www.qatom.ai/learn/x402-in-2026)). **Wallet-to-wallet settlement on Qatom.** Each buyer's AI spends from an agent twin, a small secure wallet that holds USD-TDN, a US-dollar token where 1 USD-TDN equals 1 USD. Payments settle between twins in under one second, with no gas and no public ledger. Qatom charges a 0% take rate and no transaction fees, and the cost does not scale with the value or volume of the payment. The smallest paid price is 0.001 USD-TDN. | Approach | Smallest practical price | Sign-up per seller | Receipt per call | |---|---|---|---| | Card charge per call | Above about $0.30 to break even | Yes | Card statement line | | Prepaid credits or subscription | Fraction of a cent, after a card top-up | Yes, plus an API key | Depends on the seller | | x402 | Per request, in stablecoins onchain | No | Onchain settlement plus X-PAYMENT-RESPONSE | | Qatom | 0.001 USD-TDN | No, one MCP connection | Transaction id and emailed receipt | These approaches can complement each other. A seller can keep a subscription for heavy users and add pay per request for agents. Our [agent payment protocols compared](https://www.qatom.ai/learn/agent-payment-protocols-compared) guide covers x402, AP2 and ACP in more depth. Note that MCP, the open protocol AI assistants use to reach tools, has no payment step of its own ([MCP specification](https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization)). Payment has to come from a layer like the ones above. ## How do you set up pay per request on Qatom? A seller needs one HTTPS endpoint and a catalog item for each price. The full path, step by step, is in the [Capabilities Index](https://www.qatom.ai/capabilities). 1. **Pick one item and a price.** Choose something that answers in one call and is cheap to serve. Set a price of at least 0.001 USD-TDN with no more than three decimals, and add a free sibling check ([B1](https://www.qatom.ai/capabilities#B1)). 2. **Build the endpoint.** Put the product behind one HTTPS endpoint; the Worker template is the fastest start ([B2](https://www.qatom.ai/capabilities#B2)). 3. **Guard the paid route.** Protect it with a secret Authorization header that only Qatom sends, and answer 404 without it ([B3](https://www.qatom.ai/capabilities#B3), [B12](https://www.qatom.ai/capabilities#B12)). 4. **Write the agent read-me.** Generate an llms.txt that tells agents how to call and pay you ([B4](https://www.qatom.ai/capabilities#B4)). 5. **Create the catalog item.** Enter the name, descriptor, price, method and endpoint, plus an input schema with additionalProperties set to false ([B9](https://www.qatom.ai/capabilities#B9), [B11](https://www.qatom.ai/capabilities#B11)). 6. **Buy it once.** Test each item with a real purchase through the master MCP before announcing ([B19](https://www.qatom.ai/capabilities#B19)). 7. **Serve each sale once.** For anything costly to serve, verify the X-Qatom-Transaction-Id on each call and keep the ids you have served ([B20](https://www.qatom.ai/capabilities#B20)). 8. **Announce.** Confirm the item shows in catalog_search, then share your llms.txt ([B21](https://www.qatom.ai/capabilities#B21)). Buyers connect any MCP client to the Qatom master MCP at https://mcp.m.todaq.net/mcp, find your item with catalog_search and pay from their agent twin. Purchases under the buyer's auto-approve limit go through without asking. For the full seller walkthrough, read [how to charge AI agents for API calls](https://www.qatom.ai/learn/charge-ai-agents-per-api-call). The API reference and SDKs are in the [developer docs](https://docs.qatom.ai/). ## How should you price micropayments for APIs? A few rules keep per-call pricing clear for agents and fair for you. - **One item, one price.** Several prices means several catalog items, each with its own description of what the higher tier adds. - **Price from your cost.** Start from what one answer costs you to produce, then add your margin. - **Offer a free check.** A free sibling item lets an agent confirm the input works before it pays. - **Return complete answers.** Each call should stand alone, with a one-sentence summary and clear errors. - **Mind the plan limits.** Plans set how many agents, items and transactions the account gets. Builder is free with 1 agent, up to 5 items and 25 transactions a month; Pro is $20 a month and Max $300 a month ([plans and pricing](https://www.qatom.ai/#pricing)). ## What does it cost to take micropayments on Qatom? Qatom takes 0% of each sale and charges no gas and no transaction fees. Revenue lands in USD-TDN, and you can split it across up to 200 payees ([split revenue](https://www.qatom.ai/capabilities#C18)). To move money to a bank, you cash out to a US or Canadian account. A cash-out needs at least 10 USD-TDN, carries a flat $1 fee and arrives by ACH in 2 to 5 business days ([cash out](https://www.qatom.ai/capabilities#C26)). RBC holds the reserve funds backing USD inside Qatom. The launch offer on the site gives 6 months of Max free, with no card to start. To talk through a larger catalog or a VPC, on-premises or air-gapped deployment, [contact us](https://www.qatom.ai/contact). ## Next steps - Follow the seller steps in [how to charge AI agents for API calls](https://www.qatom.ai/learn/charge-ai-agents-per-api-call). - Read the basics in [what are agentic payments](https://www.qatom.ai/learn/what-are-agentic-payments). - Check [Qatom plans and pricing](https://www.qatom.ai/#pricing) and start on Builder for free. ## Frequently asked questions ### What are micropayments for APIs? Micropayments for APIs are small payments made for each API request, often under a dollar and sometimes under a cent. The caller pays per use instead of buying a subscription or prepaid credits. They suit AI agents that call a service once or a few times. ### Why don't credit cards work for micropayments? Card processing charges a fixed fee on every transaction. Stripe's standard US online price is 2.9% plus 30 cents per successful domestic card charge, so a $0.10 sale costs about $0.30 in fees. Any price below about 30 cents loses money on every single card charge. ### What is the smallest amount you can charge per API call? It depends on the payment rail. Card charges usually need a minimum to cover the fixed fee. On Qatom the smallest paid price is 0.001 USD-TDN per call, which is a tenth of a cent, and a price of 0 makes an item free. ### How do AI agents make micropayments? An AI agent pays from a wallet or credential it has been given, under a spending limit its owner sets. It finds a priced service, pays for one call and gets the result and a receipt back. Systems such as x402 pay onchain in stablecoins, while Qatom pays between USD-TDN wallets called twins. ### What is pay per request pricing? Pay per request pricing charges the caller a set amount for each call to a service. The caller pays only for what it uses, with no plan or monthly minimum. It works best when each call returns a complete, useful answer. ### Are sub-cent payments possible? Yes, on rails without a card-style fixed fee. x402 settles stablecoin payments onchain, and Qatom settles USD-TDN between twins with no gas and no transaction fees. Card rails cannot carry sub-cent payments one at a time at a profit. ### How do I stop a paid API call from being served twice? Check each fulfilment call against a settled sale and record the ids you have served. On Qatom, each fulfilment call carries an X-Qatom-Transaction-Id header that your endpoint can look up through the API. Refuse any id that is unknown, belongs to another item or was already served. ## Sources - [Stripe pricing](https://stripe.com/pricing) - [Coinbase: Introducing x402](https://www.coinbase.com/developer-platform/discover/launches/x402) - [Coinbase Developer Platform: x402 Foundation (Apr 2026)](https://docs.cdp.coinbase.com/x402/support/x402-foundation) - [Model Context Protocol specification: Authorization](https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization) --- # How to sell an API, dataset or service to AI assistants Source: https://www.qatom.ai/learn/sell-to-ai-assistants Updated: 2026-10-14 To sell an API to AI assistants, put it behind one HTTPS endpoint, list it as a priced catalog item that assistants can search over MCP, and describe it so an agent knows what it returns before paying. Add an input schema, an llms.txt read-me and a free item, buy each item once to test, then announce it. ## Key takeaways - AI assistants find tools through MCP connections, so your listing has to be searchable from an MCP client such as Claude, Grok or Muse. - The item name, description and input schema are what an agent reads to decide whether to buy, so write them for a model. - An llms.txt read-me at your site root gives agents worked examples, prices and error meanings in one place. - A free item beside each paid one lets agents and people try your service before they spend anything. - Buy every item once through the same path a customer uses before you announce it. ## Step by step 1. **Pick one thing agents will pay for** Choose one item that answers in one call and is cheap to serve, and set a price per call in USD-TDN. 2. **Put it behind one HTTPS endpoint** Host the endpoint yourself, starting from the Worker template, and guard the paid route with a secret Authorization header that only Qatom sends. 3. **Write and serve llms.txt** Generate a Markdown read-me from your catalog and serve it at /llms.txt on your own domain. 4. **Create the catalog item** Set a clear name, a descriptor, a price, a method and the endpoint, then write the description and the input schema. 5. **Add a free feedback item** List a free item next to your paid ones so buyers can try the store and send you feedback at no cost. 6. **Test by buying each item once** Connect the master MCP, search for your item with catalog_search and buy it with agent_checkout, with and without inputs. 7. **Confirm you are findable, then announce** Check each public item in catalog_search, then share your llms.txt URL and add your store to STORES.md. ## How do you sell an API to AI assistants? To sell an API to AI assistants, three things have to be true. An agent must be able to find your service from inside a chat, understand what it returns before paying, and pay without a person filling in a card form for every call. Assistants act through tools, so your product has to show up as a tool with a price, a description and a schema. This guide covers each part, from discovery to announcing a finished store. The same steps work for an API, a dataset or a service such as a file, a video stream or a report. On Qatom the path follows one value chain: set up, publish, distribute, transact, settle, report. Every step is also in the [Capabilities Index](https://www.qatom.ai/capabilities#B1). ## How do AI assistants find tools through MCP? Many assistants reach outside tools through MCP, the [Model Context Protocol](https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization). It is an open protocol for connecting AI assistants to tools and data, and remote servers authorize with OAuth 2.1. MCP itself has no payment step, which is the gap a storefront fills. On Qatom, a buyer adds one connection, the master MCP at `https://mcp.m.todaq.net/mcp`, in Claude, Grok, Muse or any other MCP client ([A1](https://www.qatom.ai/capabilities#A1)). That one connection gives the assistant every public catalog item plus wallet tools. When a user asks for something, the assistant calls `catalog_search` with plain words such as "weather" ([A10](https://www.qatom.ai/capabilities#A10)). Each result carries an id, name, description, price, seller and input schema. The assistant then reads the listing, checks the price and buys with `agent_checkout`, which pays from the agent's own wallet and returns your answer in the same call. That flow tells you where to spend your effort. Your name and description help an agent match you to a query. Your description and schema help it decide whether to buy. Your endpoint's answers shape whether it buys again. ## What is an agentic storefront? An agentic storefront is a set of items that AI agents discover, order from and pay for on their own, inside limits a person sets. On Qatom, each catalog item is one thing for sale at one price with one endpoint ([B9](https://www.qatom.ai/capabilities#B9)). The item name becomes the tool name agents see. Payment, delivery and a verifiable receipt happen in one call. The agent pays in USD-TDN, a US-dollar token (1 USD-TDN = 1 USD), and Qatom calls your endpoint after the payment settles. Settlement takes under one second, and every purchase returns a transaction id and an emailed receipt. For the payment side in more depth, read [how to charge AI agents per API call](https://www.qatom.ai/learn/charge-ai-agents-per-api-call). ## How do you get your API discovered by AI agents? Follow these steps in order. Each one links to the matching step in the Capabilities Index. 1. **Pick one first item.** Choose something that answers in one call and is cheap to serve. The seller guide skill helps: `npx skills add StarwaterHeaven/qatom-seller-guide --skill qatom-seller-guide` ([B1](https://www.qatom.ai/capabilities#B1)). 2. **Register a seller account.** Sign up at dashboard.qatom.ai, choose a plan and start your MCP server ([B34](https://www.qatom.ai/capabilities#B34)). 3. **Build one HTTPS endpoint.** Start from the Worker template, which reads one catalog.json, validates inputs, guards the paid route and serves /llms.txt ([B2](https://www.qatom.ai/capabilities#B2)). 4. **Guard the paid route.** Check a secret Authorization header that only Qatom sends, and answer 404 when it is missing or wrong ([B3](https://www.qatom.ai/capabilities#B3), [B12](https://www.qatom.ai/capabilities#B12)). 5. **Write llms.txt.** Generate it from your catalog and serve it at your site root ([B4](https://www.qatom.ai/capabilities#B4)). 6. **Create the catalog items.** Set name, descriptor, price, method, endpoint, description and input schema ([B9](https://www.qatom.ai/capabilities#B9) to [B11](https://www.qatom.ai/capabilities#B11)). 7. **Buy each item once.** Test through the master MCP before you tell anyone ([B19](https://www.qatom.ai/capabilities#B19)). 8. **Check search, then announce.** Confirm each item in `catalog_search`, then share your read-me and add your store to STORES.md ([B21](https://www.qatom.ai/capabilities#B21)). ## What should an agent read-me (llms.txt) include? llms.txt is a Markdown read-me for language models, served at your site root. Agents that find your items look for it before calling. Generate it from catalog.json or from the live public catalog (`GET https://pay.m.todaq.net/v4/catalog/items`). Never write it by hand, and regenerate it on every catalog change so it never drifts from what is listed. Include: - Your seller name, a short summary and a Generated timestamp. - How to call: `catalog_search`, then `agent_checkout`. - Worked examples and a table of items with prices. - Input schemas, every error code with its next step, and your free feedback item. Put the llms.txt URL in every item description. The Qatom Demo store serves its own at `https://qatom-demo.agentkepler.tech/llms.txt`, listing each item, its price and its inputs. ## How do you write item names and descriptions agents will choose? The name is the tool name agents see, so make it predictable. Use a shared prefix in the form "Brand: item", such as "Qatom Demo: space station video". A shared prefix lets buyers, and you, search for your whole store at once. The descriptor is a separate field: it is the line on the buyer's receipt and card statement. Renaming an item later does not change the descriptor, so set it with care. The description is what an agent reads to decide whether to buy ([B10](https://www.qatom.ai/capabilities#B10)). Keep it at or under 1,024 characters. | Do | Avoid | |---|---| | Say what the item returns in the first sentence | Marketing lines with no facts | | Say what is free and which inputs change the answer | Listing every ticker, SKU or ID you cover | | Point to your llms.txt URL | Giving an item count that will go out of date | | Add a not-advice line for health, finance, investment or legal items | Leaving the risk unstated | | Say what a higher tier adds, if the same content sells at two prices | Two near-identical listings with no difference explained | One catalog item has one price. If you want several prices, create several items. Prices go down to 0.001 USD-TDN per call, with no more than three decimals, and 0 makes an item free. ## What makes an agent choose your item and repeat it correctly? The AAIF Ambassador talk "Agentic commerce for sellers" at [MCP Dev Summit Toronto 2026](https://www.qatom.ai/events) argued that agents compete on the payload, so every fact an agent must repeat (fees, currency, times) belongs in typed fields. Its rule: "If it isn't in the response, it doesn't exist." - Put every fact the buyer must know (price, currency, limits, delivery time) in the item description and in typed fields of your response, not only in prose. - Name the item by the outcome it delivers, so the agent can match it to the user's request. - Return errors that say what to do next, so the agent can recover without guessing. ## What should the input schema look like? The input schema tells agents exactly which arguments to send ([B11](https://www.qatom.ai/capabilities#B11)). Qatom forwards only declared arguments and rejects the rest, so a loose schema leads to failed calls. Read the schema off your endpoint. Use one required string that identifies the item, and one optional property per real input. Give every property a description with its unit, range and default, and set `"additionalProperties": false`. Describe formats instead of giving example IDs or item names. For instance, the Qatom Demo video item takes one optional input, `ttl_seconds`, from 60 to 86400, default 3600. Never accept raw SQL, code or query strings as inputs; turn them into named inputs. Return every error with a code, a plain message and a next step, such as `bad_value` with a 400 status, so an agent can correct itself. ## Why add a free feedback item? A free item lowers the cost of trying your store to zero. Agents and people can check that your service works, and you collect feedback from real buyers. The seller guide pairs each first item with a free sibling check for the same reason. The Qatom Demo store sells a video at 0.01 and an agent skill at 0.005, beside a free feedback item. Free items also cost nothing to test. ## How do you test before you launch? A real purchase is the only full test of price, schema, header and endpoint together ([B19](https://www.qatom.ai/capabilities#B19)). Call your endpoint directly first, because Qatom may relay a failed call as a generic payment error. Then connect the master MCP, put a small amount in your agent wallet and buy each item with `agent_checkout`: once alone, once with inputs and once with a bad input. Check that the receipt shows your endpoint's answer and a transaction id. A call your endpoint rejects can still be charged, and a retry is a new charge. For anything expensive to serve, such as downloads or stream keys, read the `X-Qatom-Transaction-Id` header on each call and look it up, so each sale is served once ([B20](https://www.qatom.ai/capabilities#B20)). | Launch check | How to confirm | |---|---| | Endpoint answers directly | A free route returns JSON with `ok: true` | | Paid route is guarded | A direct call without the header gets 404 | | Schema is strict | The editor validates it and shows the tool arguments | | Each item sells | A test purchase returns your answer and a transaction id | | Item is findable | `catalog_search` lists it with your business name as seller | | Read-me is current | /llms.txt shows a fresh Generated timestamp | ## Can I list my service in ChatGPT and other assistants? ChatGPT is among the assistants and channels listed on qatom.ai, along with Claude, Microsoft Copilot, Gemini, Muse, WhatsApp, iMessage, Grok and Hermes Agent. Buyers in any MCP client can add the master MCP and reach your public items. Treat these as places your storefront can be found, and check the steps for each client in [A1](https://www.qatom.ai/capabilities#A1). Other routes into assistants exist. The [Agentic Commerce Protocol](https://stripe.com/blog/developing-an-open-standard-for-agentic-commerce), co-developed by Stripe and OpenAI, powers Instant Checkout in ChatGPT and passes the merchant a scoped payment token. It rides card rails and suits physical goods at checkout. At [Stripe's standard 2.9% + 30¢](https://stripe.com/pricing), a $0.10 charge would cost about $0.30 in fees, so per-call pricing works better on a wallet that settles without card fees. These approaches can complement each other. See [agent payment protocols compared](https://www.qatom.ai/learn/agent-payment-protocols-compared) for the wider picture. ## How do you announce your store? Announce only once your items show in `catalog_search` and pass your launch checks. Search the master MCP for your brand prefix and check each public item's name, price, seller name and description. Delist or archive test and placeholder items first. Then tell people where to find you: - Share your llms.txt URL wherever developers and buyers look. - Add your store to STORES.md. - If you run your own MCP server, consider publishing it to the [official MCP Registry](https://modelcontextprotocol.info/tools/registry/), which exists for publishing servers. Private items never show in `catalog_search`; they are reachable only through your own MCP instance. Choose public or private when you create an item, because the choice is fixed ([B14](https://www.qatom.ai/capabilities#B14)). ## How much does it cost to sell to AI assistants? Qatom takes 0% of each sale, charges no transaction fees and has no gas. Cost does not scale with the value or volume of the payment. | Plan | Price | |---|---| | Builder | Free (1 agent, up to 5 items, 25 transactions a month) | | Pro | $20/month | | Max | $300/month | | Enterprise | See [pricing](https://www.qatom.ai/#pricing) | The site's launch offer gives 6 months of Max free, with no card to start. Cashing out to a US or Canadian bank needs at least 10 USD-TDN, costs a flat $1 and takes 2 to 5 days by ACH ([C26](https://www.qatom.ai/capabilities#C26)). See [pricing](https://www.qatom.ai/#pricing) for current plans, and the [developer docs](https://docs.qatom.ai/) for the API and SDKs. ## Next steps - Follow the seller steps from [B1 in the Capabilities Index](https://www.qatom.ai/capabilities#B1). - Read [how to monetize an MCP server](https://www.qatom.ai/learn/monetize-mcp-server) if you already run one. - Talk to the team about hosted, VPC, on-premises or air-gapped setups on the [contact page](https://www.qatom.ai/contact). ## Frequently asked questions ### How do AI assistants find APIs to use? Many assistants reach outside tools through MCP, the Model Context Protocol, which connects an AI client to tools and data. On Qatom, a buyer connects one master MCP and the assistant calls catalog_search to find public items by need or name. The search result shows each item's name, description, price, seller and input schema. ### Can I list my service in ChatGPT? Qatom storefronts are discoverable in the assistants and channels listed on qatom.ai, and ChatGPT is on that list. Buyers in any MCP client can also add the Qatom master MCP at https://mcp.m.todaq.net/mcp. If you sell physical goods at a checkout, OpenAI and Stripe's Agentic Commerce Protocol powers Instant Checkout in ChatGPT and is worth reading too. ### How do I sell data to AI agents? Serve the data from one HTTPS endpoint, then list each query or dataset as a catalog item with one price per call. Describe what a call returns and which inputs change the answer, and declare those inputs in a strict schema. Agents buy it from their own wallet and get the answer in the same call. ### What is an agentic storefront? An agentic storefront is a set of catalog items that AI agents can discover, order from and pay for without a human filling in a checkout form. On Qatom, each item is one thing for sale at one price with one endpoint, and every purchase returns a verifiable receipt with a transaction id. ### What should go in an llms.txt file for my API? Include your seller name, a short summary, a generated timestamp, how to call your items, worked examples and a table of items with prices. Add the input schemas, every error code with its next step, and your free feedback item. Generate it from your catalog and regenerate it on every change so it never drifts. ### How much does it cost to sell an API through Qatom? Qatom charges a 0% platform take rate and no transaction fees, and there is no gas. The Builder plan is free, Pro is $20 a month and Max is $300 a month, plus an Enterprise plan. Cashing out to a US or Canadian bank costs a flat $1 per transfer, with a 10 USD-TDN minimum. ### Should I publish my MCP server to the official MCP Registry? The official MCP Registry is a place to publish MCP servers so clients and people can find them. It is a separate step from listing on Qatom, where public items are found through catalog_search on the master MCP. Publishing in both places can widen who sees your server. ### How do I test that AI agents can buy my API? Connect the master MCP, put a small amount in your agent wallet, find your item with catalog_search and buy it with agent_checkout. Try it with no inputs, with valid inputs and with a bad input, and check that the error is clear. A call your endpoint rejects can still be charged, so check the receipt before retrying. ## Sources - [Model Context Protocol specification: Authorization](https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization) - [Official MCP Registry](https://modelcontextprotocol.info/tools/registry/) - [Stripe: Developing an open standard for agentic commerce](https://stripe.com/blog/developing-an-open-standard-for-agentic-commerce) - [Stripe pricing](https://stripe.com/pricing) - [Qatom developer docs](https://docs.qatom.ai/) - [Qatom Capabilities Index](https://www.qatom.ai/capabilities) --- # Cryptographic proof of payment: what it proves and how to verify it Source: https://www.qatom.ai/learn/cryptographic-proof-of-payment Updated: 2026-10-15 Cryptographic proof of payment is evidence, carried by the payment itself, that a specific transfer was executed, authorized and settled. When the proof is bound to the transaction and its settlement at the moment of execution, any counterparty, auditor, insurer or regulator can verify it independently, without trusting the organization that produced the record. ## Key takeaways - A cryptographic proof of payment is bound to the transaction at execution, so there is no separate record to reconcile or reconstruct later. - In Qatom, each holding is a TODA file whose Proof of Provenance travels with it and can be verified locally and offline. - The proof establishes integrity: what was paid and settled, by whom, under which authorization, and that the history was not altered. - It does not prove an agent's decision was correct, that the agent stayed within its intended policy, or that the underlying data was accurate. - Proof complements operational controls such as budgets, approvals, key management and role-based access; it does not replace them. ## What is cryptographic proof of payment? Cryptographic proof of payment is evidence that a payment happened, created by the payment itself and protected so that any change can be detected. The test that matters to a risk or audit team is simple: can someone outside the paying organization check it, without trusting that organization? Much conventional payment evidence does not meet that test. A bank statement, a processor dashboard or an application log is a statement made by one institution about its own activity. It can be accurate. But a counterparty, insurer or court has to take the institution's word for it, or demand access to its systems. The stronger form binds the proof to the transaction and its settlement at the moment of execution. Qatom uses this model. In the words of the TODAQ Press essay [Settlement Without Proof](https://todaq.substack.com/p/settlement-without-proof), "Settlement and verifiable record become the same operation rather than two operations that must be reconciled." Three terms recur in this guide: - **Integrity:** the record shows what happened and has not been altered. - **Non-equivocation:** no conflicting version of the history was produced. - **Independently verifiable:** a third party can check the proof with no intermediary. ## Why isn't a receipt or log the same as proof of transaction? A receipt and a proof of transaction answer different questions. A receipt says what the seller or platform recorded. A proof says what can be shown to anyone, whatever any party now claims. TODAQ Press argues that the gap widens when AI agents act. Its essay [When The Transaction Becomes The Record](https://todaq.substack.com/p/when-the-transaction-becomes-the) puts it this way: "a record generated separately from an action, and stored separately from an action, can always be questioned." The same essay frames the difference as "the difference between evidence and testimony." The argument is about evidentiary weight, and logs still have a job. Operational logs remain the main source for debugging and for explaining why a system acted. The point is narrower: when the record's own author is a party to a dispute, a self-kept record carries less weight than one the other side can verify. Agent commerce makes this concrete. Agents buy many small items from many sellers, often with no human watching each purchase. The [Invisible Shelf](https://todaq.substack.com/p/the-invisible-shelf-how-headless) essay calls such transactions "inherently unwitnessed." If each purchase carries its own proof, the missing witness matters less. ## How is the proof bound to settlement? Qatom is built on the TODA file protocol. Money inside Qatom is USD-TDN, a US-dollar token (1 USD-TDN = 1 USD). Each holding sits in a "twin," a small secure wallet app, and each holding is a self-verifying TODA file. RBC holds the reserve funds backing USD inside Qatom. The mechanism has four parts. Its primary specifications are the [Rigging Specifications](https://trie.site/rigging_specifications.pdf) and the [Abject Specification](https://trie.site/abject-specs-v1.pdf): 1. **Proof of Provenance.** Each TODA file carries a Proof of Provenance built from "rigs," which the essays describe as "an unbroken, verifiable chain of custody from creation onward." 2. **Non-equivocation.** A rig proves that no conflicting version of the asset's history was produced. 3. **Double-spend prevention.** This is a proved theorem, shown by structural induction in [Simple Rigs Hold Fast](https://arxiv.org/abs/2208.13617) (Coward and Toliver). 4. **Authorization in the file.** Each update must carry a satisfaction of the previous step's requirements, such as specific signatures or weighted multi-signature lists. Because the payment and its proof are one object, the record exists the instant settlement does. Settlement between twins takes under one second. TODAQ Press describes the result as a record that "cannot be reconstructed after the fact, because it was never separate to begin with." TODA is not a blockchain. There is no global consensus, no shared ledger and no gas. Dann Toliver, Qatom's CSO, co-authored the Rigging Specifications and Simple Rigs Hold Fast; see [About us](https://www.qatom.ai/about-us) for the team and research heritage. ## What makes tamper-evident transaction records different? A tamper-evident record is one where any alteration can be detected by whoever checks it. That is the accurate claim, and it is the one to hold any vendor to, including this one. With TODA files, the proof travels inside the file, so verification is local and can run offline. The Invisible Shelf essay describes it as verification "with no network call, no consensus round, and no external validator." The verifier does not need the originating system to be online or cooperative. TODAQ Press summarizes what this guarantees in When The Transaction Becomes The Record: "the execution history cannot be retroactively altered, selectively reconstructed, or institutionally withheld." For an auditor, the practical meaning is chain of custody that survives the loss of cooperation from the party that produced it. ## What does non-repudiation for payments mean here? Non-repudiation for payments means a party cannot credibly deny a transfer it authorized. In card systems this rests on network rules and the issuer's records. In TODA, it rests on the file: each step must satisfy the authorization requirements set by the step before it. In Qatom, those requirements sit beside product controls. An agent spends from its own agent wallet with its own budget ([A3](https://www.qatom.ai/capabilities#A3), [A8](https://www.qatom.ai/capabilities#A8)). Purchases above an auto-approve limit need the owner's approval by passkey or phone app ([A9](https://www.qatom.ai/capabilities#A9), [A14](https://www.qatom.ai/capabilities#A14)), and the owner checks the item, seller and price before approving ([A31](https://www.qatom.ai/capabilities#A31)). ## What does the proof show, and what does it not? This table is the one to show your audit committee. The limits come from the TODAQ Press essays themselves. | Proves | Does not prove | |---|---| | That a specific transfer was executed and settled | That the agent's decision to buy was correct | | Which twin paid, which received, and the amount | That the agent acted within its intended policy scope | | Under which authorization the transfer was released | That the original data or judgment behind it was accurate ("Verification does not equal truth") | | That the history was not altered or substituted, and no conflicting version exists | A system-wide view for macro-prudential monitoring; there is no built-in global view | | That any party can check it offline, without trusting the originator | That regulators accept such records; regulators have not formally opined on them, and supervisors are not yet familiar with rigging trees | When The Transaction Becomes The Record states the first limit directly: "It cannot guarantee that an autonomous decision was correct, or that the agent acted within its intended policy scope." What the proof guarantees is integrity. Judgment and policy remain your controls. ## How do verifiable receipts for AI agents work in Qatom? Every Qatom purchase returns a transaction id and an emailed receipt with proof of purchase ([A15](https://www.qatom.ai/capabilities#A15), [A17](https://www.qatom.ai/capabilities#A17)). Behind the receipt sits the TODA file, which carries the proof. The Qatom Console (console.todaq.net) shows TODA files, provenance and verification for each twin. A counterparty or auditor can check a payment like this: 1. **Get the transaction id** from the agent's receipt or the emailed proof of purchase. 2. **Open the twin in the Console** and inspect the note's minting info and provenance history ([C7](https://www.qatom.ai/capabilities#C7)). 3. **Verify the file's integrity** and download the .toda file ([C8](https://www.qatom.ai/capabilities#C8)). 4. **Share the file** with the reviewer, who verifies it locally. The protocol has an [open-source JavaScript implementation](https://github.com/TODAQopen/toda). 5. **Reconcile with the books** by exporting the twin's ledger as CSV ([C9](https://www.qatom.ai/capabilities#C9)). Sellers use the same id in the request path. They verify each fulfillment call with the X-Qatom-Transaction-Id header, so each sale is served once ([B20](https://www.qatom.ai/capabilities#B20)). ## Which risks does cryptographic proof of payment address? Cryptographic proof of payment covers integrity risks. Operational risks need operational controls, several of which Qatom provides in the product. | Risk | Evidence or control | |---|---| | A party disputes that a payment happened | Transaction id, emailed proof of purchase, downloadable .toda file (A15, A17, C8) | | A record is altered or rewritten after the fact | Proof of Provenance and non-equivocation in the TODA file | | The same funds are spent twice | Double-spend prevention proved in Simple Rigs Hold Fast | | A retried call charges twice | Retries are new charges; check the receipt before retrying ([A28](https://www.qatom.ai/capabilities#A28)) | | A forged or replayed fulfillment call | X-Qatom-Transaction-Id check and a secret header on paid endpoints (B20, [B12](https://www.qatom.ai/capabilities#B12)) | | An agent overspends | Separate agent wallet with its own budget; approval above the auto-approve limit (A3, A8, A9, A14) | | Credentials leak or staff overreach | Key rotation, revocable API keys, role-based access to who can see or move funds ([B24](https://www.qatom.ai/capabilities#B24), [B29](https://www.qatom.ai/capabilities#B29), [C29](https://www.qatom.ai/capabilities#C29)) | | Evidence is locked in one party's systems | Exportable ledger and .toda files (C8, C9) | For a fuller control set, see [agentic payments risk controls](https://www.qatom.ai/learn/agentic-payments-risk-controls). ## How can anyone verify it without exposing private data? Using cryptographic proof of payment does not mean making payment data public. The trusted system can anchor a proof without seeing the data, a technique the essays call "shielding." The [Missing Middle](https://todaq.substack.com/p/the-agentic-economys-missing-middle) essay states the principle: "Privacy is the default; visibility is conferred by consent." A counterparty or regulator can be given the full record while others see nothing. The essays call an exportable record a "Transaction Binder," which can be shared with a regulator or audit firm and verified offline. Who receives it is your decision, and what disclosure your obligations require is a question to confirm with your counsel. ## How does this compare with other agent payment approaches? Other approaches solve different parts of the problem. [x402](https://www.coinbase.com/developer-platform/discover/launches/x402), created by Coinbase and now governed by the x402 Foundation, revives HTTP 402: a facilitator verifies the payment and settles onchain in stablecoins. Google's AP2 records consent in signed intent and cart mandates. The [Agentic Commerce Protocol](https://stripe.com/blog/developing-an-open-standard-for-agentic-commerce), from Stripe and OpenAI, passes the merchant a scoped, logged payment token. Visa Intelligent Commerce and Mastercard Agent Pay focus on agent identity and agent-bound tokens on card rails. TODAQ Press argues that protocols such as x402, AP2 and ACP were not designed to carry proof across institutional boundaries: "Evidentiary portability is outside their stated scope." That describes their scope and is no criticism of how well they do their own jobs. These approaches can complement each other. See [agent payment protocols compared](https://www.qatom.ai/learn/agent-payment-protocols-compared) for the detail. ## Further reading - TODAQ Press, [Settlement Without Proof](https://todaq.substack.com/p/settlement-without-proof) (19 May 2026) - TODAQ Press, [When The Transaction Becomes The Record](https://todaq.substack.com/p/when-the-transaction-becomes-the) (20 May 2026) - TODAQ Press, [The Agentic Economy's Missing Middle](https://todaq.substack.com/p/the-agentic-economys-missing-middle) (7 Aug 2026) - Coward and Toliver, [Simple Rigs Hold Fast](https://arxiv.org/abs/2208.13617), and the [Rigging Specifications](https://trie.site/rigging_specifications.pdf) ## Next steps - Read the overview for risk, security and compliance teams: [Qatom assurance](https://www.qatom.ai/assurance). - See verification, approvals and record export on your own transactions: [book an enterprise demo](https://www.qatom.ai/enterprise-demo). - Learn how proof fits into agent oversight: [AI agent audit trail](https://www.qatom.ai/learn/ai-agent-audit-trail). ## Frequently asked questions ### What is cryptographic proof of payment? It is evidence, produced as part of the payment, that a specific transfer was executed, authorized and settled. The evidence is protected by cryptography, so any change to it can be detected. A party who receives it can check it without asking the payer's systems to vouch for it. ### How is a proof of transaction different from a receipt or a log? A receipt or log is a statement written by one party and stored in that party's systems. A cryptographic proof of transaction is bound to the payment itself and can be checked by anyone holding it. The receipt still matters for bookkeeping, but the proof is what a third party can verify independently. ### Are cryptographic payment records tamper-proof? The accurate term is tamper-evident, and no system should promise more in an absolute sense. A TODA file's Proof of Provenance is built so that altering or substituting its history can be detected by anyone who verifies it. A rig proves that no conflicting version of the asset's history was produced. ### What does non-repudiation for payments mean? Non-repudiation means a party cannot credibly deny a transaction it authorized. In TODA files, each update must carry a satisfaction of the previous step's requirements, such as specific signatures or weighted multi-signature lists. That ties the transfer to the authorization that released it. ### Can an auditor verify a payment without access to our systems? Yes. The proof travels inside the TODA file, so verification is local and can be done offline, with no call to the originating system. You can download a payment's .toda file from the Qatom Console and hand it to the auditor. ### Does cryptographic proof of payment show that an AI agent made the right purchase? No. It proves what was executed, paid and settled, and under which authorization. It cannot show that an autonomous decision was correct, that the agent acted within its intended policy scope, or that the data behind the decision was accurate. ### Is Qatom's proof of payment built on a blockchain? No. It is built on the TODA file protocol, which has no global consensus, no shared ledger and no gas. Double-spend prevention is a proved property of the data structure, published in the paper Simple Rigs Hold Fast. ### Have regulators accepted TODA records as evidence? Regulators have not formally opined on TODA records or rigging trees, and supervisors are not yet familiar with them. Treat the proof as strong integrity evidence and discuss its use in your own regulatory context with your compliance team and counsel. ## Sources - [Coward & Toliver, Simple Rigs Hold Fast (arXiv:2208.13617)](https://arxiv.org/abs/2208.13617) - [Rigging Specifications](https://trie.site/rigging_specifications.pdf) - [Abject Specification](https://trie.site/abject-specs-v1.pdf) - [TODA open-source JavaScript implementation](https://github.com/TODAQopen/toda) - [TODAQ Press: Settlement Without Proof](https://todaq.substack.com/p/settlement-without-proof) - [TODAQ Press: When The Transaction Becomes The Record](https://todaq.substack.com/p/when-the-transaction-becomes-the) - [TODAQ Press: The Agentic Economy's Missing Middle](https://todaq.substack.com/p/the-agentic-economys-missing-middle) - [TODAQ Press: The Invisible Shelf](https://todaq.substack.com/p/the-invisible-shelf-how-headless) - [Coinbase: Introducing x402](https://www.coinbase.com/developer-platform/discover/launches/x402) - [Stripe: Developing an open standard for agentic commerce](https://stripe.com/blog/developing-an-open-standard-for-agentic-commerce) --- # AI agent audit trail: logs, proof and what auditors can verify Source: https://www.qatom.ai/learn/ai-agent-audit-trail Updated: 2026-10-14 An AI agent audit trail is the record of what an agent did, under whose authority, and with what result. Logs explain decisions, but they are written by the system that acted. For payments, a stronger record binds proof to each transaction and its settlement at execution, so any party can verify it without trusting the originator. ## Key takeaways - An AI agent audit trail needs four layers: delegated authority, decision context, execution and outcome. - Agent logs are useful for explaining decisions, but TODAQ Press argues they are reconstructions written by the same system that acted. - EU AI Act Article 12 asks high-risk AI systems to allow automatic logging of events; Annex III high-risk obligations now apply from 2 December 2027. - Proof bound to the transaction at execution gives auditors integrity evidence they can verify offline, without trusting the organization that kept it. - Proof cannot show a decision was correct or within policy, so budgets, approvals and access controls remain essential. ## What is an AI agent audit trail? An AI agent audit trail is the record an auditor uses to answer four questions about an agent's conduct. Who gave the agent its authority, and what were the limits? What did it decide, and on what basis? What did it actually execute? What came back? Each question needs a different source of evidence: - **Delegated authority:** the budget, approval limits and access rights a person granted. - **Decision context:** prompts, tool calls and the agent's own account of its reasoning. - **Execution:** what was paid, settled or changed, by whom and when. - **Outcome:** what the counterparty delivered in return. Many teams already capture decision context in application logs. Execution needs particular care. When an agent spends money, the execution layer is where disputes, chargebacks and regulatory questions land, and it is where the evidence has to hold up under adversarial scrutiny. ## Why are audit logs for AI agents hard to rely on? Audit logs for AI agents are indispensable for debugging and for explaining behavior. Their limit is evidentiary. A log is written by the system that acted and stored by the organization that runs it, so its weight depends on trusting both. TODAQ Press makes a sharper argument in [You Cannot Audit a Probability](https://todaq.substack.com/p/you-cannot-audit-a-probability-the). When an agent reports what it did, "that log is itself a language model output: a reconstruction, produced by the same probabilistic engine that executed the action." Such a record "can be internally consistent, confidently written, and factually wrong." The essay adds that engineering discipline helps, within limits: "Better reliability practices reduce the frequency of errors; they do not change the nature of the record." On hardware attestation, it notes that "The hardware integrity is provable; the semantic accuracy of the record is not." The practical question for an audit team, in the essay's words: "The question is not whether logs exist. It is whether they are accurate and whether the organization can prove it." ## What are the EU AI Act logging requirements? The EU AI Act sets explicit logging obligations for high-risk AI systems. Article 12 states that "High-risk AI systems shall technically allow for the automatic recording of events (logs) over the lifetime of the system." The logs support traceability, risk identification, post-market monitoring and monitoring of operation ([Article 12](https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-12)). [Article 19](https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-19) covers retention by providers, and [Article 26(6)](https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-26) covers deployers: each keeps the automatically generated logs under its control for a period appropriate to the purpose, at least six months unless other law says otherwise. Providers that are financial institutions keep them as part of their documentation under financial services law. The dates have moved. The Digital Omnibus on AI, Regulation (EU) 2026/1744, entered into force on 27 July 2026. It moved stand-alone (Annex III) high-risk obligations, including credit assessment, from 2 August 2026 to 2 December 2027, and AI in products under Annex I to 2 August 2028 ([Legal 500](https://www.legal500.com/intelligence/european-union/technology/eu-digital-omnibus-on-ai-enters-into-force)). Some earlier commentary still cites August 2026. Whether a given agent is a high-risk system, and which logs you must keep, depends on its use. Confirm with your counsel. ### What do other frameworks ask for? - **NIST AI RMF 1.0** (January 2023) is voluntary. Its four functions are Govern, Map, Measure and Manage, and its trustworthy-AI characteristics include "accountable and transparent" ([NIST](https://www.nist.gov/itl/ai-risk-management-framework)). - **ISO/IEC 42001:2023** sets requirements for establishing, implementing, maintaining and continually improving an AI management system ([ISO](https://www.iso.org/standard/81230.html)). - **OSFI Guideline E-23** (Canada), effective 1 May 2027, covers AI and machine-learning models at federally regulated financial institutions. Vendors must supply adequate documentation, and third-party models are validated and monitored commensurate with risk ([OSFI](https://www.osfi-bsif.gc.ca/en/guidance/guidance-library/guideline-e-23-model-risk-management-2027-letter)). For a framework-by-framework map, see [AI governance for agentic payments](https://www.qatom.ai/learn/ai-governance-agentic-payments). ## What does AI agent accountability require? AI agent accountability starts from a position that recent law and decisions support: automating an action does not move responsibility onto the software. California AB 316, signed on 13 October 2025, adds Civil Code section 1714.46. A defendant that developed, modified or used AI may not assert that "the artificial intelligence autonomously caused the harm to the plaintiff" ([LegiScan](https://legiscan.com/CA/bill/AB316/2172); [Baker Botts commentary](https://ourtake.bakerbotts.com/post/102m29i/california-eliminates-the-autonomous-ai-defense-what-ab-316-means-for-ai-deplo)). In Moffatt v. Air Canada, 2024 BCCRT 149, a company was held responsible for what its chatbot told a customer. Central-bank and IMF commentary is also relevant. As reported in the TODAQ Press essays, a Bank of England Bank Underground post (21 May 2026) said legal responsibility for an agent's actions remains with the human deployer. An IMF Policy Note by Davidovic and Tourpe (24 April 2026) proposed separating probabilistic AI decisions from deterministic payment execution. If the deployer carries the liability, the deployer needs evidence it can stand behind. See [AI agent liability](https://www.qatom.ai/learn/ai-agent-liability-evidence) for more on disputes. ## How does proof at execution improve agentic AI auditability? Agentic AI auditability improves when the execution layer stops depending on anyone's account of it. TODAQ Press puts the design requirement this way: "The record of what happened needs to be bound to the transaction at the moment of execution, before any language model generates a summary of it." Qatom transactions work this way. Each holding is a TODA file whose Proof of Provenance, built from "rigs," forms an unbroken, verifiable chain of custody. A rig proves non-equivocation: no conflicting version of the history was produced. Double-spend prevention is a proved theorem in [Simple Rigs Hold Fast](https://arxiv.org/abs/2208.13617). Authorization lives in the file too: each update must satisfy the previous step's requirements, such as specific signatures. Settlement and the verifiable record are the same operation. The proof travels inside the file, so an auditor verifies it locally and offline. As the essay [When The Transaction Becomes The Record](https://todaq.substack.com/p/when-the-transaction-becomes-the) states, any party "can verify it independently without trusting the organization that originated it." The [cryptographic proof of payment](https://www.qatom.ai/learn/cryptographic-proof-of-payment) guide covers the mechanism in detail. ## What does the proof show, and what does it not? | Proves | Does not prove | |---|---| | What was executed, paid and settled, and when | That the agent's autonomous decision was correct | | Which twin paid, which received, and under which authorization | That the agent stayed within its intended policy scope | | That the history was not altered or substituted | That the original data or judgment was accurate | | That any party can verify it offline, without the originator | A system-wide view for macro-prudential monitoring | | That no conflicting version of the history exists | That regulators accept it; regulators have not formally opined on such records, and supervisors are not yet familiar with rigging trees | When The Transaction Becomes The Record is explicit about the first limit: "It cannot guarantee that an autonomous decision was correct, or that the agent acted within its intended policy scope." The Missing Middle essay adds: "Verification does not equal truth." ## What should an AI agent audit trail contain? Map each audit question to its evidence and to the control that still has to exist around it. | Audit question | Evidence | Control you still need | |---|---|---| | What authority did the agent have? | Separate agent wallet and budget ([A3](https://www.qatom.ai/capabilities#A3), [A8](https://www.qatom.ai/capabilities#A8)); auto-approve limit ([A9](https://www.qatom.ai/capabilities#A9)) | A written delegation policy per agent | | Did a human approve larger spends? | Approval by passkey or phone app above the limit ([A14](https://www.qatom.ai/capabilities#A14)) | Approvers check item, seller and price ([A31](https://www.qatom.ai/capabilities#A31)) | | What was paid, to whom, and was it altered? | Transaction id, emailed proof of purchase, TODA proof ([A15](https://www.qatom.ai/capabilities#A15), [A17](https://www.qatom.ai/capabilities#A17), [C8](https://www.qatom.ai/capabilities#C8)) | Retention aligned with your obligations | | Was each sale delivered once? | Seller checks X-Qatom-Transaction-Id ([B20](https://www.qatom.ai/capabilities#B20)) | Monitoring of retries, which are new charges ([A28](https://www.qatom.ai/capabilities#A28)) | | Why did the agent act? | Application and model logs | Log review; logs cannot be verified by the proof | | Who could move funds or keys? | Role-based access per twin ([C29](https://www.qatom.ai/capabilities#C29)); revocable keys ([B29](https://www.qatom.ai/capabilities#B29)) | Access reviews and key rotation ([B24](https://www.qatom.ai/capabilities#B24)) | | Can the record go to an auditor? | Ledger export as CSV ([C9](https://www.qatom.ai/capabilities#C9)); .toda file download | A disclosure process by consent | ## How do you build an AI agent audit trail for payments? 1. **Write the delegation down.** For each agent, record its purpose, budget and the approval limit above which a human must say yes. 2. **Enforce it in the wallet.** Give the agent its own funded wallet, so the budget is a hard ceiling, and set the auto-approve limit. 3. **Require strong approval.** Use passkeys or the phone app for approvals, and train approvers to check the item, seller and price. 4. **Keep decision logs.** Capture prompts and tool calls in your own logging, and treat them as context, with the limits above. 5. **Keep execution proof.** Store transaction ids and receipts, and download the .toda files for material payments ([C7](https://www.qatom.ai/capabilities#C7), C8). 6. **Export on a schedule.** Export twin ledgers as CSV and reconcile them with your books. 7. **Test verification.** Have internal audit verify a sample of files offline, outside your production systems. Privacy holds throughout. TODAQ Press describes the principle as "Privacy is the default; visibility is conferred by consent," so you decide which auditor or supervisor receives the full record. ## Further reading - TODAQ Press, [You Cannot Audit a Probability: The Agentic AI Trust Wall](https://todaq.substack.com/p/you-cannot-audit-a-probability-the) (12 May 2026) - TODAQ Press, [When The Transaction Becomes The Record](https://todaq.substack.com/p/when-the-transaction-becomes-the) (20 May 2026) - TODAQ Press, [Settlement Without Proof](https://todaq.substack.com/p/settlement-without-proof) (19 May 2026) - Coward and Toliver, [Simple Rigs Hold Fast](https://arxiv.org/abs/2208.13617), and the [Rigging Specifications](https://trie.site/rigging_specifications.pdf) ## Next steps - Read the overview for risk, security and compliance teams: [Qatom assurance](https://www.qatom.ai/assurance). - Walk through approvals, proof and record export with the team: [book an enterprise demo](https://www.qatom.ai/enterprise-demo). - Turn this into a control set: [agentic payments risk controls](https://www.qatom.ai/learn/agentic-payments-risk-controls). ## Frequently asked questions ### What is an AI agent audit trail? It is the record of what an AI agent did, who authorized it, what it spent or changed, and what resulted. A complete trail links the authority a person delegated to each action the agent took. Auditors use it to reconstruct and test the agent's conduct. ### Are audit logs for AI agents enough for an audit? Logs are necessary for explaining why an agent acted, but they are kept by the system or organization that acted. TODAQ Press argues that an agent's log is itself model output and can be confident and wrong. For payments and other high-stakes actions, pair logs with evidence that a third party can verify independently. ### What are the EU AI Act logging requirements? Article 12 says high-risk AI systems shall technically allow for the automatic recording of events (logs) over the lifetime of the system. Article 19 requires providers to keep those logs, and Article 26(6) requires deployers to keep the logs under their control for a period appropriate to the purpose, at least six months unless other law says otherwise. Whether your agent is a high-risk system is a question to confirm with legal advisers. ### When do the EU AI Act high-risk rules apply? The Digital Omnibus on AI, Regulation (EU) 2026/1744, entered into force on 27 July 2026. It moved stand-alone (Annex III) high-risk obligations, including credit assessment, from 2 August 2026 to 2 December 2027. Obligations for AI in products under Annex I now apply from 2 August 2028. ### Who is accountable when an AI agent makes a payment? Recent law and commentary point to the people and organizations behind the agent, not the agent itself. California AB 316 bars a defendant that developed, modified or used AI from arguing that the AI autonomously caused the harm. As reported by TODAQ Press, the Bank of England's Bank Underground blog has written that legal responsibility for an agent's actions remains with the human deployer. ### What makes agentic AI auditable? An agentic system is auditable when each action can be tied to the authority that allowed it and the evidence can be checked by someone outside the system. That needs clear delegation, such as budgets and approval limits, plus records whose integrity does not depend on trusting the operator. Proof bound to each transaction at execution supplies the second part for payments. ### Can a cryptographic audit trail prove the agent made the right decision? No. Cryptographic proof shows what was executed, paid and settled, by whom and under which authorization, and that the history was not altered. It cannot show that an autonomous decision was correct, that the agent stayed within its intended policy scope, or that the underlying data was accurate. ## Sources - [EU AI Act Service Desk: Article 12, Record-keeping](https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-12) - [EU AI Act Service Desk: Article 19](https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-19) - [Legal 500: EU Digital Omnibus on AI enters into force](https://www.legal500.com/intelligence/european-union/technology/eu-digital-omnibus-on-ai-enters-into-force) - [NIST AI Risk Management Framework](https://www.nist.gov/itl/ai-risk-management-framework) - [ISO/IEC 42001:2023](https://www.iso.org/standard/81230.html) - [OSFI Guideline E-23, Model Risk Management](https://www.osfi-bsif.gc.ca/en/guidance/guidance-library/guideline-e-23-model-risk-management-2027-letter) - [California AB 316 (LegiScan)](https://legiscan.com/CA/bill/AB316/2172) - [Baker Botts: California eliminates the autonomous AI defense](https://ourtake.bakerbotts.com/post/102m29i/california-eliminates-the-autonomous-ai-defense-what-ab-316-means-for-ai-deplo) - [TODAQ Press: You Cannot Audit a Probability](https://todaq.substack.com/p/you-cannot-audit-a-probability-the) - [TODAQ Press: When The Transaction Becomes The Record](https://todaq.substack.com/p/when-the-transaction-becomes-the) - [Coward & Toliver, Simple Rigs Hold Fast (arXiv:2208.13617)](https://arxiv.org/abs/2208.13617) --- # Agentic payments risk controls: a practical control set for AI agents Source: https://www.qatom.ai/learn/agentic-payments-risk-controls Updated: 2026-10-14 Agentic payments risk controls limit what an AI agent may spend, who approves it, which keys it holds and how each payment is proven. The strongest evidence is proof bound to the transaction and its settlement at execution, verifiable by any party without trusting the originator. Your organization still owns the policy, the scope and the review. ## Key takeaways - Give each agent its own wallet and a small budget: the balance is a hard ceiling on what it can spend. - Require human approval above a set limit, and check the item, seller, quantity and price before approving. - Keep secrets server-side, rotate them, and verify every fulfillment call against a settled sale. - Proof bound to each transaction shows what was paid, by whom and under which authorization; it does not show the decision was correct. - Write down who owns each control, because policy scope, data accuracy and review stay with your organization. ## Step by step 1. **Write the agent's spending authority** Record what each agent may buy, from which sellers, up to what amount, and who approves above that amount. 2. **Segregate wallets and fund a small budget** Give the agent its own wallet, apart from the primary wallet, and fund it with only what the mandate allows. 3. **Set the approval threshold** Set an auto-approve limit and require human approval, by passkey or phone app, for anything above it. 4. **Assign roles and protect secrets** Limit who can see or move funds on each wallet, keep credentials in a secret store, and plan rotation. 5. **Verify every fulfillment** On the seller side, check each fulfillment call's transaction id against a settled sale; on the buyer side, check receipts before any retry. 6. **Export and reconcile records** Keep transaction ids and receipts, export the wallet ledger, and match it to your books on a set schedule. 7. **Test revocation** Rehearse revoking an API key, rotating a secret and stopping an agent's funding before you need to do it for real. ## What are agentic payments risk controls? Agentic payments risk controls are the limits, approvals, key protections and records that govern money an AI agent can move. They answer the four questions an auditor asks: who authorized the agent, how much could it spend, what did it pay for, and can you prove it? Most of the control set is familiar from treasury and payments operations. The actor is what changes. An agent works at machine speed, can retry without asking, and may write its own account of what it did. TODAQ Press puts the evidence problem bluntly: "A log generated after the fact by the same system that acted answers nothing" ([Settlement Without Proof](https://todaq.substack.com/p/settlement-without-proof)). This guide maps each risk to a control and to the evidence that control leaves. It uses Qatom's controls as the worked example, with each step linked to the [Capabilities Index](https://www.qatom.ai/capabilities). ## Which risks do AI agent payment controls need to cover? Start with a risk register. Each row below names a risk, the control that addresses it, and the evidence the control leaves for review. | Risk | Control | Evidence it leaves | |---|---|---| | Agent spends beyond its mandate | Separate agent wallet with a small budget ([A3](https://www.qatom.ai/capabilities#A3), [A8](https://www.qatom.ai/capabilities#A8)) | Approved transfer into the agent wallet; agent wallet ledger | | Large or unexpected purchase | Auto-approve limit, with approval required above it ([A14](https://www.qatom.ai/capabilities#A14)) | No settlement without approval; transaction id and receipt | | Paying the wrong seller or a test listing | Check item, seller, quantity and price before approving ([A31](https://www.qatom.ai/capabilities#A31)) | Receipt names the item and amount ([A15](https://www.qatom.ai/capabilities#A15)) | | Silent double charge from a retry | Treat every retry as a new charge; check first ([A28](https://www.qatom.ai/capabilities#A28)) | One receipt per intended purchase; matching balance | | Too many people can move funds | Role-based access per wallet ([C29](https://www.qatom.ai/capabilities#C29)) | Role assignments for each twin | | Leaked fulfillment secret | Secret header, secret store, rotation ([B12](https://www.qatom.ai/capabilities#B12), [B24](https://www.qatom.ai/capabilities#B24)) | Direct calls without the header get 404 | | Compromised API key | Revocable API keys; server-only credentials ([B29](https://www.qatom.ai/capabilities#B29), [S2](https://www.qatom.ai/capabilities#S2)) | Your key inventory and revocation records | | Replayed or forged fulfillment call | Verify X-Qatom-Transaction-Id against the settled sale ([B20](https://www.qatom.ai/capabilities#B20)) | Served ids matched to settled sales | | Disputed or altered history | Proof-bound transaction files ([C7](https://www.qatom.ai/capabilities#C7), [C8](https://www.qatom.ai/capabilities#C8)) | Downloadable .toda file, verifiable offline | | Records missing at audit | Ledger export and emailed receipts ([C9](https://www.qatom.ai/capabilities#C9), [A17](https://www.qatom.ai/capabilities#A17)) | CSV ledger; receipt emails | ## How do you set AI agent spending authority? AI agent spending authority is the mandate: what the agent may buy, from whom, up to what amount, and who approves beyond it. Write it down per agent, with a named human owner. The Bank of England's Bank Underground blog, as reported by TODAQ Press in [The Invisible Shelf](https://todaq.substack.com/p/the-invisible-shelf-how-headless), notes that legal responsibility for an agent's actions remains with the human deployer. Then enforce the mandate in two layers. **The budget.** In Qatom, each user has a primary wallet and a separate agent wallet, called twins. The agent can never spend more than its twin holds, and never touches the primary wallet or a card ([A3](https://www.qatom.ai/capabilities#A3)). Moving funds into it from the primary wallet is an approved transfer: nothing moves until the owner approves ([A8](https://www.qatom.ai/capabilities#A8)). **The approval threshold.** Purchases under the auto-approve limit settle without a prompt; above it, a person approves each one by passkey or phone app ([A14](https://www.qatom.ai/capabilities#A14)). Approval links expire after about 15 minutes and belong to one account. For a cart, if a price changes after approval, nothing more is charged and the approver is asked again ([A34](https://www.qatom.ai/capabilities#A34)). Kong's talk "From Tool Calls to Revenue" at [MCP Dev Summit Toronto 2026](https://www.qatom.ai/events) framed why metering must sit in the request path: "a meter that cannot say no is accounting, not control." ## How should wallets and duties be segregated? Segregation limits the blast radius of any one mistake. Apply it to wallets and to people. - **Agent and owner.** Keep the agent wallet apart from the primary wallet, and fund it like petty cash. - **Per product.** Give each paid product its own twin, with a standing distribution sweeping revenue to the primary ([C17](https://www.qatom.ai/capabilities#C17), [C21](https://www.qatom.ai/capabilities#C21)). - **People.** Use role-based access to set who can see or move funds on each twin ([C29](https://www.qatom.ai/capabilities#C29)). Sending funds needs the Transfer role ([C14](https://www.qatom.ai/capabilities#C14)), and so does a bank cash-out ([C26](https://www.qatom.ai/capabilities#C26)). - **Bank details.** The account owner types banking details; an agent never does ([C25](https://www.qatom.ai/capabilities#C25)). One gap to train for: the approval screen does not name the paying wallet. Approvers must confirm they are signed in to the account they mean to pay from ([A31](https://www.qatom.ai/capabilities#A31)). ## How do you protect keys and secrets? Treat every credential an agent or endpoint touches as a secret with an owner, a store and a rotation plan. - **Client credentials** stay on the server, never in a browser, app or repo ([S2](https://www.qatom.ai/capabilities#S2)). - **Fulfillment tokens** live in the host's secret store; the endpoint checks the Authorization header with a constant-time compare and answers 404 when it is wrong ([B3](https://www.qatom.ai/capabilities#B3)). Sensitive header values are never shown again after saving ([B12](https://www.qatom.ai/capabilities#B12)). - **Rotation** uses a short overlap so no call fails ([B24](https://www.qatom.ai/capabilities#B24)). API keys are revocable ([B29](https://www.qatom.ai/capabilities#B29)). - **Passkeys** make each sign-in and approval one tap on the approver's own device; an agent never creates or uses one ([S11](https://www.qatom.ai/capabilities#S11)). Never put secrets in endpoint URLs, chat, tickets or listings. Other dashboard users can see endpoint URLs ([B2](https://www.qatom.ai/capabilities#B2)). ## How do you verify every fulfillment? Verification runs on both sides of each sale. **Seller side.** For anything expensive to serve, read the X-Qatom-Transaction-Id header on each fulfillment call, look up the sale, refuse unknown ids or ids for another item, and keep the ids already served ([B20](https://www.qatom.ai/capabilities#B20)). This stops replayed or forged calls. **Buyer side.** Every purchase returns a transaction id and an emailed receipt with proof of purchase ([A15](https://www.qatom.ai/capabilities#A15), [A17](https://www.qatom.ai/capabilities#A17)). A retry is a new charge, and a call the seller rejects can still be charged ([A28](https://www.qatom.ai/capabilities#A28)). Before any retry, the agent should check the last receipt and the balance. ## What does the proof show, and what does it not? Qatom transactions carry cryptographic proof bound to the transaction and its settlement at execution. Settlement and the verifiable record are one operation, so there is no separate record to reconcile later. The proof is built on the TODA file protocol, whose double-spend prevention is a published theorem ([Simple Rigs Hold Fast](https://arxiv.org/abs/2208.13617)). Be precise about its scope. | Proves | Does not prove | |---|---| | What was executed, paid and settled | That the agent's decision was correct | | Who paid, and under which authorization | That the agent stayed within its intended policy scope | | That no conflicting version of the history was produced | That the original data or judgment was accurate | | That the history was not altered or substituted afterwards | A system-wide view for macro-prudential monitoring | | That any party can verify it, offline, without trusting the originator | That a regulator has accepted this form of record | TODAQ Press states the first limit in its own words: "It cannot guarantee that an autonomous decision was correct, or that the agent acted within its intended policy scope" ([When The Transaction Becomes The Record](https://todaq.substack.com/p/when-the-transaction-becomes-the)). Supervisors are also not yet familiar with rigging trees, and regulators have not formally opined on such records. Your policy controls fill these gaps. ## What records should you keep and export? Keep records that an outside party can check without your systems. - The transaction id and receipt email for every purchase. - The wallet ledger, exported as CSV ([C9](https://www.qatom.ai/capabilities#C9)). - The .toda file for transactions under review. Its integrity can be verified and its provenance history inspected ([C7](https://www.qatom.ai/capabilities#C7), [C8](https://www.qatom.ai/capabilities#C8)). The proof travels inside the file, so verification can run locally and offline. - Distribution runs, with per-payee transfers ([C20](https://www.qatom.ai/capabilities#C20)). The [Qatom Console](https://console.todaq.net) shows TODA files, provenance and verification per twin. TODAQ Press describes an exportable "Transaction Binder" ([The Agentic Economy's Missing Middle](https://todaq.substack.com/p/the-agentic-economys-missing-middle)) that can be shared with a regulator or audit firm and verified offline. Visibility is by consent: you choose who sees the full record. Add your own records of mandates, approval policy and role changes. Those sit outside the payment proof. For how this fits wider logging, see the [AI agent audit trail guide](https://www.qatom.ai/learn/ai-agent-audit-trail). ## How do you revoke access and reconcile? **Revocation.** Rehearse it before go-live. Revoke the agent's API keys ([B29](https://www.qatom.ai/capabilities#B29)), rotate fulfillment secrets ([B24](https://www.qatom.ai/capabilities#B24)), remove roles ([C29](https://www.qatom.ai/capabilities#C29)) and stop funding the agent wallet, whose balance caps further spending. Expired approval links cannot be reused ([A14](https://www.qatom.ai/capabilities#A14)). **Reconciliation.** Because the record is created with settlement, reconciliation becomes a check against your own books. Match the ledger export to receipts, confirm one receipt per intended purchase, and read seller revenue by API (GET /v4/catalog/revenue, [B22](https://www.qatom.ai/capabilities#B22)). Two operational rules: a transfer API call that returns 202 has moved the money and is never retried ([S2](https://www.qatom.ai/capabilities#S2)), and a submitted bank cash-out cannot yet be canceled ([C26](https://www.qatom.ai/capabilities#C26)). ## Which deployment model fits your risk appetite? Qatom runs hosted, in your VPC, on-premises or air-gapped. RBC holds the reserve funds backing USD inside Qatom and supports bank on-ramp and off-ramp transfers. | Deployment | Typical reason to choose it | |---|---| | Hosted | Fastest start; lowest operating load | | VPC | Network and data stay inside your cloud boundary | | On-premises | Infrastructure stays under your own operations team | | Air-gapped | No external network; offline verification of files still works | Agentic payments compliance depends on your sector, jurisdiction and use case, so confirm with your counsel which obligations apply. The [AI governance framework guide](https://www.qatom.ai/learn/ai-governance-agentic-payments) maps NIST AI RMF, ISO/IEC 42001, the EU AI Act and OSFI E-23. ## What is the CISO checklist for AI agents? Use this order when you approve agentic payments risk controls for a first deployment. 1. Name each agent, its owner and its written spending authority. 2. Create a separate agent wallet and fund only the mandated budget. 3. Set the auto-approve limit and train approvers to check item, seller, quantity, price and account. 4. Assign roles per wallet; keep transfer and cash-out rights narrow. 5. Store credentials server-side and schedule rotation. 6. Require fulfillment verification for anything costly to serve. 7. Set the record set, export schedule and retention period. 8. Rehearse revocation and run a test reconciliation. 9. Choose the deployment model and document why. ## Further reading - TODAQ Press, [Settlement Without Proof](https://todaq.substack.com/p/settlement-without-proof) (19 May 2026) - TODAQ Press, [You Cannot Audit a Probability: The Agentic AI Trust Wall](https://todaq.substack.com/p/you-cannot-audit-a-probability-the) (12 May 2026) - TODAQ Press, [The Agentic Economy's Missing Middle](https://todaq.substack.com/p/the-agentic-economys-missing-middle) (7 Aug 2026) - [Rigging Specifications](https://trie.site/rigging_specifications.pdf) and [Simple Rigs Hold Fast](https://arxiv.org/abs/2208.13617) ## Next steps - Read the overview for risk and assurance teams: [Qatom assurance](https://www.qatom.ai/assurance). - See the controls and records live: [book an enterprise demo](https://www.qatom.ai/enterprise-demo). - Walk the buyer controls step by step in [how to let an AI agent make purchases](https://www.qatom.ai/learn/let-ai-agent-make-purchases). ## Frequently asked questions ### What are agentic payments risk controls? They are the limits, approvals, key protections and records that govern money an AI agent can move. A sound set covers spending authority, budgets, approvals, wallet segregation, secrets, fulfillment checks, records, revocation and reconciliation. Each control should leave evidence an auditor can check. ### How do you limit an AI agent's spending authority? Use two layers. Give the agent a separate wallet holding only a small budget, so its balance is a hard ceiling. Then set an auto-approve limit so that anything above it waits for a person to approve it. ### What should a CISO checklist for AI agents include? It should name each agent and its owner, its spending authority, the wallet it spends from, the approval threshold, who holds which roles, where secrets live and how they rotate. It should also say how fulfillment is verified, how records are exported and how access is revoked. Test the revocation steps before go-live. ### Can a cryptographic record prove an AI agent made the right decision? No. A proof-bound record shows what was executed, paid and settled, by whom and under which authorization, and that the history was not altered. It cannot show that the decision was correct, that the agent stayed within its intended policy, or that the input data was accurate. ### Why is a retry a risk in agentic payments? If an agent's output is cut off, the purchase may already have gone through, and a retry is a new charge. Under an auto-approve limit the retry can pass without a prompt, so double charges can happen silently. Check the last receipt and the wallet balance before any retry. ### How should sellers verify an AI agent's payment before serving it? Guard the paid route with a secret header that only Qatom sends, and refuse calls without it. For anything expensive to serve, read the X-Qatom-Transaction-Id header, look up the settled sale, refuse unknown or mismatched ids, and keep the ids already served so no sale is served twice. ### Does agentic payments compliance depend on where the platform runs? Deployment affects data location, access and who operates the system, which matter to many policies. Qatom can be hosted, or deployed in your VPC, on-premises or air-gapped. Which obligations apply depends on your sector, jurisdiction and use case. ### What records should we keep for AI agent payments? Keep the transaction id and emailed receipt for every purchase, the wallet ledger export, and the transaction files that carry each payment's provenance. Add your own records of mandates, approvals policy and role changes, because those sit outside the payment proof. ## Sources - [Qatom Capabilities Index](https://www.qatom.ai/capabilities) - [Qatom developer docs](https://docs.qatom.ai/) - [Simple Rigs Hold Fast (Coward and Toliver, arXiv:2208.13617)](https://arxiv.org/abs/2208.13617) - [Rigging Specifications](https://trie.site/rigging_specifications.pdf) - [EU AI Act, Article 12: Record-keeping](https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-12) - [TODAQ Press: Settlement Without Proof](https://todaq.substack.com/p/settlement-without-proof) --- # AI governance framework for AI agents: NIST AI RMF, ISO/IEC 42001, EU AI Act and OSFI E-23 mapped to evidence Source: https://www.qatom.ai/learn/ai-governance-agentic-payments Updated: 2026-10-14 An AI governance framework for AI agents sets who is accountable, how risk is assessed and what evidence is kept. NIST AI RMF, ISO/IEC 42001, the EU AI Act and OSFI E-23 ask for traceable records. Proof bound to the transaction and its settlement at execution, verifiable by any party without trusting the originator, supplies part of that evidence. ## Key takeaways - The four frameworks differ in force: NIST AI RMF is voluntary, ISO/IEC 42001 is a management-system standard, the EU AI Act is law and OSFI E-23 is a supervisory guideline. - The EU AI Act's stand-alone high-risk obligations now apply from 2 December 2027, and AI in Annex I products from 2 August 2028. - Proof-bound transactions give independently verifiable evidence of what an agent paid, to whom and under which authorization. - Accountability, risk classification, model validation, decision logging and policy scope remain controls your organization owns. ## What is an AI governance framework for AI agents? An AI governance framework for AI agents is the set of roles, risk assessments, controls and records an organization uses to deploy agents responsibly. When agents can move money, the framework must also cover spending authority and the payment record. Four common reference points for risk and compliance teams are the NIST AI Risk Management Framework, ISO/IEC 42001, the EU AI Act and, for Canadian financial institutions, OSFI Guideline E-23. They differ in legal force, but each asks for evidence that can be traced and reviewed. TODAQ Press argues that evidence has to start at the payment: "The record of what happened needs to be bound to the transaction at the moment of execution, before any language model generates a summary of it" ([You Cannot Audit a Probability](https://todaq.substack.com/p/you-cannot-audit-a-probability-the)). The essays also report that an IMF Policy Note (Davidovic and Tourpe, April 2026) proposes separating probabilistic AI decisions from deterministic payment execution. ## How do the four frameworks compare? Start with what each instrument is and when it applies. | Framework | Type | Applies to | Key dates | |---|---|---|---| | [NIST AI RMF 1.0](https://www.nist.gov/itl/ai-risk-management-framework) | Voluntary framework | Organizations that choose to adopt it | Released January 2023 | | [ISO/IEC 42001:2023](https://www.iso.org/standard/81230.html) | Management-system standard | Any organization providing or using AI-based products or services | Published 18 December 2023 | | EU AI Act, [Article 12](https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-12) and [Article 19](https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-19) | Regulation | High-risk AI systems | Annex III: 2 December 2027; Annex I products: 2 August 2028 | | [OSFI Guideline E-23](https://www.osfi-bsif.gc.ca/en/guidance/guidance-library/guideline-e-23-model-risk-management-2027-letter) | Supervisory guideline | Federally regulated financial institutions in Canada | Final letter September 2025; effective 1 May 2027 | Then map what each AI governance framework for AI agents asks for to the evidence proof-bound transactions provide, and to the controls that stay with you. | Framework ask | Evidence proof-bound transactions provide | Controls you still own | |---|---|---| | NIST Govern: accountability and transparency | Who paid, what was paid and under which authorization, verifiable by any party | Named owners, mandates, policies | | NIST Map: context and impact | A per-agent record of where money moved | Agent inventory, use-case and impact assessment | | NIST Measure: valid and reliable | An exact record of financial outcomes to measure against | Testing, evaluation, accuracy metrics | | NIST Manage: respond to risk | Budget transfers and approved purchases, each with a transaction id and receipt | Incident response, limits, kill decisions | | ISO/IEC 42001: operate and improve an AI management system | Records an auditor can verify without your systems | Scope, objectives, internal audit, management review | | EU AI Act Art. 12: automatic event logs over the system's lifetime | Payment events recorded at execution, which cannot be altered without detection | Logs of inputs, outputs and operation beyond payments | | EU AI Act Art. 19 and 26(6): keep logs at least six months | Exportable .toda files that verify offline, plus CSV ledgers | Retention schedule and storage | | OSFI E-23: model risk management, vendor documentation | Published protocol specifications and proofs for the payment layer | Model inventory, validation and monitoring | ## How does NIST AI RMF apply to agentic AI? NIST AI RMF 1.0 is voluntary. It organizes AI risk work into four functions, Govern, Map, Measure and Manage, and lists trustworthy-AI characteristics that include "accountable and transparent", "valid and reliable" and "secure and resilient". Under NIST AI RMF, agentic AI fits the same four functions as any other AI system. Applied to agents that pay, the payment record speaks most directly to accountability and transparency. A proof-bound transaction shows what an agent executed, paid and settled, and by whom, without anyone trusting your logs. Security and resilience come from controls around it: a separate agent wallet with its own budget ([A3](https://www.qatom.ai/capabilities#A3), [A8](https://www.qatom.ai/capabilities#A8)), approval above a set limit ([A14](https://www.qatom.ai/capabilities#A14)) and revocable keys ([B29](https://www.qatom.ai/capabilities#B29)). Validity and reliability stay with you. A payment record cannot show the agent chose well. TODAQ Press, drawing on IBM's AGENTSAFE paper, argues that frameworks such as the EU AI Act and NIST AI RMF "address AI risk primarily through pre-deployment certification" ([Built Before It Was Named](https://todaq.substack.com/p/built-before-it-was-named)). In fairness, NIST's Manage function and the AI Act's lifetime logging both reach into operation. The practical point stands: runtime evidence must come from somewhere, and the payment is one place it can be bound. ## What does ISO 42001 mean for AI agents? ISO/IEC 42001:2023 sets requirements for establishing, implementing, maintaining and continually improving an AI management system. It applies to any organization providing or using AI-based products or services. For ISO 42001, AI agents raise a scoping question first: do agent payments sit inside your management system? If they do, the records feeding internal audit and management review should be ones an auditor can check independently. Qatom transactions carry proof that travels inside the file, so a reviewer can verify integrity locally and offline ([C8](https://www.qatom.ai/capabilities#C8)). The wallet ledger exports as CSV ([C9](https://www.qatom.ai/capabilities#C9)). The rest of the management system, such as setting objectives, treating risk and improving over time, is organizational work that no payment layer performs. ## What does the EU AI Act require of AI agents? Article 12 says: "High-risk AI systems shall technically allow for the automatic recording of events (logs) over the lifetime of the system." The purpose is traceability, risk identification, post-market monitoring and monitoring of operation. Article 19 covers retention by providers and [Article 26(6)](https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-26) covers deployers. Automatically generated logs under their control are kept for a period appropriate to the intended purpose, at least six months unless other law provides otherwise. Providers that are financial institutions keep them as part of their documentation under financial services law. The dates have moved. The Digital Omnibus on AI, Regulation (EU) 2026/1744, entered into force on 27 July 2026. It moved stand-alone (Annex III) high-risk obligations, including credit assessment, from 2 August 2026 to 2 December 2027, and AI in products under Annex I to 2 August 2028 ([Legal 500](https://www.legal500.com/intelligence/european-union/technology/eu-digital-omnibus-on-ai-enters-into-force)). Older material, including some TODAQ Press essays, still gives 2 August 2026. On the EU AI Act, AI agents raise two cautions. Whether an agent is high-risk depends on its use, so confirm with your counsel how your systems are classified and what you must log. And payment events are one strand of an event log; prompts, inputs, outputs and operation need their own records. TODAQ Press argues why the payment strand matters in a dispute: "A log generated by the system that acted answers nothing when that system’s account of itself is precisely what is in dispute" ([When The Transaction Becomes The Record](https://todaq.substack.com/p/when-the-transaction-becomes-the)). ## How does OSFI E-23 apply to AI models? OSFI Guideline E-23 sets model risk management expectations for federally regulated financial institutions. The final guideline letter came in September 2025 and takes effect on 1 May 2027. It explicitly covers AI and machine-learning models, is risk-based and proportional, expects vendors to supply adequate documentation, and expects third-party models to be validated and monitored commensurate with risk. Under OSFI E-23, AI models that drive agents can fall in scope, and their validation is yours. The payment layer can support monitoring with a verifiable record of each financial outcome. For vendor documentation, the technology behind Qatom is published: the [Rigging Specifications](https://trie.site/rigging_specifications.pdf), the formal double-spend proof in [Simple Rigs Hold Fast](https://arxiv.org/abs/2208.13617) and an [open-source JavaScript implementation](https://github.com/TODAQopen/toda). Qatom deploys hosted, in a VPC, on-premises or air-gapped. Banks should also read [agentic payments for banks](https://www.qatom.ai/learn/agentic-payments-for-banks). ## What does the proof show, and what does it not? Qatom transactions carry cryptographic proof bound to the transaction and its settlement at execution. Settlement and the verifiable record are one operation, and the history cannot be retroactively altered, selectively reconstructed or institutionally withheld, as TODAQ Press describes it. | Proves | Does not prove | |---|---| | What was executed, paid and settled | That the agent's decision was correct | | Who paid, and under which authorization | That the agent stayed within its intended policy scope | | That no conflicting version of the history was produced | That the original data or judgment was accurate | | That the history was not altered or substituted | A system-wide view for macro-prudential monitoring | | That any party can verify it offline, without trusting the originator | That regulators have formally opined on such records | TODAQ Press is candid on the last row: "Teaching a supervisor to trust a rigging tree is a heavy lift" ([The Agentic Economy's Missing Middle](https://todaq.substack.com/p/the-agentic-economys-missing-middle)). Visibility is by consent: a regulator or auditor can be given the full record while others see nothing. ## Which controls does your organization still own? Build an AI governance framework for AI agents in this order. Each step maps to at least one framework above. 1. **Inventory agents and classify each use.** Note which ones pay, and whether any could be high-risk under the EU AI Act (NIST Map). 2. **Name an accountable owner per agent.** The Bank of England's Bank Underground blog, as reported by TODAQ Press in [The Invisible Shelf](https://todaq.substack.com/p/the-invisible-shelf-how-headless), says legal responsibility for an agent's actions remains with the human deployer. 3. **Set spending authority.** Budgets, approval thresholds and approved sellers; see [agentic payments risk controls](https://www.qatom.ai/learn/agentic-payments-risk-controls). 4. **Log decisions, not only payments.** Keep inputs, outputs and reasoning records alongside the payment proof; see the [AI agent audit trail guide](https://www.qatom.ai/learn/ai-agent-audit-trail). 5. **Validate and monitor models.** Size the effort to risk, as OSFI E-23 expects, and map it to NIST Measure. 6. **Set retention.** At least six months where Article 19 or Article 26(6) applies, unless other law says otherwise. 7. **Plan access for auditors and supervisors.** Decide which records you export and to whom. 8. **Review and improve.** Feed findings back into the management system, which ISO/IEC 42001 expects to be continually improved. ## Further reading - TODAQ Press, [When The Transaction Becomes The Record](https://todaq.substack.com/p/when-the-transaction-becomes-the) (20 May 2026) - TODAQ Press, [You Cannot Audit a Probability: The Agentic AI Trust Wall](https://todaq.substack.com/p/you-cannot-audit-a-probability-the) (12 May 2026) - TODAQ Press, [Built Before It Was Named](https://todaq.substack.com/p/built-before-it-was-named) (15 Mar 2026) - [Rigging Specifications](https://trie.site/rigging_specifications.pdf) and [Simple Rigs Hold Fast](https://arxiv.org/abs/2208.13617) ## Next steps - Read the overview for risk, compliance and governance teams: [Qatom assurance](https://www.qatom.ai/assurance). - See the records and verification in your own environment: [book an enterprise demo](https://www.qatom.ai/enterprise-demo). - Turn the framework into controls with the [agentic payments risk controls checklist](https://www.qatom.ai/learn/agentic-payments-risk-controls). ## Frequently asked questions ### What is an AI governance framework for AI agents? It is the set of roles, policies, risk assessments, controls and records an organization uses to deploy AI agents responsibly. Common reference points are NIST AI RMF, ISO/IEC 42001, the EU AI Act and, for federally regulated financial institutions in Canada, OSFI E-23. For agents that pay, it must also cover spending authority and payment records. ### How does NIST AI RMF apply to agentic AI? NIST AI RMF 1.0 is voluntary and organizes work into four functions: Govern, Map, Measure and Manage. For agentic AI, those functions can be applied to who is accountable for each agent, where it acts, how its behavior is measured and how risks are handled at runtime. Its trustworthy-AI characteristics include accountable and transparent, valid and reliable, and secure and resilient. ### Does ISO 42001 cover AI agents? ISO/IEC 42001:2023 sets requirements for establishing, implementing, maintaining and continually improving an AI management system. It applies to any organization providing or using AI-based products or services, so agents an organization builds or uses fall within the scope it defines. ### When do EU AI Act logging requirements apply to AI agents? Article 12 asks high-risk AI systems to allow automatic recording of events over their lifetime. Under the Digital Omnibus on AI, Regulation (EU) 2026/1744, stand-alone high-risk obligations moved to 2 December 2027, and AI in products under Annex I to 2 August 2028. Whether an agent is high-risk depends on its use. ### How long must EU AI Act logs be kept? Article 19 (for providers) and Article 26(6) (for deployers) say automatically generated logs under their control are kept for a period appropriate to the intended purpose, at least six months unless other law provides otherwise. Providers that are financial institutions keep them as part of the documentation required under financial services law. ### Does OSFI E-23 apply to AI models? Yes. OSFI Guideline E-23 on model risk management explicitly covers AI and machine-learning models at federally regulated financial institutions. The final guideline letter was issued in September 2025 and takes effect on 1 May 2027, with a risk-based, proportional approach and expectations for vendor documentation. ### Do cryptographic payment records meet AI governance requirements on their own? No. Proof-bound records give independently verifiable evidence of what was executed, paid and settled, and under which authorization. Classification, accountability, model validation and decision logging are still controls the organization owns. ## Sources - [NIST AI Risk Management Framework](https://www.nist.gov/itl/ai-risk-management-framework) - [ISO/IEC 42001:2023 Artificial intelligence management system](https://www.iso.org/standard/81230.html) - [EU AI Act, Article 12: Record-keeping](https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-12) - [EU AI Act, Article 19: Automatically generated logs](https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-19) - [Legal 500: EU Digital Omnibus on AI enters into force](https://www.legal500.com/intelligence/european-union/technology/eu-digital-omnibus-on-ai-enters-into-force) - [OSFI Guideline E-23, Model Risk Management (2027)](https://www.osfi-bsif.gc.ca/en/guidance/guidance-library/guideline-e-23-model-risk-management-2027-letter) - [TODAQ Press: When The Transaction Becomes The Record](https://todaq.substack.com/p/when-the-transaction-becomes-the) --- # AI agent liability: who is liable when an AI agent makes a mistake, and what evidence holds up Source: https://www.qatom.ai/learn/ai-agent-liability-evidence Updated: 2026-10-14 Recent rules and cases point AI agent liability to the people and organizations that develop, modify or use the agent. California AB 316 bars the defense that the AI acted on its own. In a dispute, strong evidence is proof bound to the transaction and its settlement at execution, verifiable by any party without trusting the originator. ## Key takeaways - Recent rules and cases point the same way: automating an action does not move responsibility onto the AI itself. - California AB 316 bars the defense that the AI autonomously caused the harm; commentary says it applies from 1 January 2026. - The EU Product Liability Directive covers AI software, lets courts order evidence disclosure, and allows a presumption of defect when required evidence is not disclosed. - A log produced by the party in dispute is that party's account; a record bound to the transaction at execution can be checked by anyone. - Verifiable proof shows what was executed, paid and settled, and under which authorization; it does not prove the agent's decision was correct. ## What is AI agent liability? AI agent liability is the question of who answers, legally and financially, when software acting for someone causes harm. The harm can be a wrong refund, a payment to the wrong party, a duplicate charge or a misleading statement to a customer. The agent cannot carry the liability itself, so it lands on a person or an organization. For risk and compliance teams the question has two parts. The first is allocation: which party carries the loss under law and contract. The second is evidence: what each party can prove about what the agent did, under whose authority, and what was paid and settled. This guide covers both. It describes what recent rules and cases say. It is not legal advice. TODAQ Press puts the shift in one line: "Liability, in other words, is becoming a technical problem" ([Settlement Without Proof](https://todaq.substack.com/p/settlement-without-proof)). ## Who is liable when an AI agent makes a mistake? The sources point the same way. Responsibility stays with the people and organizations behind the agent. - **Moffatt v. Air Canada, 2024 BCCRT 149.** A company was held responsible for what its chatbot told a customer. TODAQ Press reads the case as showing that "liability is not avoided by automating the actions in question." - **Bank of England.** A Bank Underground post of 21 May 2026, as reported by TODAQ Press, takes the view that legal responsibility for an agent's actions remains with the human deployer. - **California AB 316.** A defendant that developed, modified or used AI cannot argue that the AI caused the harm on its own. - **Contracts.** TODAQ Press cites a February 2026 [Clifford Chance note](https://www.cliffordchance.com/insights/resources/blogs/talking-tech/en/articles/2026/02/agentic-ai-and-the-liability-gap-your-contracts-may-not-cover.html) that "standard disclaimers typically leave the customer holding liability for a system they did not design and cannot fully audit." TODAQ Press describes the resulting gap as "deployer liability without deployer visibility." The deployer carries the risk but often cannot see, or prove, what the agent did. That is where AI agent liability becomes an evidence problem. ## What does California AB 316 change? [California AB 316](https://legiscan.com/CA/bill/AB316/2172) (Chapter 672, Statutes of 2025) adds section 1714.46 to the Civil Code. It was signed on 13 October 2025. Under it, a defendant that developed, modified or used artificial intelligence may not assert that "the artificial intelligence autonomously caused the harm to the plaintiff." TODAQ Press, drawing on [Baker Botts commentary](https://ourtake.bakerbotts.com/post/102m29i/california-eliminates-the-autonomous-ai-defense-what-ab-316-means-for-ai-deplo), says the law applies from 1 January 2026 and "forecloses the autonomous-harm defense." The statute addresses one specific argument: pointing at the model. Its effect on a given claim depends on the facts. What remains in any dispute is what the defendant did, authorized and controlled, and that is answered with records. ## How does the EU Product Liability Directive treat AI software? The [EU Product Liability Directive (EU) 2024/2853](https://www.hlc.com/en/publications/eu-introduces-comprehensive-digitalera-product-liability-directive) entered into force on 8 December 2024. Member states must transpose it by 9 December 2026, and it applies to products placed on the market after that date. "Product" includes software, including AI. TODAQ Press summarizes it as classifying "AI as a product subject to strict liability." Two provisions bear directly on evidence: - **Disclosure.** Courts can order a defendant to disclose relevant evidence. - **Presumption.** A product can be presumed defective if required evidence is not disclosed. Read together, these rules put weight on whoever holds the records. A provider that cannot produce credible evidence of what its system did can be in a weaker position. Which obligations apply to your products, and from when, is a question to confirm with your counsel. ## What evidence matters in an AI agent dispute? In a dispute about an agent's action, each side asks the same questions. What did the agent do? Who authorized it? What was paid, to whom, and when did it settle? Has the record changed since? TODAQ Press argues that typical agent logs are weak on exactly these points ([You Cannot Audit a Probability](https://todaq.substack.com/p/you-cannot-audit-a-probability-the); [When The Transaction Becomes The Record](https://todaq.substack.com/p/when-the-transaction-becomes-the)): - An agent's log "is itself a language model output: a reconstruction, produced by the same probabilistic engine that executed the action." It "can be internally consistent, confidently written, and factually wrong." - A record "generated separately from an action, and stored separately from an action, can always be questioned." - In indemnification disputes, "the party whose infrastructure generated the logs is also a party to the dispute." The essays frame this as "the difference between evidence and testimony." A log held by one party is that party's account. A record any party can check, without trusting its originator, is evidence. TODAQ Press also argues that insurers "are beginning to price the absence of portable provenance." The essays point to Estate of Gene B. Lokken v. UnitedHealth Group (D. Minn.), where, they write, "logs existed, assembled after the fact from records that did not travel with the decisions, and a court order was required to surface them." The claims in that case are allegations, and UnitedHealth disputes them. Logs still matter. Article 12 of the [EU AI Act](https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-12) asks high-risk systems to "technically allow for the automatic recording of events (logs)." Our [AI agent audit trail guide](https://www.qatom.ai/learn/ai-agent-audit-trail) covers that. For the transaction itself, the question is narrower: can the other side verify it? ### Evidence for AI agent disputes: what a bound record provides | Dispute question | Evidence from a proof bound at execution | What you still need | |---|---|---| | What was executed and paid? | One record of the transaction and its settlement, with a transaction id and an emailed proof of purchase ([A15](https://www.qatom.ai/capabilities#A15), [A17](https://www.qatom.ai/capabilities#A17)) | The business reason for the action | | Who authorized it? | Authorization carried in the file: each update satisfies the previous step's requirements, such as specific signatures; human approval above the limit ([A14](https://www.qatom.ai/capabilities#A14)) | Identity proofing of the approver | | Was the right seller paid, once? | Payee in the record; sellers check X-Qatom-Transaction-Id so each sale is served once ([B20](https://www.qatom.ai/capabilities#B20)) | The seller's own fulfilment records | | Was spending authority respected? | Agent wallet balance as a hard ceiling and an auto-approve limit ([A8](https://www.qatom.ai/capabilities#A8), [A9](https://www.qatom.ai/capabilities#A9)) | Evidence the agent's choice was within policy | | Was the record changed later? | Non-equivocation proved by rigs; history cannot be altered without detection | Key and device custody controls | | Can a court or insurer check it without us? | Local, offline verification against the file itself ([C8](https://www.qatom.ai/capabilities#C8)) | Counsel's view on admissibility | ## How does a record that any party can verify work? Qatom transactions run on the TODA file protocol. Each TODA file carries a Proof of Provenance built from rigs: an unbroken, verifiable chain of custody. A rig proves non-equivocation, meaning no conflicting version of the asset's history was produced. Double-spend prevention is a proved theorem in "Simple Rigs Hold Fast" ([Coward & Toliver, arXiv:2208.13617](https://arxiv.org/abs/2208.13617)). TODA is not a blockchain: there is no global consensus, shared ledger or gas. The proof is bound to the transaction and its settlement at the moment of execution. In TODAQ Press's words, "Settlement and verifiable record are the same atomic operation." Because the record was never separate, it "cannot be reconstructed after the fact." Verification is local and works offline, because the proof travels inside the file. As TODAQ Press puts it, "Any party, a counterparty, regulator, insurer, or court, can verify it independently without trusting the organization that originated it." Privacy holds by default. The owner can shield data before anchoring, so the trusted system records a proof without seeing the contents. Visibility is granted by consent: a counterparty or regulator can receive the full record, and others see nothing. The essays call the exportable record a "Transaction Binder" that a regulator or audit firm can verify offline ([The Agentic Economy's Missing Middle](https://todaq.substack.com/p/the-agentic-economys-missing-middle)). In the product, you can inspect a note's minting information and provenance history ([C7](https://www.qatom.ai/capabilities#C7)), verify a file's integrity and download the .toda file ([C8](https://www.qatom.ai/capabilities#C8)), and export a twin's ledger as CSV ([C9](https://www.qatom.ai/capabilities#C9)). The [Qatom Console](https://console.todaq.net) shows TODA files, provenance and verification for each twin. ## How do you prepare evidence before a dispute starts? Evidence is cheapest to secure before anyone disagrees. A practical sequence: 1. **List the agent actions that carry liability.** Start with anything that moves money, commits to a purchase or issues a refund. 2. **Bind those actions to a verifiable record.** Route payments through a rail where settlement and the record are one operation. 3. **Put spending authority in the money.** Give each agent its own wallet with a small budget, set an auto-approve limit, and require passkey or phone approval above it ([A8](https://www.qatom.ai/capabilities#A8), [A9](https://www.qatom.ai/capabilities#A9), [A14](https://www.qatom.ai/capabilities#A14)). 4. **Retain the records.** Keep transaction ids and receipts, export ledgers ([C9](https://www.qatom.ai/capabilities#C9)) and store .toda files ([C8](https://www.qatom.ai/capabilities#C8)) in your retention system. 5. **Capture decision context separately.** Keep prompts, model versions and approval reasons, since the payment proof does not show why the agent acted. 6. **Discuss evidence terms for contracts with counsel.** Consider stating which records each party accepts and how they are verified. 7. **Test the handover.** Give a sample record to someone outside the team, such as internal audit, and have them verify it offline. ## What does the proof show, and what does it not? Be precise with auditors, insurers and counsel about scope. Overstating it costs more credibility than it gains. | Proves | Does not prove | |---|---| | What was executed, paid and settled, and when | That the agent's decision was correct | | Who acted, under which authorization | That the agent stayed within its intended policy scope | | That the history was not altered, substituted or selectively rebuilt | That the original data or human judgment was accurate ("Verification does not equal truth.") | | That no conflicting version of the history was produced | A system-wide view for macro-prudential monitoring | | That any party can verify it without trusting the originator | That regulators have accepted such records; none has formally opined | TODAQ Press states the first limit directly: embedded provenance "cannot guarantee that an autonomous decision was correct, or that the agent acted within its intended policy scope." What it does guarantee is that "the execution history cannot be retroactively altered, selectively reconstructed, or institutionally withheld." ## Further reading - [When The Transaction Becomes The Record](https://todaq.substack.com/p/when-the-transaction-becomes-the) (TODAQ Press, 20 May 2026) - [Settlement Without Proof](https://todaq.substack.com/p/settlement-without-proof) (TODAQ Press, 19 May 2026) - [You Cannot Audit a Probability: The Agentic AI Trust Wall](https://todaq.substack.com/p/you-cannot-audit-a-probability-the) (TODAQ Press, 12 May 2026) - [Simple Rigs Hold Fast](https://arxiv.org/abs/2208.13617) (Coward & Toliver) and the [Rigging Specifications](https://trie.site/rigging_specifications.pdf) ## Next steps - Read the [assurance overview](https://www.qatom.ai/assurance) for risk, security and compliance teams. - Book an [enterprise demo](https://www.qatom.ai/enterprise-demo) to verify a live transaction record yourself. - Learn how [cryptographic proof of payment](https://www.qatom.ai/learn/cryptographic-proof-of-payment) works, step by step. ## Frequently asked questions ### Who is liable when an AI agent makes a mistake? The sources covered here point to the humans and organizations behind the agent. Moffatt v. Air Canada held a company responsible for what its chatbot told a customer, and a Bank of England Bank Underground post, as reported by TODAQ Press, said legal responsibility for an agent's actions remains with the human deployer. How liability splits between a developer, a vendor and a deployer depends on the facts and the contracts, which is a question for counsel. ### What is California AB 316? AB 316 is a California law, Chapter 672 of the Statutes of 2025, that adds section 1714.46 to the Civil Code. It says a defendant that developed, modified or used AI may not assert that the artificial intelligence autonomously caused the harm to the plaintiff. It was signed on 13 October 2025, and commentary cited by TODAQ Press says it applies from 1 January 2026. ### Does the EU Product Liability Directive apply to AI software? Yes. Directive (EU) 2024/2853 defines product to include software, including AI. It entered into force on 8 December 2024, member states must transpose it by 9 December 2026, and it applies to products placed on the market after that date. ### What does the EU Product Liability Directive say about evidence? Courts can order a defendant to disclose relevant evidence. If the defendant does not disclose evidence it was required to disclose, the product can be presumed defective. That makes the quality and availability of records a practical concern for any provider of AI software in the EU. ### Are AI agent logs good evidence in a dispute? Logs help, but they have limits as evidence. TODAQ Press argues that an agent's log can be a reconstruction written by the same system that acted, held by a party to the dispute. A record bound to the transaction at execution, which others can verify without trusting the originator, is harder to contest. ### Can a cryptographic record prove an AI agent made the right decision? No. A record bound to the transaction proves what was executed, paid and settled, by whom and under which authorization, and that the history was not altered. It cannot prove the decision was correct, that the agent stayed within its intended policy, or that the input data was accurate. ### Have regulators accepted TODA records as evidence? Regulators have not formally opined on TODA records. TODAQ Press itself notes that supervisors are not yet familiar with rigging trees. Treat the record as strong technical evidence of integrity and ask counsel how it fits your evidentiary rules. ## Sources - [LegiScan: California AB 316](https://legiscan.com/CA/bill/AB316/2172) - [Baker Botts: California eliminates the autonomous AI defense](https://ourtake.bakerbotts.com/post/102m29i/california-eliminates-the-autonomous-ai-defense-what-ab-316-means-for-ai-deplo) - [HLC: EU introduces comprehensive digital-era Product Liability Directive](https://www.hlc.com/en/publications/eu-introduces-comprehensive-digitalera-product-liability-directive) - [TODAQ Press: When The Transaction Becomes The Record](https://todaq.substack.com/p/when-the-transaction-becomes-the) - [TODAQ Press: Settlement Without Proof](https://todaq.substack.com/p/settlement-without-proof) - [TODAQ Press: You Cannot Audit a Probability](https://todaq.substack.com/p/you-cannot-audit-a-probability-the) - [TODAQ Press: The Invisible Shelf](https://todaq.substack.com/p/the-invisible-shelf-how-headless) - [TODAQ Press: The Agentic Economy's Missing Middle](https://todaq.substack.com/p/the-agentic-economys-missing-middle) - [Coward & Toliver: Simple Rigs Hold Fast (arXiv:2208.13617)](https://arxiv.org/abs/2208.13617) - [EU AI Act, Article 12: Record-keeping](https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-12) --- # Agentic payments for banks: settlement, verifiable records and risk controls Source: https://www.qatom.ai/learn/agentic-payments-for-banks Updated: 2026-10-14 Agentic payments for banks are payments that AI agents start and complete for customers or the bank itself, under limits a human sets. The bank's core need is evidence: proof bound to each transaction and its settlement at execution, which a counterparty, auditor or supervisor can verify without trusting the bank or the agent's own account. ## Key takeaways - A Bank of England Bank Underground post, as reported by TODAQ Press, says that legal responsibility for an agent's actions remains with the human deployer. - An IMF Policy Note proposes separating probabilistic AI decisions from deterministic payment execution; TODAQ Press argues the surrounding record must also be bound to execution. - OSFI Guideline E-23 covers AI and machine-learning models from 1 May 2027 and expects adequate vendor documentation. - Qatom can run hosted, in a VPC, on-premises or air-gapped, with RBC holding the reserve funds backing USD inside Qatom. - The proof shows what was executed, paid and settled under which authorization; it gives no system-wide view and cannot prove a decision was right. ## What are agentic payments for banks? Agentic payments for banks are payments that AI agents start and complete for a bank's customers, or for the bank itself, within limits a human sets. The agent finds a service, checks the price, pays and keeps a receipt. The human sets the budget and decides which payments need approval. For a bank, the payment step is familiar. Three other parts are new: who carries responsibility when the agent errs, how spending authority is enforced, and what record survives for customers, auditors and supervisors. This guide covers what banks are being asked, how deployment and reserves work, and where the evidence stops. It describes what rules and public bodies have said. It is not legal advice. ## What are regulators asking about AI agent payments in banking? Several public bodies, and publications by their staff, have set out views that bear on AI agent payments in banking. - **Bank of England.** A Bank Underground post of 21 May 2026, as reported in [The Invisible Shelf](https://todaq.substack.com/p/the-invisible-shelf-how-headless), says legal responsibility for an agent's actions remains with the human deployer. TODAQ Press also reports that Deputy Governor Sarah Breeden warned in June 2026 that AI agents could "amplify volatility in stress." - **IMF.** The Policy Note "How Agentic AI Will Reshape Payments" (Davidovic & Tourpe, 24 April 2026), as reported by TODAQ Press, proposes separating probabilistic AI decisions from deterministic payment execution. - **OSFI Guideline E-23.** [E-23, Model Risk Management](https://www.osfi-bsif.gc.ca/en/guidance/guidance-library/guideline-e-23-model-risk-management-2027-letter) was finalized in a September 2025 letter and takes effect on 1 May 2027. It applies to federally regulated financial institutions, explicitly covers AI and machine-learning models, and is risk-based and proportional. Vendors must supply adequate documentation, and third-party models are validated and monitored commensurate with risk. - **EU AI Act.** Credit assessment is a stand-alone (Annex III) high-risk use. Under the [Digital Omnibus on AI](https://www.legal500.com/intelligence/european-union/technology/eu-digital-omnibus-on-ai-enters-into-force), those obligations now apply from 2 December 2027. [Article 19](https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-19) and [Article 26(6)](https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-26) say providers and deployers that are financial institutions keep automatically generated logs as part of their documentation under financial services law. TODAQ Press adds one caution from a MAS and IMDA paper: "The regulatory obligations, including the Travel Rule, persist regardless of the technology rail used." A new rail does not remove existing duties. Which of these apply to your institution, and how, is something to confirm with your counsel. ## Why should settlement and the verifiable record be one operation? The IMF's separation addresses execution. TODAQ Press argues it leaves the record exposed: "even with deterministic settlement, the surrounding record may remain probabilistic, generated after execution by the same system that executed" ([Settlement Without Proof](https://todaq.substack.com/p/settlement-without-proof)). That matters for banks because agents behave differently from the systems compliance was built around. TODAQ Press puts it this way: "The same agent, given the same input, produces different financial outputs, breaking standard compliance assumptions built around deterministic systems." The answer TODAQ Press proposes is to bind the two. In Qatom, "Settlement and verifiable record are the same atomic operation." The record of what settled is produced with the settlement itself, so there is nothing to reconcile later and nothing to reconstruct. ## How does verifiable settlement for AI agents work? Verifiable settlement for AI agents in Qatom runs on the TODA file protocol. - **Money.** Money inside Qatom is USD-TDN, a US-dollar token (1 USD-TDN = 1 USD). Settlement between twins (small wallet apps) takes under one second. - **Proof.** Each TODA file carries a Proof of Provenance built from rigs: an unbroken, verifiable chain of custody. A rig proves non-equivocation, meaning no conflicting version of the history was produced. Double-spend prevention is a proved theorem in [Simple Rigs Hold Fast](https://arxiv.org/abs/2208.13617). - **Authorization.** Each update must carry a satisfaction of the previous step's requirements, such as specific signatures or weighted multi-signature lists. - **Verification.** The proof travels inside the file, so verification is local and works offline. Any party can verify it without trusting the bank that produced it. - **No ledger.** TODA is not a blockchain: no global consensus, no shared ledger and no gas. Qatom charges a 0% take rate and no transaction fees, and transaction cost does not scale with the value or volume of the payment. ## What are the main bank AI agent risks, and which controls apply? The table maps common bank AI agent risks to controls in the product and to the evidence each leaves. Step IDs link to the [Capabilities Index](https://www.qatom.ai/capabilities). | Risk | Control | Evidence it leaves | What you still need | |---|---|---|---| | Agent overspends | Separate agent wallet with its own budget; the balance is a hard ceiling ([A3](https://www.qatom.ai/capabilities#A3), [A8](https://www.qatom.ai/capabilities#A8)) | Transfers into the agent wallet and each purchase | Budget policy per agent | | Large payment without consent | Auto-approve limit, with passkey or phone approval above it ([A9](https://www.qatom.ai/capabilities#A9), [A14](https://www.qatom.ai/capabilities#A14)) | No settlement above the limit without approval | Rules for who may approve | | Wrong seller or price approved | Check item, seller and price before approving ([A31](https://www.qatom.ai/capabilities#A31)) | Payee and amount in the record | Approver training | | Duplicate charge on retry | Retries are new charges; check the receipt first ([A28](https://www.qatom.ai/capabilities#A28)) | One transaction id per purchase ([A15](https://www.qatom.ai/capabilities#A15)) | Agent retry logic | | Replayed or forged fulfilment call | Seller verifies X-Qatom-Transaction-Id; secret header on paid endpoints ([B20](https://www.qatom.ai/capabilities#B20), [B12](https://www.qatom.ai/capabilities#B12)) | Settled sale matched to delivery | Seller-side monitoring | | Leaked credentials | Key rotation and revocable API keys ([B24](https://www.qatom.ai/capabilities#B24), [B29](https://www.qatom.ai/capabilities#B29)) | Your key inventory and rotation records | Secrets management | | Too many people can move funds | Role-based access to each twin ([C29](https://www.qatom.ai/capabilities#C29)) | Who can see or move funds | Access reviews | | Model behaves badly | None in the payment layer | What the agent paid, never why | Model risk management under E-23 | TODAQ Press also cites Capco and Info-Tech Research Group warning that machine commerce will create duplicate payments that banks cannot detect in real time. Double-spend prevention stops the same funds being spent twice, but it does not stop an agent paying twice by retry or by mistake: each payment gets its own transaction id, so retry checks ([A28](https://www.qatom.ai/capabilities#A28)) and reconciliation are the controls here. ## How can a bank deploy agentic payments? Deployment is an early question in agentic payments for banks, because it sets where the data sits and who controls the network. Qatom offers four options. | Option | Where it runs | Consider it when | |---|---|---| | Hosted | Qatom's infrastructure | You are running a pilot or a lower-risk use case | | VPC | A private cloud network your institution controls | Policy requires network isolation or data residency in your cloud | | On-premises | Your own data centers | You need full control of the infrastructure | | Air-gapped | An isolated network with no outside connection | The environment must stay offline; verification still works | Air-gapped deployment fits the protocol's design, since a TODA proof verifies against the file itself with no network call. ## Where do the reserves sit, and how does money leave? RBC holds the reserve funds backing USD inside Qatom and supports bank on-ramp and off-ramp transfers. A cash-out sells USD-TDN to TODAQ Treasury, which pays US dollars to a US or Canadian bank account by ACH. The minimum is 10 USD-TDN, with a flat $1 fee, and ACH takes 2–5 business days ([C25](https://www.qatom.ai/capabilities#C25), [C26](https://www.qatom.ai/capabilities#C26)). ## How do privacy by consent and record export to supervisors work? TODAQ Press summarizes the privacy model as "Privacy is the default; visibility is conferred by consent." The owner can shield data before anchoring, so the trusted system records a proof without seeing the contents. A counterparty or regulator can then be given the full record, while others see nothing. For export, the essays describe a "Transaction Binder": "a Transaction Binder can be exported and shared with any defined party, a regulator, an audit firm, a supply-chain consortium, or a sector supervisor" ([The Agentic Economy's Missing Middle](https://todaq.substack.com/p/the-agentic-economys-missing-middle)). In the product today, you can export a twin's ledger as CSV ([C9](https://www.qatom.ai/capabilities#C9)), verify a file and download the .toda file ([C8](https://www.qatom.ai/capabilities#C8)), and inspect provenance history ([C7](https://www.qatom.ai/capabilities#C7)). The [Qatom Console](https://console.todaq.net) shows TODA files, provenance and verification per twin. For E-23 vendor documentation, the primary sources are public: the [Rigging Specifications](https://trie.site/rigging_specifications.pdf), the [Abject Specification](https://trie.site/abject-specs-v1.pdf), the formal proofs and the [open-source JavaScript implementation](https://github.com/TODAQopen/toda). Dann Toliver (CSO) co-authored the Rigging Specifications and Simple Rigs Hold Fast; Adam Gravitis (CTO) co-authored the Abject Specification. ## How should a bank evaluate agentic payments? A sensible evaluation of agentic payments for banks starts small and tests the evidence as closely as the payment. 1. **Pick one bounded use case.** Choose agent purchases of data or API calls with a small, fixed budget. 2. **Choose the deployment.** Decide between hosted, VPC, on-premises or air-gapped based on data and network policy. 3. **Set authority in the money.** Fund a separate agent wallet, set an auto-approve limit, and require passkey approval above it. 4. **Map the evidence.** List what your auditors and supervisors will ask for, against the risk table above. 5. **Run test transactions.** Make several purchases, including a retry, and check one transaction id per intended payment. 6. **Hand over a record.** Export the ledger and a .toda file, and have internal audit verify the file offline. 7. **Document the gaps.** Record what the payment proof does not cover, and the model risk and monitoring controls that fill it. ## What does the proof show, and what does it not? | Proves | Does not prove | |---|---| | What was executed, paid and settled, and when | That the agent's decision was correct | | Who acted, under which authorization | That the agent stayed within its intended policy scope | | That the history was not altered or substituted | That the original data or judgment was accurate ("Verification does not equal truth.") | | That no conflicting history was produced, so no double-spend | A system-wide view for macro-prudential monitoring ("TODAQ has no native global observation surface") | | That any party can verify it without trusting the originator | That supervisors accept such records; none has formally opined | TODAQ Press is direct about the last point: "Teaching a supervisor to trust a rigging tree is a heavy lift." Plan for that conversation early. ## Further reading - [Settlement Without Proof](https://todaq.substack.com/p/settlement-without-proof) (TODAQ Press, 19 May 2026) - [When The Transaction Becomes The Record](https://todaq.substack.com/p/when-the-transaction-becomes-the) (TODAQ Press, 20 May 2026) - [The Agentic Economy's Missing Middle](https://todaq.substack.com/p/the-agentic-economys-missing-middle) (TODAQ Press, 7 Aug 2026) - [Simple Rigs Hold Fast](https://arxiv.org/abs/2208.13617) (Coward & Toliver) and the [Rigging Specifications](https://trie.site/rigging_specifications.pdf) ## Next steps - Read the [assurance overview](https://www.qatom.ai/assurance) for bank risk and payments teams. - Book an [enterprise demo](https://www.qatom.ai/enterprise-demo) to discuss deployment options and verify a live record. - Work through the [agentic payments risk controls](https://www.qatom.ai/learn/agentic-payments-risk-controls) checklist. ## Frequently asked questions ### What are agentic payments for banks? They are payments that AI agents initiate and complete on behalf of a bank's customers or the bank itself, within limits a human sets. For a bank, the hard questions are authority, settlement and evidence. Each payment needs a record that the bank, its customer and its supervisor can rely on. ### Who is responsible when a bank's AI agent makes a payment error? A Bank of England Bank Underground post of 21 May 2026, as reported by TODAQ Press, says legal responsibility for an agent's actions remains with the human deployer. California AB 316 also bars a defendant that used AI from arguing that the AI autonomously caused the harm. How this applies to a specific bank is a question for its counsel. ### Does OSFI E-23 apply to AI agents? OSFI Guideline E-23 on model risk management explicitly covers AI and machine-learning models used by federally regulated financial institutions. It takes effect on 1 May 2027, is risk-based and proportional, and expects vendors to supply adequate documentation. Third-party models must be validated and monitored commensurate with their risk. ### What does the IMF say about agentic AI and payments? An IMF Policy Note by Davidovic and Tourpe, How Agentic AI Will Reshape Payments (24 April 2026), proposes separating probabilistic AI decision-making from deterministic payment execution, as reported by TODAQ Press. TODAQ Press calls this a sound instinct. It argues that, even with deterministic settlement, the surrounding record may remain probabilistic unless it is bound to execution. ### Can Qatom run inside a bank's own infrastructure? Yes. Qatom deployment options are hosted, VPC, on-premises and air-gapped. Because TODA proofs travel inside the file and verify locally, verification does not need a network call to an outside service. ### Who holds the reserves behind USD inside Qatom? RBC holds the reserve funds backing USD inside Qatom and supports bank on-ramp and off-ramp transfers. Money inside Qatom is USD-TDN, a US-dollar token at 1 USD-TDN to 1 USD. Payouts to US or Canadian bank accounts go by ACH. ### Can a bank give a supervisor the transaction record? Yes. A twin's ledger can be exported as CSV and individual .toda files can be downloaded and verified offline. TODAQ Press describes an exportable Transaction Binder that can be shared with a regulator or audit firm. No supervisor has yet formally opined on records of this kind. ### Is Qatom built on a blockchain? No. Qatom runs on the TODA file protocol, which has no global consensus, no shared ledger and no gas. Each file carries its own proof of provenance, and double-spend prevention is a proved theorem published in Simple Rigs Hold Fast. ## Sources - [OSFI Guideline E-23: Model Risk Management (2027)](https://www.osfi-bsif.gc.ca/en/guidance/guidance-library/guideline-e-23-model-risk-management-2027-letter) - [EU AI Act, Article 19: Automatically generated logs](https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-19) - [Legal 500: EU Digital Omnibus on AI enters into force](https://www.legal500.com/intelligence/european-union/technology/eu-digital-omnibus-on-ai-enters-into-force) - [TODAQ Press: Settlement Without Proof](https://todaq.substack.com/p/settlement-without-proof) - [TODAQ Press: The Invisible Shelf](https://todaq.substack.com/p/the-invisible-shelf-how-headless) - [TODAQ Press: The Agentic Economy's Missing Middle](https://todaq.substack.com/p/the-agentic-economys-missing-middle) - [TODAQ Press: When The Transaction Becomes The Record](https://todaq.substack.com/p/when-the-transaction-becomes-the) - [Coward & Toliver: Simple Rigs Hold Fast (arXiv:2208.13617)](https://arxiv.org/abs/2208.13617) - [Rigging Specifications](https://trie.site/rigging_specifications.pdf) - [Abject Specification](https://trie.site/abject-specs-v1.pdf) --- # Past events Source: https://www.qatom.ai/past-events ## Hack the Andes by Crafter Station Oct 17 to 18, 2026 · Lima, Perú · In person Qatom's role: The agentic commerce rail for the weekend. A 30-hour hackathon in Lima, hosted by Crafter Station. Teams turned APIs, datasets and models into things an AI agent can find, order from and pay for, and every participant was offered six months of Qatom Max. - https://hacktheandes.com/ ## The Foundry Vol. 1: Water Hackathon Sat Oct 17, 2026 · Toronto · In person Qatom's role: Hassan Khan, Founder and CEO, and Susana Khan, CMO, each joined a team. A hackathon for good in aid of WaterAid Canada, at Toronto Metropolitan University: one day, eleven real-world challenges identified with WaterAid Canada, across operations, strategy and technology. Co-produced by The AI Fellowship (Toronto Chapter) and SOON. - https://luma.com/9o6jes1o ## Qatom Demo & Tutorial: Warm-Up for Hack The Andes Fri Oct 9, 2026 · Online, on Zoom · Online Qatom's role: Host, with a live Q&A with Hassan Khan, CEO. Ninety minutes, built live for Hack the Andes participants: a catalog, a selling agent and a real paid call, end to end. - https://luma.com/830d5l83 ## Workshop: Build a Payment Capable MCP Catalog, Publishing Agent, and Shopper Skill in 60 Minutes Oct 5 to 6, 2026 · Toronto · In person Qatom's role: Workshop led by Matthew Mihok, Technical Lead, at MCP Dev Summit Toronto 2026. A working, payment-capable multi-agent MCP workflow in one hour, from service catalog and agent identity to paid transactions, custody transfer and audit logs. - https://luma.com/tdeyxs5p - https://events.linuxfoundation.org/mcp-dev-summit-toronto/program/schedule/?id=1287449