Skyfire · closed-loop card-network agent payment issuer

Wiki route

This entry sits under AI Agent payment protocols seven-protocol overview. Read it against x402 · HTTP 402 stablecoin rail and AP2 · Google mandate protocol for peer / contrast, Visa / Mastercard agentic-commerce pilots for card-network framing, and payments index for the broader regulatory boundary.

Key facts

• Skyfire raised Series A in 2024-2025 to operate as an agent payment issuer — a closed-loop platform where AI agents get an identity + funded virtual card
• Partnership with Visa for card rails and Visa Trusted Agent Protocol alignment
• Stripe / Visa-issued virtual cards routed through Skyfire’s agent-identity layer
• Contrast with x402 (HTTP + USDC stablecoin) and AP2 (mandate VC over multiple rails)
• Closed-loop = Skyfire mints agent identity, issues card, sets spend caps, monitors merchant authorization in one bundle

Mechanism — what closed-loop means here

Skyfire’s architecture compresses three functions into one operator:

1. Agent identity / KYA (Know-Your-Agent) — Skyfire onboards the agent, verifies controlling principal, stores identity proofs
2. Virtual card issuance — Visa-network card with merchant-category whitelist, per-transaction cap, daily / monthly ceiling
3. Authorization gateway — when agent calls merchant API, Skyfire authorizes against scoped rules in real time

Compared with the open-protocol stack:

The closed-loop model trades interoperability for fast onboarding + clean liability: merchants accept Skyfire-routed cards as ordinary card transactions, chargeback / dispute follow standard Visa rails (read agent actorship debate for liability framing).

Where Skyfire sits in the seven-protocol map

• HTTP transport: not opinionated (works over any agent runtime)
• Authorization layer: proprietary (vs AP2’s W3C VC standard)
• Settlement layer: Visa card rail (vs x402’s USDC, AP2’s multi-rail)
• Identity layer: Skyfire KYA (vs decentralized agent identity via ERC-7715)

Practical implication: Skyfire is the fastest path to “agent has a payment instrument that any merchant already accepts” — but locks the agent inside Skyfire’s risk perimeter. Contrast with Stripe Agent Toolkit which provides issuing primitives without the closed-loop opinionation.

Competitive positioning

Origin and evolution

Skyfire emerged from the 2024 “agents need payment instruments” wave alongside Stripe Agent Toolkit, Visa’s Trusted Agent Protocol announcements, and Coinbase CDP agent SDK. The bet: card networks remain the merchant-acceptance default for years, so wrapping agents in a card-network-native issuance layer is a real business — even if x402 / stablecoin rails grow underneath.

Series A investors / partners (Visa, prior Anthropic ecosystem signaling) point to the enterprise-issuer-distribution thesis: enterprises buying AI agents want one bill, audit trail, and policy-controlled card — not a USDC wallet. Skyfire fills that procurement-friendly slot.

Related

• INDEX
• ai-agent-payment-protocols-overview
• x402-http-payment-overview
• ap2-overview
• visa-mastercard-agentic-commerce-pilots
• stripe-agent-toolkit-position
• coinbase-cdp-developer-platform
• erc-7715-overview
• agent-actorship-debate
• INDEX
• FinWiki index

Sources

• skyfire.xyz product pages and documentation.
• Visa: agentic-commerce program and Trusted Agent Protocol announcements.
• Stripe newsroom: agent-issuing partner program references.
• Coverage of Series A funding and Visa partnership.