Picture this. You run cost allocation for a small team, and an agent with a budget is about to start calling an email-and-calendar API on your behalf. Before it does, you want to know which actions actually cost money. You don't want to find out when the invoice shows up. So you go looking for a machine-readable description of how the provider bills.
That is what the FinOps collection on apis.io is for. It holds 7,145 FinOps profiles across 7,124 providers, with 16,129 billable meters among them. Each profile maps a provider's billing onto the FinOps Foundation Framework and the FOCUS cost-and-usage specification. You get a billing model (currency, frequency, pricing category, charge categories) and a list of meters. Each meter has an aggregation, a unit and the dimensions you would allocate cost by. You also get a set of FOCUS columns you can drop into a report. Every profile that declares a FOCUS version declares 1.3, which is 2,822 of them.
Now look at how the profiles got there. Of the 7,145, 6,478 are marked method: generated. Exactly one is marked provider-published. The post that reports this says that ratio is the whole story of the artifact, and that it is mostly the catalog's own story.
Most of the collection came from API Evangelist bulk sweeps in May 2026. The provenance stamps say so: written by the bulk sweep, not harvested from the provider. The numbers behind that are worth holding in your head before you trust any single profile. Only 31 are evidence-backed. 1,976 carry reconciled: false in their source, against 976 marked reconciled. 321 describe themselves as placeholders. 2,316 define no meters at all. Just 98 have a primary unit set, and 8 list discount models. Pricing category leans heavily toward Usage-Based, at 2,663, which the post calls a split worth suspecting when nine in ten profiles were generated.
None of this counts toward any provider's Kin Score as their own work, and the post says it should not. A meter the catalog inferred from a pricing page is a hypothesis about someone's bill.
Here is where the post shows why that matters. Say the provider you were about to point your agent at is Nylas. It is the single provider-published profile in the whole collection, and it opens with a correction. In its own words, it corrects a generated scaffold that modelled Nylas as a per-API-request platform with a request pricing unit, and with meters for billable API requests and compute-seconds. Nylas does not meter API requests and does not bill compute time.
The real model is a monthly plan fee plus overage. The overage applies to connected accounts and to Nylas-hosted Agent Account mailboxes, and both are aggregated as a maximum rather than a sum.
Read that against your plan. The generated profile counted the wrong thing, which was requests. It aggregated the wrong way, which was a sum. And it invented a meter, which was compute-seconds. If you had built allocation on it, you would have been allocating a bill that does not exist. Worse, overage on connected accounts is the kind of meter an agent can actually trigger, so it is exactly the one that needed to be right.
This is where the post turns on its own side. It does not blame providers for being quiet. It says the weak record is mostly the catalog's doing, and it names a fix for the catalog's end. The 321 self-declared placeholders should be marked as such on the page, not presented as profiles.
What do you take away? First, treat a generated FinOps profile as a hypothesis, not a bill. Check the method field, and check whether the profile is evidence-backed or reconciled, before you let anything drive allocation. Second, the collection's value today is its shape, a FOCUS-aligned place to put a provider's billing truth, more than its contents. Third, if you work at a provider, the path is open. Publish a finops/ file in your own repo, or correct the catalog's version through the listing tools, and the catalog flips it to provider-published.
Read the original: https://apis.io/2026/10/21/finops-on-apis-io-7145-profiles-and-one-written-by-the-provider/