# 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.

- Profile: https://b2binfluencer.marketing/creators/richard-crone/
- LinkedIn: https://www.linkedin.com/in/richardcrone
- LinkedIn followers: 21,561
- Median of last 9 posts: 36 reactions, 31 comments (checked 2026-11-02)
- Topics: artificial-intelligence, agentic-commerce
- Based on 8 dated posts, latest 2026-10-07

## Summary

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.
- Check first: Confirm scope, deliverables, fees, disclosure terms, and that figures are estimates.

### 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.

## Main ideas

- **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. 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.
- **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. 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.
- **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. 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.
- **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. 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.
- **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. 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.
- **The per-token model has a ceiling; gain-sharing on transactions does not**: Crone contrasts two revenue models. 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.
- **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. 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.
- **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. 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.
- **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. 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.

## Work to read

- [Claude for Commerce and the case for Committed CPA](https://www.linkedin.com/posts/richardcrone_llms-agenticpayments-byoai-activity-7501068572455161856-bA65)
- [Agent-as-a-Wallet and the Secure Verification Gateway](https://www.linkedin.com/posts/richardcrone_byoai-activity-7511072452484005888-Pp_8)
- [Holiday 2026 and the missing standard for Agent-as-a-Wallet](https://www.linkedin.com/posts/richardcrone_poppy-blackfriday-activity-7518721026550116354-0pvN)
- [Why blocking personal agents is not like blocking Apple Pay](https://www.linkedin.com/posts/richardcrone_byoai-poppy-kya-activity-7520866416712093697-gF4O)
- [Walmart, Bank of America, and the Poppy question](https://www.linkedin.com/posts/richardcrone_pap-byoai-kya-activity-7515802155891494912-uBr6)
- [Mastercard-OpenAI and the market for verified intent](https://www.linkedin.com/posts/richardcrone_agenticpayments-agenticcommerce-activity-7523079344932573185-AP0G)
- [Google Pay, Gemini, and a revenue model beyond ads](https://www.linkedin.com/posts/richardcrone_gpay-botblocking-ccpa-activity-7521962002576171008-bzGk)
- [Digital banking platforms and the Agent-as-a-Wallet threat](https://www.linkedin.com/posts/richardcrone_byoai-agenticpayments-activity-7513258183956795393-Uy3-)
- [Walmart's Agent Gateway and the 2026 holiday checkout](https://www.linkedin.com/posts/richardcrone_sparky-alexa-byoai-activity-7519049674926964736-RJay)
- [Amex Intent Intelligence and selling fraud reduction to networks](https://www.linkedin.com/posts/richardcrone_llms-bankingindustry-creditunionmovement-activity-7516895861759438848-y3pq)

## Brand relationships

- **Crone Consulting LLC** (disclosed_partnership)

## Partnerships

Richard Crone's reviewed posts do not describe a sponsorship, paid-placement, or creator-partnership offer. 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.

## Alternatives

- Stephen Moock: Choose Moock when the open question is distribution and integration rather than attribution. 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.
- Jill Willard: Choose Willard when the decision turns on whether consumers will let an agent buy for them. 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.
- Paolo Andrade: Choose Andrade when the first obstacle is the security and governance review rather than the commercial model. 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.

---
AI-assisted summary of public posts. Audience demographics are not available. Engagement appears only where we checked recent posts. Method: https://b2binfluencer.marketing/methodology/