Who this is for
Providers of official records, specialist databases, geo and business data. Platforms where others automate their workflows. Providers of AI for companies, with their own interface and their own users. Operators running AI servers for others, on their own hardware or in European data centres. And everyone building an assistant that gets things done for its users.
Most of them buy AI themselves. What they spend on it, they want to allocate to a team, a project or a customer.
Why many buyers stay away today
Billing per call has been around for a long time. Anyone using a language model or a database through an interface pays by volume, and the prices are published. The same thing is required every time: a framework agreement with that particular service, an account there, an invoice at the end of the month, and behind it a company that answers for it. For the next service it starts over.
Anyone who needs something once therefore does not become a buyer. An agent sent to fetch a single record on behalf of its user would first have to become a customer, and it cannot.
Part of the market names no price at all. Register records are only issued on application and by official notice, footfall and mobility data only on quotation. There it is not only the framework agreement that is missing, but the unit in which a single call would be expressed.
What can be sold one at a time
The buyer needs neither a framework agreement nor a subscription with you. The contract is made with each single purchase, paid from credit topped up beforehand or, for business customers, collectively afterwards.
- The section instead of the document. A technical standard comes only in full and at the price of the whole document, while what is needed is often a table on one page out of 48. Selling the section on its own reaches the buyers for whom the whole document is too expensive.
- The excerpt instead of the licence. A camera at a junction yields seven different kinds of data, from the lorry count per quarter hour to visibility. A customer often needs only one of them, and only for 14 days. There is no annual licence for that, but there can be a price per use.
- The record without the application. Official records are only issued on application and by official notice, and the fee at times exceeds the value of the single piece of information. An agent files no application. Offering the same record as a call sells it to machines.
- The single call instead of the aggregator licence. Commentary, rulings and market reports sit with the aggregator, where the single call is not provided for. Offer it yourself and you sell to the buyer who never becomes the aggregator’s customer.
- The single calculation instead of the software. Simulation and route planning come as software with a licence, not per calculation. Charge for them one at a time and you sell to the occasional user, for whom a licence was never an option.
- The analysis instead of the annual plan. The cheapest plan at one weather data provider costs 2,400 euros a year, even where a single analysis needs 200 calls. Selling those 200 calls one by one wins a customer who does not buy today.
What can be attributed per call
Spending on AI is under observation almost everywhere by now. In the FinOps Foundation’s State of FinOps 2026, 98 per cent of respondents report managing AI spend, against 31 per cent two years ago.
Observation, however, is not attribution. What the platforms deliver is an evaluation drawn from logs.
With NemosGo, every call is paid for separately, and every receipt names what triggered it: which application, which team, which department. Attribution happens at the point of purchase, not at the end of the month. Where many departments use the same AI, each carries its share. Once a team’s budget is spent, the agent stops. And anyone building custom software shows their client the receipt per transaction instead of billed hours.
Less to steal
A weather data service that sells through NemosGo sees only a pseudonym, the amount and the receipt per call in its interface. No customer accounts, card numbers or passwords end up there, and names only if a buyer shares one. The interface delivers only to the checkout, which identifies itself with credentials of its own. What payment requires sits separately in the NemosGo installation, with bank details encrypted. The service can run it itself, or we do. Its weather data stays free of customer and payment data.
Which products fit
- Usage-based: billing runs per call, outwards as much as inwards. The price sits on the endpoint, the calling application pays it in the same step, and the receipt names who triggered the call.
- Single purchase: one call carries a fixed price that you set. Payment comes from a credit balance, delivery follows right away.
- Delegated: when a user sends their agent off with a task, they approve an amount and a purpose beforehand, and the agent buys from you within those limits.
- Buy and allocate costs: you approve an amount, a purpose and a period for your agent, 20 euros for seven days, say, and it buys only within that.
In practice
- Use of an AI model is paid for per call. An application calls, pays from credit, and the receipt names which application, team or department caused the cost. Recorded in the field test since August 2026.
- The purchase of an official record by an agent has been built.
- Research on a budget, built and demonstrable in a test application. An analyst approves a budget of 20 euros for her agent for seven days, purpose “profiles of our competitors”. The agent buys company profiles and two trade articles, and every purchase refers back to that approval.
- Not built yet: splitting the proceeds when several providers contribute data to one call.
Let’s talk
Tell us what a single call is worth in your case and how it is billed today. We will look at your interface.
What you bring, what the path to your first sale looks like and what it costs are set out under For sellers, and for allocating your own AI costs under For companies that buy.