An AI agent picks Twilio, pays for it, and connects it — all on its own. Your job? Nothing.
What Is This?
Sapiom is a startup building the financial layer that lets AI agents directly purchase and access software, APIs, data, and compute. Founded by Ilan Zerbib, a former Shopify payments engineering director, it closed a $15.75M seed round led by Accel.
The investor lineup is telling — Accel, Gradient Ventures (Google), Menlo Ventures, Okta Ventures, Anthropic, and Coinbase Ventures all joined. Payments, AI, authentication, and crypto players all at one table.
The core idea is simple. When an AI agent needs to send SMS via Twilio or spin up an AWS server, someone currently has to manually sign up, add a credit card, and copy API keys. Sapiom makes the agent handle all of that autonomously.
Accel's Amit Kumar puts it this way: "Every API call is a payment. Every text message, every server spin-up — it's all a payment".
Why Does It Matter?
| Current Approach | Sapiom Approach | |
|---|---|---|
| API connection | Manual signup + card + API key | Agent auto-purchases + connects |
| Payment actor | Human (developer/admin) | AI agent (usage-based) |
| Scalability | Manual setup per service | Agent scales on demand |
| Vibe coding | Backend infra required | Built into Lovable/Bolt |
Vibe coders benefit first. When someone builds an app on Lovable and needs SMS or payments, they won't have to manually sign up for Twilio or Stripe. Sapiom handles it in the background as a pass-through fee.
The bigger picture is that agents are becoming independent economic actors. Stripe's x402 protocol already lets AI agents pay $0.01 USDC per API request. Visa launched CLI-based agent payment infrastructure too. Sapiom is the next step in this evolution.
If you run a SaaS
When agents choose tools autonomously, traditional "compare and pick" SaaS marketing loses relevance. API documentation quality and pricing transparency become the new marketing.
How to Prepare
- Understand the agent payment ecosystem
Sapiom, Visa CLI, Stripe x402 — the infrastructure for agents to spend money is already being built. Don't miss the trend. - Audit your API strategy
Check if your SaaS product is agent-friendly. Clear API docs and usage-based pricing are key. - Test vibe coding platforms
Try connecting external services on Lovable, Bolt, or Replit. That experience will mirror what agents face. - Design agent budget governance
When giving agents payment authority, pre-define spending limits and approval rules. An agent once spent $8,000 on courses because it thought they'd be "helpful".
Caution: Autonomous spending risks
An AI agent reportedly spent $8,000 on online courses because it judged them "work-relevant". Not a bug — an agent judgment call. Autonomous purchasing always needs limits and approval workflows.
