Mercury

What it is

Mercury is a digital bank designed for startups and tech companies. It offers standard banking services—checking, savings, debit cards—but its key differentiator for my use case is the developer-friendly API. This API provides programmatic access to account balances and transaction history, which is critical for the automated financial operations at Total Ventures. It's a no-frills banking experience focused on core functionality and integration.

How I use it

At Total Ventures, Mercury is the financial backbone for all studio brands, including Total Formula 1, Pregnancy Power Hour, and Inky. Every morning, the `tv refresh` agent pulls the latest balances and transaction data from Mercury via its API. This data is then processed to generate a daily financial brief, which includes current runway projections and categorized spend across all products. For instance, I can see ad spend for Total Formula 1, content creation costs for Pregnancy Power Hour, or infrastructure costs for Inky's PDF generation service, all consolidated.

This agentic engineering approach means I don't manually log into a banking portal daily. The system flags unusual transactions or nearing-threshold balances, allowing me to focus on building rather than administrative overhead. When I'm working on a new feature or product, like integrating a new payment gateway for Total Formula 1 subscriptions, I can quickly verify transaction flows against the Mercury data. It's a direct feed into the studio's operational intelligence. I also use their virtual cards for specific vendor payments, which helps categorize expenses and manage subscriptions more effectively. This granular control is essential for tracking profitability per product line, especially when iterating on features built with Next.js App Router or styling with Tailwind CSS v4.

Why this over alternatives

I evaluated several traditional banks and fintech alternatives. Traditional banks often lack a robust, developer-friendly API, or their API access is gated behind enterprise agreements and complex onboarding processes. For a solo operator running multiple brands, that overhead is prohibitive. Other fintech solutions sometimes offer better rates or more complex features, but often at the cost of API stability or clear documentation.

Mercury's API is well-documented and straightforward to integrate. The read-only nature of the API is also a security feature I appreciate—my automation can monitor but not initiate transactions. This balance of access and security is important. The user interface is clean, and the support has been responsive when I've needed it. I prioritize stability and predictable behavior for core infrastructure, and Mercury delivers that for banking. It integrates cleanly into the automated financial reporting that informs strategic decisions for the studio.

Where it falls short

While Mercury excels at core business banking and API access, it's not a full-service financial platform. It doesn't offer advanced lending options, complex international wire capabilities beyond basic transfers, or integrated payroll services directly. For specialized financial needs, I still rely on other providers or manual processes. The lack of direct payroll integration means I handle contractor payments and my own distributions through separate platforms, which then get reconciled against Mercury's transaction feed. It's also not the cheapest option for every single fee, but the value derived from its API and operational efficiency outweighs minor cost differences. For a studio focused on lean operations and agentic workflows, these are acceptable trade-offs.