Billing systems weren't built for agents, but Solvimon is

Billing systems weren't built for agents, but Solvimon is

Arnon Shimoni

✓ Expert opinion

Listen to this post (narrated by ElevenLabs)

Arnon Shimoni
Billing systems weren't built for agents, but Solvimon is
0:00

During March, we had a little event to announce Solvimon for AI. At that event, we also announced Reson8 as our first AI model and lab customer. And while our launch was focused around companies selling inference, running credit wallets, and managing hybrid pricing at scale - the reaction told us something else.

We heard that developers needed a product that fit how they actually build in 2026 - in their IDE, through their agents, without a dashboard (and more people) in the critical path.

We’re ready to show you where we’re taking Solvimon in 2026 and onwards.

The unit of value has changed

Recently, the units of value have changed because AI companies stopped selling just seats. We see it in our data, as companies sell complex sets of inference, billable API calls, add-ons, and a lot more.

As Hybrid pricing became the default, the fastest-growing companies we work with today run seats plus credits plus overages plus enterprise commits simultaneously and nobody else builds cleanly for this. We’re helping teams who ended up up gluing five tools together and writing orchestration code that slowly became their very fragile billing system.

Today, agents became users. Not in the metaphorical sense - a developer in Cursor and Claude Code today can ask their coding agent to configure a pricing model, add a meter, check an entitlement - all without using a dashboard. Not even to sign up.

What headless monetization means

Headless doesn't mean no UI and it doesn’t mean we’ll abandon that. For us, it means the UI is one part of our surface among several - instead of being the only one. Because every billing operation in Solvimon is now accessible as an API call or MCP tool, you can configure pricing, create meters, check entitlements, issue credits, and diagnose billing issues all from your agent, your IDE, or your own application.

Our MCP server is already live and has seen some good uptake, with one customer exclaiming “it was insanely fast and easy to set it up in my app with just one prompt”. Unlike other MCP servers we’ve seen, it isn't read-only. Solvimon’s MCP can make actual changes to your billing configuration.

Our CLI is next, and it can already scaffold your checkout page, usage meters, entitlement middleware, and pricing page into any Node.js app with one command.

It’s not that "SaaS is Dead" as many say, but rather SaaS is becoming headless. The model of interaction AND monetization of it changes.

The source of truth stays inside Solvimon with our battle-tested business logic, workflows, compliance, and audit trails. Billing accuracy is the top priority for every company we work with, and headless doesn't change that. It means you access that accuracy through more surfaces, not fewer guardrails.

The UI stays too. Dashboards, the plan builder, interactive CPQ and even Docusign integration get better. Some things are easier to see than to query.

A continuation from before

In March we proved Solvimon works for AI companies, and today we're defining what billing infrastructure should look like when AI and agents are first-class users of software.

This is a new category called Headless Monetization, built by the team that ran billing at €1T+ annual volume at Adyen, for a world where the next customer to evaluate your billing system might not be human.

→ See the MCP server: solvimon.com/forai/mcp

→ Join the CLI waitlist: solvimon.com/forai/cli

→ Read the full vision on why headless monetization matters: solvimon.com/forai/why