Search creators⌘K
  1. Home
  2. Creators
  3. Richard Crone

Richard Crone

Richard Crone analyzes how AI agents could change shopping, payments and banking. His work focuses on secure agent authorization, payment verification and attributing sales to AI recommendations.

21.6K followersAgentic commerceAgentic paymentsBased on 8 posts · latest Oct 2026
LinkedIn

At a glance

They are most useful for frameworks on secure agent authorization, payment verification and attributing sales to AI recommendations.

Best for

A payments platform building an agentic commerce strategy and needing verification and attribution frameworks.

Not for

A consumer packaged goods brand seeking short-form video, lifestyle content, and high-volume reach.

Key takeaways

  • Register agents through a Secure Verification Gateway and Repository.
  • Extend KYC to Know Your Agent, and roll out in two phases.
  • Sell verified intent as a revenue line, not just a feature.

Check first: Confirm scope, deliverables, fees, disclosure terms, and that figures are estimates.

Main ideas
The one who enrolls the customer is the one who controls the relationship · Register agents through a Secure Verification Gateway and Repository · Extend KYC to Know Your Agent, and roll out in two phases
Audience
21,561 LinkedIn followers
Read first
Claude for Commerce and the case for Committed CPA
Sources for this section

What they are known for

Richard Crone writes about how AI agents could change shopping, payments and banking.

  • His posts argue that businesses should let customers use their preferred agents while retaining control over who is authorized, what the agent may do, and how a completed sale is verified.
  • In his proposed model, an agent shapes purchase intent, a merchant keeps the customer and order record, and payment evidence helps confirm the outcome.
  • He develops this argument through examples involving retailers, banks, payment networks and AI companies, including a proposal for charging only when verified, incremental sales occur.
  • Readers interested in agentic commerce can follow his work for a connected view of its security, attribution and business-model questions.

Crone’s distinctive contribution in this material is to connect agent identity and permission to the economics of a transaction.

  • Rather than treating an API connection as sufficient, he proposes registering the customer’s chosen agent, setting limits and revocation rules, and keeping an auditable link from authorization to item and receipt.
  • His Claude for Commerce post makes the case concrete: it distinguishes the AI’s role in forming intent, the merchant’s role as record-holder, and payment’s role as evidence, then proposes a fee earned only after an eligible sale is verified.
  • Across posts on Walmart, Google, banks and payment networks, he applies that framework to different strategic choices.
  • His forecasts and market-size figures are his own estimates and scenarios in the reviewed posts, not established outcomes; the posts also show exceptions to a simple “open the door” thesis, including the need for customer review and release before autonomous execution.
Sources for this section

Ideas and priorities

Richard Crone's posts argue that agentic commerce — shopping and banking done through personal AI agents — will be decided by who enrolls the customer and holds the verified record of that relationship.

Read more

The recurring claim, which Crone states as "Crone's Rule," is that the one who enrolls is the one who controls, and that anyone who is not the system of record for customer intent and outcomes is "always struggling for relevancy."

  • From that starting point, Crone proposes a specific architecture for registering and verifying agents, a two-phase rollout that starts with customer-reviewed payments, a cost argument for accepting the customer's own AI, and several ways to charge for verified intent rather than impressions.
  • The work is explicitly scenario-driven: figures are labeled Crone Consulting independent estimates, and each post invites readers to challenge the thesis in comments.

The one who enrolls the customer is the one who controls the relationship

Crone applies a single rule across very different businesses: whichever party registers the customer and their chosen agent keeps discovery, checkout and the customer relationship, while everyone else competes for relevance.

Read more

The posts assign roles to make the point — Claude as the "System of Intent," the merchant as the "System of Record," and payment as the "System of Proof." Crone recommends capturing the registered agent in the CRM beside KYC, with permissions, expiry, revocation and attribution, because that link carries delegated authority and context that an email address or phone number does not.

In the analysis of Anthropic's Claude for Commerce, Crone writes that Claude becomes the system of intent, the merchant remains the system of record, and payment becomes the system of proof, with the customer's registered agent treated as the asset that preserves the merchant's franchise value.

In a later post on the Personal Agent Protocol, Crone adds a caveat: the protocol "alone doesn't explain returns," and banks that did not back it outperformed those that did, so enrollment is not offered as a complete explanation of market outcomes.

Read original · Original 2 · Original 3 · Original 4

Register agents through a Secure Verification Gateway and Repository

The most repeated concrete recommendation is an architecture Crone calls a Secure Verification Gateway and Repository.

Read more

The gateway authenticates the customer, verifies the chosen agent's identity and delegated authority, then enforces consent, spending limits, approvals and revocation.

  • The repository links the customer, the authorized agent, permissions and verified outcomes so the operator has an auditable record for attribution and data rights.
  • Crone frames this as the alternative both to bot blocking and to relying on Model Context Protocol connectivity alone, which they say reduces a merchant's digital assets to a "fulfillment pipe" while the AI model controls discovery and checkout.

Crone compares registering an agent to recording an email address or mobile number, and to retailers eliminating guest checkout, arguing the agent relationship should be registered as a digital asset in the CRM before holiday traffic rather than blocked at the door.

Crone acknowledges that no current standard delivers the entire chain — from discovery and identity through delegated authority, payment, receipt, refund, dispute and incrementality — so the gateway is presented as an assembly of existing pieces, not a shipped product.

Read original · Original 2 · Original 3 · Original 4 · Original 5

Extend KYC to Know Your Agent, and roll out in two phases

Crone proposes Know Your Agent: verified agent identity, its developer, permissions, data rights, expiry, revocation and attribution, bound to the customer's existing contact credentials.

Read more

That binding enables out-of-band multi-factor authentication and a consumer "Review and Release" step before a purchase completes.

  • The recommendation maps to a two-phase plan: in Phase 1, a customer approves the specific purchase; in Phase 2, agent-to-agent execution runs autonomously.
  • Crone treats the registered human-to-agent link as the fraud defense as well as the commercial record.

In the pre-Black Friday post, Crone describes multi-factor authentication with Review and Release as Phase 1 and autonomous agent-to-agent execution as Phase 2, and ties both to registering the customer's preferred agent in the bank's or retailer's own system of record.

Read original · Original 2 · Original 3 · Original 4

Accept the customer's own AI: it shifts deliberation costs to their provider

Crone argues that hosts should let customers bring their own AI rather than build isolated assistants.

Read more

The reasoning is economic: the customer's model provider absorbs the cost of deliberation, while the host keeps registration, security and execution — and keeps the attribution trail.

  • Crone models token costs and compares them with the thin margins of retail and banking, concluding that duplicating the customer's conversational interface is a bad trade.
  • The point reframes accepting third-party agents as a compute-arbitrage decision, not only a control decision.

Crone cites Meta Muse reportedly offering up to 100 million free tokens per week, models banking sessions at 15,000 to 50,000 tokens, and notes that at a billion sessions every $0.10 per session is $100 million. For Walmart, Crone estimates internal AI compute and token costs could consume about 111% of a 3% retail profit pool even if Walmart captured every projected off-site agentic sale.

Read original · Original 2 · Original 3 · Original 4 · Original 5

Sell verified intent as a revenue line, not just a feature

Crone prices several ways to monetize intent, all tied to a verified sale rather than exposure.

Read more

Committed Cost per Acquisition charges a seller-committed fee that the AI earns only when a signed trail — intent, recommendation, approval, SKU, tokenized payment, receipt — validates an eligible sale, with holdouts proving incrementality.

  • Related lines are Consented Intent Scoring and Cost Per Lost Sale, which sells post-purchase insight into why non-winners lost.
  • A second version of the idea sells intent validation to payment networks as a pre-authorization screen that checks a purchase against the customer's signed mandate.

Crone models per-user annual revenue rising from $33.60 today to $121.50–$243.00 for Committed Cost per Acquisition, $24.00–$60.00 for Consented Intent Scoring and $28.35–$45.00 for Cost Per Lost Sale. Elsewhere, Crone estimates 10 to 25 cents per intent check across 51 billion projected agentic transactions as a $5.1 billion to $12.75 billion annual business.

Crone labels all of these figures Crone Consulting independent estimates rather than reported results, and the Mastercard figures explicitly require assumed fraud and false-decline savings, so the numbers are inputs to re-run rather than outcomes to cite.

Read original · Original 2 · Original 3 · Original 4

The per-token model has a ceiling; gain-sharing on transactions does not

Crone contrasts two revenue models.

Read more

Anthropic's business, Crone notes, is mostly per-token compute fees to businesses, which Crone describes as a "fee-per-ping" model with an inherent revenue ceiling.

  • Google's is described as consumer-driven and value-based, taking a share of transactions and consumer savings, which scales with commerce rather than compute.
  • Crone argues the difference decides which AI platforms can fund agentic commerce organically, and proposes three paid services built on that consumer model.

Crone sketches Google Pay with a tokenized payment and an "Intent Receipt" binding mandate, SKU, order and refund status, and models $35 billion to $79 billion in new annual revenue at 250 million users, arguing the path from Search to AI Overview to Gemini to Spark to Google Pay is constructive graduation rather than cannibalization.

Read original · Original 2

Blocking agents is expensive, and blocked agent traffic reroutes rather than bounces

Crone argues that turning away personal agents repeats a mistake incumbents already made with wallets.

Read more

The mechanical point is that a blocked agent does not simply disappear: it is programmatically rerouted to the next available merchant, so the sale goes elsewhere.

  • Crone also argues that failing to register the customer's preferred agent strips lifetime value and forces reacquisition spending.
  • The recommended response is governed registration — access with identity, permissions and limits — rather than an open door or a wall.

Crone cites Walmart's decade-long block on Apple Pay, Google Pay and contactless payments as an estimated $110 billion-plus in lost sales, models $4 billion to $21 billion of Walmart exposure in 2026 holiday sales from blocking personal agents, and puts the cost of failing to register a customer's agent at about $1,298 in lost customer lifetime value plus roughly $600 to reacquire that customer.

Crone notes firsthand mystery shopping of Walmart's Sparky and Alexa for Shopping that showed both defaulting to off-site rerouting when they did not carry the item, which is offered as evidence that the rerouting is real rather than hypothetical.

Read original · Original 2 · Original 3 · Original 4

Attribution is the design problem: payment proves what was authorized and settled

Crone treats proof of what happened as the core requirement of agentic commerce.

Read more

A tokenized payment plus an intent receipt binds mandate, SKU, order and refund status, replacing cookies and identity trackers that can show exposure but not causation.

  • Holdouts establish incrementality, and attribution must be visible: merchants need to see which agent earned credit.
  • Crone also reports that the Mastercard and OpenAI work rejects one-time virtual card numbers in favor of agentic tokenization, on the reasoning that preserving the card does not create intent or grant control of the AI model's private data.

In the Claude for Commerce post, Crone describes the validating trail as signed intent, recommendation, approval, SKU, tokenized payment and receipt, with holdouts proving incrementality. In the Mastercard analysis, Crone cites Jack Forestell of Visa, who states merchants must retain the customer relationship, visibility and control, and that attribution cannot be a black box.

Read original · Original 2 · Original 3 · Original 4

How Crone works: charted scenarios, named sources and an open invitation to challenge

The posts follow a consistent format: a long structured argument broken into numbered mechanisms, dollar ranges and per-transaction fee models, a reference to an accompanying chart, and a closing invitation to challenge the thesis in comments for what Crone calls a quantified, analytically grounded response.

Read more

Each carries a disclaimer that figures are independent estimates with no company guidance, sponsorship or conflicts. Crone also reports firsthand mystery shopping and names human sources, separating their views from Crone's own conclusions.

Crone cites Lexi Sydow and Ian Simpson of Sensor Tower on AI chatbot usage shares and retention, and Steve Klebe, formerly of Cybersource, on that company's history of charging $0.25 and later $0.10 for a standalone fraud screen before sending an authorization to the payment networks. Those views are reported as the named individuals' accounts, distinct from Crone's own estimates.

Read original · Original 2 · Original 3 · Original 4 · Original 5 · Original 6 · Original 7

Sources for this section

Start with their work

Claude for Commerce and the case for Committed CPA

This is the clearest entry to Richard Crone's core vocabulary and to the question of how agentic commerce could pay for itself without advertising bias.

Read more

Richard Crone walks through Anthropic's Claude for Commerce as an example of LLMs monetizing retail without ads.

  • The post separates roles: Claude as System of Intent, the merchant as System of Record, and payment as System of Proof.
  • It proposes Committed Cost per Acquisition/Action, where a fee is earned only after a signed intent, recommendation, approval, SKU, tokenized payment, and receipt trail validate an eligible sale.
  • Holdouts are used to establish incrementality, and the post includes revenue math from a McKinsey 2030 range.

For brands planning a campaign

A payments platform should test an attribution model tied to signed intent and a verified sale, not to exposure or last-click cookies.

Agent-as-a-Wallet and the Secure Verification Gateway

This answers why enrolling the customer and registering the preferred agent matters before any agentic checkout.

Read more

Richard Crone describes ChatGPT Voice and personal agents as wallets, arguing that "payment always follows something."

  • The post warns that relying on Model Context Protocol connectivity alone can reduce a merchant's digital assets to a fulfillment pipe while the LLM controls discovery and checkout.
  • It proposes a Secure Verification Gateway and Repository that authenticates the customer, verifies the agent's identity and delegated authority, and enforces consent, spending limits, approvals, and revocation.
  • The repository links the customer, authorized agent, permissions, and verified outcomes.

For brands planning a campaign

Build the enrollment and identity layer first; do not assume an API connection creates a commercial System of Record.

Holiday 2026 and the missing standard for Agent-as-a-Wallet

This gives the time-bound stakes and the clearest gap analysis for agentic commerce before a major shopping season.

Read more

Richard Crone forecasts that Meta Muse, ChatGPT, Gemini, and other LLMs will be the starting point for roughly 18% to 32% of holiday sales by year-end 2026.

  • The post argues that only about 25% of retailers and less than 1% of financial institutions can accept a ping from a bot, and that no current standard delivers the full chain from discovery and identity through delegated authority, tender selection, payment, SKU receipt, refund, dispute, and incrementality.
  • It points to Google's search and Shopping Graph position, notes Poppy as a draft protocol, and warns that a bot blocker can block the highest-intent buyer.

For brands planning a campaign

Map which links of the agentic chain are covered by existing partners and prioritize governed agent registration before holiday traffic.

Why blocking personal agents is not like blocking Apple Pay

This is the strongest argument for access over walls and explains why agent blocking is an economic decision, not a technical preference.

Read more

Richard Crone forecasts personal agent enrollment rising from about 14% of LLM monthly active users by year-end 2026 to about 68% by 2032, partly because large platforms can activate agents without acquiring new users.

  • The post asks why banks and retailers deploy bot blockers while accepting paid pings from open banking aggregators.
  • It cites Walmart's estimated losses from blocking Apple Pay and contactless payments, and argues that blocking agents can strip customer lifetime value and force reacquisition spending.
  • It recommends Know Your Agent registration with out-of-band multi-factor authentication.

For brands planning a campaign

Quantify the cost of blocking against registering the customer's preferred agent, and build KYA plus out-of-band review-and-release into the checkout path.

Walmart, Bank of America, and the Poppy question

This connects named launch partners to the strategic tradeoffs behind accepting personal agents.

Read more

Richard Crone asks why Walmart with Sparky and Bank of America with Erica would back Meta Muse and Sierra's Personal Agent Protocol, known as Poppy, while bank cores and digital platforms stay off the announced roster.

  • The post shows a valuation divide since ChatGPT launched and gives three economic reasons to open the door: escaping the walled garden trap, offloading AI compute costs, and preserving attribution and revenue-share.
  • It points to a Rocket Mortgages demonstration where a Meta Muse agent and Rocket's agent worked toward mortgage preapproval after customer authorization.

For brands planning a campaign

Evaluate an open-agent strategy against a walled garden, and register the verified human-agent relationship as a durable CRM asset.

Mastercard-OpenAI and the market for verified intent

This explains how verified intent becomes a saleable pre-authorization product rather than another card pre-auth.

Read more

Richard Crone treats the Mastercard and OpenAI partnership as validation of a greenfield opportunity worth at least $5.1 billion to $12.75 billion annually for selling verified intent before a transaction reaches the payment network.

  • The post argues that payment networks are not the System of Record for intent signals, buyer reasoning, or SKU-level details.
  • It describes a paid intent-validation service that checks whether a purchase matches the customer's signed intended mandate, and gives a range of 10 to 25 cents per check across 51 billion projected agentic transactions.
  • It also urges financial institutions to register preferred LLMs and personal agents in the central information file with KYC, permissions, expiry, and revocation.

For brands planning a campaign

A payments platform can build an intent-validation and fraud-reduction offer, then negotiate data rights and revenue-share with issuers and acquirers.

Google Pay, Gemini, and a revenue model beyond ads

This is the most detailed revenue math for turning agentic intent into paid outcomes while keeping the experience organic.

Read more

Richard Crone contrasts Anthropic's B2B per-token compute model with Google's consumer value-based model, then proposes three greenfield services around Gemini, the Spark personal agent, and Google Pay: Committed Cost per Acquisition, Consented Intent Scoring, and Cost Per Lost Sale.

  • The post describes a Google Pay tokenized payment plus Intent Receipt that binds mandate, SKU, order, and refund status.
  • It models $35 billion to $79 billion in new annual revenue at 250 million users and argues that Search to AI Overview to Gemini to Spark to Google Pay can be constructive graduation rather than cannibalization.

For brands planning a campaign

If a platform has consumer distribution, model committed outcomes, intent scoring, and post-purchase lost-sale insights instead of relying only on ads.

Digital banking platforms and the Agent-as-a-Wallet threat

This applies the agent-as-a-wallet thesis directly to banking software and explains which vendors face disintermediation.

Read more

Richard Crone argues that personal banking agents such as Meta Muse, Instinct, and ChatGPT Finances could erode the market caps of digital banking platforms because static dropdown menus are being replaced by conversational agents.

  • The post says about 60% of consumers now start their financial journey on a preferred LLM, notes that every major LLM has led banking services with a Plaid integration, and points to Chase charging for screen scraping pings.
  • It sees a vertical re-integration opportunity for core processors using services such as Fiserv AllData Connect and agentOS plus a Secure Verification Gateway and Repository.

For brands planning a campaign

A banking technology provider should reposition as an agent gateway and registry, or risk being bypassed by the consumer's preferred agent.

Walmart's Agent Gateway and the 2026 holiday checkout

This turns the strategic argument into an operational holiday checklist for a large retailer.

Read more

Richard Crone explains that Walmart will accept customers' preferred LLMs and personal agents before Black Friday because Walmart does not allow guest checkout.

  • The post calls check-in the new checkout, estimates that blocking personal agents could cost Walmart $4 billion to $21 billion in 2026 holiday sales, and argues that internal AI compute and token costs would consume about 111% of a 3% retail profit pool.
  • It describes Walmart's Agent Gateway linking agent profiles with MCP-based access to inventory and permissions, and warns that anonymous agent checkout would rupture the customer-to-agent-to-basket-to-payment-to-SKU attribution trail.

For brands planning a campaign

A retail platform should implement an agent gateway with customer identity, agent registration, and attribution before the holiday season.

Amex Intent Intelligence and selling fraud reduction to networks

This links intent data to fraud reduction, startup opportunity, and payment-network M&A.

Read more

Richard Crone asks whether American Express's published Intent Intelligence framework accidentally defines a new product line for hyperscalers and personal agents.

  • The post argues that if LLMs control the System of Intent, they can charge for access to that signal as a fraud-reduction tool.
  • It cites Steve Klebe's experience at Cybersource, where a standalone proprietary fraud screen was charged before pinging branded payment networks, and applies that pattern to 51 billion projected agentic transactions to estimate a $5.1 billion to $12.7 billion verification business.
  • It also names agentic payment startups as potential verification providers and raises M&A implications for PayPal and others.

For brands planning a campaign

A payments platform can sell an intent-based fraud screen to networks and LLMs, positioning itself as a verification layer before authorization.

Sources for this section

Topics and approach

Posts cited for each topic
The competitive map Crone tracks7
How Crone works: charted scenarios, named sources and public challenge7
The System of Record argument: enrollment decides who controls the customer5
Secure Verification Gateway and Repository: the recurring architecture proposal5
Bring Your Own AI: the cost argument for accepting the customer's model5
Know Your Agent and a two-phase rollout4
Selling verified intent as a new revenue line4
Blocking agents as the expensive default4
Attribution: payment as proof of what was authorized and settled4

The System of Record argument: enrollment decides who controls the customer

Crone returns in almost every post to a rule they state as "Crone's Rule": the one who enrolls the customer is the one who controls.

Read more

The application varies — Claude as "System of Intent," the merchant as "System of Record," payment as "System of Proof" — but the conclusion is stable: whoever holds the verified human-to-agent link keeps discovery, checkout and the customer relationship, and anyone who is not that record is "always struggling for relevancy." They recommend capturing the registered agent in the CRM beside KYC, with permissions, expiry, revocation and attribution.

Crone applies the same rule to four different parties across the corpus (Anthropic, Google, banks and cores, and payment networks), which is useful for seeing how the same principle maps onto different business models.

In the post on Walmart, Bank of America and the Personal Agent Protocol, Crone warns that the protocol "alone doesn't explain returns" and notes that non-PAP banks outperformed PAP banks — a caveat against treating enrollment as a complete explanation of market outcomes.

For brands planning a campaign

This is the cleanest single sentence a payments platform can take from the corpus. Crone's framing gives a client a way to argue that owning agent enrollment and the resulting record — not just processing a transaction — is the position worth building for.

Examples: Source 1 · Source 2 · Source 3 · Source 4 · Source 5

Secure Verification Gateway and Repository: the recurring architecture proposal

The most repeated concrete recommendation is a Secure Verification Gateway and Repository.

Read more

The gateway authenticates the customer, verifies the chosen agent's identity and delegated authority, then enforces consent, spending limits, approvals and revocation.

  • The repository links the customer, the authorized agent, permissions and verified outcomes, giving the operator an auditable record for attribution and data rights.
  • Crone presents this as the alternative both to relying on Model Context Protocol connectivity alone, which they say turns digital assets into a "fulfillment pipe," and to bot blocking.

Crone uses analogies to make the case concrete — registering an agent the way a retailer records an email address or mobile number, and the third-party delivery aggregator risk merchants already accept.

In the pre-Black Friday post, Crone states that no current standard delivers the whole chain (discovery through dispute and incrementality), so the gateway is a proposed assembly of existing pieces, not a shipped product.

For brands planning a campaign

For a payments platform, this is a named, testable architecture blueprint: identity verification, delegated authority, consent and limits, revocation, and an auditable outcome record. It is the component Crone says every other party in the chain is missing.

Examples: Source 1 · Source 2 · Source 3 · Source 4 · Source 5

Know Your Agent and a two-phase rollout

Crone proposes extending KYC to Know Your Agent: verified agent identity, developer, permissions, data rights, expiry, revocation and attribution.

Read more

Binding agent registration to existing cell or email credentials enables out-of-band multi-factor authentication and a consumer "Review and Release" step. That maps to a two-phase plan — Phase 1 requires multi-factor authentication and customer release before a purchase completes; Phase 2 lets agent-to-agent execution run autonomously.

For brands planning a campaign

This gives a payments platform a staged adoption path to propose to clients rather than an all-or-nothing switch to autonomous agent payments, and a concrete answer to the fraud question that consumer-scale agentic checkout raises.

Examples: Source 1 · Source 2 · Source 3 · Source 4

Bring Your Own AI: the cost argument for accepting the customer's model

A recurring economic claim: hosts that accept the customer's own LLM offload deliberation costs while keeping registration and execution.

Read more

Crone cites Meta Muse reportedly offering up to 100 million free tokens per week, models banking sessions at 15,000 to 50,000 tokens, and notes that at a billion sessions every $0.10 per session is $100M. For Walmart they argue internal AI compute and token costs could consume about 111% of a 3% retail profit pool even if Walmart captured every projected off-site agentic sale.

For brands planning a campaign

This is the cost model a payments platform can re-run against its own clients. It reframes accepting third-party agents as a compute-arbitrage decision, not only a control decision.

Examples: Source 1 · Source 2 · Source 3 · Source 4 · Source 5

Selling verified intent as a new revenue line

Crone prices several ways to monetize intent.

Read more

Committed Cost per Acquisition charges a seller-committed fee that the LLM earns only when a signed trail — intent, recommendation, approval, SKU, tokenized payment, receipt — validates an eligible sale, with holdouts proving incrementality.

  • Other named lines are Consented Intent Scoring and Cost Per Lost Sale, with per-user figures rising from $33.60 today to $121.50-$243.00, $24.00-$60.00 and $28.35-$45.00 respectively.
  • Elsewhere they frame intent validation as a pre-authorization screen sold to payment networks, citing Cybersource charging $0.25 then $0.10 for a standalone fraud screen before an authorization ping, and estimate $5.1B-$12.75B in annual fees at 10 to 25 cents per check across 51 billion projected agentic transactions.

Crone labels these Crone Consulting independent estimates, not reported company results, and the Mastercard figures are explicitly scenario fees requiring assumed fraud and false-decline savings.

For brands planning a campaign

This is the monetization menu a payments platform would actually be evaluating, and the mechanism is consistent: the payment rail proves completion, holdouts prove incrementality, and the fee attaches to verified net-new sales rather than impressions.

Examples: Source 1 · Source 2 · Source 3 · Source 4

Blocking agents as the expensive default

Crone argues that refusing personal agents repeats a mistake incumbents already made with wallets.

Read more

They cite Walmart's decade-long block on Apple Pay, Google Pay and contactless as an estimated $110B+ in lost sales, and say banks and credit unions that blocked wallet payments saw 15% fewer new accounts, 15% higher attrition and a customer base 30% older.

  • Failing to register a customer's preferred agent is put at about $1,298 in lost customer lifetime value plus roughly $600 to reacquire the customer.
  • A key mechanical point: blocked agentic traffic does not bounce, it is programmatically rerouted to the next available merchant, with Walmart exposure modeled at $4B-$21B in 2026 holiday sales.

Crone calls these modeled exposures, not reported losses, and the Walmart and bank figures are their own scenarios.

For brands planning a campaign

This supplies the risk narrative a payments platform can bring to hesitant merchants and banks, including the argument that bot blockers built for scraping will stop the highest-intent buyers at the door.

Examples: Source 1 · Source 2 · Source 3 · Source 4

Attribution: payment as proof of what was authorized and settled

Crone treats attribution as the design problem underneath agentic commerce.

Read more

A tokenized payment plus an intent receipt binds mandate, SKU, order and refund status, replacing cookies and identity trackers that prove exposure but not causation.

  • Holdouts establish incrementality, and attribution must be visible rather than a black box, with merchants able to see which agent earned credit — a point Crone attributes to Jack Forestell of Visa.
  • In the Mastercard analysis they also describe rejecting one-time virtual card numbers in favor of agentic tokenization, since preserving the card does not create intent or grant control of the LLM and its private data.

For brands planning a campaign

These are concrete requirements a payments platform can put into a product spec: signed mandate, tokenized execution, receipt-level evidence, holdout testing, and a visible attribution ledger for merchants.

Examples: Source 1 · Source 2 · Source 3 · Source 4

The competitive map Crone tracks

The posts double as a running map of who is moving.

Read more

Google is repeatedly placed in pole position: Search as the start of around 35% of online shopping journeys, more than a billion Gemini monthly users, a Shopping Graph of over 60 billion product detail pages with more than 2 billion refreshed hourly, Universal Cart, and Google Pay or Wallet.

  • PayPal is framed as an Agent-as-a-Wallet bridge across 439 million monthly users and $1.79 trillion in total payment volume via Store Sync.
  • Also covered: Shopify Agentic Storefronts, Target, Best Buy, Walmart's Sparky and Agent Gateway, Anthropic's Claude for Commerce and its shopping and merchant agent scaffolding, the Mastercard and OpenAI Agent Pay and Verifiable Intent work, Visa IntelligentCommerce, Amex Intent Intelligence, and a Rocket Mortgages demonstration of a Meta Muse agent working with Rocket's agent toward a mortgage preapproval.

For brands planning a campaign

This is a ready-made benchmark list for a client's competitive review, and it shows where Crone thinks the gaps are — particularly for banks and core processors that are absent from the announced rosters.

Examples: Source 1 · Source 2 · Source 3 · Source 4 · Source 5 · Source 6 · Source 7

How Crone works: charted scenarios, named sources and public challenge

The format is consistent: long structured posts that break a thesis into numbered mechanisms, attach dollar ranges and per-transaction fee models, reference an accompanying chart, and close by inviting readers to challenge the thesis in comments for a "quantified, analytically grounded" response.

Read more

Each post carries a disclaimer that the figures are Crone Consulting independent estimates with no company guidance, sponsorship or conflicts. Crone also reports firsthand mystery shopping of Amazon "Buy for Me," Walmart Sparky and Alexa for Shopping, and names sources such as Lexi Sydow and Ian Simpson of Sensor Tower, Steve Klebe formerly of Cybersource, and Jack Forestell of Visa.

For brands planning a campaign

A brand should treat this as thesis-driven, model-heavy work: strong on frameworks, market mechanics and quantified scenarios, but the numbers are inputs to re-run rather than reported outcomes. The public comment invitation also means Crone engages directly with counterarguments.

Examples: Source 1 · Source 2 · Source 3 · Source 4 · Source 5 · Source 6 · Source 7

Sources for this section

Brands and businesses

The reviewed posts do not document sponsorships, affiliate deals, client engagements or investments with the companies Crone analyzes.

Read more

They repeatedly carry a Crone Consulting LLC disclaimer and state no sponsorship or conflicts of interest involving the companies analyzed. Crone Consulting LLC is the one recurring business name; the posts do not say whether Crone owns or works for it.

Crone Consulting LLC

Disclosed partnership

Crone Consulting LLC is credited with the independent estimates, scenarios and disclaimers in these posts.

Read more

The posts offer a quantified custom response via comments, but they do not state Richard Crone's ownership or employment role at the firm.

Original disclosure

Crone Consulting LLC independent estimates & scenarios, not company guidance. No sponsorship or conflicts of interest involving the companies analyzed.

View example

Sources for this section

Topics and similar creators

Richard Crone writes long, charted LinkedIn posts about how AI agents will reshape shopping and banking.

Read more

The through-line is a practical question: who registers the customer and their chosen agent, and who holds the verified record that proves what was authorized and paid?

  • A good way to explore the work is to start with the recurring architecture argument — the Secure Verification Gateway and Repository, Know Your Agent, and the two-phase rollout — then read the monetization posts on Committed Cost per Acquisition, Consented Intent Scoring, and Cost Per Lost Sale.
  • The competitive posts on Google, Walmart, PayPal, Stripe, Mastercard, Visa, and Amex are useful as a map of who is moving, and the pre-holiday posts show how Crone applies the same framework to retail and banking.
  • Follow the tags below for agentic commerce, payment attribution, agent identity, digital wallets, and scenario modeling.
  • If you want another creator to follow, the closest comparators in this material write on agentic commerce infrastructure, consumer trust, or AI agent security, but each takes a different angle: Moock from inside a payments platform, Willard from consumer trust and liability, and Andrade from cybersecurity governance.
Agentic commerce Agentic payments Payment attribution and verification Agent identity and authorization Know Your Agent (KYA) System of record strategy Digital wallets Retail and banking strategy Charted scenario modeling Long-form analysis posts Payments and fintech executives Retail and banking strategy teams

Stephen Moock

Moock writes about the same shift Crone tracks — commerce moving from search-and-scroll to ask-and-receive, with AI agents becoming a distribution channel.

Read more

Both treat catalog discoverability, agent-ready checkout, payment processing, and fraud protection as the infrastructure layer for agentic commerce.

Moock writes from inside a payments infrastructure provider and focuses on the practical integration problem: connecting a catalog once, managing agent channels, and getting merchants agent-ready without bespoke builds. Crone writes independent market scenarios and quantified revenue models, with more emphasis on who owns the customer record and how intent is monetized.

Read original · Original 2 · Original 3 · Original 4

Jill Willard

Willard also follows agentic commerce adoption and argues that trust, not checkout mechanics, decides whether consumers let agents spend on their behalf.

Read more

Both point to liability protection and consumer confidence as adoption drivers, and both compare the moment to earlier shifts in card and ecommerce trust.

Willard's angle is consumer trust and the protection story, using historical analogies about credit cards and ecommerce to explain why a liability guarantee could unlock agent spending. Crone's angle is enrollment, the system of record, and the commercial architecture for registering and verifying agents.

Read original · Original 2 · Original 3 · Original 4

Paolo Andrade

Andrade writes about AI agent identity, credentials, authorization, least privilege, logging, and extending Zero Trust to autonomous identities.

Read more

That overlaps with Crone's calls for Know Your Agent, permissions, revocation, and an auditable record of what an agent was authorized to do.

Andrade frames the problem mainly as cybersecurity governance and risk control for agentic AI. Crone frames the same registration and verification needs as commercial infrastructure — how a merchant or bank keeps the customer relationship, proves attribution, and monetizes verified intent.

Read original · Original 2 · Original 3 · Original 4 · Original 5

Sources for this section

Audience

Richard Crone's audience evidence here is one account-level figure: 21,561 LinkedIn followers, observed 11 October 2026.

Read more

Everything else supplied is post text, which shows what readers are asked to read but not who is reading.

  • For a payments platform exploring agentic commerce, that sets the placement decision: Crone is a way to reach a self-selected LinkedIn following of payments, retail banking and commerce professionals, not a way to buy verified coverage of a named job-title segment.
  • The posts indicate the audience being addressed.
  • They are long, chart-led analyses built on cost models, named company examples (PayPal, Visa, Mastercard, Google, Walmart) and Crone's own framing, each closing with an invitation to comment or request a quantified response.
  • That format rewards readers who will work through numbers and strategy arguments, and it screens out readers wanting short updates.
  • Two dated posts in the supplied set sit about four weeks apart (3 September and 30 September 2026), which shows a regular rhythm across that window but is not a reliable posting frequency.
  • Measured audience composition is not available.
  • The follower figure says how many accounts follow the profile; it does not establish geography, employer, occupation, seniority, or what share of followers buy payments technology.
  • The posts' readability for a strategy-minded reader is a content-appeal observation, not evidence of who actually follows the account.
  • Before committing budget, ask for post-level results — impressions, comments and profile visits — on recent posts closest to your brief (agent payment verification, merchant attribution), plus any audience survey covering industry, company size and job function.
  • Follower count alone will not tell you whether the readership overlaps your target buyer.

LinkedIn followers

21,561

LinkedIn profile account record · 2026-10-11

Sources for this section

Partnership options

Richard Crone's reviewed posts do not describe a sponsorship, paid-placement, or creator-partnership offer.

Read more

Every post that names companies carries an independence disclaimer attributed to Crone Consulting LLC — for example, "Crone Consulting LLC independent estimates, no public disclosure by companies analyzed" and "No sponsorship or conflicts of interest involving the companies analyzed."

  • That is a statement about how the analysis was produced, not a published sponsor policy, and it gives a brand no rate, format, or booking terms to plan against.
  • The only engagement the posts invite is a reply: several close by asking readers to comment or ask a question to receive a "quantified, analytically grounded custom response."
  • That is a public discussion prompt, not a partnership or advertising inquiry route.
  • Practical consequence for a buyer: nothing in the reviewed material supports planning a sponsored post, affiliate placement, or paid content integration with Crone.
  • If a payments platform wants his analysis applied to its own agentic commerce or agent-verification problem, the implied path is a direct consulting or advisory engagement through Crone Consulting LLC, and that is an inference from how the work is labeled rather than a documented commercial offer.
  • Confirm scope, deliverables, fees, and any disclosure requirements directly, and do not assume that a company mentioned favourably in a post has any commercial relationship.
  • This section records a documented absence of partnership formats in the reviewed material; it does not establish that Crone never accepts sponsorship or consulting work.
Sources for this section

Campaign fit

A campaign to shortlist

A payments platform is building an agentic commerce strategy and wants a framework for secure agent verification and payment attribution when shopping runs through LLMs and personal agents.

Read more

Reasons

  • The recurring proposal is a Secure Verification Gateway and Repository: the gateway authenticates the customer, verifies the chosen agent's identity and delegated authority, and enforces consent, spending limits, approvals and revocation; the repository links customer, agent, permissions and verified outcomes so the operator keeps an auditable record. That is a verification framework a payments platform can evaluate immediately.
  • Attribution is treated as the design problem underneath the architecture, not an afterthought. A tokenized payment plus an intent receipt binds mandate, SKU, order and refund status; holdouts establish incrementality; and Crone argues merchants must see which agent earned credit rather than accept a black box.
  • Crone extends KYC to Know Your Agent and proposes a two-phase rollout: Phase 1 requires out-of-band multi-factor authentication and a consumer review-and-release step; Phase 2 lets agent-to-agent execution run with more autonomy. That gives a platform a staged path instead of a single binary switch to autonomous payments.
  • The commercial model is spelled out in enough detail to argue internally: cost per acquisition earned only on a validated sale trail, intent validation priced as a pre-authorization screen sold to networks, and other named lines for consented intent scoring and lost-sale insight.
  • The format suits a platform evaluating strategy: long, structured, chart-led posts that break a thesis into numbered mechanisms, attach fee and volume ranges, and invite public challenge. Crone answers counterarguments in comments, which is useful for testing a position before committing to it.

Cautions

Every dollar figure in the sourced posts is labelled as Crone Consulting independent estimates or a scenario, not reported company or market results. A platform should re-run the assumptions rather than quote them as findings.

The material describes a proposed assembly of existing pieces, not a shipped standard. Crone states that no current standard covers the full chain from discovery through dispute and incrementality.

The posts are the sourcing for analysis and frameworks. They do not document a published rate card, media kit, or sponsorship format, so the workable commercial route is a direct consulting or advisory engagement, and scope, deliverables, fees and disclosure terms need to be confirmed rather than assumed.

Verdict

Good fit. This is the problem Crone writes about continuously, and the material maps almost one-to-one onto the brief.

When to choose a specialist

A consumer packaged goods brand wants a paid creator campaign for a new consumer product: short-form vertical video and lifestyle content aimed at a general consumer audience aged 18 to 34, booked as fixed-fee posts with usage rights and an expectation of high-volume reach and entertainment value.

Read more

Reasons

  • Format mismatch is the clearest problem. The reviewed posts are long, argument-led, chart-referenced analyses written for payments, banking and retail professionals. Nothing in the material shows short-form video, lifestyle imagery, or entertainment-led content.
  • Audience evidence is one account-level figure: 21,561 LinkedIn followers. There is no supplied breakdown by geography, employer, occupation, seniority, or consumer behaviour, so the readership cannot be shown to overlap a general 18-to-34 consumer audience.
  • There is no documented sponsorship or paid-placement offer. Each post carries an independence disclaimer, and the only engagement the posts invite is a written reply or question about the analysis. A fixed-fee paid post is not something the reviewed material supports.
  • The subject matter would not carry a consumer product launch. The recurring content is agent verification, payment attribution, bank cores, retail media economics and customer lifetime value modelling.
  • The economics point the other way as well. The cost argument Crone makes is that hosts should push deliberation compute to the customer's model provider; that is an infrastructure argument, not a consumer reach argument.

Alternatives note

If the goal is genuinely consumer reach with short-form assets, this creator is the wrong placement and the brief should go to creators with demonstrated consumer video work. If the goal is credibility with payments and retail-banking decision-makers, a different brief is worth writing against this same material.

Verdict

Poor fit. The sourced work is a specialist analysis practice, not a consumer content offer, and none of the material shows the assets or formats this brief needs.

A worked campaign example
Angle

Build the pilot around governed agent enrollment rather than a new checkout feature. Position the platform as the operator of the verification gateway and the repository that holds the verified customer-to-agent relationship, so the platform owns the record that discovery, checkout and settlement all point back to.

Brief

Payments platform, six-week strategy engagement: stand up a verification and attribution framework for LLM-driven shopping, with a defensible commercial model attached.

Gaps to close before booking

No audience composition data was supplied, so a platform targeting specific job functions or regions cannot confirm reach overlap.

No rate card, format sheet, or engagement terms are documented. Scope, deliverables, fees, exclusivity and disclosure requirements need to be agreed directly.

Chart images, linked comments and any external sources referenced but not reproduced were unavailable, so individual figures could not be checked against an original.

Stages
Detail

Extend existing customer identity records so a registered agent sits beside KYC and contact credentials, with verified identity, delegated authority, permissions, expiry and revocation. Treat this the way the posts treat recording an email address or mobile number: the enrollment is what creates the durable asset, and per Crone's framing, connectivity through a protocol does not by itself create a commercial system of record.

Stage

1. Enroll the agent as a relationship asset

Detail

Phase 1 should require out-of-band multi-factor authentication and a customer review-and-release confirmation. This is the fraud control Crone pairs with Know Your Agent registration, and it is also the step that creates a signed mandate to test attribution against.

Stage

2. Put a release step in front of the first purchase

Detail

Design an intent receipt that binds mandate, recommendation, approval, SKU, tokenized payment and refund status into one trail, and reject one-time virtual card numbers in favour of agentic tokenization. The testable claim is that the payment rail proves what was authorized and settled, while cookies and identity trackers only prove exposure.

Stage

3. Make the payment itself the evidence

Detail

Run holdouts so any fee attaches to verified net-new sales rather than impressions or last-click credit. This is the precondition Crone sets for outcome-based pricing, and it is what makes the model defensible with finance teams.

Stage

4. Prove incrementality before charging on it

Detail

Model two revenue lines to pressure-test: a committed fee per acquisition earned only on a validated sale trail, and a per-check intent validation service sold to payment networks as a pre-authorization screen. Re-run the volume and fee assumptions against the platform's own transaction data rather than adopting the published ranges.

Stage

5. Carry a commercial model alongside the architecture

Why this creator

The framework, the phase split, the attribution mechanism and the pricing logic are all drawn from the reviewed posts and can be quoted to internal stakeholders as an external strategic position, with the estimate caveat attached.

Sources for this section

Who else to consider

Stephen Moock

Choose Moock when the open question is distribution and integration rather than attribution.

Read more

The supplied posts describe the infrastructure layer from the inside: connect a product catalog once, distribute it to a range of AI agents, manage the agent channels from a dashboard, and let checkout, payment processing and fraud protection ride along, with named early adopters across retail platforms and marketplaces.

  • The second post is a useful counterweight to hype, reading OpenAI moving Instant Checkout out of ChatGPT search and into apps as evidence that discovery works and forced in-chat checkout did not, and arguing that catalog indexing matters more than a native buy button, that no strategy should rest on one agent's roadmap, and that open protocols and shared payment tokens are the durable layer.
  • Pick Moock if the platform already accepts the case for agentic commerce and needs a credible view of how merchants actually get plugged in, or if the team wants a practical read on an early rollout that underperformed.

Moock's material is shorter and sits closer to a product position than to an independent market model, and it does not answer who owns the verified customer-to-agent record, how intent is priced, or how incrementality is proven.

  • A platform that needs the verification gateway design, the intent-receipt trail and the fee architecture will still be working from Crone's posts.
  • The reverse also holds: Crone's posts argue the economics and the standards gap but do not show the integration-level picture of a catalog that is written once and distributed across agents, so the two answer different halves of the same brief.

Examples: Source 1 · Source 2

Jill Willard

Choose Willard when the decision turns on whether consumers will let an agent buy for them.

Read more

Both posts frame the barrier as trust and liability rather than technology or user experience: the historical sequence runs from cards existing with low trust, to the 1974 Fair Credit Billing Act capping liability, to zero-liability policies and tokenization, with each step unlocking more spending, and the argument is that agentic commerce has to build trust in the actor, not just in the channel.

  • The Amex post is the concrete case, reading a protection-backed posture as the move most likely to shift consumer behaviour.
  • Pick Willard if the platform's launch depends on consumer opt-in, or if the deliverable includes a protection guarantee co-designed with a card network and you need the argument for why that guarantee is the adoption lever.

These posts are analogy-led and do not carry the architecture.

  • There is no verification gateway, no signed mandate, no SKU-to-receipt attribution trail and no fee model, so a team that needs to build and price the mechanism gets much less here than from Crone's posts.
  • Crone supplies the mechanism and the numbers but not this concentrated case for consumer trust as the growth constraint, so the tradeoff is trust argument versus buildable design.

Examples: Source 1 · Source 2

Paolo Andrade

Choose Andrade when the first obstacle is the security and governance review rather than the commercial model.

Read more

The posts set out the operating controls for agents with credentials and API access: do not grant unrestricted credentials, use least privilege with short-lived credentials, require authorization at the moment a sensitive action is taken, log every agent action, keep AI development and testing separate from production, and put data-loss controls around AI applications.

  • The second post extends this to identity, arguing that Zero Trust has to cover autonomous identities and asking what authority is being granted to AI and how that authority is continuously verified.
  • Pick Andrade if the platform must clear an internal security or risk function before any pilot, or if the immediate design question is the scope of an agent's authority and how revocation and auditing work in practice.

Andrade writes about enterprise agent risk, not commerce, so there is no catalog discovery, checkout, sale attribution, merchant economics or intent pricing in the supplied material. A platform whose deliverable is a commercial and attribution framework will still need Crone's posts for the money side, and Crone's posts do not spell out credential lifetime, runtime authorization checks or environment separation in the same operational detail.

Examples: Source 1 · Source 2

Sources for this section

Build your campaign brief

Editable Markdown templates for planning a campaign with this creator.

Agentic commerce strategy campaign brief

Worked example: payment platform agent-verification strategy

Sources for this section

Research methodology

  • This profile is built from the full text of ten LinkedIn posts by Richard Crone on agentic commerce, agent identity and verification, payment attribution, digital wallets, and retail and banking strategy.
  • The posts reviewed include analyses of Claude for Commerce, the Mastercard and OpenAI partnership, Google Pay and Gemini, Walmart's agent gateway, and the Personal Agent Protocol.
  • All ten posts were read in full rather than from titles or excerpts.
  • Comparator posts by three other creators, used only for the similar-creator section, range from December 2025 to October 2026; dates were available for only a couple of Crone's own posts, so change over time in the main body of work could not be established.
  • Every dollar figure, adoption forecast and fee range in the posts is labeled as a Crone Consulting independent estimate or scenario, not a reported company or market result, and is treated that way here.
  • The charts the posts refer to and the comments they link to were not reproduced, so those individual figures could not be checked against an original.
  • No rate card, media kit or sponsorship policy appears in the material, and no documentation of paid placements was found; that is recorded as absent from what was reviewed, not as a statement about what Crone accepts.
  • The account-level follower figure was observed on October 11, 2026.
  • No audience breakdown by role, region or employer was supplied.
  • No supplied evidence covers earlier career history, books, shows or other signature work, so that part of the name-search picture remains open and needs primary evidence before the page can be treated as complete.

Recent engagement

Across their last 9 LinkedIn posts, the median post got 36 reactions and 31 comments. Checked 2026-11-02.

Brands they talk about