Last updated October 26, 2026. By Paul Johnson, Co-founder and Head of Operations, Lumanu. Updates: vendor pricing and payout coverage figures checked against published website information  on October 23, 2026.

No single payouts API is the right answer for every creator-economy business. The biggest decisions to make are:

• Who owns payee onboarding and tax compliance when an agent manages payouts?

• Do you want humans involved in the payout process?

Best payouts API for AI agents: the short answer

All five of these APIs can manage payouts while your agents control the process. They have different approaches for what happens when a creator has not finished onboarding, has a stale bank account, or is unable to receive your payment. An agent cannot always verify someone's identity or explain how to correctly fill out a W-9 so whoever owns that work so you need to plan for edge cases and support needs.

Many teams run two: one system for customer charges, a second for creator payouts.

AI agent payments market size, and what it does not measure

Agentic payouts are very new and just starting to become part of the creator marketing ecosystem in the end of 2026. These forecasts are of agentic payments in related fields and likely to be wrong and wildly different, but it’s worth taking a quick scan of where the ecosystem is potentially going and the billions of dollars expected to be managed by agents.

Every row measures agents spending money. None measures agents paying people. No published figure tracks creator, contractor or affiliate payout volume initiated by an agent.

Lumanu’s ledger is the one payout-side dataset we can cite. Lumanu processed more than $1.5B in creator and contractor payouts in the 12 months to October 2026 (Lumanu, 2026). More than $100M of that volume was created or approved by an AI agent (Lumanu, 2026). That figure grew 10x year over year, from a little over $10M to more than $100M (Lumanu, 2026).

93% of payouts on the Lumanu network still require a human approval before processing (Lumanu, 2026). That approval runs in scheduled batches rather than payment by payment, most commonly a weekly review (Lumanu, 2026). The common approach is a Marketing budget owner, an accounts payable director or even a CFO reviewing and releasing approved queued payables on a set cadence (weekly or bi-weekly).

Agents manage creating, monitoring deliverables, approving and queueing. The actual releasing funds stays human. Savings shows up in headcount: payout operations that previously took three or more people are run by one person working with agents (Lumanu, 2026).

Payout-side infrastructure arrived on these dates. Google published the Agent Payments Protocol (AP2) in September 2025 with more than 60 launch partners, including Mastercard, PayPal, American Express and Coinbase (Google, 2025). Stripe's Treasury tools for agents, covering sending money, transferring between balances and converting currency, are in public preview on its MCP server (Stripe, October 2026). Stripe requires human confirmation before an agent executes an outbound payment, and that approval token expires after 24 hours (Stripe, October 2026). Stripe stops accepting full-access secret keys and untagged restricted keys on its MCP server in December 2026, with a migration deadline of November 30, 2026 (Stripe, October 2026).

Accounts payable is a close adoption proxy to creator payouts. Accounts payable automation is the second most common live AI use case in finance functions, cited by 37% of finance teams using AI (Gartner, November 2025). 54% of CFOs name integrating AI agents into finance a transformation priority (Deloitte CFO Signals, Q4 2025). 16% of organizations report broad or embedded AI use across accounts payable workflows (Accounts Payable Automation Trends Report, 2026). 66% of accounts payable teams still key invoices into their accounting system by hand (IFOL Accounts Payable Automation Trends, 2025).

Payouts API requirements for AI agents

The usual API requirements stay the same: a sandbox, readable errors, SDKs, webhooks in addition to polling. Agents add more requirements. An agent runs when nobody is watching, so any failure it cannot resolve turns into a silent stall or a duplicate payment.

Idempotency on every write. An agent that times out and retries will call your payout endpoint a second time. Without an idempotency key that collapses the retry into the original, the creator gets paid twice and your team finds out at reconciliation.

An obligation object that exists before the money moves. The payment should land first as a record that a person or a rule can approve or review, rather than going straight from deliverable_approved to funds leaving the account. Lumanu's three-step create, approve and fund pattern is one version of this. On Stripe you build the equivalent yourself before calling transfers.create.

Payee readiness as one readable state. The agent needs a single call that answers whether this creator can be paid today. When readiness is spread across capability flags, a requirements.currently_due array, a pending_verification list and a separate tax form status, the agent has to encode your compliance rules in its prompt or its code.

Credentials scoped below the agent's job. Give the agent a key that creates payables and reads status, and keep funding on a credential a person holds. Stripe's restricted keys do this.

Agent tooling is uneven. Stripe ships an official agent toolkit for the OpenAI Agents SDK, LangChain, CrewAI and the Vercel AI SDK, plus a hosted MCP server at mcp.stripe.com. Most payout vendors have not shipped an equivalent. In their absence, a REST API with an OpenAPI spec and a published llms.txt is enough for a coding agent to integrate against, and a well-scoped internal tool wrapper gives a runtime agent what it needs.

Payouts API comparison: Stripe Connect, Trolley, Dots, Airwallex and Lumanu

]Onboarding tells you who talks to the creator when verification fails. Filing tells you whose EIN appears on the form in January.

Only Stripe publishes an agent toolkit, a hosted MCP server and agent skills in its CLI. The other four expose REST APIs, webhooks and a sandbox, which a coding agent integrates against and a runtime agent reaches through a tool wrapper you write. That wrapper is a day of work. The compliance model is an ongoing decision which impacts support needed to manage your payouts.

Stripe Connect: coverage, agent tooling and what you still own

Stripe sets the standard for API documentation in this category. The reference is date-versioned, the errors explain themselves, the sandbox behaves like production, and the SDK you want exists in the language you use. A coding agent writes a working Stripe integration on the first pass more often than it writes anyone else's.

Stripe also owns the most developed agent surface of the five. It hosts an MCP server at mcp.stripe.com, ships an open-source agent toolkit for the OpenAI Agents SDK, LangChain, CrewAI and the Vercel AI SDK, and installs both through stripe agent setup in its CLI. Autonomous clients authenticate with an Agent API key instead of OAuth, and calls against a connected account need that key plus a Stripe-Account header. Stripe's migration deadline is November 30, 2026; from December the MCP server rejects full-access secret keys and restricted keys without the Agent tag.

Two limits matter for creator payouts. The MCP server's supported API methods cover listing and retrieving transfers and payouts, with no method for creating them, so a Connect transfer goes through the API directly. Stripe also requires human confirmation before certain writes, including outbound payments, and the approval token expires after 24 hours. An unattended run that trips that gate waits for a person.

Where it fits. You already process customer charges through Stripe, your recipients sit in the US, UK, EEA, Canada or Switzerland, and you have engineering capacity to spend on the payee lifecycle. Under those conditions Connect is a short integration.

What you take on. Connect is a federated sub-account system. Every creator becomes a connected account scoped to your platform, with its own verification state, its own bank details and its own tax relationship with you. A creator working with five Connect platforms completes five onboardings and signs five W-9s. That structure generates the work an agent cannot finish:

• Requirements remediation. A connected account surfaces requirements.currently_due, pending_verification and new document requests over the life of the relationship. Each one sends the creator back through an Account Link, and the return_url fires whether or not they completed it. Your agent can detect the state. Only the creator can clear it.

• Failed payouts. payout.failed lands on your webhook when a creator's bank rejects the transfer. Your code notifies them, prompts a bank update, retries, and your support queue absorbs the rest.

• 1099 issuance. Your platform is the reporting party. Stripe helps you collect tax information and generate forms. Your finance team owns the January mismatches, the corrections and the inbound creator questions.

Stripe Connect Express takes roughly 17 API steps between a new creator and a settled payment, including the remediation loop above and a 5 to 6 business day ACH settlement wait (Lumanu teardown, 2026).

The country ceiling. Stripe supports self-serve cross-border Connect payouts only between platforms and connected accounts in the US, UK, EEA, Canada and Switzerland (Stripe, 2026). Outside those regions you contact sales or move to Global Payouts, which decouples payouts from payments and hands back the compliance obligation: Stripe's own comparison says you then "manage your own legal and compliance requirements," which may require a money transmitter license if you hold customer funds.

For a creator roster across Southeast Asia and Latin America, that ceiling ends the evaluation.

Trolley: tax filing coverage and pricing

Trolley sells payouts and tax compliance as separate modules: Pay for the money movement, Tax for forms and filing, Trust for identity verification, Sync for the ERP connection. Trolley covers 210+ countries and territories and 135+ currencies, the widest list of the five (Trolley, 2026).

Tax is the reason most creator platforms shortlist Trolley. The module collects W-9 and W-8 forms at onboarding, runs IRS TIN matching, applies withholding where required, and e-files 1099-NEC, 1099-MISC, 1099-K and 1042-S as an IRS transmitter. It also produces DAC7 and OECD digital platform reports for the EU, UK, Canada, Australia and New Zealand. For an affiliate network paying European sellers, that reporting is the whole evaluation.

Tax on the Standard plan covers a single jurisdiction. A platform that files with the IRS and reports under DAC7 needs Trolley Plus, which carries custom pricing. Trolley Pay costs $2,399 a year and Trolley Tax costs $2,399 a year on the Standard plan (Trolley, October 2026). Trust costs $1,199 a year and Sync costs $1,199 a year (Trolley, October 2026). Transaction fees add $1 per domestic ACH payout, $4 for a cross-rail payment and $10 for a wire with FX (Trolley, October 2026). Tax statements cost $2 per IRS form and $3 per digital platform form, and identity scans cost $2.50 each (Trolley, October 2026). Trolley charges a 2% currency conversion margin that drops with volume (Trolley, October 2026). That is four times what Airwallex charges on major currencies.

For agent work, Trolley gives you REST endpoints, SDKs, a recipient widget, webhooks, a sandbox and native payment approval workflows in Pay. The approval workflow covers the obligation-object requirement: an agent queues a batch and leaves the release to a person or a rule. Trolley publishes no MCP server or agent toolkit, so a runtime agent reaches it through a wrapper you write.

The structural limit matches Stripe's. Trolley moves money and files forms on your behalf, and your platform stays the reporting party. The creator still has to finish onboarding before anything settles, and Trolley runs that chase instead of your team.

Dots: instant US rails and published pricing

Dots optimizes for settlement speed. Dots reaches 190+ countries across 300+ payout rails (Dots, 2026). The US set includes the ones creators ask for: RTP, FedNow, ACH, Venmo, Cash App, PayPal and push-to-card. Instant payouts carry no surcharge, which separates Dots from providers that bill 1% to 1.5% for the same thing.

Two features suit agent-driven workflows. Dots Onboard runs a white-labeled flow for W-9 and W-8 collection, ID checks and sanctions screening, and it supports staggered onboarding: you can send a creator a payout before they have finished setting up, and collect the rest when they claim it. Payout Links extend that to an email address or a phone number with no account on either side. An agent that detects a completed deliverable can pay it the same hour instead of blocking on a profile.

Dots Tax handles W-9 collection, TIN verification against IRS records, and 1099 generation and e-filing. The published scope is North America. A platform paying EU sellers under DAC7 or non-US creators needing 1042-S will find less here than in Trolley, so confirm coverage against your own payee distribution.

Dots Core costs $19 a month and does not include API access (Dots, October 2026). Dots Scale costs $999 a month and includes API access (Dots, October 2026). On Scale, a domestic payout costs $1 and an international payout costs 2.9% plus $1 (Dots, October 2026). A 1099 costs $3.50 and an identity verification costs $3 (Dots, October 2026). International is priced as a percentage, so your average payment size drives the comparison: a $2,000 payment costs about $59 before FX. Model it against your own payment sizes.

Dots publishes no MCP server or agent toolkit. Documentation sits at docs.usedots.com, with a sandbox and a REST API.

Airwallex: FX pricing and US tax filing limits

Airwallex is a treasury platform first: multi-currency accounts, local collection accounts in 70+ markets, FX, corporate cards, and a Payouts API on top. Creator payouts are one use case inside a stack built for companies holding money in several currencies.

The FX line is the strongest argument. Airwallex charges 0.5% over interbank on major currencies and 1% on all others (Airwallex, 2026). Trolley charges a 2% conversion margin (Trolley, October 2026). On $5M of annual conversion, that 1.5-point spread is $75,000. Local transfers to 120+ countries carry no fee and SWIFT transfers cost $15 to $25 (Airwallex, 2026). Airwallex supports local and SWIFT payouts to 200+ countries and 90+ currencies, with local clearing in 120+ (Airwallex, 2026).

Tax support has limits. Airwallex ships an Embedded Tax Form component that collects W-9, W-8BEN, W-8BEN-E, W-8ECI, W-8EXP and W-8IMY, matches TINs against IRS records, and e-delivers forms. At year end it files 1099-K or 1099-NEC on your behalf, and the documentation states that it supports one or the other rather than both. Published coverage stops short of 1042-S and DAC7. PartnerStack runs partner payouts and US tax reporting on Airwallex.

Embedded is the operative word. You integrate the tax form component into your own product flow, so your platform still owns the screens, the reminders and the support when a creator abandons the form halfway. Airwallex gives your agent cheaper FX and better rails, and leaves the payee lifecycle where it was.

Pick Airwallex when currency control is the point and your compliance needs stop at US 1099 filing. Pair it with something else when they do not.

Lumanu: master vendor of record for creator payouts

Disclosure: we build Lumanu. The tradeoffs below are the ones we give engineering teams who end up choosing something else.

Lumanu runs a network wallet model behind a master vendor of record. A creator verifies with Lumanu once and carries that identity, that wallet and that tax form across every platform on the network. Your platform credits the wallet. The creator withdraws to a bank account or debit card in their own currency on their own schedule. Lumanu pays creators in 180+ countries and 132 currencies (Lumanu, 2026). Lumanu processed more than $1.5B in payouts in the 12 months to October 2026 (Lumanu, 2026). Lumanu acts as merchant of record in the US, UK, EU and Canada, and vendor of record for international payouts.

The API uses three calls: create a payable, approve it, fund it. Creator payments usually pass an approval gate, so the obligation lives as an object before money moves. An agent can create and approve a payable for a creator who has no Lumanu account yet. Lumanu collects the signup and the tax form, sends the reminders, and releases the funds when the payee completes it. The payment never blocks on onboarding. The median onboarding time for a US-based creator on Lumanu is 2 minutes 38 seconds (Lumanu, 2026), against the roughly 17 API steps and repeated Account Link cycles that Connect Express requires.

What leaves your codebase. Identity verification and document collection sit with Lumanu, so your product has no concept of a creator whose tax form just expired. Bank details sit with Lumanu, so no code path exists for bank updates, verification or retry on failure. Payout scheduling and threshold screens go away, because the creator configures withdrawal inside their own wallet. payout.failed never reaches your webhook handler, because the withdrawal is between the creator and Lumanu. Year-end filing sits with Lumanu as master vendor rather than with your finance team. Your remaining event surface is partner status, payable lifecycle and funding.

What you give up. Three things:

• No charge processing. Lumanu moves money out. A marketplace that takes customer payments and disburses in one coupled system gets a cleaner build on Connect.

• A Lumanu-branded payee experience. Full control of the creator-facing UI needs Connect Custom, and you pay for it in ongoing engineering.

• An opinionated model. Programmatic splits across several recipients in one transaction, escrow with platform-controlled release, and netting platform fees against a creator's balance are all more flexible on Connect.

One-off vendor payments fit poorly. Asking someone you will pay once to set up a wallet adds friction with no payoff.

For agent work, Lumanu publishes a REST API, webhooks, a sandbox, and docs that serve a markdown version of every page plus an index at developers.lumanu.com/llms.txt. No MCP server yet. Pricing is a variable funding fee, with an annual platform fee that volume often waives.

What AI agents cannot do in a payout workflow

An agent handles the payment side. It watches for a completed deliverable or an affiliate commission crossing a threshold, matches it to a rate card, creates the payable, checks it against a budget rule, approves or escalates, writes the reconciliation entry, and answers the creator who asks where the money is.

Four things sit outside its reach, because only the creator can do them:

1. Upload a passport or driving licence for identity verification

2. Sign a W-9 or W-8BEN, which needs a legal signature from the payee

3. Supply or correct bank details

4. Clear a sanctions or KYC flag raised against their own record

Four more sit with your team: funding the account, approving above a threshold, accepting liability for a filing, and deciding a disputed deliverable. Those gates should stay with a person.

The payee-side four behave differently. Each parks a payment, and none resolves on its own. An agent running Friday night finds eleven creators ready to pay and three stuck on a tax form. If your platform owns the chase, the agent's output is three tickets and the automation stops where the value was. If the payouts provider owns the chase, those three resolve over the weekend with no one at your company involved.

The network behind the API changes the odds. Lumanu was built for the creator ecosystem, and more than 500,000 creators, talent managers and affiliates are already onboarded and payable on the network (Lumanu, 2026). A creator your agent pays for the first time has often verified identity, signed a tax form and set a withdrawal method years earlier, on another platform's campaign. The readiness check returns yes before your integration asks for anything. That effect is measurable. 41.2% of payments on the Lumanu network go to a payee receiving a single one-off payment (Lumanu, 2026). The other 58.8% go to payees receiving multiple payments from multiple payors (Lumanu, 2026). The one-and-done share fell from roughly 52% a year earlier (Lumanu, 2026), so the share of payments landing on an already-onboarded payee is rising. A per-platform sub-account model cannot produce that, because the identity it creates belongs to one platform and starts empty.

Entity structure is the other thing an agent cannot reason its way through. Talent managers represent under 1% of vendors on the Lumanu network but roughly 10% of payments (Lumanu, 2026). They also carry the most complicated arrangements: loan-out companies, payments routed to a manager on behalf of a performer, and splits that change deal by deal. The creator named on the brief and the legal entity that has to be paid and reported are frequently different, and no amount of prompt engineering resolves which is which. That mapping belongs in the payee record, maintained by whoever onboarded the payee.

Tax thresholds make the same point. The US 1099-NEC filing threshold rose to $2,000 for payments made in 2026, up from $600 (IRS, 2026). An agent paying one creator across four campaigns has to track cumulative totals per legal entity per calendar year, know when a W-9 becomes mandatory, and apply withholding where a W-8 is missing. That logic belongs inside the payouts provider, because it changes by statute and your agent will not notice.

Settle the payee state machine before you settle on an API. Two architectures exist: your platform owns payee state, as with Stripe Connect, Airwallex, and in part Trolley and Dots, or a vendor of record owns it, as with Lumanu. Both ship. They differ in how much of the loop closes unattended.

AI agent payout workflow: reference architecture

Every provider evaluated supports the budget gate on the top row, and it catches most payments rather than the exceptions: 93% of payouts on the Lumanu network wait on a human release, usually in a weekly batch (Lumanu, 2026). The ready to pay step on the second row determines how much can actually run without support. When you own onboarding, you own support.

AI agent payout statistics (2026)

Each figure below is stated with its source and the year it was published.

• Lumanu processed more than $1.5B in creator and contractor payouts in the 12 months to October 2026 (Lumanu, 2026).

• More than $100M of Lumanu's payout volume was created or approved by an AI agent (Lumanu, 2026).

• Agent-created payout volume on Lumanu grew 10x year over year, from a little over $10M to more than $100M (Lumanu, 2026).

• 93% of payouts on the Lumanu network still require a human approval before processing (Lumanu, 2026).

• Human approval of agent-created payouts happens in scheduled batches rather than payment by payment, most commonly a weekly review (Lumanu, 2026).

• Payout operations that previously took three or more people are run by one person working with agents on Lumanu (Lumanu, 2026).

• 41.2% of payments on the Lumanu network go to a payee receiving a single one-off payment, down from roughly 52% a year earlier (Lumanu, 2026).

• 58.8% of payments on the Lumanu network go to payees receiving multiple payments from multiple payors (Lumanu, 2026).

• Talent managers represent under 1% of vendors on the Lumanu network but roughly 10% of payments (Lumanu, 2026).

• The median onboarding time for a US-based creator on Lumanu is 2 minutes 38 seconds (Lumanu, 2026).

• More than 500,000 creators, talent managers and affiliates are onboarded and payable on the Lumanu network (Lumanu, 2026).

• Lumanu pays creators in 180+ countries and 132 currencies (Lumanu, 2026).

• Global agentic commerce transaction value is forecast at $8B in 2026, rising to $3.5T by 2031 (Juniper Research, 2026).

• Accounts payable automation is the second most common live AI use case in finance, cited by 37% of finance teams using AI (Gartner, November 2025).

• 16% of organizations report broad or embedded AI use across accounts payable workflows (Accounts Payable Automation Trends Report, 2026).

• 66% of accounts payable teams still key invoices into their accounting system by hand (IFOL Accounts Payable Automation Trends, 2025).

• 54% of CFOs name integrating AI agents into finance a transformation priority (Deloitte CFO Signals, Q4 2025).

• The US 1099-NEC filing threshold is $2,000 for payments made in 2026, up from $600 (IRS, 2026).

• Stripe supports self-serve cross-border Connect payouts only to connected accounts in the US, UK, EEA, Canada and Switzerland (Stripe, 2026).

• Trolley covers 210+ countries and territories and 135+ currencies (Trolley, 2026).

• Dots reaches 190+ countries across 300+ payout rails (Dots, 2026).

• Airwallex charges 0.5% over interbank FX on major currencies and 1% on all others (Airwallex, 2026).

No published figure tracks total creator, contractor or affiliate payout volume initiated by AI agents across the industry. The Lumanu figures above are first-party data from a single network.

Frequently asked questions about AI agent payouts

What is the best payouts API for AI agents to pay creators and freelancers?

No single API wins outright. Stripe Connect has the best documentation and the only first-party agent toolkit, and suits platforms already processing charges on Stripe with recipients in the US, UK, EEA, Canada or Switzerland. Trolley suits platforms needing 1099, 1042-S and DAC7 filing across 210+ countries. Dots suits US-heavy programs that want instant rails with no surcharge. Airwallex suits teams whose main cost is FX. Lumanu suits platforms that want payee onboarding, tax forms and 1099 issuance to sit with a master vendor of record instead of their own team, which is the structure that lets an agent close the loop unattended.

Can an AI agent send a payout through Stripe?

Yes, through the Stripe API with an Agent API key. Stripe's hosted MCP server at mcp.stripe.com exposes read methods for transfers and payouts rather than a method to create them, so the money movement itself runs against the API. Calls against a connected account need an agent key plus a Stripe-Account header. Migrate to agent-tagged keys by November 30, 2026; from December the MCP server rejects full-access secret keys and untagged restricted keys.

Which payouts API collects W-9 and W-8 forms automatically?

Trolley, Dots, Airwallex and Lumanu all collect them. Who files is the distinction that matters. Trolley, Dots and Airwallex collect and e-file on your behalf while your platform remains the reporting party. Lumanu is the reporting party itself as master vendor of record. Stripe Connect leaves your platform as the 1099 issuer in every tier.

Can an agent onboard a creator without a human?

No. Identity verification, a signed W-9 or W-8BEN, bank details and any sanctions flag all require the creator to act. An agent can detect the state, send the reminder and route the exception. It cannot complete any of the four.

What is a master vendor of record?

A master vendor of record is a single compliant vendor that a brand or platform onboards once, which then pays every individual creator on its behalf. The vendor of record carries the onboarding, KYC, tax collection and year-end filing obligation for each payee, so the brand's procurement system sees one vendor instead of hundreds.

What changed about 1099-NEC reporting in 2026?

The US 1099-NEC filing threshold rose to $2,000 for payments made in 2026, up from $600 (IRS, 2026). An agent paying the same creator across several campaigns has to track cumulative totals per legal entity per calendar year against that figure. Confirm the current rule with your tax advisor before encoding it anywhere.

Should an AI agent release payouts without human approval?

Most teams decide no. 93% of payouts on the Lumanu network still require a human approval before processing (Lumanu, 2026). That approval runs in scheduled batches rather than payment by payment (Lumanu, 2026). The working pattern is an agent creating, matching and queueing payables continuously, with a person releasing the queue weekly. Pick an API that treats the payable as an object you can approve separately from funding it.

How long does it take to onboard a creator for payouts?

The median onboarding time for a US-based creator on Lumanu is 2 minutes 38 seconds (Lumanu, 2026). Onboarding time varies by model more than by vendor. Where the payouts provider acts as master vendor of record, a creator completes one identity verification and one tax form for the whole network, then carries it to every platform on that network. Where the platform owns onboarding, as on Stripe Connect, each creator onboards separately for each platform, and Connect Express takes roughly 17 API steps between a new creator and a settled payment.

Sources

All figures checked 23 October 2026. Pricing and coverage in this category change often, so confirm against the website.

• Stripe, Cross-border payouts to recipients

• Stripe, Model Context Protocol (MCP)

• Trolley, Pricing

• Dots, Payouts API pricing

• Airwallex, US tax reporting

• Airwallex, Bank account payout network

• Airwallex, Plans and pricing

• Lumanu, Lumanu vs. Stripe Connect: a technical evaluation

• Juniper Research, Agentic Commerce Market 2026-2031

• commercetools, AI and agentic commerce statistics 2026, for the Bain and Gartner figures

• Agentic commerce statistics and benchmarks, for the Morgan Stanley and eMarketer figures

• Docsumo, AI in finance statistics, for the Gartner and Ardent Partners AP figures

• ACARP, AP automation trends 2026

• Digital Commerce 360, Google launches payments protocol for AI commerce