Visa Intelligent Commerce

Drive the product through a documented public API G

Agent access

Connect an agent via an official MCP server G

Agent access

Delegate tasks to a built-in AI assistant inside the product G

Agentic features

Plug MCP servers into this product so it can use their tools G

Agent access

Point an agent at llms.txt or agent-oriented docs G

Agent access

Build against official SDKs G

Agent access

Issue scoped/least-privilege API credentials for an agent G

Agent access

Download a machine-readable API spec (OpenAPI or equivalent) G

Api quality

Operate the product with natural-language commands G

Agentic features

Run the product headlessly / in CI for automation G

Agent access

Set up automations that run autonomously in the background G

Agentic features

Rely on versioned APIs with a documented deprecation policy G

Api quality

Explore an interactive API reference with runnable examples G

Api quality

Use an official CLI G

Agent access

Get AI-generated insights and suggestions from my data inside the product G

Agentic features

Subscribe to events via webhooks G

Agent access

Test against a sandbox environment without touching production data G

Api quality

Hand my agent a scoped, limited-use payment credential — amount limits, expiry, merchant restrictions — instead of a raw card number C

Delegated credentials

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

Agent identity

My agent can complete a purchase end-to-end — checkout session, delegated payment credential, confirmed order C

Checkout

Sensitive agent spending requires my documented approval — a confirmation step, signed mandate, or per-purchase consent — before money moves C

Human oversight

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

My agent can create and update a cart or order draft through a documented protocol call C

Cart

Define rules that trigger actions automatically on events G

Monetize an API or service with HTTP 402 machine payments that agents pay per call without a checkout UI C

Machine payments

Provision a wallet my agent holds and spends from — funded and controlled by me, with balance visibility C

Wallets

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

Spec publication

My agent or backend can subscribe to order lifecycle events — created, updated, fulfilled, canceled — pushed programmatically C

Order events

Export all of my data in open formats and leave G

My agent can programmatically search products or services across merchants — keylessly or with self-service credentials, no private partnership required C

Agent search

Prevent my data from being used to train AI models G

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

Self-host the core product G

Set per-agent spend caps and usage limits and revoke an agent's payment authority instantly G

Spend controls

Build against a versioned commerce protocol with a published schema and conformance or validation tooling C

Protocol conformance

Buyers can complete purchases of my products inside chat and assistant surfaces (ChatGPT, Claude, Gemini, Copilot and peers) C

Embedded surfaces

My agent can discover payable services and APIs through a published directory or discovery index C

Service discovery

Rate-limit, allow, or deny specific agents and agent platforms accessing my catalog and checkout C

Traffic controls

Orders are attributed to the originating agent and I can report on or filter transactions by agent C

Attribution analytics

Read the product's source under an open license G

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

Liability

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

Ecosystem adoption

Control data retention and deletion G

Disputes and chargebacks on agent transactions can be handled via API — evidence submission, status, outcomes C

Disputes

My agent can query the status and tracking of an order it placed, after the purchase C

Post purchase status

Perform bulk operations across many items at once G

Refunds on agent-placed orders can be initiated and tracked programmatically C

Refunds

Settle agent-initiated payments in stablecoins over documented rails C

Settlement rails

The fees for agent-originated transactions are published — I can price agentic channels without asking sales C

Fees transparency

Choose where my data is stored (region/residency) G

Do everything through the API that I can do in the UI G

Opt out of telemetry and usage tracking G

Read machine-readable offer data — price, availability, variants, checkout links — for any listed product or service C

Machine readable offers

Schedule recurring jobs or workflows G

Agent-originated payments settle through documented payout and reporting flows, reconcilable like any other channel C

Payouts

Version, review, and roll back my automations G