PayPal Agentic Commerce vs Crossmint

Cart

1. ai-native userMy agent can create and update a cart or order draft through a documented protocol call

   weight 3 · round drawn
   PayPal Agentic Commerce✓fullclaimed8/10

   PayPal documents a concrete, callable cart protocol: POST /merchant-cart createcart to create a cart from a PayPalCart object and getcart to retrieve/update cart status, validation issues, and totals, explicitly invoked by AI agents/PayPal Shopping Cart during checkout; the agent toolkit also exposes create_order and related order-management tools callable by AI agents via MCP/LangChain/etc. Missing for 10: no independent hands-on developer report confirming a live end-to-end agent-driven cart creation/update flow beyond PayPal's own docs, and cart update (vs. only create/get) isn't explicitly documented as a separate call.

   • [claimed-docs] “Creates a new cart with the provided PayPalCart object. This is called by PayPal Shopping Cart when an AI agent or customer initiates a chec…”
   • [claimed-docs] “Retrieves the current state of a cart. Used by PayPal Shopping Cart to check cart status, validation issues, and current totals.”
   • [claimed-docs] “Cart execution is a reverse API the merchant hosts: POST /merchant-cart "Creates a new cart with the provided PayPalCart object. This is cal…”
   • [claimed-docs] “The companion read endpoint keeps agent-side cart state fresh: get cart "Retrieves the current state of a cart. Used by PayPal Shopping Cart…”
   • [claimed-docs] “Post-purchase operations are first-class agent tools: refunds via create_refund / get_refund (a "refund for a captured payment", where "If n…”
   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using" Amazon Bedrock, CrewAI, LangChain, MCP, OpenA…”

   proof ↗⚑ flag

   Crossmint✓fullprobed8/10

   Crossmint's Agent Checkouts API is a documented protocol call that lets an agent submit a product URL and spending cap to create an order/checkout, and runtime probing confirms the endpoint is live and agent-scoped (requiring ServerKeyAgent auth). The lifecycle supports polling for status updates, which functions as order-draft state updates, and agent cards similarly document order-intent creation/tracking (total, reserved, spent, available). missing for 10: no explicit 'update cart' verb or partial-order-edit API, no OpenAPI/schema confirmation (openapi.json probes 404), and no independent third-party corroboration beyond first-party docs and the vendor's own runtime probe.

   • [claimed-docs] “Let your agent buy from any merchant with a single API.”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Agent Checkouts endpoint is live and agent-scoped — a keyless POST to https://www.crossmint.com/api…”
   • [claimed-docs] “"An agent card is an order intent that gives an agent a bounded amount to spend before a fixed expiration." Merchant locking: "The merchant …”
   • [claimed-docs] “Scoped card spending: "An order intent gives the agent a fixed allowance with an amount, description, and expiration, enforced through Visa …”

   proof ↗⚑ flag

Checkout

1. ai-native userMy agent can complete a purchase end-to-end — checkout session, delegated payment credential, confirmed order

   weight 3 · round to Crossmint
   PayPal Agentic Commerce~partialprobed6/10

   Docs describe a real end-to-end path: agent-initiated checkout session (ACP requestCheckout / UCP checkout-session), a delegated one-time-use payment credential (Braintree nonce / Google Pay token), and order confirmation flowing into the merchant's existing order system, backed by a cart API and agent toolkit tools (create_order, pay_order). However this is gated behind Braintree accounts, PayPal's form-based approval, Google's separate merchant enablement, and Store Sync's narrow scope (US, physical goods only) — all from first-party docs with no independent or hands-on confirmation of a completed purchase. Missing for 10: independent/hands-on evidence of an actual completed agent purchase, broader (non-gated) merchant eligibility, and real-world confirmation beyond sandbox/spec descriptions.

   • [claimed-docs] “The ACP path is an in-ChatGPT checkout build: "Implement an MCP server with the `complete_checkout` tool to receive tokens", "Call `requestC…”
   • [claimed-docs] “The UCP path targets Google surfaces: "This enables AI-powered checkout experiences through Google AI Mode (Gemini), where Google Pay return…”
   • [claimed-docs] “Store Sync is the full-catalog path, "enabling AI agents to discover your products, create and manage shopping carts, and complete purchases…”
   • [claimed-docs] “Cart execution is a reverse API the merchant hosts: POST /merchant-cart "Creates a new cart with the provided PayPalCart object. This is cal…”
   • [claimed-docs] “Post-purchase operations are first-class agent tools: refunds via create_refund / get_refund (a "refund for a captured payment", where "If n…”
   • [claimed-docs] “Access to PayPal's agentic commerce services is form-gated, not self-serve: merchants must complete a form "to contact the AI team at PayPal…”
   • [probe] “PROBE runtime (recorded 2026-09-14): PayPal's remote MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.paypal.com/mcp a…”

   proof ↗⚑ flag

   Crossmint✓fullprobed8/10

   Crossmint's Agent Checkouts API lets an agent be handed a product URL and spending cap and complete checkout on the user's behalf, with delegated payment credentials (agent cards/order intents or delegated wallet signer permissions) and a poll-driven order lifecycle to confirm terminal state; runtime probe confirms the endpoint is live and enforces agent-scoped auth. missing for 10: independent/third-party confirmation of a fully completed order in production (docs note no staging/test environment and no webhooks in v1, so end-to-end success is self-reported), and no public case study of a real merchant purchase completing.

   • [claimed-docs] “Let your agent buy from any merchant with a single API.”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”
   • [claimed-docs] “"An agent card is an order intent that gives an agent a bounded amount to spend before a fixed expiration." Merchant locking: "The merchant …”
   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Agent Checkouts endpoint is live and agent-scoped — a keyless POST to https://www.crossmint.com/api…”

   proof ↗⚑ flag

Embedded surfaces

1. merchantBuyers can complete purchases of my products inside chat and assistant surfaces (ChatGPT, Claude, Gemini, Copilot and peers)

   weight 2 · round to PayPal Agentic Commerce
   PayPal Agentic Commerce~partialprobed6/10

   PayPal offers real infrastructure for in-chat checkout: ACP for ChatGPT (via Braintree delegated tokens), UCP for Google AI Mode/Gemini (via Google Pay tokens), and Store Sync for broader catalog/agent discovery, plus an MCP server and agent toolkit. However, coverage is fragmented and gated — Store Sync is US-only, physical-goods-only, and access is form-gated with manual onboarding; ACP/UCP require an existing Braintree relationship or separate Google merchant registration; no evidence of Claude or Copilot checkout support is present. Missing for 10: broader platform coverage beyond ChatGPT/Google (Claude, Copilot), self-serve enablement without form gating, and independent/hands-on confirmation of live buyer transactions completing in-chat.

   • [claimed-docs] “"Agent Ready helps Braintree merchants accept payments from AI shopping assistants across major platforms, including ChatGPT, Google AI Mode…”
   • [claimed-docs] “The ACP path is an in-ChatGPT checkout build: "Implement an MCP server with the `complete_checkout` tool to receive tokens", "Call `requestC…”
   • [claimed-docs] “The UCP path targets Google surfaces: "This enables AI-powered checkout experiences through Google AI Mode (Gemini), where Google Pay return…”
   • [claimed-docs] “Store Sync is the full-catalog path, "enabling AI agents to discover your products, create and manage shopping carts, and complete purchases…”
   • [claimed-docs] “Access to PayPal's agentic commerce services is form-gated, not self-serve: merchants must complete a form "to contact the AI team at PayPal…”
   • [claimed-docs] “Catalog publishing is feed-file based: "PayPal supports 3 feed specifications", including the Google Product Feed ("you can reuse it to powe…”
   • [probe] “PROBE runtime (recorded 2026-09-14): PayPal's remote MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.paypal.com/mcp a…”

   proof ↗⚑ flag

   Crossmint~partialclaimed3/10

   Crossmint documents generic agent-payment infrastructure (Agent Cards, Agent Wallets, Agent Checkouts) that lets any AI agent buy from merchants via API, which could theoretically be wired into chat surfaces, but there is no evidence of concrete integration or partnership with ChatGPT, Claude, Gemini, Copilot or similar assistant surfaces. Missing for 10: named integrations/plugins with specific chat/assistant platforms, evidence of buyers actually completing purchases inside those surfaces, and any merchant-facing onboarding flow tied to those platforms.

   • [claimed-docs] “Let your agent buy from any merchant with a single API.”
   • [claimed-docs] “Crossmint's agent stack is three composable products, verbatim: Agent Cards — "a card for your agent to pay with, secured by Visa VIC and Ma…”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”

   proof ↗⚑ flag

Protocol conformance

1. developerBuild against a versioned commerce protocol with a published schema and conformance or validation tooling

   weight 2 · round to PayPal Agentic Commerce
   PayPal Agentic Commerce~partialclaimed4/10

   PayPal does version its agentic-commerce cart API (v1 createcart/getcart) and provides catalog-feed validation tooling for Store Sync ('a validated product catalog file' against Google/OpenAI ACP feed specs), and it interoperates with external versioned protocols (ACP, UCP). But there's no evidence of a published, standalone schema (e.g., OpenAPI/JSON Schema) for PayPal's own agentic-commerce protocol nor a formal conformance/test suite for developers to validate protocol implementations beyond feed-file field checks. Missing for 10: published protocol schema/spec document, dedicated conformance or validation test suite for the cart/checkout API (not just catalog feed format), and independent evidence of developers using such tooling.

   • [claimed-docs] “Creates a new cart with the provided PayPalCart object. This is called by PayPal Shopping Cart when an AI agent or customer initiates a chec…”
   • [claimed-docs] “Retrieves the current state of a cart. Used by PayPal Shopping Cart to check cart status, validation issues, and current totals.”
   • [claimed-docs] “Catalog publishing is feed-file based: "PayPal supports 3 feed specifications", including the Google Product Feed ("you can reuse it to powe…”
   • [claimed-docs] “Cart execution is a reverse API the merchant hosts: POST /merchant-cart "Creates a new cart with the provided PayPalCart object. This is cal…”
   • [claimed-docs] “The companion read endpoint keeps agent-side cart state fresh: get cart "Retrieves the current state of a cart. Used by PayPal Shopping Cart…”

   proof ↗⚑ flag

   Crossmint—none0/10

   Crossmint documents payment flows (x402, MPP, agent checkouts) but there is no evidence of a versioned commerce protocol with a published schema or conformance/validation tooling — probes for OpenAPI/swagger specs all 404'd, and the live agent-checkouts endpoint is explicitly path-versioned as '/api/unstable/', signaling the opposite of a stable published protocol.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.crossmint.com/openapi.json, https://docs.crossmint.com/swagger.json, https://docs.cross…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Agent Checkouts endpoint is live and agent-scoped — a keyless POST to https://www.crossmint.com/api…”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”

   proof ↗⚑ flag

Agent search

1. ai-native userMy agent can programmatically search products or services across merchants — keylessly or with self-service credentials, no private partnership required

   weight 3 · round to PayPal Agentic Commerce
   PayPal Agentic Commerce!disputedcontradicted3/10

   PayPal frames agentic commerce as 'connect once to reach many platforms', but access to Store Sync/agentic commerce services is explicitly form-gated ('merchants must complete a form... to request access... PayPal AI team will follow up to guide onboarding'), Agent Ready requires an existing Braintree merchant relationship, and UCP requires separate Google merchant registration — none of this is keyless or self-service, and runtime probing confirms the live MCP server itself demands OAuth Bearer authentication (401 + www-authenticate) rather than allowing keyless discovery calls. This contradicts the story's requirement of keyless or self-service, no-partnership product search across merchants. Missing for 10: keyless/anonymous cross-merchant product search, a genuinely self-serve onboarding path without a sales/approval form, and evidence of catalog search working without a pre-existing Braintree/PayPal merchant relationship.

   • [claimed-docs] “Access to PayPal's agentic commerce services is form-gated, not self-serve: merchants must complete a form "to contact the AI team at PayPal…”
   • [claimed-docs] “Store Sync is the full-catalog path, "enabling AI agents to discover your products, create and manage shopping carts, and complete purchases…”
   • [claimed-docs] “"Agent Ready helps Braintree merchants accept payments from AI shopping assistants across major platforms, including ChatGPT, Google AI Mode…”
   • [probe] “PROBE runtime (recorded 2026-09-14): PayPal's remote MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.paypal.com/mcp a…”

   proof ↗⚑ flag

   Crossmint—none0/10

   Crossmint's agent products (Agent Cards, Agent Wallets, Agent Checkouts) are all payment/execution infrastructure that require the agent to already have a specific product URL or merchant endpoint — 'hand it a product URL and a spending cap' — none of the evidence describes a search or product-discovery API across merchants. There is no documented catalog search, product query, or merchant-discovery endpoint; discovery is assumed to happen elsewhere before Crossmint is invoked.

   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”
   • [claimed-docs] “Let your agent buy from any merchant with a single API.”
   • [claimed-docs] “Crossmint's agent stack is three composable products, verbatim: Agent Cards — "a card for your agent to pay with, secured by Visa VIC and Ma…”

   proof ↗⚑ flag

Machine readable offers

1. developerRead machine-readable offer data — price, availability, variants, checkout links — for any listed product or service

   weight 2 · round to PayPal Agentic Commerce
   PayPal Agentic Commerce~partialclaimed5/10

   PayPal's Store Sync catalog feed spec and agent-toolkit's list_product/show_product_details tools do define machine-readable offer fields (id, title, price, availability, description, image_link, link — with each row representing a product variant) and cart-read endpoints expose price/checkout totals, so the core data model the story asks for exists. But this is a gated, merchant-onboarding pathway (form approval required, US-only physical goods, Braintree/PayPal-account prerequisite) rather than an open read surface for 'any listed product,' and there's no evidence of a simple public GET-offer endpoint or checkout-link retrieval independent of the full agentic-commerce integration. Missing for 10: an open/self-serve read API (vs form-gated onboarding), broader product/geography scope, explicit example of returning a checkout link, independent/hands-on corroboration of reading catalog data.

   • [claimed-docs] “Catalog publishing is feed-file based: "PayPal supports 3 feed specifications", including the Google Product Feed ("you can reuse it to powe…”
   • [claimed-docs] “Store Sync is the full-catalog path, "enabling AI agents to discover your products, create and manage shopping carts, and complete purchases…”
   • [claimed-docs] “Post-purchase operations are first-class agent tools: refunds via create_refund / get_refund (a "refund for a captured payment", where "If n…”
   • [claimed-docs] “The companion read endpoint keeps agent-side cart state fresh: get cart "Retrieves the current state of a cart. Used by PayPal Shopping Cart…”
   • [claimed-docs] “Access to PayPal's agentic commerce services is form-gated, not self-serve: merchants must complete a form "to contact the AI team at PayPal…”

   proof ↗⚑ flag

   Crossmint—none0/10

   Crossmint's docs describe agent checkout as handing it a merchant product URL and letting Crossmint execute the purchase, but nowhere is there evidence that Crossmint itself exposes machine-readable offer data (price, availability, variants, checkout links) for developers to read — it's a payment/checkout executor, not a product-data or listing API. Missing for 10: any API/schema returning structured product price/availability/variant data, any catalog or listing endpoint, any documentation of reading offer metadata rather than just completing a purchase given a URL.

   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”
   • [claimed-docs] “Let your agent buy from any merchant with a single API.”

   proof ↗⚑ flag

Service discovery

1. ai-native userMy agent can discover payable services and APIs through a published directory or discovery index

   weight 2 · round to PayPal Agentic Commerce
   PayPal Agentic Commerce~partialprobed5/10

   PayPal provides discovery mechanisms — Store Sync product-catalog feeds (Google Product Feed / OpenAI ACP Product Feed) that let AI agents 'discover your products' and a live MCP server discoverable via RFC 9728 well-known metadata — but there is no published cross-merchant directory or marketplace index of payable services/APIs; discovery is scoped to a single merchant's catalog after form-gated onboarding, and Store Sync itself is limited to US physical goods only. missing for 10: a cross-merchant/public discovery index of payable services or APIs, evidence of self-serve (non form-gated) discoverability, and support beyond US physical goods.

   • [claimed-docs] “It connects your product catalog and commerce API with PayPal's agentic commerce services, enabling AI agents to discover your products, cre…”
   • [claimed-docs] “Store Sync is the full-catalog path, "enabling AI agents to discover your products, create and manage shopping carts, and complete purchases…”
   • [claimed-docs] “Catalog publishing is feed-file based: "PayPal supports 3 feed specifications", including the Google Product Feed ("you can reuse it to powe…”
   • [claimed-docs] “Access to PayPal's agentic commerce services is form-gated, not self-serve: merchants must complete a form "to contact the AI team at PayPal…”
   • [probe] “PROBE runtime (recorded 2026-09-14): PayPal's remote MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.paypal.com/mcp a…”
   • [probe] “official MCP server documented at https://developer.paypal.com/ai-tools/mcp-server”

   proof ↗⚑ flag

   Crossmint—none0/10

   The evidence covers Crossmint's payment rails (cards, wallets, x402, MPP, checkouts) but nothing describes a published directory or discovery index of payable services/APIs that an agent could browse or query; llms.txt is a docs-crawling aid, not a service discovery index. This is a fair axis for an agent-payments platform, but no capability is evidenced.

   ⚑ flag

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round drawn
   PayPal Agentic Commerce✓fullprobed9/10

   There's a confirmed live llms.txt at developer.paypal.com/llms.txt (HTTP 200) plus per-page .md agent-readable docs (e.g. agent-ready/overview.md), and the docs are explicitly agent-oriented (MCP server, agent toolkit, ACP/UCP guides) that an AI agent could consume directly. Missing for 10: no independent third-party report of an agent actually consuming llms.txt successfully in the wild, just first-party probes.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.paypal.com/llms.txt # PayPal Developer Documentation > PayPal's developer documentation for i…”
   • [probe] “PROBE docs-md: HTTP 200 at https://developer.paypal.com/agent-ready/overview.md # Agent Ready overview (/agent-ready/overview) Agent Read…”
   • [probe] “official MCP server documented at https://developer.paypal.com/ai-tools/mcp-server”
   • [probe] “PROBE runtime (recorded 2026-09-14): PayPal's remote MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.paypal.com/mcp a…”

   proof ↗⚑ flag

   Crossmint✓fullprobed9/10

   Crossmint serves a live llms.txt (confirmed by direct probe returning HTTP 200 with agent-oriented content) and every docs page is also available as markdown via the same URL + .md suffix, directly matching the story of pointing an agent at llms.txt or agent-oriented docs. Missing for 10: no independent third-party report of an agent successfully consuming these docs end-to-end, and no OpenAPI spec (all candidates 404) to complement the llms.txt for structured agent consumption.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.crossmint.com/llms.txt # Crossmint > Crossmint is a blockchain infrastructure platform for develop…”
   • [probe] “PROBE runtime (recorded 2026-09-14): docs.crossmint.com serves llms.txt keylessly — '# Crossmint... checkout for onchain and physical-world …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.crossmint.com/openapi.json, https://docs.crossmint.com/swagger.json, https://docs.cross…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round drawn
   PayPal Agentic Commerce~partialprobed6/10

   PayPal's agent toolkit (npm/PyPI packages) and REST APIs, plus the sandbox environment, can be scripted headlessly and invoked from CI pipelines via SDKs (LangChain, CrewAI, OpenAI Agents SDK, MCP) without a UI; webhooks and sandbox credentials support automated testing. However the remote MCP server requires interactive OAuth/PKCE authorization flow (dynamic client registration, bearer auth), which complicates pure headless/CI use, and there's no explicit CI/automation guide or example pipeline in the evidence. missing for 10: documented headless auth flow for CI (service-account/client-credentials for MCP), explicit CI/automation examples, and independent confirmation of unattended operation.

   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using" Amazon Bedrock, CrewAI, LangChain, MCP, OpenA…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the PayPal Agent Toolkit resolves on the public npm registry (npm view @paypal/agent-toolkit → 1.11.0, …”
   • [claimed-docs] “The PayPal sandbox "is a self-contained, virtual testing environment that simulates the live PayPal production environment" — "a shielded sp…”
   • [probe] “PROBE runtime (recorded 2026-09-14): PayPal's remote MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.paypal.com/mcp a…”
   • [claimed-docs] “The developer portal's REST API getting-started page anchors the agent surface: "REST APIs, including orders, payments, subscriptions, invoi…”

   proof ↗⚑ flag

   Crossmint~partialprobed6/10

   Crossmint's core products are REST/headless APIs (explicit 'headless checkout API', agent checkouts API, wallet API) designed for programmatic, UI-less automation, and probes confirm keyless API-key-based auth suitable for scripted/CI calls. However there is no explicit documentation of CI pipeline usage, SDK examples for automated test suites, or non-interactive auth setup, and agent-checkouts testing is noted as production-only with no staging environment, complicating CI use. Missing for 10: documented CI/automation examples, staging/sandbox support for safe automated testing, and explicit non-interactive credential provisioning guidance.

   • [claimed-docs] “Crossmint's headless checkout API is a set of REST APIs that allow you to integrate credit card and cross-chain crypto payments inside your …”
   • [claimed-docs] “Let your agent buy from any merchant with a single API.”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Agent Checkouts endpoint is live and agent-scoped — a keyless POST to https://www.crossmint.com/api…”
   • [claimed-docs] “Crossmint offers secure, programmable smart wallet infrastructure through a single API that is configurable for any use case”

   proof ↗⚑ flag

3. ai-native userDrive the product through a documented public API

   weight 3 · round to PayPal Agentic Commerce
   PayPal Agentic Commerce✓fullprobed9/10

   PayPal publishes extensive, concrete developer documentation (REST API reference, Agent Toolkit, MCP server, agentic-commerce cart API, Store Sync, ACP/UCP guides) with runtime confirmation of a live MCP endpoint and published npm/PyPI SDK packages, giving AI-native developers a genuinely documented public API surface to build against. Missing for 10: some flows are form-gated/partner-gated (Braintree, Store Sync approval) rather than fully self-serve, slightly limiting pure API-driven access.

   • [claimed-docs] “PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using Amazon Bedrock, CrewAI, LangChain, Model Contex…”
   • [claimed-docs] “PayPal built an MCP server that lets merchants use natural language with their favorite MCP clients. This helps users complete business task…”
   • [claimed-docs] “Creates a new cart with the provided PayPalCart object. This is called by PayPal Shopping Cart when an AI agent or customer initiates a chec…”
   • [claimed-docs] “Retrieves the current state of a cart. Used by PayPal Shopping Cart to check cart status, validation issues, and current totals.”
   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using" Amazon Bedrock, CrewAI, LangChain, MCP, OpenA…”
   • [probe] “PROBE runtime (recorded 2026-09-14): PayPal's remote MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.paypal.com/mcp a…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the PayPal Agent Toolkit resolves on the public npm registry (npm view @paypal/agent-toolkit → 1.11.0, …”
   • [claimed-docs] “The developer portal's REST API getting-started page anchors the agent surface: "REST APIs, including orders, payments, subscriptions, invoi…”
   • [claimed-docs] “The PayPal sandbox "is a self-contained, virtual testing environment that simulates the live PayPal production environment" — "a shielded sp…”

   proof ↗⚑ flag

   Crossmint✓fullprobed8/10

   Crossmint exposes a documented REST API surface (wallets, agent cards, agent checkouts, payment flows) with quickstarts and runtime probes confirming the endpoints are live and API-key/agent-key authenticated, and llms.txt/markdown docs are served for machine consumption. The main gap is the absence of a discoverable formal OpenAPI/Swagger spec (probe-2 shows all standard OpenAPI paths 404), so full machine-readable API introspection isn't confirmed. Missing for 10: a published OpenAPI/Swagger schema, independent third-party confirmation of API robustness beyond Crossmint's own docs.

   • [claimed-docs] “Crossmint offers secure, programmable smart wallet infrastructure through a single API that is configurable for any use case”
   • [claimed-docs] “Let your agent buy from any merchant with a single API.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.crossmint.com/llms.txt # Crossmint > Crossmint is a blockchain infrastructure platform for develop…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.crossmint.com/openapi.json, https://docs.crossmint.com/swagger.json, https://docs.cross…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Agent Checkouts endpoint is live and agent-scoped — a keyless POST to https://www.crossmint.com/api…”
   • [probe] “PROBE runtime (recorded 2026-09-14): docs.crossmint.com serves llms.txt keylessly — '# Crossmint... checkout for onchain and physical-world …”
   • [claimed-docs] “Crossmint's agent stack is three composable products, verbatim: Agent Cards — "a card for your agent to pay with, secured by Visa VIC and Ma…”

   proof ↗⚑ flag

4. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round to Crossmint
   PayPal Agentic Commerce~partialprobed4/10

   There's no explicit 'issue a scoped API key/token for an agent' feature for the general Agent Toolkit or REST API surface, but agent-specific payment tokens are documented as scoped/least-privilege by design — the ACP delegated token is 'bound to your merchant ID and includes amount and time restrictions that you can configure,' and the MCP server enforces OAuth with PKCE and dynamic client registration rather than static keys. This shows some least-privilege credentialing pattern for agent checkout flows but not a general-purpose scoped-credential system for arbitrary agent API access. Missing for 10: documented scope/permission tiers (e.g., read-only vs write) for the Agent Toolkit or REST OAuth tokens, and any self-serve UI/API to mint restricted credentials per agent.

   • [claimed-docs] “The ACP path is an in-ChatGPT checkout build: "Implement an MCP server with the `complete_checkout` tool to receive tokens", "Call `requestC…”
   • [probe] “PROBE runtime (recorded 2026-09-14): PayPal's remote MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.paypal.com/mcp a…”
   • [claimed-docs] “Cart execution is a reverse API the merchant hosts: POST /merchant-cart "Creates a new cart with the provided PayPalCart object. This is cal…”

   proof ↗⚑ flag

   Crossmint✓fullprobed7/10

   Crossmint documents explicit least-privilege delegation for agents: user-owned wallets grant an agent a bound signer key with a spend cap, allowed counterparties, and a time window, all enforced onchain and revocable at any time; agent cards similarly use order-intent 'fixed allowance' credentials with amount/expiration limits and network-level enforcement. A runtime probe further shows an agent-specific credential type (ServerKeyAgent) is live on the Agent Checkouts API, confirming agent-scoped API keys exist in practice, not just in docs. Missing for 10: independent/third-party corroboration of these scoping guarantees, and clearer documentation of general-purpose (non-payment) API key scoping/role management beyond the wallet/card/checkout domain.

   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [claimed-docs] “Scoped card spending: "An order intent gives the agent a fixed allowance with an amount, description, and expiration, enforced through Visa …”
   • [claimed-docs] “"An agent card is an order intent that gives an agent a bounded amount to spend before a fixed expiration." Merchant locking: "The merchant …”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Agent Checkouts endpoint is live and agent-scoped — a keyless POST to https://www.crossmint.com/api…”
   • [claimed-docs] “Crossmint's agent stack is three composable products, verbatim: Agent Cards — "a card for your agent to pay with, secured by Visa VIC and Ma…”

   proof ↗⚑ flag

5. ai-native userBuild against official SDKs

   weight 2 · round to PayPal Agentic Commerce
   PayPal Agentic Commerce✓fullprobed8/10

   PayPal publishes an official Agent Toolkit SDK (npm/PyPI, versioned and actively published) integrating with MCP, OpenAI Agents SDK, LangChain, CrewAI, Vercel AI SDK, and Bedrock, plus documented pre-built functions for orders, invoices, subscriptions, refunds, disputes, and catalog management, backed by REST API docs, sandbox testing, and webhooks. This is corroborated by runtime probes confirming the toolkit is live on public registries and the MCP server is reachable. Missing for 10: independent third-party developer reviews/case studies of building against these SDKs beyond PayPal's own docs and registry probes.

   • [claimed-docs] “PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using Amazon Bedrock, CrewAI, LangChain, Model Contex…”
   • [claimed-docs] “PayPal built an MCP server that lets merchants use natural language with their favorite MCP clients. This helps users complete business task…”
   • [claimed-docs] “Integrate with PayPal APIs to access orders, invoices, subscriptions, shipment tracking, transaction details, and dispute management through…”
   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using" Amazon Bedrock, CrewAI, LangChain, MCP, OpenA…”
   • [claimed-docs] “Post-purchase operations are first-class agent tools: refunds via create_refund / get_refund (a "refund for a captured payment", where "If n…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the PayPal Agent Toolkit resolves on the public npm registry (npm view @paypal/agent-toolkit → 1.11.0, …”
   • [probe] “PROBE runtime (recorded 2026-09-14): PayPal's remote MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.paypal.com/mcp a…”
   • [claimed-docs] “The PayPal sandbox "is a self-contained, virtual testing environment that simulates the live PayPal production environment" — "a shielded sp…”
   • [claimed-docs] “The developer portal's REST API getting-started page anchors the agent surface: "REST APIs, including orders, payments, subscriptions, invoi…”
   • [github] “create_order: Create an order in PayPal system based on provided details”

   proof ↗⚑ flag

   Crossmint~partialprobed5/10

   Crossmint's docs show a single REST API accessed via quickstarts (agent checkouts, cards, stablecoin wallets) and protocol-specific clients like @x402/core and mppx, implying SDK-style tooling, but no evidence names an official multi-language SDK package (e.g., npm/pip installable Crossmint SDK) and the OpenAPI probe found no published spec, undercutting a clean 'official SDK' story. missing for 10: explicit official SDK package names/install instructions, multi-language SDK coverage, and a discoverable OpenAPI/schema reference.

   • [claimed-docs] “Create a user-owned smart wallet, authorize an agent as a delegated signer, and send USDXM on Base Sepolia.”
   • [claimed-docs] “Let your agent buy from any merchant with a single API.”
   • [claimed-docs] “MPP support is a first-class payment flow: "This guide shows how to pay MPP (Machine Payment Protocol) endpoints using a Crossmint wallet." …”
   • [claimed-docs] “Crossmint wallets pay x402 endpoints through the @x402/core client (prerequisite: "A funded Crossmint EVM wallet on Base with USDC."): on a …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.crossmint.com/openapi.json, https://docs.crossmint.com/swagger.json, https://docs.cross…”

   proof ↗⚑ flag

6. ai-native userSubscribe to events via webhooks

   weight 2 · round to PayPal Agentic Commerce
   PayPal Agentic Commerce✓fullclaimed7/10

   PayPal's webhook API is explicitly documented: merchants can subscribe up to 10 webhook URLs per app, scoped to specific event types, with durable retry (25 attempts over 3 days) and signature verification guidance — enabling event-driven, agentic integrations. Missing for 10: explicit agentic-commerce-specific event types (e.g., cart/order events tied to AI checkout flows) and independent/hands-on corroboration beyond first-party docs.

   • [claimed-docs] “"Webhooks are HTTPS posts from PayPal to an endpoint on your server whenever the corresponding event type occurs" — "Up to 10 webhook URLs m…”
   • [claimed-docs] “The developer portal's REST API getting-started page anchors the agent surface: "REST APIs, including orders, payments, subscriptions, invoi…”

   proof ↗⚑ flag

   Crossmint—none0/10

   The only explicit evidence about webhooks states the opposite of the story: Agent Checkouts documentation says 'no webhooks in v1' and requires polling until a terminal state is reached, with no other evidence pack item describing a webhook subscription mechanism anywhere in Crossmint's API.

   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”

   proof ↗⚑ flag

Agentic features

1. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to PayPal Agentic Commerce
   PayPal Agentic Commerce~partialprobed6/10

   PayPal provides the building blocks for background automation — an agent toolkit with pre-built functions (orders, refunds, disputes, subscriptions) usable in LangChain/CrewAI/Bedrock workflows, an MCP server for natural-language triggered actions, and webhooks that fire asynchronously with retry logic — enabling autonomous background agent workflows. However, PayPal's own docs explicitly recommend keeping 'human oversight in areas where personal judgment matters most,' and much of the deeper commerce automation (Store Sync, agentic commerce services) is gated behind manual application forms rather than self-serve autonomous setup. Missing for 10: evidence of a fully autonomous, unattended scheduling/orchestration layer, independent confirmation of agents running unattended in production, and self-serve (non-form-gated) enablement.

   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using" Amazon Bedrock, CrewAI, LangChain, MCP, OpenA…”
   • [claimed-docs] “"Webhooks are HTTPS posts from PayPal to an endpoint on your server whenever the corresponding event type occurs" — "Up to 10 webhook URLs m…”
   • [probe] “PROBE runtime (recorded 2026-09-14): PayPal's remote MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.paypal.com/mcp a…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the PayPal Agent Toolkit resolves on the public npm registry (npm view @paypal/agent-toolkit → 1.11.0, …”
   • [claimed-docs] “Post-purchase operations are first-class agent tools: refunds via create_refund / get_refund (a "refund for a captured payment", where "If n…”
   • [claimed-docs] “Access to PayPal's agentic commerce services is form-gated, not self-serve: merchants must complete a form "to contact the AI team at PayPal…”

   proof ↗⚑ flag

   Crossmint~partialclaimed5/10

   Crossmint lets agents transact autonomously once delegated: onchain-enforced spend limits, counterparties, and time windows mean the agent acts 'with no user prompt per action' and checkouts/x402/MPP payments proceed without human intervention ([crossmint-supp-4], [crossmint-supp-6], [crossmint-supp-7]). However this is scoped strictly to payment/checkout automation, not a general-purpose background job/workflow scheduler, and agent checkouts require manual polling with no webhooks or staging ('no webhooks in v1', 'no staging environment') ([crossmint-supp-7]). Missing for 10: general-purpose automation/scheduling framework beyond payments, webhook/event-driven triggers, and evidence of autonomous background operation outside the payment domain.

   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [claimed-docs] “Crossmint wallets pay x402 endpoints through the @x402/core client (prerequisite: "A funded Crossmint EVM wallet on Base with USDC."): on a …”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”
   • [claimed-docs] “MPP support is a first-class payment flow: "This guide shows how to pay MPP (Machine Payment Protocol) endpoints using a Crossmint wallet." …”

   proof ↗⚑ flag

2. ai-native userOperate the product with natural-language commands

   weight 2 · round to PayPal Agentic Commerce
   PayPal Agentic Commerce~partialprobed6/10

   PayPal supports natural-language operation via its MCP server and agent toolkit (LangChain, OpenAI Agents SDK, CrewAI, etc.), letting AI agents issue commands for orders, refunds, disputes, and shopping carts in conversational form, and a runtime probe confirms the MCP endpoint is live. However, the 'user' operating this isn't typically an end consumer speaking to PayPal directly — most flows are merchant-hosted or gated behind Braintree/Google/form approval, and the natural-language surface is mediated through third-party chat assistants (ChatGPT, Gemini) or developer-built agents rather than a native PayPal NL interface. missing for 10: independent/hands-on evidence of an end user directly issuing free-form natural-language commands to PayPal itself (not via a third-party chat assistant or developer-built agent), and confirmation the MCP server/agent toolkit works smoothly without heavy setup/gating.

   • [claimed-docs] “PayPal built an MCP server that lets merchants use natural language with their favorite MCP clients. This helps users complete business task…”
   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using" Amazon Bedrock, CrewAI, LangChain, MCP, OpenA…”
   • [claimed-docs] “Post-purchase operations are first-class agent tools: refunds via create_refund / get_refund (a "refund for a captured payment", where "If n…”
   • [probe] “PROBE runtime (recorded 2026-09-14): PayPal's remote MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.paypal.com/mcp a…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the PayPal Agent Toolkit resolves on the public npm registry (npm view @paypal/agent-toolkit → 1.11.0, …”
   • [claimed-docs] “"Agent Ready helps Braintree merchants accept payments from AI shopping assistants across major platforms, including ChatGPT, Google AI Mode…”
   • [claimed-docs] “Access to PayPal's agentic commerce services is form-gated, not self-serve: merchants must complete a form "to contact the AI team at PayPal…”

   proof ↗⚑ flag

   Crossmint—none0/10

   Crossmint's evidence describes REST APIs, SDKs, and agent-delegated payment flows (cards, wallets, checkouts, x402/MPP), but nothing shows a natural-language command interface for the human/AI-native user to directly operate Crossmint itself — no chat UI, NL-to-API translation layer, or documented conversational control surface. The axis is fair to ask of a product marketed as 'payment infrastructure for AI agents,' but no such capability is evidenced.

   • [claimed-docs] “Crossmint offers secure, programmable smart wallet infrastructure through a single API that is configurable for any use case”
   • [claimed-docs] “Crossmint's agent stack is three composable products, verbatim: Agent Cards — "a card for your agent to pay with, secured by Visa VIC and Ma…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.crossmint.com/openapi.json, https://docs.crossmint.com/swagger.json, https://docs.cross…”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   PayPal Agentic Commerce—none0/10

   Evidence shows static API reference pages (createcart, getcart) and REST API docs, plus a sandbox environment for testing, but nothing describing an interactive reference with embedded runnable/try-it-out examples (e.g., live code execution in docs, Swagger-style console). Missing for 10: any mention of an interactive API console, embedded runnable code snippets, or in-docs request execution.

   • [claimed-docs] “Creates a new cart with the provided PayPalCart object. This is called by PayPal Shopping Cart when an AI agent or customer initiates a chec…”
   • [claimed-docs] “Retrieves the current state of a cart. Used by PayPal Shopping Cart to check cart status, validation issues, and current totals.”
   • [claimed-docs] “The developer portal's REST API getting-started page anchors the agent surface: "REST APIs, including orders, payments, subscriptions, invoi…”
   • [claimed-docs] “The PayPal sandbox "is a self-contained, virtual testing environment that simulates the live PayPal production environment" — "a shielded sp…”

   proof ↗⚑ flag

   Crossmint—none0/10

   The evidence shows only markdown-based docs and an llms.txt feed; explicit probes for an OpenAPI/Swagger spec (openapi.json, swagger.json, etc.) all returned 404, and no evidence mentions an interactive API console, sandbox, or runnable code examples.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.crossmint.com/openapi.json, https://docs.crossmint.com/swagger.json, https://docs.cross…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.crossmint.com/llms.txt # Crossmint > Crossmint is a blockchain infrastructure platform for develop…”
   • [probe] “PROBE runtime (recorded 2026-09-14): docs.crossmint.com serves llms.txt keylessly — '# Crossmint... checkout for onchain and physical-world …”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   PayPal Agentic Commerce—none0/10

   The evidence pack documents REST API references, SDKs, webhooks, and endpoint descriptions (e.g., createcart/getcart docs), but nowhere mentions a downloadable OpenAPI/Swagger file or other machine-readable spec artifact for the agentic-commerce or general PayPal APIs. This axis is clearly applicable to an API-based commerce product, but no evidence shows PayPal exposing such a spec for download.

   • [claimed-docs] “The developer portal's REST API getting-started page anchors the agent surface: "REST APIs, including orders, payments, subscriptions, invoi…”
   • [claimed-docs] “Cart execution is a reverse API the merchant hosts: POST /merchant-cart "Creates a new cart with the provided PayPalCart object. This is cal…”
   • [claimed-docs] “The companion read endpoint keeps agent-side cart state fresh: get cart "Retrieves the current state of a cart. Used by PayPal Shopping Cart…”

   proof ↗⚑ flag

   Crossmint—none0/10

   A direct probe found no OpenAPI/Swagger spec at any standard path (all 404s), and while an llms.txt/markdown docs format exists, that is not a machine-readable API spec. missing for 10: an OpenAPI/Swagger JSON or YAML spec, any documented spec download link, or equivalent machine-readable API schema.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.crossmint.com/openapi.json, https://docs.crossmint.com/swagger.json, https://docs.cross…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.crossmint.com/llms.txt # Crossmint > Crossmint is a blockchain infrastructure platform for develop…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round to PayPal Agentic Commerce
   PayPal Agentic Commerce✓fullclaimed8/10

   PayPal documents a dedicated sandbox that mirrors production, allowing developers/agents to test agent-toolkit tools, cart API, and checkout flows without touching live accounts, and confirms the same REST rails (Orders, cart API) run against sandbox credentials. Missing for 10: no independent/hands-on verification of sandbox parity for agentic-commerce-specific flows (cart API, ACP/UCP checkout) and no explicit documentation of sandbox mode for the MCP server or agent toolkit specifically.

   • [claimed-docs] “The PayPal sandbox "is a self-contained, virtual testing environment that simulates the live PayPal production environment" — "a shielded sp…”
   • [claimed-docs] “The developer portal's REST API getting-started page anchors the agent surface: "REST APIs, including orders, payments, subscriptions, invoi…”
   • [claimed-docs] “Cart execution is a reverse API the merchant hosts: POST /merchant-cart "Creates a new cart with the provided PayPalCart object. This is cal…”
   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using" Amazon Bedrock, CrewAI, LangChain, MCP, OpenA…”

   proof ↗⚑ flag

   Crossmint~partialclaimed4/10

   Crossmint documents genuine testnet sandboxes for some flows (e.g., the stablecoin wallet quickstart runs on Base Sepolia, crossmint-docs-3), but for Agent Checkouts the docs explicitly state 'there is no staging environment for it' and testing is production-only (crossmint-supp-7). So sandboxed testing exists for part of the agent stack but is explicitly absent for another major agent capability. missing for 10: a unified sandbox/staging environment across all agent products (cards, checkouts, wallets), independent confirmation of testnet behavior beyond docs, and any sandbox coverage for Agent Cards/Checkouts specifically.

   • [claimed-docs] “Create a user-owned smart wallet, authorize an agent as a delegated signer, and send USDXM on Base Sepolia.”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   PayPal Agentic Commerce—none0/10

   The evidence pack documents PayPal's agentic-commerce APIs (createcart, getcart, agent toolkit, REST APIs) including a versioned path like /v1/createcart, but nowhere is there any documented deprecation policy, versioning strategy, or backward-compatibility commitment for AI agents to rely on. The axis is clearly applicable (PayPal is an API-first commerce platform) but no supporting evidence exists.

   • [claimed-docs] “Creates a new cart with the provided PayPalCart object. This is called by PayPal Shopping Cart when an AI agent or customer initiates a chec…”
   • [claimed-docs] “Retrieves the current state of a cart. Used by PayPal Shopping Cart to check cart status, validation issues, and current totals.”
   • [claimed-docs] “The developer portal's REST API getting-started page anchors the agent surface: "REST APIs, including orders, payments, subscriptions, invoi…”

   proof ↗⚑ flag

   Crossmint—none0/10

   No evidence pack item documents API versioning conventions or a deprecation policy; the only version-related signal is an endpoint path containing 'unstable' (crossmint-probe-rt-1), which if anything suggests unversioned/experimental APIs rather than a documented deprecation policy.

   ⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   PayPal Agentic Commerce—none0/10

   The evidence shows only single-item agent tools (create_order, create_refund, get_dispute, etc.) and a one-time bulk catalog feed upload for merchant setup, but no documented bulk/batch operation capability (e.g., batch refunds, batch order processing, multi-item transaction endpoints) that an AI agent could invoke across many items at once.

   • [claimed-docs] “Post-purchase operations are first-class agent tools: refunds via create_refund / get_refund (a "refund for a captured payment", where "If n…”
   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using" Amazon Bedrock, CrewAI, LangChain, MCP, OpenA…”
   • [claimed-docs] “Catalog publishing is feed-file based: "PayPal supports 3 feed specifications", including the Google Product Feed ("you can reuse it to powe…”

   proof ↗⚑ flag

   Crossmint—none0/10

   The evidence pack covers single-item agent payment flows (cards, wallets, checkouts, x402/MPP) and mentions managing funds 'at scale' in passing, but there is no documented batch/bulk API, bulk wallet creation, or multi-item transaction endpoint that would let a user perform operations across many items at once.

   • [claimed-docs] “Secure, programmable wallets to manage and move company funds at scale.”
   • [claimed-docs] “Let your agent buy from any merchant with a single API.”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Crossmint
   PayPal Agentic Commerce—none0/10

   Evidence shows PayPal offers webhooks (event notifications) and an agent toolkit with individual API tools, but nothing resembling a rules engine where a user defines 'if event X then action Y' automation — webhooks merely deliver raw event notifications that require the merchant to write custom code to act on, not a rule-definition interface. Missing for 10: any rule-builder/automation-trigger UI or API, conditional logic definition, and evidence of automatic action execution tied to rules rather than manual webhook handling.

   • [claimed-docs] “"Webhooks are HTTPS posts from PayPal to an endpoint on your server whenever the corresponding event type occurs" — "Up to 10 webhook URLs m…”

   proof ↗⚑ flag

   Crossmint~partialclaimed4/10

   Crossmint lets users define scoped rules (spend caps, counterparty allow-lists, time windows) that once set let an agent act autonomously without per-action prompts, and states 'Transaction rules enforced onchain' — a form of automatic rule-based action. However this is closer to pre-authorized permission bounds than true event-triggered automation, and the docs explicitly note agent checkouts have 'no webhooks in v1', meaning event-driven triggering isn't supported there. Missing for 10: an explicit rules/automation engine that fires actions on arbitrary external or on-chain events, webhook/event-subscription support, and independent confirmation of automated rule execution beyond spend-limit enforcement.

   • [claimed-docs] “Transaction rules enforced onchain”
   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [claimed-docs] “Scoped card spending: "An order intent gives the agent a fixed allowance with an amount, description, and expiration, enforced through Visa …”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”

   proof ↗⚑ flag

Fees transparency

1. merchantThe fees for agent-originated transactions are published — I can price agentic channels without asking sales

   weight 2 · round to PayPal Agentic Commerce
   PayPal Agentic Commerce~partialclaimed5/10

   Evidence shows agent-originated transactions run through existing Braintree/PayPal Checkout rails and thus inherit the standard published US commercial fee schedule (2.99–4.99% + fixed fee), so merchants aren't quoted a hidden or sales-negotiated rate for the payment processing itself. However, the same evidence explicitly states 'No separate agentic/AI-channel fee schedule is published,' and access to Agent Ready/Store Sync/ACS is gated behind a sales-contact form, leaving open whether any additional platform or enablement fee applies to the agentic channel — so a merchant cannot fully price the agentic channel without engaging sales for onboarding. Missing for 10: an explicit agentic-channel fee page or fee line item, and self-serve (non-form-gated) enrollment that would let a merchant confirm total costs without sales contact.

   • [claimed-docs] “The published US commercial rates that agent-initiated orders inherit: "PayPal Checkout" and "PayPal Guest Checkout" at "3.49% +" fixed fee,…”
   • [claimed-docs] “Access to PayPal's agentic commerce services is form-gated, not self-serve: merchants must complete a form "to contact the AI team at PayPal…”
   • [claimed-docs] “Store Sync is the full-catalog path, "enabling AI agents to discover your products, create and manage shopping carts, and complete purchases…”

   proof ↗⚑ flag

   Crossmint—none0/10

   Crossmint publishes general wallet MAU overage pricing and checkout fee tiers, but the evidence pack explicitly states 'No agent-card- or agent-checkout-specific price is published on the pricing page' (crossmint-supp-9), meaning a merchant cannot price the agent-specific channels (Agent Cards, Agent Checkouts) without contacting sales.

   • [claimed-docs] “Published pricing: wallets are "Free 1,000 Monthly Active Wallets" then "Overages start at $0.05 per MAU. Volume discounts available."; onra…”

   proof ↗⚑ flag

Payouts

1. merchantAgent-originated payments settle through documented payout and reporting flows, reconcilable like any other channel

   weight 1 · round to PayPal Agentic Commerce
   PayPal Agentic Commerce~partialclaimed6/10

   Agent-originated orders flow into the merchant's existing order management, payment, refund/dispute, and webhook systems (create_order, refund/dispute tools, webhooks with signature verification, existing Orders v2/Braintree rails), and docs explicitly state Store Sync orders arrive 'just as it would from any other channel,' suggesting standard reconciliation. However, there is no dedicated agentic-channel reporting/settlement documentation, no separate transaction tagging or reconciliation report distinguishing agent-originated payments, and fee schedules show no distinct line item for agent transactions, making channel-level reconciliation an inference rather than a documented flow. missing for 10: dedicated agent-channel reporting/settlement statements, explicit reconciliation tooling or transaction tags identifying agent-originated payments, independent merchant confirmation of clean reconciliation in production.

   • [claimed-docs] “Store Sync is the full-catalog path, "enabling AI agents to discover your products, create and manage shopping carts, and complete purchases…”
   • [claimed-docs] “Post-purchase operations are first-class agent tools: refunds via create_refund / get_refund (a "refund for a captured payment", where "If n…”
   • [claimed-docs] “"Webhooks are HTTPS posts from PayPal to an endpoint on your server whenever the corresponding event type occurs" — "Up to 10 webhook URLs m…”
   • [claimed-docs] “The published US commercial rates that agent-initiated orders inherit: "PayPal Checkout" and "PayPal Guest Checkout" at "3.49% +" fixed fee,…”
   • [claimed-docs] “The developer portal's REST API getting-started page anchors the agent surface: "REST APIs, including orders, payments, subscriptions, invoi…”
   • [claimed-docs] “Cart execution is a reverse API the merchant hosts: POST /merchant-cart "Creates a new cart with the provided PayPalCart object. This is cal…”

   proof ↗⚑ flag

   Crossmint~partialclaimed3/10

   Evidence shows transaction-lifecycle tracking (order intents track total/reserved/spent/available amounts) and a documented authorization-hold/capture and dispute-management model for card checkout, which are reconciliation-adjacent, plus tiered per-transaction pricing. But there is no documented merchant payout schedule, settlement-to-bank-account flow, transaction reporting dashboard, or export/reconciliation tooling specific to agent-originated payments, and the agent-checkouts flow explicitly lacks webhooks ('no webhooks in v1' — poll until terminal state), undermining real-time reconciliation. Missing for 10: merchant payout/settlement documentation, reporting/dashboard or export tools, reconciliation-specific guidance for agent transactions, and webhook-based confirmation.

   • [claimed-docs] “Scoped card spending: "An order intent gives the agent a fixed allowance with an amount, description, and expiration, enforced through Visa …”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”
   • [claimed-docs] “For card checkout, Crossmint absorbs dispute risk: "Crossmint will take on the risk and manage disputes directly with the bank.", using an a…”
   • [claimed-docs] “Published pricing: wallets are "Free 1,000 Monthly Active Wallets" then "Overages start at $0.05 per MAU. Volume discounts available."; onra…”

   proof ↗⚑ flag

Attribution analytics

1. merchantOrders are attributed to the originating agent and I can report on or filter transactions by agent

   weight 2 · round drawn
   PayPal Agentic Commerce—none0/10

   Evidence covers agent-initiated checkout flows (ACP/UCP/Store Sync/cart API/agent toolkit) but nowhere describes orders being tagged with an originating-agent identifier, nor any merchant dashboard/report/filter capability by agent; in fact Store Sync docs state orders arrive 'just as it would from any other channel,' suggesting no special agent attribution.

   • [claimed-docs] “Store Sync is the full-catalog path, "enabling AI agents to discover your products, create and manage shopping carts, and complete purchases…”
   • [claimed-docs] “Cart execution is a reverse API the merchant hosts: POST /merchant-cart "Creates a new cart with the provided PayPalCart object. This is cal…”
   • [claimed-docs] “The companion read endpoint keeps agent-side cart state fresh: get cart "Retrieves the current state of a cart. Used by PayPal Shopping Cart…”

   proof ↗⚑ flag

   Crossmint—none0/10

   The evidence describes agent payment mechanisms (cards, wallets, checkouts, spending rules) but contains no mention of merchant-facing reporting, dashboards, or transaction filtering by originating agent — the core of this story. Order intents and delegated signers are documented for controlling agent spend, not for merchant attribution/reporting.

   ⚑ flag

Onboarding to agents

1. merchantI have a documented self-serve path to start accepting agent traffic — enable a setting, sign an agreement, or publish an endpoint

   weight 3 · round to PayPal Agentic Commerce
   PayPal Agentic Commerce~partialclaimed5/10

   There is documented onboarding material (Agent Ready guides, Store Sync docs, catalog feed specs), but the path is explicitly gated rather than self-serve: PayPal's own docs state that agentic commerce services access is 'form-gated, not self-serve' requiring a form submission and manual follow-up from PayPal's AI team, Store Sync eligibility requires an existing Braintree/Orders v2 account plus the same approval gate, and the UCP/Google Pay path requires separate 'merchant registration with Google. Contact Google for enablement.' Agent Ready itself assumes an existing Braintree merchant relationship rather than a simple toggle or self-issued agreement. Missing for 10: a true no-approval self-serve enablement (setting flip, standard clickthrough agreement, or endpoint publish without a contact-form/manual review step), and confirmation of approval turnaround time.

   • [claimed-docs] “Access to PayPal's agentic commerce services is form-gated, not self-serve: merchants must complete a form "to contact the AI team at PayPal…”
   • [claimed-docs] “"Agent Ready helps Braintree merchants accept payments from AI shopping assistants across major platforms, including ChatGPT, Google AI Mode…”
   • [claimed-docs] “The UCP path targets Google surfaces: "This enables AI-powered checkout experiences through Google AI Mode (Gemini), where Google Pay return…”
   • [claimed-docs] “Store Sync is the full-catalog path, "enabling AI agents to discover your products, create and manage shopping carts, and complete purchases…”
   • [claimed-docs] “Catalog publishing is feed-file based: "PayPal supports 3 feed specifications", including the Google Product Feed ("you can reuse it to powe…”

   proof ↗⚑ flag

   Crossmint—none0/10

   Evidence covers agent-side integrations (agent wallets, agent cards, x402/MPP payment flows, agent checkouts) but nothing documents a merchant-facing onboarding step — no setting to enable, agreement to sign, or endpoint-publishing guide aimed at merchants who want to accept agent traffic. The 'buy from any merchant' framing implies merchants need no explicit action, but this is never documented as a self-serve merchant enablement path.

   ⚑ flag

Traffic controls

1. merchantRate-limit, allow, or deny specific agents and agent platforms accessing my catalog and checkout

   weight 2 · round drawn
   PayPal Agentic Commerce—none0/10

   Evidence shows PayPal gates agentic-commerce access at the platform/onboarding level (Braintree account, Google UCP registration, PayPal AI-team approval form) and gives merchants brand/communication control, but nothing describes merchant-configurable rate limits or per-agent/per-platform allow/deny controls over catalog or checkout access.

   • [claimed-docs] “"Agent Ready helps Braintree merchants accept payments from AI shopping assistants across major platforms, including ChatGPT, Google AI Mode…”
   • [claimed-docs] “Access to PayPal's agentic commerce services is form-gated, not self-serve: merchants must complete a form "to contact the AI team at PayPal…”
   • [claimed-docs] “Store Sync is the full-catalog path, "enabling AI agents to discover your products, create and manage shopping carts, and complete purchases…”

   proof ↗⚑ flag

   Crossmint—none0/10

   The evidence details user-side and agent-side spending controls (spend caps, counterparties, time windows, order intents) but nothing about merchants controlling which agents/agent platforms may access their catalog or checkout, nor any rate-limiting/allow-deny mechanism exposed to merchants. Crossmint's agent-checkout flow treats the merchant as an arbitrary third-party target ('buy from any merchant'), not as a Crossmint customer configuring agent access policies.

   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”
   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [claimed-docs] “"An agent card is an order intent that gives an agent a bounded amount to spend before a fixed expiration." Merchant locking: "The merchant …”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round drawn
   PayPal Agentic Commerce~partialclaimed6/10

   PayPal's agent toolkit and REST APIs expose a broad set of merchant operations (orders, invoices, subscriptions, refunds, disputes, shipment tracking, catalog management) that mirror much of what's doable in the PayPal/Braintree dashboards, and there's a documented MCP server, SDKs, and sandbox for building against these. However, the flagship agentic-commerce paths are heavily gated rather than self-serve: Agent Ready requires a Braintree account, Store Sync and Agentic Commerce Services require a manual form-based approval process, UCP requires separate Google merchant registration, and Store Sync itself is scoped only to US physical goods in USD — none of which are pure API-driven equivalents of UI actions. Missing for 10: explicit UI-vs-API feature-parity mapping, self-serve (non-gated) access to the agentic commerce APIs, and confirmation that all dashboard-level configuration/reporting is API-accessible without approval gates.

   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using" Amazon Bedrock, CrewAI, LangChain, MCP, OpenA…”
   • [claimed-docs] “Post-purchase operations are first-class agent tools: refunds via create_refund / get_refund (a "refund for a captured payment", where "If n…”
   • [claimed-docs] “Access to PayPal's agentic commerce services is form-gated, not self-serve: merchants must complete a form "to contact the AI team at PayPal…”
   • [claimed-docs] “Store Sync is the full-catalog path, "enabling AI agents to discover your products, create and manage shopping carts, and complete purchases…”
   • [claimed-docs] “The UCP path targets Google surfaces: "This enables AI-powered checkout experiences through Google AI Mode (Gemini), where Google Pay return…”
   • [claimed-docs] “The developer portal's REST API getting-started page anchors the agent surface: "REST APIs, including orders, payments, subscriptions, invoi…”
   • [claimed-docs] “The PayPal sandbox "is a self-contained, virtual testing environment that simulates the live PayPal production environment" — "a shielded sp…”

   proof ↗⚑ flag

   Crossmint~partialprobed6/10

   Crossmint is built API-first — wallets, agent cards, agent checkouts, and headless checkout are all exposed as REST APIs, with headless checkout explicitly positioned as the API-only alternative to Crossmint's embedded iframe UI, giving 'full control of the user experience' (crossmint-docs-1, crossmint-docs-7, crossmint-docs-8, crossmint-supp-1). However, there's no explicit claim or evidence of full UI/API feature parity across the whole platform, and the probe found no discoverable OpenAPI spec (404s on all candidate paths), suggesting some API surface may be undocumented or incomplete relative to the dashboard. Missing for 10: an explicit parity statement or audit showing every dashboard/UI action (account/team management, dispute handling, analytics) has an API equivalent, and a published OpenAPI spec confirming full API surface.

   • [claimed-docs] “Crossmint offers secure, programmable smart wallet infrastructure through a single API that is configurable for any use case”
   • [claimed-docs] “Crossmint's headless checkout API is a set of REST APIs that allow you to integrate credit card and cross-chain crypto payments inside your …”
   • [claimed-docs] “Embedded iframe with customizable UI.”
   • [claimed-docs] “Crossmint's agent stack is three composable products, verbatim: Agent Cards — "a card for your agent to pay with, secured by Visa VIC and Ma…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.crossmint.com/openapi.json, https://docs.crossmint.com/swagger.json, https://docs.cross…”

   proof ↗⚑ flag

Order events

1. developerMy agent or backend can subscribe to order lifecycle events — created, updated, fulfilled, canceled — pushed programmatically

   weight 3 · round to PayPal Agentic Commerce
   PayPal Agentic Commerce~partialclaimed5/10

   PayPal's generic webhooks system (developer.paypal.com/api/webhooks/overview) lets a merchant subscribe up to 10 URLs to specific event types, with durable retry (up to 25 attempts/3 days) and signature verification — and the agent-toolkit/cart API run on the same REST/order rails, so this infrastructure would carry order events. However, no evidence pack item explicitly names order-lifecycle event types (ORDER.CREATED/UPDATED/CANCELLED/fulfilled) tied to the agentic-commerce cart or Store Sync flows — those docs describe merchant-hosted reverse endpoints (createcart/getcart) rather than push-based lifecycle events for agents. Missing for 10: explicit order-lifecycle event-type list for agentic commerce, confirmation that Store Sync/cart orders emit standard webhook events, and any hands-on/independent proof of an agent successfully subscribing to these events.

   • [claimed-docs] “"Webhooks are HTTPS posts from PayPal to an endpoint on your server whenever the corresponding event type occurs" — "Up to 10 webhook URLs m…”
   • [claimed-docs] “The developer portal's REST API getting-started page anchors the agent surface: "REST APIs, including orders, payments, subscriptions, invoi…”
   • [claimed-docs] “Cart execution is a reverse API the merchant hosts: POST /merchant-cart "Creates a new cart with the provided PayPalCart object. This is cal…”
   • [claimed-docs] “The companion read endpoint keeps agent-side cart state fresh: get cart "Retrieves the current state of a cart. Used by PayPal Shopping Cart…”

   proof ↗⚑ flag

   Crossmint—none0/10

   Crossmint's own docs explicitly state agent checkouts have 'no webhooks in v1' and require polling until a terminal state is reached, meaning there is no programmatic push-based subscription to order lifecycle events (created/updated/fulfilled/canceled). No other product area (wallets, cards) documents webhook/event subscription either.

   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”

   proof ↗⚑ flag

Post purchase status

1. ai-native userMy agent can query the status and tracking of an order it placed, after the purchase

   weight 2 · round drawn
   PayPal Agentic Commerce~partialprobed6/10

   PayPal's agent toolkit and REST surface explicitly advertise agent access to 'orders...shipment tracking, transaction details' for post-purchase queries, and the agent-tools page lists concrete order-related functions (create_order, pay_order, create_shipment) alongside webhooks for order events. However, no specific 'get_order_status' or 'track_shipment' tool call is named or demonstrated end-to-end, so the tracking-query capability is asserted at a high level rather than shown working. Missing for 10: an explicitly named order-status/tracking query tool/function, and independent or hands-on confirmation that an agent can actually retrieve tracking info post-purchase.

   • [claimed-docs] “Integrate with PayPal APIs to access orders, invoices, subscriptions, shipment tracking, transaction details, and dispute management through…”
   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using" Amazon Bedrock, CrewAI, LangChain, MCP, OpenA…”
   • [claimed-docs] “Post-purchase operations are first-class agent tools: refunds via create_refund / get_refund (a "refund for a captured payment", where "If n…”
   • [claimed-docs] “"Webhooks are HTTPS posts from PayPal to an endpoint on your server whenever the corresponding event type occurs" — "Up to 10 webhook URLs m…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the PayPal Agent Toolkit resolves on the public npm registry (npm view @paypal/agent-toolkit → 1.11.0, …”

   proof ↗⚑ flag

   Crossmint~partialclaimed6/10

   Docs explicitly describe agent checkouts as poll-driven — 'no webhooks in v1... you poll until it reaches a terminal state' — and order intents/rails each carry their own status, so an agent can query order status after purchase via polling. However, this is documented only for the Agent Checkouts flow (not agent cards or wallet payments), lacks any true package/shipment tracking detail, and has no independent or hands-on corroboration beyond first-party docs. Missing for 10: shipment/delivery tracking detail, webhook or push-based status updates, and third-party verification of the polling flow actually working in production.

   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”
   • [claimed-docs] “An order intent can have multiple rails, each with its own status, credential formats, and verification.”
   • [claimed-docs] “Let your agent buy from any merchant with a single API.”

   proof ↗⚑ flag

Delegated credentials

1. ai-native userHand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card number

   weight 3 · round to Crossmint
   PayPal Agentic Commerce~partialclaimed6/10

   PayPal's ACP/UCP flows use Braintree single-use payment tokens/nonces that are explicitly described as 'bound to your merchant ID and includes amount and time restrictions that you can configure' — a genuine scoped, limited-use credential rather than a raw card number, and Google's UCP path similarly returns a tokenized, single-use credential. However this is merchant-side infrastructure (tokens generated by the merchant's Braintree integration for a specific checkout), not a consumer/end-user-controlled credential that an AI-native user personally hands to their own agent with self-set amount/expiry/merchant limits; there's no evidence of a user-facing wallet-style scoped credential issuance flow. missing for 10: end-user-facing UI/API for a consumer to mint their own scoped credential (set their own amount cap, expiry, merchant allowlist) independent of a specific merchant checkout session, and independent/hands-on confirmation of these restriction configs working in practice.

   • [claimed-docs] “The ACP path is an in-ChatGPT checkout build: "Implement an MCP server with the `complete_checkout` tool to receive tokens", "Call `requestC…”
   • [claimed-docs] “The UCP path targets Google surfaces: "This enables AI-powered checkout experiences through Google AI Mode (Gemini), where Google Pay return…”
   • [claimed-docs] “Cart execution is a reverse API the merchant hosts: POST /merchant-cart "Creates a new cart with the provided PayPalCart object. This is cal…”

   proof ↗⚑ flag

   Crossmint✓fullprobed9/10

   Crossmint's Agent Cards give agents a one-time card number, expiration, and CVC scoped by an order intent with amount, description, merchant lock, and expiration — never exposing the real card number — enforced via Visa/Mastercard network rails (crossmint-supp-2, crossmint-supp-3, crossmint-supp-8). This is corroborated by a live runtime probe showing the agent-scoped checkout endpoint requiring agent-specific credentials (crossmint-probe-rt-1). Missing for 10: independent third-party (non-vendor) verification of the card-scoping behavior in production beyond the docs and single runtime probe.

   • [claimed-docs] “Scoped card spending: "An order intent gives the agent a fixed allowance with an amount, description, and expiration, enforced through Visa …”
   • [claimed-docs] “Credentials are one-time and network-verified: minting returns "the secure one-time card number, expiration, and CVC", and verification is a…”
   • [claimed-docs] “"An agent card is an order intent that gives an agent a bounded amount to spend before a fixed expiration." Merchant locking: "The merchant …”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Agent Checkouts endpoint is live and agent-scoped — a keyless POST to https://www.crossmint.com/api…”
   • [claimed-docs] “Give agents permission to pay with a user's card using Crossmint's Agentic Payments API.”

   proof ↗⚑ flag

Machine payments

1. developerMonetize an API or service with HTTP 402 machine payments that agents pay per call without a checkout UI

   weight 3 · round drawn
   PayPal Agentic Commerce—none0/10

   All evidence describes PayPal's agentic commerce as checkout-flow based (carts, ACP/UCP delegated tokens, Store Sync, agent toolkit for orders/refunds/disputes) — none of it describes HTTP 402 status-code machine payments or per-call API monetization without a checkout UI, which is a distinct technical pattern. Since PayPal is a payments platform, this axis could plausibly apply, but there is no evidence it ships or supports the 402 pay-per-call mechanism described in the story.

   ⚑ flag

   Crossmint—none0/10

   All Crossmint evidence describes agents/wallets *paying* x402 or MPP-protected endpoints (client/payer side) — e.g. crossmint-supp-6 and crossmint-supp-5 explain how a Crossmint wallet reads a 402 challenge and retries with payment proof. There is no evidence of tooling for a developer to stand up their own API/service that returns HTTP 402 challenges and receives/settles per-call agent payments (the monetization/merchant side of x402). Missing for 10: any docs or API for creating/serving a 402-gated endpoint, receiving settlement, or configuring per-call pricing as a service provider — evidence only covers the consuming side.

   • [claimed-docs] “Crossmint wallets pay x402 endpoints through the @x402/core client (prerequisite: "A funded Crossmint EVM wallet on Base with USDC."): on a …”
   • [claimed-docs] “MPP support is a first-class payment flow: "This guide shows how to pay MPP (Machine Payment Protocol) endpoints using a Crossmint wallet." …”
   • [claimed-docs] “This guide shows how to pay x402-protected endpoints using a Crossmint wallet.”
   • [claimed-docs] “This guide shows how to pay MPP (Machine Payment Protocol) endpoints using a Crossmint wallet.”

   proof ↗⚑ flag

Settlement rails

1. developerSettle agent-initiated payments in stablecoins over documented rails

   weight 2 · round to Crossmint
   PayPal Agentic Commerce—none0/10

   The evidence pack details PayPal's agentic commerce rails extensively (ACP/UCP via Braintree tokens, agent toolkit, cart APIs, webhooks, fees) but none of it mentions stablecoins, PYUSD, crypto, or blockchain-based settlement rails for agent-initiated payments — all documented settlement is via traditional card/Braintree processing and standard PayPal fee schedules.

   • [claimed-docs] “"Agent Ready helps Braintree merchants accept payments from AI shopping assistants across major platforms, including ChatGPT, Google AI Mode…”
   • [claimed-docs] “The ACP path is an in-ChatGPT checkout build: "Implement an MCP server with the `complete_checkout` tool to receive tokens", "Call `requestC…”
   • [claimed-docs] “The UCP path targets Google surfaces: "This enables AI-powered checkout experiences through Google AI Mode (Gemini), where Google Pay return…”
   • [claimed-docs] “The published US commercial rates that agent-initiated orders inherit: "PayPal Checkout" and "PayPal Guest Checkout" at "3.49% +" fixed fee,…”

   proof ↗⚑ flag

   Crossmint✓fullprobed8/10

   Crossmint documents stablecoin settlement for agent payments via user-owned wallets with delegated signer permissions (USDXM/USDC), and explicit rails including x402 and MPP protocols with runtime-verified endpoint behavior, giving strong first-party and probe corroboration of documented stablecoin rails. missing for 10: independent (non-vendor) real-world case studies of production stablecoin settlement volume, and confirmation the x402/MPP flows work beyond testnet/Base Sepolia examples.

   • [claimed-docs] “Create a user-owned smart wallet, authorize an agent as a delegated signer, and send USDXM on Base Sepolia.”
   • [claimed-docs] “This guide shows how to pay x402-protected endpoints using a Crossmint wallet.”
   • [claimed-docs] “This guide shows how to pay MPP (Machine Payment Protocol) endpoints using a Crossmint wallet.”
   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [claimed-docs] “MPP support is a first-class payment flow: "This guide shows how to pay MPP (Machine Payment Protocol) endpoints using a Crossmint wallet." …”
   • [claimed-docs] “Crossmint wallets pay x402 endpoints through the @x402/core client (prerequisite: "A funded Crossmint EVM wallet on Base with USDC."): on a …”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Agent Checkouts endpoint is live and agent-scoped — a keyless POST to https://www.crossmint.com/api…”

   proof ↗⚑ flag

Wallets

1. ai-native userProvision a wallet my agent holds and spends from — funded and controlled by me, with balance visibility

   weight 3 · round to Crossmint
   PayPal Agentic Commerce—none0/10

   All evidence describes merchant-side infrastructure (Agent Ready, Store Sync, agent toolkit, cart APIs) that lets AI agents check out with merchants or lets merchants build agents for order/refund/dispute management — none of it describes a consumer-provisioned wallet that a user funds, an agent holds/spends from, with balance visibility. The delegated tokens in ACP/UCP are single-use, merchant-bound checkout credentials, not a persistent user wallet.

   ⚑ flag

   Crossmint~partialclaimed7/10

   Crossmint's Agent Wallets docs show a user-owned, non-custodial wallet that a user funds and controls, with the agent authorized as a scoped, revocable delegated signer (spend cap, counterparties, time window) enforced onchain, and a working stablecoin-wallet quickstart (crossmint-docs-3, crossmint-supp-4, crossmint-supp-5). However, the evidence never explicitly documents a balance-visibility feature (e.g., a balance/dashboard API for the funding user) — missing for 10: explicit balance-check/visibility API or UI evidence, independent/hands-on corroboration of the wallet flow.

   • [claimed-docs] “Create a user-owned smart wallet, authorize an agent as a delegated signer, and send USDXM on Base Sepolia.”
   • [claimed-docs] “Crossmint's agent stack is three composable products, verbatim: Agent Cards — "a card for your agent to pay with, secured by Visa VIC and Ma…”
   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [claimed-docs] “MPP support is a first-class payment flow: "This guide shows how to pay MPP (Machine Payment Protocol) endpoints using a Crossmint wallet." …”
   • [claimed-docs] “Crossmint wallets pay x402 endpoints through the @x402/core client (prerequisite: "A funded Crossmint EVM wallet on Base with USDC."): on a …”

   proof ↗⚑ flag

Ecosystem adoption

1. developerAt least two independent parties beyond the vendor implement the protocol or platform — it is an ecosystem, not a private integration

   weight 2 · round drawn
   PayPal Agentic Commerce—none0/10

   The evidence shows PayPal/Braintree acting as an implementer of protocols defined by other parties (OpenAI's ACP, Google's UCP, and the Anthropic-originated MCP), but nothing shows independent third parties implementing PayPal's own agentic-commerce platform (Cart API, Store Sync, agent toolkit) as an open ecosystem. Merchants and partners (Wix, Shopware, BigCommerce) are consumers/integrators of PayPal's platform, not independent implementers of its protocol.

   • [claimed-docs] “The ACP path is an in-ChatGPT checkout build: "Implement an MCP server with the `complete_checkout` tool to receive tokens", "Call `requestC…”
   • [claimed-docs] “The UCP path targets Google surfaces: "This enables AI-powered checkout experiences through Google AI Mode (Gemini), where Google Pay return…”
   • [claimed-docs] “Store Sync is the full-catalog path, "enabling AI agents to discover your products, create and manage shopping carts, and complete purchases…”
   • [claimed-docs] “Access to PayPal's agentic commerce services is form-gated, not self-serve: merchants must complete a form "to contact the AI team at PayPal…”

   proof ↗⚑ flag

   Crossmint—none0/10

   Evidence describes Crossmint as a single-vendor proprietary API/platform (wallets, checkout, agent cards) — even where it interoperates with external protocols like x402 or MPP, those are third-party specs Crossmint merely consumes, not evidence that independent parties implement Crossmint's own protocol/platform. No evidence pack item shows any other company or independent implementer building a competing or parallel implementation of Crossmint's infrastructure.

   ⚑ flag

Spec publication

1. developerThe commerce protocol this product speaks is published as an open, versioned specification I can read and implement without signing anything

   weight 3 · round drawn
   PayPal Agentic Commerce—none0/10

   The evidence pack shows PayPal implements OpenAI's ACP and Google's UCP protocols and tells developers to 'follow the ACP agentic checkout specification,' but never provides or links a version number, license, or spec document for ACP/UCP that a developer could read independently of PayPal. Instead, everything documented is gated: Braintree merchant account required, PayPal AI team form-approval required for agentic commerce services, and separate Google merchant registration required for UCP enablement — none of this evidences an open, versioned, sign-nothing spec.

   • [claimed-docs] “The ACP path is an in-ChatGPT checkout build: "Implement an MCP server with the `complete_checkout` tool to receive tokens", "Call `requestC…”
   • [claimed-docs] “The UCP path targets Google surfaces: "This enables AI-powered checkout experiences through Google AI Mode (Gemini), where Google Pay return…”
   • [claimed-docs] “Access to PayPal's agentic commerce services is form-gated, not self-serve: merchants must complete a form "to contact the AI team at PayPal…”
   • [claimed-docs] “"Agent Ready helps Braintree merchants accept payments from AI shopping assistants across major platforms, including ChatGPT, Google AI Mode…”

   proof ↗⚑ flag

   Crossmint—none0/10

   Crossmint documents its own REST/agent APIs (cards, wallets, checkouts) but the evidence shows no open, versioned specification of its own commerce protocol — the OpenAPI/swagger probe returned 404 on all candidate paths, and no spec repository or versioning scheme is mentioned. While Crossmint implements external protocols like x402 and MPP, it does not publish its own commerce protocol as an open spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.crossmint.com/openapi.json, https://docs.crossmint.com/swagger.json, https://docs.cross…”

   proof ↗⚑ flag

Disputes

1. developerDisputes and chargebacks on agent transactions can be handled via API — evidence submission, status, outcomes

   weight 2 · round to PayPal Agentic Commerce
   PayPal Agentic Commerce~partialclaimed6/10

   The agent toolkit exposes dispute tools — list_disputes, get_dispute, and accept_dispute_claim — plus the general REST API surface explicitly lists 'disputes' alongside orders/payments, giving developers programmatic access to dispute status and resolution outcomes. However, no evidence-submission endpoint (e.g., uploading documents/evidence for a dispute) is documented anywhere in the pack, so the 'evidence submission' part of the story is unsupported. missing for 10: documented evidence-submission API/tool for disputes, and any hands-on/independent confirmation that these dispute tools work end-to-end in production.

   • [claimed-docs] “Post-purchase operations are first-class agent tools: refunds via create_refund / get_refund (a "refund for a captured payment", where "If n…”
   • [claimed-docs] “Integrate with PayPal APIs to access orders, invoices, subscriptions, shipment tracking, transaction details, and dispute management through…”
   • [claimed-docs] “The developer portal's REST API getting-started page anchors the agent surface: "REST APIs, including orders, payments, subscriptions, invoi…”
   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using" Amazon Bedrock, CrewAI, LangChain, MCP, OpenA…”

   proof ↗⚑ flag

   Crossmint—none0/10

   The only relevant evidence states that Crossmint itself absorbs dispute risk and manages chargebacks directly with the bank on the user's behalf (crossmint-supp-10), which is for the general Checkout product, not agent-specific. There is no documentation of any developer-facing API for submitting dispute evidence, checking dispute status, or retrieving outcomes. Missing for 10: any dispute-management API endpoints, evidence-submission workflow, or status/outcome reporting for agent transactions.

   • [claimed-docs] “For card checkout, Crossmint absorbs dispute risk: "Crossmint will take on the risk and manage disputes directly with the bank.", using an a…”

   proof ↗⚑ flag

Refunds

1. developerRefunds on agent-placed orders can be initiated and tracked programmatically

   weight 2 · round to PayPal Agentic Commerce
   PayPal Agentic Commerce~partialprobed6/10

   The Agent Toolkit exposes create_refund/get_refund tools and dispute tools (list_disputes, get_dispute, accept_dispute_claim) so refunds on agent-placed orders can be initiated and tracked programmatically via MCP/LangChain/etc., backed by the underlying PayPal REST orders/disputes API and webhooks for status updates. However, the docs don't specifically address refund flows tied to the new agentic-commerce cart/checkout (ACP/UCP) orders, and there's no independent hands-on confirmation of refund success for agent-originated transactions. missing for 10: explicit documentation linking refund/dispute tools to agent-placed (ACP/UCP/Store Sync) orders specifically, and independent/hands-on verification of the refund tracking flow.

   • [claimed-docs] “Post-purchase operations are first-class agent tools: refunds via create_refund / get_refund (a "refund for a captured payment", where "If n…”
   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using" Amazon Bedrock, CrewAI, LangChain, MCP, OpenA…”
   • [claimed-docs] “"Webhooks are HTTPS posts from PayPal to an endpoint on your server whenever the corresponding event type occurs" — "Up to 10 webhook URLs m…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the PayPal Agent Toolkit resolves on the public npm registry (npm view @paypal/agent-toolkit → 1.11.0, …”
   • [claimed-docs] “The developer portal's REST API getting-started page anchors the agent surface: "REST APIs, including orders, payments, subscriptions, invoi…”

   proof ↗⚑ flag

   Crossmint—none0/10

   Evidence covers dispute/chargeback risk absorption for general card Checkout (crossmint-supp-10), but this describes Crossmint handling bank disputes, not a developer-facing refund API for initiating/tracking refunds on agent-placed orders. No refund endpoint, refund object, or tracking mechanism is documented anywhere for Agent Cards, Agent Wallets, or Agent Checkouts. Missing for 10: any refund API/endpoint, refund status tracking, and agent-order-specific refund workflow documentation.

   • [claimed-docs] “For card checkout, Crossmint absorbs dispute risk: "Crossmint will take on the risk and manage disputes directly with the bank.", using an a…”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”
   • [claimed-docs] “Scoped card spending: "An order intent gives the agent a fixed allowance with an amount, description, and expiration, enforced through Visa …”

   proof ↗⚑ flag

Agent identity

1. merchantAgents identify themselves verifiably — registered profiles, signatures, or trust tiers — so I can tell trusted agent traffic from anonymous bots

   weight 3 · round to Crossmint
   PayPal Agentic Commerce—none0/10

   PayPal's docs describe payment-token authentication (Braintree single-use tokens bound to merchant ID), PayPal-issued JWTs for verifying that requests come from PayPal's own Shopping Cart service, and webhook signature verification — but none of this constitutes a verifiable agent identity system (no registered agent profiles, agent-level signatures, or trust tiers that would let a merchant distinguish which specific AI agent or bot is originating traffic). The authentication documented is merchant-to-PayPal or PayPal-to-merchant channel security, not agent-to-merchant identity/trust signaling.

   • [claimed-docs] “Cart execution is a reverse API the merchant hosts: POST /merchant-cart "Creates a new cart with the provided PayPalCart object. This is cal…”
   • [claimed-docs] “The ACP path is an in-ChatGPT checkout build: "Implement an MCP server with the `complete_checkout` tool to receive tokens", "Call `requestC…”
   • [claimed-docs] “"Webhooks are HTTPS posts from PayPal to an endpoint on your server whenever the corresponding event type occurs" — "Up to 10 webhook URLs m…”
   • [probe] “PROBE runtime (recorded 2026-09-14): PayPal's remote MCP server is live — a keyless JSON-RPC initialize POST to https://mcp.paypal.com/mcp a…”

   proof ↗⚑ flag

   Crossmint~partialprobed5/10

   Crossmint's agent stack does embed verifiable-identity mechanisms — onchain delegated signer keys with scoped, revocable permissions (crossmint-supp-4), card-network verified 'Agent Cards' secured by Visa VIC/Mastercard Agent Pay (crossmint-supp-1, -3), and a distinct 'ServerKeyAgent' credential type confirmed live at the Agent Checkouts endpoint (crossmint-probe-rt-1). These give merchants some cryptographic/network-level basis to distinguish agent-initiated, permissioned transactions from anonymous traffic. However, there is no documented merchant-facing registry, trust-tier system, or API for merchants to look up/verify an agent's identity or reputation directly — the verification lives inside Crossmint/card-network infrastructure rather than being exposed as a merchant-consumable signal. Missing for 10: an explicit merchant-facing agent identity/reputation lookup or trust-tier classification, and independent confirmation that merchants can actually distinguish trust levels using this data.

   • [claimed-docs] “Crossmint's agent stack is three composable products, verbatim: Agent Cards — "a card for your agent to pay with, secured by Visa VIC and Ma…”
   • [claimed-docs] “Credentials are one-time and network-verified: minting returns "the secure one-time card number, expiration, and CVC", and verification is a…”
   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Agent Checkouts endpoint is live and agent-scoped — a keyless POST to https://www.crossmint.com/api…”

   proof ↗⚑ flag

Human oversight

1. ai-native userSensitive agent spending requires my documented approval — a confirmation step, signed mandate, or per-purchase consent — before money moves

   weight 3 · round to Crossmint
   PayPal Agentic Commerce~partialclaimed5/10

   PayPal's ACP/UCP flows use single-use, time- and amount-bound delegated tokens tied to a specific merchant and transaction, and the toolkit docs explicitly recommend 'human oversight' for judgment-sensitive actions — both suggest transaction-level guardrails rather than fully autonomous spending. However, the evidence never documents an explicit user-facing confirmation screen, signed mandate artifact, or per-purchase consent UI shown to the end user before the token is used to move money; the checkout flow (requestCheckout/Instant Checkout) is described only at a technical/token level, not from the consent-UX perspective. Missing for 10: an explicit documented consent/confirmation step or mandate artifact shown to the payer, and any independent/hands-on confirmation that this consent step actually blocks unauthorized charges.

   • [claimed-docs] “The ACP path is an in-ChatGPT checkout build: "Implement an MCP server with the `complete_checkout` tool to receive tokens", "Call `requestC…”
   • [claimed-docs] “The UCP path targets Google surfaces: "This enables AI-powered checkout experiences through Google AI Mode (Gemini), where Google Pay return…”
   • [claimed-docs] “"PayPal's agent toolkit supports the integration of PayPal APIs into AI agent workflows using" Amazon Bedrock, CrewAI, LangChain, MCP, OpenA…”
   • [claimed-docs] “Cart execution is a reverse API the merchant hosts: POST /merchant-cart "Creates a new cart with the provided PayPalCart object. This is cal…”

   proof ↗⚑ flag

   Crossmint~partialclaimed6/10

   Crossmint documents strong pre-authorized consent mechanisms — user-signed onchain delegation with spend caps, counterparties, and time windows, plus order-intent 'agent cards' with fixed allowances and expiration — enforced without a per-purchase prompt, and revocable at any time. However, the story asks for documented approval INCLUDING per-purchase consent or signed mandate at time of spend, and Crossmint's model explicitly favors upfront scoped delegation with 'no user prompt per action' rather than a per-transaction confirmation step; this is a deliberate design tradeoff, not a failure, so it's partial rather than disputed. missing for 10: evidence of an optional per-purchase confirmation/step-up flow, independent/hands-on verification of the delegation and revocation actually working in production, and clarity on how disputes/approval work for agent checkouts specifically (dispute coverage is only confirmed for general checkout, not agent checkouts).

   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [claimed-docs] “Scoped card spending: "An order intent gives the agent a fixed allowance with an amount, description, and expiration, enforced through Visa …”
   • [claimed-docs] “"An agent card is an order intent that gives an agent a bounded amount to spend before a fixed expiration." Merchant locking: "The merchant …”
   • [claimed-docs] “Crossmint's agent stack is three composable products, verbatim: Agent Cards — "a card for your agent to pay with, secured by Visa VIC and Ma…”
   • [claimed-docs] “For card checkout, Crossmint absorbs dispute risk: "Crossmint will take on the risk and manage disputes directly with the bank.", using an a…”

   proof ↗⚑ flag

Liability

1. merchantThe fraud, liability, and chargeback rules for agent-initiated transactions are documented so I know who bears the risk

   weight 2 · round to Crossmint
   PayPal Agentic Commerce—none0/10

   Evidence shows general dispute-management and refund tools (list_disputes, accept_dispute_claim, create_refund) and standard PayPal fee/webhook docs, but nothing documents fraud, liability, or chargeback allocation specifically for agent-initiated transactions (e.g., who bears risk when a delegated token or AI agent purchase is disputed). The delegated-token docs mention tokens are 'bound to your merchant ID' but stop short of stating liability shift or chargeback rules for agent-driven checkouts.

   • [claimed-docs] “Post-purchase operations are first-class agent tools: refunds via create_refund / get_refund (a "refund for a captured payment", where "If n…”
   • [claimed-docs] “The ACP path is an in-ChatGPT checkout build: "Implement an MCP server with the `complete_checkout` tool to receive tokens", "Call `requestC…”
   • [claimed-docs] “The published US commercial rates that agent-initiated orders inherit: "PayPal Checkout" and "PayPal Guest Checkout" at "3.49% +" fixed fee,…”
   • [claimed-docs] “"Webhooks are HTTPS posts from PayPal to an endpoint on your server whenever the corresponding event type occurs" — "Up to 10 webhook URLs m…”

   proof ↗⚑ flag

   Crossmint~partialclaimed4/10

   Crossmint documents dispute handling for its general Checkout product (Crossmint absorbs card dispute risk via authorization holds, per crossmint-supp-10) and describes spend caps/order-intent controls for agent cards and wallets, but explicitly notes this chargeback/liability coverage is not specific to agent-initiated transactions. There is no dedicated documentation defining fraud/liability/chargeback allocation rules for agent checkouts or agent-card/agent-wallet flows. missing for 10: explicit agent-transaction-specific liability/chargeback policy, merchant-facing dispute-resolution terms for agent checkouts, and clarity on who bears risk when an agent-initiated purchase is fraudulent or disputed.

   • [claimed-docs] “For card checkout, Crossmint absorbs dispute risk: "Crossmint will take on the risk and manage disputes directly with the bank.", using an a…”
   • [claimed-docs] “Scoped card spending: "An order intent gives the agent a fixed allowance with an amount, description, and expiration, enforced through Visa …”
   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [claimed-docs] “Merchant coverage is URL-universal: "Let your agent buy from any merchant with a single API." — hand it "a product URL and a spending cap, a…”

   proof ↗⚑ flag

Spend controls

1. ai-native userSet per-agent spend caps and usage limits and revoke an agent's payment authority instantly

   weight 2 · round to Crossmint
   PayPal Agentic Commerce—none0/10

   Evidence shows per-transaction delegated tokens with configurable amount/time restrictions bound to a merchant (paypal-ac-supp-acp-chatgpt), but nothing about a user or merchant setting persistent per-agent spend caps/usage limits across multiple transactions, or an instant revoke-authority mechanism for a given agent's payment access. No dashboard, API, or docs reference for agent-level authorization management or revocation is present.

   • [claimed-docs] “The ACP path is an in-ChatGPT checkout build: "Implement an MCP server with the `complete_checkout` tool to receive tokens", "Call `requestC…”
   • [claimed-docs] “The UCP path targets Google surfaces: "This enables AI-powered checkout experiences through Google AI Mode (Gemini), where Google Pay return…”
   • [claimed-docs] “Cart execution is a reverse API the merchant hosts: POST /merchant-cart "Creates a new cart with the provided PayPalCart object. This is cal…”

   proof ↗⚑ flag

   Crossmint✓fullprobed8/10

   Crossmint documents onchain-enforced per-agent spend caps, allowed counterparties, and time windows for agent wallets, plus order-intent allowances with amount/expiration for agent cards, and explicitly states permissions are revocable at any time by the user. This is corroborated by detailed docs on delegation mechanics and a runtime probe confirming agent-scoped auth is live in production. Missing for 10: independent (non-vendor) confirmation that revocation is instantaneous in practice, and no evidence of a unified dashboard/UI for setting caps or revoking across all three agent products (cards, wallets, checkouts) in one place.

   • [claimed-docs] “Scoped card spending: "An order intent gives the agent a fixed allowance with an amount, description, and expiration, enforced through Visa …”
   • [claimed-docs] “Agent wallets are user-owned with onchain-enforced delegation: "The user owns a non-custodial wallet and grants the agent scoped permissions…”
   • [claimed-docs] “Crossmint's agent stack is three composable products, verbatim: Agent Cards — "a card for your agent to pay with, secured by Visa VIC and Ma…”
   • [claimed-docs] “"An agent card is an order intent that gives an agent a bounded amount to spend before a fixed expiration." Merchant locking: "The merchant …”
   • [probe] “PROBE runtime (recorded 2026-09-14): the Agent Checkouts endpoint is live and agent-scoped — a keyless POST to https://www.crossmint.com/api…”

   proof ↗⚑ flag