API Billing: What It Means for Dental Claims

An API is how one piece of software asks another piece of software for information, or sends it information, without a person opening a web page. Every time a verification tool asks a payer whether a patient is active, what the deductible is, or what's left on the yearly max, it is making an API call. API billing is simply how the company on the other end charges for that call.

Most billing built on APIs falls into one of three patterns. The provider charges per call, so the bill moves with volume. The provider charges per unit of work inside the call, like tokens for AI text or minutes for a phone call. Or the provider sells a monthly plan with a set number of calls included and charges extra past that. OpenAI and Google's Gemini API both meter by tokens processed, shown on a live billing dashboard inside each platform. Insurance verification tools built for dental and medical offices usually use the third pattern instead, a monthly plan with an included number of checks, because a front desk wants a number it can plan around, not a dashboard that changes by the hour.

Most front desk staff never type the word "API." They see a screen that says "check eligibility" and a result a few seconds later. Behind that button, software is calling at least one API, sometimes several: one to the clearinghouse, one to the payer's own system, one to a database that matches the plan to the member ID. Each of those calls can carry its own charge, and the vendor usually rolls them into a single rate on your invoice.

This matters because two tools built on the same clearinghouse connection can price it very differently. One vendor might charge per check with nothing included. Another might bundle a number of checks into a flat monthly plan and charge a small fee only for the checks that find active coverage. Ask your vendor which pattern they use before comparing prices, because a flat per-check rate and a per-call rate behind the screen are not the same math once one check triggers several calls underneath.

At Valian, insurance verification is priced by the check the office actually runs, not a hidden count of calls behind the screen. The office signs in and runs each check in one click. Plans start at $49 a month plus $2.50 or less per check we find, and you pick a plan based on how many checks your office runs a month, from 50 checks up to a plan built for 10,000. The number on the invoice is the number your front desk recognizes: checks run, not API calls made.

The largest billing dashboards a practice manager might stumble into belong to the AI platforms. OpenAI's billing page meters usage by tokens, the small chunks of text a model reads and writes, and totals the running cost for the month. Google's Gemini API works the same way, with separate rates depending on the model version and whether you send text, images, or both. Neither platform publishes one flat monthly fee for API access; you turn on billing for a project, send requests, and the meter runs from there.

That setup works for a developer testing an app on their own schedule. It works less well for a practice trying to set a monthly budget, because nobody at the front desk has time to watch a token counter between patients. According to the ADA Health Policy Institute's 2026 survey, 43.3% of dentists already use AI for at least one task in the practice, and insurance verification is the number two planned use, at 32.6% planned versus 13.6% in use today. Most of those offices want a plan with a known monthly number, not a meter they have to check every afternoon.

Clearinghouse connections, the ones that move claims and eligibility data between a practice and a payer, bill differently again. Some charge the software vendor a wholesale rate per transaction, and that cost gets folded into whatever plan the practice pays for its verification or billing tool. A practice almost never sees the raw clearinghouse rate directly. What shows up on the invoice is the vendor's plan price, which is why comparing two dental tools means comparing the finished plan, not the wholesale rate underneath it. Our guide to insurance eligibility verification APIs walks through how that connection actually works.

Before a front desk signs anything priced by the call, we tell practices to ask four things:

• What counts as one billable unit: one check, one claim, one API call, or one "transaction" that might bundle several calls.
• What happens past the included amount: does the per-unit price go up, or does the whole plan jump to the next tier.
• Is the number on the invoice the same number shown in your dashboard, or does the vendor round up.
• Is there a cap, so one busy month can't produce a bill nobody budgeted for.

A plan billed strictly by the call can look cheap on a slow week and expensive on a busy one. A plan with an included number of checks and a small fee past that, like the insurance verification plan described above, gives a front desk a number it can write into next year's budget. Ask for that number in writing before you sign anything, and ask what the overage rate actually is, not just the headline price. For more on how real time checks are priced and run, see our real time eligibility verification guide.

Insurance verification is one piece of the revenue cycle, and claims work the same way underneath: data moves between the practice, the clearinghouse, and the payer, and somewhere in that chain, an API call is being billed to somebody. The practice still books the appointment in its own schedule, and the team enters it into the practice management system the office already runs; Valian works alongside the practice management system a practice uses today, not instead of it.

Our claims and collections tools are in development, and we are taking our first offices now as we build that piece out. We do not promise a dollar amount recovered, and the office still picks its own billing codes; the software does not pick them. If you want to see how checks and claims work fit together across a full revenue cycle, our dental revenue cycle management page walks through each step, and our breakdown of RCM software covers what's typically included in that category today.

If you want to see a check run in one click at the front desk, you can book a time to see it.

What is API billing?

API billing is how a software provider charges for calls made to its API, usually by the request, by a unit of work like tokens or minutes, or through a monthly plan with a set number of calls included. In a dental or medical office, it usually shows up as the price behind an insurance check, a claim submission, or a text message sent through a messaging platform, even though nobody at the front desk sees the word "API."

What is an API payment?

An API payment is the actual charge a provider bills once calls are metered and totaled, either run automatically against a card on file or added to a monthly invoice. For most practices this is invisible: the office pays one vendor a flat plan price, and that vendor pays the clearinghouse or API provider behind the scenes.

How much does an API subscription cost?

It depends entirely on what is being metered. Dental insurance verification plans built on these connections commonly start at $49 a month plus $2.50 or less per check found, scaling up to a plan built for 10,000 checks a month. Developer AI platforms like OpenAI or Google's Gemini API don't sell a flat subscription at all; they meter by token and show the running total on a billing dashboard instead.

Which payment API is free?

Most developer API providers, including OpenAI and Google's Gemini API, offer a small number of calls at no charge so a developer can test integration before billing starts, but ongoing use at real volume is metered. No clearinghouse or insurance verification connection used at real patient volume runs at no cost, because each call carries a wholesale charge from the payer connection itself.