← Back to Payloads
AI2026-04-12

Mercury nears $5B valuation 🚀, Payment rails for AI agents 🤖, Bolt fires 1/3 sta

Mercury is in late-stage talks to raise at a $5B+ valuation, up from $3.5B a year ago, while simultaneously acquiring payroll startup Central ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌  ‌ ‌ ‌...
Mercury nears $5B valuation 🚀, Payment rails for AI agents 🤖, Bolt fires 1/3 sta
**TL;DR** - Mercury Bank closes on $5B valuation; emerging payment rails infrastructure purpose-built for AI agents.

The 10-Second Pitch

  • Mercury valuation jump reflects business banking market opportunity for tech-native companies
  • Agent-native payment rails (programmable, API-first, sub-second settlement) now a funded category
  • Bolt second act involves AI agent payment delegation - letting agents pay on behalf of users with limits

Setup in 3 Steps

1. If building agentic payment workflows, Mercury API most developer-friendly option right now

2. Design agent payment primitives around idempotency - agents retry, and retries must be safe

3. Evaluate whether your current payment stack handles agent-initiated sub-minute settlements

**Example Prompt:**

Design a payment authorization system for an AI agent that makes purchases up to $50 without user confirmation.

Verdict

ProsCons
Mercury API genuinely goodMercury does not support international payments well

AI agent payment infrastructure race underfunded relative to the problem. Watch this space.

#ai#automation
Related Dispatches
AI
🦞 Claude's AI agent usage problem
Read dispatch →
AI
Claude Codes new UI , Codex Scratchpad , multi-agent coordin
Read dispatch →
AI
Org design in the age of AI , focus is expensive , writing a
Read dispatch →
AI
Your AI Agent Team is Live
Read dispatch →
← All payloads
Agent-native payments is a real categoryRegulatory compliance for agent-initiated payments unclear
Bolt retry and idempotency handling is matureStill early days for agent payment UX