Stripe Crypto & Stablecoins

Connect an agent via an official MCP server G

Agent access

Drive the product through a documented public API G

Agent access

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

Agent access

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

Agentic features

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

Agent access

Use an official CLI G

Agent access

Build against official SDKs G

Agent access

Operate the product with natural-language commands G

Agentic features

Run the product headlessly / in CI for automation G

Agent access

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

Api quality

Explore an interactive API reference with runnable examples G

Api quality

Rely on versioned APIs with a documented deprecation policy G

Api quality

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

Agentic features

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

Agent access

Set up automations that run autonomously in the background G

Agentic features

Subscribe to events via webhooks G

Agent access

Test against a sandbox environment without touching production data G

Api quality

Take crypto payments but settle in fiat — a documented option to auto-convert stablecoin receipts into a fiat balance or bank payout so my books never hold crypto C

Fiat settlement

Accept a stablecoin payment from a customer through a documented checkout or payment API — create the payment, present the address or flow, and confirm settlement programmatically C

Acceptance

I never operate blockchain infrastructure — the platform abstracts nodes, gas, and chain mechanics behind a conventional REST API with client libraries in my language C

Abstraction

My business can hold a stablecoin balance on the platform — documented custodial accounts with stated availability, geographies, and any gating quoted honestly C

Balances

Send stablecoin payouts programmatically — pay a wallet address or stored recipient through the API with documented status tracking to final settlement C

Payouts

An agent can move stablecoins under scoped authority — documented agent payment flows where an agent initiates a payment or payout with spend controls a human configured C

Agent payments

Define rules that trigger actions automatically on events G

Export all of my data in open formats and leave G

Prevent my data from being used to train AI models G

Rehearse everything without real funds — a documented sandbox or testnet mode covering payments, payouts, and conversions with test values that behave deterministically C

Sandbox

Self-host the core product G

Embed a fiat-to-stablecoin onramp — a documented widget or API where end users buy stablecoins with cards or bank transfers inside my product C

Onramp

The platform documents which stablecoins and chains it supports — USDC, USDT and peers across multiple named networks — so I can match what my customers actually hold C

Chains

The platform speaks the machine-payment protocols by name — x402, ACP, MPP, or AP2 support documented with endpoints or SDKs, not just a blog aspiration C

Protocols

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

Move value between fiat and stablecoin balances on the platform — internal transfers and rebalancing through the API or dashboard, documented end to end C

Treasury

Conversion is a first-class API — quotes and executed conversions between fiat and stablecoins (and between stablecoins) with documented rates, fees, and settlement times C

Conversion

Agents can hold and use wallets safely — programmatic wallet issuance for agents with scoped keys, policy controls, and documented limits on what an agent can move C

Agent wallets

Customer and recipient onboarding is programmatic — documented KYC/KYB endpoints or flows that clear a counterparty for sending and receiving before money moves C

Kyc

Recipients can land in local fiat — documented off-ramp rails that convert stablecoins into bank transfers across a published set of currencies and countries C

Offramp

The platform documents its sanctions screening, wallet risk checks, and travel-rule handling — compliance machinery named specifically, not waved at C

Screening

Create wallets programmatically — per-customer or per-purpose wallets and deposit addresses provisioned through the API with documented key custody semantics C

Wallets

Incoming funds are attributable — named virtual accounts or dedicated deposit addresses per customer so reconciliation knows who paid without manual matching C

Virtual accounts

Run mass disbursements — batch or bulk payout APIs that push many stablecoin or fiat payouts in one documented operation with per-item status C

Batch

See who I'm actually contracting with — the licensed or registered entities behind the product and the jurisdictions they cover, published rather than buried C

Licensing

Settlement is legible — documented timing from payment to available balance, published fees per rail, and statements or reports my accounting can consume C

Settlement

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

Control data retention and deletion G

Issue a branded stablecoin on the platform's infrastructure — a documented issuance product covering minting, redemption, and reserve management, with its gating quoted honestly C

Issuance

Money movement emits signed webhooks — payment confirmed, payout settled, conversion executed — so my system tracks state without polling chains or dashboards C

Webhooks

Opt out of telemetry and usage tracking G

Perform bulk operations across many items at once G

Read the product's source under an open license G

Schedule recurring jobs or workflows G

The economics of held stablecoins are documented — reserve composition, attestations, and any yield or rewards program with its eligibility and regulatory caveats stated plainly C

Yield

Version, review, and roll back my automations G