Try itExperimental
See what an agent can do with Crossmint before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -s -X POST https://www.crossmint.com/api/unstable/agent-checkouts -d '{}' # live endpoint, names its agent credential in the challengerecorded session — replayed, not liveVerified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Agent checkout — stories about agent checkout in this arenaAgent checkoutevidence →
Stories about agent checkout in this arena
Agent discovery — stories about agent discovery in this arenaAgent discoveryevidence →
Stories about agent discovery in this arena
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Fees economics — stories about fees economics in this arenaFees economicsevidence →
Stories about fees economics in this arena
Merchant enablement — stories about merchant enablement in this arenaMerchant enablementevidence →
Stories about merchant enablement in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Order lifecycle — stories about order lifecycle in this arenaOrder lifecycleevidence →
Stories about order lifecycle in this arena
Payment credentials — stories about payment credentials in this arenaPayment credentialsevidence →
Stories about payment credentials in this arena
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Protocol openness — stories about protocol openness in this arenaProtocol opennessevidence →
Stories about protocol openness in this arena
Refunds disputes — stories about refunds disputes in this arenaRefunds disputesevidence →
Stories about refunds disputes in this arena
Trust safety — stories about trust safety in this arenaTrust safetyevidence →
Stories about trust safety in this arena
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 2 free · 0 paid · 0 enterprise · 19 not stated in evidence
Follow the green: where the map greys out is where Crossmint stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agent checkout — stories about agent checkout in this arenaAgent checkout
Stories about agent checkout in this arena
My agent can create and update a cart or order draft through a documented protocol call
✓8/10
My agent can complete a purchase end-to-end — checkout session, delegated payment credential, confirmed order
✓8/10
Buyers can complete purchases of my products inside chat and assistant surfaces (ChatGPT, Claude, Gemini, Copilot and peers)
~3/10
Build against a versioned commerce protocol with a published schema and conformance or validation tooling
—0/10
Agent discovery — stories about agent discovery in this arenaAgent discovery
Stories about agent discovery in this arena
My agent can programmatically search products or services across merchants — keylessly or with self-service credentials, no private partnership required
—0/10
Read machine-readable offer data — price, availability, variants, checkout links — for any listed product or service
—0/10
Publish my product or service catalog into agent surfaces through a documented feed or import API so AI agents can discover what I sell
n/an/a
My agent can discover payable services and APIs through a published directory or discovery index
—–
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Webhooks · Machine-readable spec · Versioning policy · Full data export · Build against a versioned commerce protocol with a published schema and conformance or validation tooling · My agent can programmatically search products or services across merchants — keylessly or with self-service credentials, no private partnership required · Read machine-readable offer data — price, availability, variants, checkout links — for any listed product or service · My agent can discover payable services and APIs through a published directory or discovery index
Subscribe to events via webhooks
—0/10
Build against official SDKs
~5/10
Issue scoped/least-privilege API credentials for an agent
✓7/10
Connect an agent via an official MCP server
n/an/a
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—–
Test against a sandbox environment without touching production data
~4/10
Explore an interactive API reference with runnable examples
—0/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
n/an/a
Operate the product with natural-language commands
—0/10
Plug MCP servers into this product so it can use their tools
n/an/a
Get AI-generated insights and suggestions from my data inside the product
n/an/a
Set up automations that run autonomously in the background
~5/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Fees economics — stories about fees economics in this arenaFees economics
Stories about fees economics in this arena
Merchant enablement — stories about merchant enablement in this arenaMerchant enablement
Stories about merchant enablement in this arena
Orders are attributed to the originating agent and I can report on or filter transactions by agent
—–
I have a documented self-serve path to start accepting agent traffic — enable a setting, sign an agreement, or publish an endpoint
—–
Rate-limit, allow, or deny specific agents and agent platforms accessing my catalog and checkout
—0/10
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Order lifecycle — stories about order lifecycle in this arenaOrder lifecycle
Stories about order lifecycle in this arena
Payment credentials — stories about payment credentials in this arenaPayment credentials
Stories about payment credentials in this arena
Hand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card number
✓9/10
Monetize an API or service with HTTP 402 machine payments that agents pay per call without a checkout UI
—0/10
Settle agent-initiated payments in stablecoins over documented rails
✓8/10
Provision a wallet my agent holds and spends from — funded and controlled by me, with balance visibility
~7/10
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Protocol openness — stories about protocol openness in this arenaProtocol openness
Stories about protocol openness in this arena
Refunds disputes — stories about refunds disputes in this arenaRefunds disputes
Stories about refunds disputes in this arena
Trust safety — stories about trust safety in this arenaTrust safety
Stories about trust safety in this arena
Agents identify themselves verifiably — registered profiles, signatures, or trust tiers — so I can tell trusted agent traffic from anonymous bots
~5/10
Sensitive agent spending requires my documented approval — a confirmation step, signed mandate, or per-purchase consent — before money moves
~6/10
The fraud, liability, and chargeback rules for agent-initiated transactions are documented so I know who bears the risk
~4/10
Set per-agent spend caps and usage limits and revoke an agent's payment authority instantly
✓8/10
Sorted by importance (agentic first) (high → low) · 56/56 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Cclaimed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partial | 4/10 | Cclaimed | |
Hand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card number C Delegated credentials | ai-native user | Payment credentials — stories about payment credentials in this arenaPayment credentials | 3 | full | 9/10 | Tprobed | |
My agent can complete a purchase end-to-end — checkout session, delegated payment credential, confirmed order C Checkout | ai-native user | Agent checkout — stories about agent checkout in this arenaAgent checkout | 3 | full | 8/10 | Tprobed | |
My agent can create and update a cart or order draft through a documented protocol call C Cart | ai-native user | Agent checkout — stories about agent checkout in this arenaAgent checkout | 3 | full | 8/10 | Tprobed | |
Provision a wallet my agent holds and spends from — funded and controlled by me, with balance visibility C Wallets | ai-native user | Payment credentials — stories about payment credentials in this arenaPayment credentials | 3 | partialfree | 7/10 | Cclaimed | |
Sensitive agent spending requires my documented approval — a confirmation step, signed mandate, or per-purchase consent — before money moves C Human oversight | ai-native user | Trust safety — stories about trust safety in this arenaTrust safety | 3 | partial | 6/10 | Cclaimed | |
Agents identify themselves verifiably — registered profiles, signatures, or trust tiers — so I can tell trusted agent traffic from anonymous bots C Agent identity | merchant | Trust safety — stories about trust safety in this arenaTrust safety | 3 | partial | 5/10 | Tprobed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | partial | 4/10 | Cclaimed | |
Monetize an API or service with HTTP 402 machine payments that agents pay per call without a checkout UI C Machine payments | developer | Payment credentials — stories about payment credentials in this arenaPayment credentials | 3 | none | 0/10 | ||
My agent can programmatically search products or services across merchants — keylessly or with self-service credentials, no private partnership required C Agent search | ai-native user | Agent discovery — stories about agent discovery in this arenaAgent discovery | 3 | none | 0/10 | ||
My agent or backend can subscribe to order lifecycle events — created, updated, fulfilled, canceled — pushed programmatically C Order events | developer | Order lifecycle — stories about order lifecycle in this arenaOrder lifecycle | 3 | none | 0/10 | ||
The commerce protocol this product speaks is published as an open, versioned specification I can read and implement without signing anything C Spec publication | developer | Protocol openness — stories about protocol openness in this arenaProtocol openness | 3 | none | 0/10 | ||
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
I have a documented self-serve path to start accepting agent traffic — enable a setting, sign an agreement, or publish an endpoint C Onboarding to agents | merchant | Merchant enablement — stories about merchant enablement in this arenaMerchant enablement | 3 | none | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | n/a | untested | none yet | |
Publish my product or service catalog into agent surfaces through a documented feed or import API so AI agents can discover what I sell C Merchant feeds | merchant | Agent discovery — stories about agent discovery in this arenaAgent discovery | 3 | n/a | untested | none yet | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | n/a | untested | none yet | |
Set per-agent spend caps and usage limits and revoke an agent's payment authority instantly G Spend controls | ai-native user | Trust safety — stories about trust safety in this arenaTrust safety | 2 | full | 8/10 | Tprobed | |
Settle agent-initiated payments in stablecoins over documented rails C Settlement rails | developer | Payment credentials — stories about payment credentials in this arenaPayment credentials | 2 | fullfree | 8/10 | Tprobed | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 6/10 | Tprobed | |
My agent can query the status and tracking of an order it placed, after the purchase C Post purchase status | ai-native user | Order lifecycle — stories about order lifecycle in this arenaOrder lifecycle | 2 | partial | 6/10 | Cclaimed | |
The fraud, liability, and chargeback rules for agent-initiated transactions are documented so I know who bears the risk C Liability | merchant | Trust safety — stories about trust safety in this arenaTrust safety | 2 | partial | 4/10 | Cclaimed | |
Buyers can complete purchases of my products inside chat and assistant surfaces (ChatGPT, Claude, Gemini, Copilot and peers) C Embedded surfaces | merchant | Agent checkout — stories about agent checkout in this arenaAgent checkout | 2 | partial | 3/10 | Cclaimed | |
Build against a versioned commerce protocol with a published schema and conformance or validation tooling C Protocol conformance | developer | Agent checkout — stories about agent checkout in this arenaAgent checkout | 2 | none | 0/10 | ||
Disputes and chargebacks on agent transactions can be handled via API — evidence submission, status, outcomes C Disputes | developer | Refunds disputes — stories about refunds disputes in this arenaRefunds disputes | 2 | none | 0/10 | ||
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | 0/10 | ||
Rate-limit, allow, or deny specific agents and agent platforms accessing my catalog and checkout C Traffic controls | merchant | Merchant enablement — stories about merchant enablement in this arenaMerchant enablement | 2 | none | 0/10 | ||
Read machine-readable offer data — price, availability, variants, checkout links — for any listed product or service C Machine readable offers | developer | Agent discovery — stories about agent discovery in this arenaAgent discovery | 2 | none | 0/10 | ||
Refunds on agent-placed orders can be initiated and tracked programmatically C Refunds | developer | Refunds disputes — stories about refunds disputes in this arenaRefunds disputes | 2 | none | 0/10 | ||
The fees for agent-originated transactions are published — I can price agentic channels without asking sales C Fees transparency | merchant | Fees economics — stories about fees economics in this arenaFees economics | 2 | none | 0/10 | ||
At least two independent parties beyond the vendor implement the protocol or platform — it is an ecosystem, not a private integration C Ecosystem adoption | developer | Protocol openness — stories about protocol openness in this arenaProtocol openness | 2 | none | untested | none yet | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | n/a | untested | none yet | |
My agent can discover payable services and APIs through a published directory or discovery index C Service discovery | ai-native user | Agent discovery — stories about agent discovery in this arenaAgent discovery | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | n/a | untested | none yet | |
Orders are attributed to the originating agent and I can report on or filter transactions by agent C Attribution analytics | merchant | Merchant enablement — stories about merchant enablement in this arenaMerchant enablement | 2 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | n/a | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | n/a | untested | none yet | |
Agent-originated payments settle through documented payout and reporting flows, reconcilable like any other channel C Payouts | merchant | Fees economics — stories about fees economics in this arenaFees economics | 1 | partial | 3/10 | Cclaimed | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | n/a | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 35 stories with headroom
What would move Crossmint’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agent discovery — stories about agent discovery in this arenaMy agent can programmatically search products or services across merchants — keylessly or with self-service credentials, no private partnership required
nonemoves PA Scoreimpact 30
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.
Payment credentials — stories about payment credentials in this arenaMonetize an API or service with HTTP 402 machine payments that agents pay per call without a checkout UI
nonemoves PA Scoreimpact 30
Missing: 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.
Merchant enablement — stories about merchant enablement in this arenaI have a documented self-serve path to start accepting agent traffic — enable a setting, sign an agreement, or publish an endpoint
nonemoves PA Scoreimpact 30
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.
Protocol openness — stories about protocol openness in this arenaThe commerce protocol this product speaks is published as an open, versioned specification I can read and implement without signing anything
nonemoves PA Scoreimpact 30
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.
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
Missing: any documented data export feature, open-format (e.g., CSV/JSON) export tooling, or explicit portability/exit guarantees for user data.
Order lifecycle — stories about order lifecycle in this arenaMy agent or backend can subscribe to order lifecycle events — created, updated, fulfilled, canceled — pushed programmatically
nonemoves PA Scoreimpact 30
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).
Agenticness — how well agents can access and operate the productOperate the product with natural-language commands
nonemoves Built-in AIimpact 30
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.
Agenticness — how well agents can access and operate the productSubscribe to events via webhooks
nonemoves agent-readyimpact 30
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.
Showing the top 8 of 35 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map6 surfaces · 21 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
Agents docs21 stories
- My agent can create and update a cart or order draft through a documented protocol call
- My agent can complete a purchase end-to-end — checkout session, delegated payment credential, confirmed order
- Buyers can complete purchases of my products inside chat and assistant surfaces (ChatGPT, Claude, Gemini, Copilot and peers)
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Issue scoped/least-privilege API credentials for an agent
- Build against official SDKs
- Set up automations that run autonomously in the background
- Test against a sandbox environment without touching production data
- Define rules that trigger actions automatically on events
- Agent-originated payments settle through documented payout and reporting flows, reconcilable like any other channel
- Do everything through the API that I can do in the UI
- My agent can query the status and tracking of an order it placed, after the purchase
- Hand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card number
- Settle agent-initiated payments in stablecoins over documented rails
- Provision a wallet my agent holds and spends from — funded and controlled by me, with balance visibility
- Agents identify themselves verifiably — registered profiles, signatures, or trust tiers — so I can tell trusted agent traffic from anonymous bots
- Sensitive agent spending requires my documented approval — a confirmation step, signed mandate, or per-purchase consent — before money moves
- The fraud, liability, and chargeback rules for agent-initiated transactions are documented so I know who bears the risk
- Set per-agent spend caps and usage limits and revoke an agent's payment authority instantly
Payments docs5 stories
- Run the product headlessly / in CI for automation
- Agent-originated payments settle through documented payout and reporting flows, reconcilable like any other channel
- Do everything through the API that I can do in the UI
- Sensitive agent spending requires my documented approval — a confirmation step, signed mandate, or per-purchase consent — before money moves
- The fraud, liability, and chargeback rules for agent-initiated transactions are documented so I know who bears the risk
OpenAPI spec4 stories
Wallets docs4 stories
llms.txt2 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -s -X POST https://www.crossmint.com/api/unstable/agent-checkouts -d '{}' # live endpoint, names its agent credential in the challengereproduced$ curl -s -X POST https://www.crossmint.com/api/unstable/agent-checkouts -d '{}' # live endpoint, names its agent credential in the challenge
{"error":true,"message":"Authentication required. Supported methods: [API [redacted], Server[redacted]Agent]."}
$curl -s https://docs.crossmint.com/llms.txt | head -3reproduced$ curl -s https://docs.crossmint.com/llms.txt | head -3 # Crossmint > Crossmint is a blockchain infrastructure platform for developers. It provides smart wallets, user identity (KYC/KYB), stablecoin orchestration, checkout for onchain and physical-world assets, fiat-to-stablecoin onramp, stablecoin-to-fiat offramp, [redacted]ization (NFTs, credentials, IP), and payment infrastructure for AI agents — all across 50+ blockchains through a single API.
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
4 of 8 testable claims verified · 2 contradicted → integrity 0/100
15 distinct capability claims found in Crossmint’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
4
Verified
2
Unverified
2
Contradicted
15
Undersold
Verified (8)
“Tutorial shows creating a user-owned smart wallet, authorizing an agent as a delegated signer, and sending stablecoin on a testnet”
Set per-agent spend caps and usage limits and revoke an agent's payment authority instantlyfullproof ↗
“Crossmint wallets pay HTTP 402 endpoints: on 402, signs stablecoin payment, retries with proof, extracts onchain settlement receipt from headers”
Settle agent-initiated payments in stablecoins over documented railsfullproof ↗
“Agent can be given a product URL and a spending cap; Crossmint completes checkout with any merchant using any payment method the merchant accepts”
My agent can complete a purchase end-to-end — checkout session, delegated payment credential, confirmed orderfullproof ↗
“Agent card order intents track total, reserved, spent, and available amounts, stopping automatically when cancelled, expired, or fully spent”
Hand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card numberfullproof ↗
“Agent card order intents are locked to a single merchant for their lifetime, with an RSA-encrypted card fallback when no card-network rail is available”
Hand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card numberfullproof ↗
“Agent cards mint one-time card numbers verified via card-network passkey ceremonies, scoped to Mastercard and eligible U.S. Visa cards”
Hand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card numberfullproof ↗
“User-owned, non-custodial agent wallets grant agents onchain-enforced permissions (spend cap, counterparties, time window) that the user can revoke at any time”
Set per-agent spend caps and usage limits and revoke an agent's payment authority instantlyfullproof ↗
“Transaction rules can be enforced directly onchain”
Set per-agent spend caps and usage limits and revoke an agent's payment authority instantlyfullproof ↗
Unverified (4)
“Single API provides secure, programmable smart-wallet infrastructure configurable for any use case”
Provision a wallet my agent holds and spends from — funded and controlled by me, with balance visibilitypartialproof ↗
“Tutorial shows creating a user-owned smart wallet, authorizing an agent as a delegated signer, and sending stablecoin on a testnet”
Provision a wallet my agent holds and spends from — funded and controlled by me, with balance visibilitypartialproof ↗
“User-owned, non-custodial agent wallets grant agents onchain-enforced permissions (spend cap, counterparties, time window) that the user can revoke at any time”
Provision a wallet my agent holds and spends from — funded and controlled by me, with balance visibilitypartialproof ↗
“For card checkout, Crossmint absorbs chargeback/dispute risk and uses an authorization-hold-then-capture model with a $2,000/user/day default limit”
The fraud, liability, and chargeback rules for agent-initiated transactions are documented so I know who bears the riskpartialproof ↗
Contradicted (3)
“Crossmint wallets pay HTTP 402 endpoints: on 402, signs stablecoin payment, retries with proof, extracts onchain settlement receipt from headers”
Monetize an API or service with HTTP 402 machine payments that agents pay per call without a checkout UInoneproof ↗
“Crossmint wallets pay Machine Payment Protocol (MPP) endpoints via the mppx client, settling through Tempo and retrying the request automatically”
Monetize an API or service with HTTP 402 machine payments that agents pay per call without a checkout UInoneproof ↗
“Published pricing: wallets free for first 1,000 MAUs, then $0.05/MAU with volume discounts; checkout/onramp/offramp fees are tiered per transaction”
The fees for agent-originated transactions are published — I can price agentic channels without asking salesnoneproof ↗
Undersold (15)
My agent can create and update a cart or order draft through a documented protocol callfullproof ↗
Buyers can complete purchases of my products inside chat and assistant surfaces (ChatGPT, Claude, Gemini, Copilot and peers)partialproof ↗
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Drive the product through a documented public APIfullproof ↗
Issue scoped/least-privilege API credentials for an agentfullproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Test against a sandbox environment without touching production datapartialproof ↗
Define rules that trigger actions automatically on eventspartialproof ↗
Agent-originated payments settle through documented payout and reporting flows, reconcilable like any other channelpartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
My agent can query the status and tracking of an order it placed, after the purchasepartialproof ↗
Agents identify themselves verifiably — registered profiles, signatures, or trust tiers — so I can tell trusted agent traffic from anonymous botspartialproof ↗
Sensitive agent spending requires my documented approval — a confirmation step, signed mandate, or per-purchase consent — before money movespartialproof ↗
Claims outside our story set (3)
Real capability claims found in Crossmint’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Headless checkout REST API lets developers embed credit-card and cross-chain crypto payments with full control of the user experience”
source ↗“Programmable wallets can manage and move company treasury funds at scale”
source ↗“A single order intent can span multiple payment rails, each with its own status, credential format, and verification”
source ↗
Business model
Start free and pay as you go per product line — e.g. 1,000 monthly active wallets free then from $0.05 per wallet; agent cards, checkout, and stablecoin rails are priced per use with custom enterprise tiers.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
