SYSTEM Cited by 1 source

Stripe Projects

Stripe Projects is a CLI + plugin from Stripe (in open beta at launch, 2026-04-30) that plays the orchestrator role in the agent-provisioning protocol co-designed with Cloudflare. Stripe Projects ships as part of the Stripe CLI; once installed, an agent can discover, provision, and pay for services at participating providers without taking the user out of the agent session.

Canonical URL: docs.stripe.com/projects.

What it does

Three commands carry the entire flow:

• stripe projects init — starts a new project bound to the Stripe-logged-in user's identity. After this command, every subsequent provider resource in the project is attested against that identity and billable against the user's Stripe payment method.
• stripe projects catalog — returns a JSON catalog of services offered across all participating providers. The agent reads this to discover what it can provision. Each provider (currently Cloudflare at launch, with more to follow) exposes a simple REST endpoint returning JSON that the Stripe Projects aggregator calls.
• stripe projects add <provider>/<service>:<resource-type> — provisions a specific resource. At launch the canonical example is stripe projects add cloudflare/registrar:domain.

Orchestrator role

Stripe Projects performs three load-bearing functions in the agent-provisioning protocol:

1. Identity attestation. The CLI is already logged in to Stripe; the user's email + account is used to attest identity to each provider. Providers either match to an existing account (drive OAuth) or auto-provision a new account keyed to the attested identity (see concepts/agent-provisioned-account).
2. Payment-token issuance. The CLI forwards a payment token — not raw card data — with each paid provisioning call; the provider redeems the token against Stripe for settlement. See concepts/payment-token-over-credit-card-sharing and PaymentIntents.
3. Spend-cap enforcement. Stripe Projects sets a default $100/month-per-provider ceiling on agent-initiated charges. Users can raise the cap explicitly; providers (e.g. Cloudflare) pair it with their own usage-dashboard surface. Canonical concepts/agent-payment-budget-cap.

Credential custody

An important design choice: credentials returned by providers (API tokens, OAuth access tokens, account IDs) are "securely stored" by the Stripe Projects CLI and "available to the agent to use to make authenticated requests" — the agent does not hold the credentials directly, it issues requests through the CLI's credential store. This makes revocation a single local action (delete the Stripe project) rather than a scatter of tokens across every provider the agent has touched.

Open-beta posture

• Launched 2026-04-30 in open beta.
• Covered providers: Cloudflare (first-party partnership); any platform offering signed-in users and a service catalog can add itself per the protocol framing.
• Stripe Atlas incorporations come with a promotional $100,000 in Cloudflare credits through Stripe Projects.

Peer systems

• Code Mode (Cloudflare) — the MCP surface the agent uses after provisioning to call Cloudflare APIs efficiently. Code Mode compresses ~3,000 Cloudflare operations into <1,000 tokens; Stripe Projects gets the agent access to the platform so Code Mode has something to drive.
• Agent Skills — the task-level how-to documents an agent reads to perform specific tasks. Stripe Projects is orthogonal (access) to Agent Skills (know-how). Both compose; neither subsumes the other.
• MCP servers more broadly — see systems/model-context-protocol. Stripe Projects is positioned above MCP: the CLI issues MCP calls (or equivalent provider APIs) on behalf of the agent once provisioning is done.

What's not disclosed

• Token TTL + refresh cadence for OAuth access tokens.
• Catalog freshness / invalidation policy.
• Multi-agent-per-project consent model.
• Fraud / abuse heuristics for auto-provisioned accounts.
• Provider onboarding cost (what a new provider implements to join the catalog beyond "a simple REST API returning JSON").
• Formal protocol specification — per the launch, "a more official specification" is forthcoming.

Seen in

• sources/2026-04-30-cloudflare-agents-can-now-create-cloudflare-accounts-buy-domains-and-deploy — launch post; canonicalises Stripe Projects as the orchestrator role in the protocol.

Related

• systems/stripe-api — Stripe's broader REST API.
• systems/stripe-paymentintents-api — the payment rail Stripe Projects composes over.
• systems/cloudflare-registrar — first provider service exposed via the catalog at launch.
• systems/code-mode — the post-provisioning agent-API surface on the Cloudflare side.
• systems/agent-skills — task-level agent documentation complementing the protocol's access story.
• patterns/agent-provisioning-protocol — the three- component pattern Stripe Projects instantiates.
• patterns/orchestrator-provider-agent-trust-triangle — the role topology.
• concepts/agent-provisioned-account, concepts/provider-service-catalog-api, concepts/agent-payment-budget-cap, concepts/payment-token-over-credit-card-sharing — the four concepts the launch post contributes.
• companies/stripe, companies/cloudflare.