The FinOps collection on apis.io holds 7,145 FinOps profiles across 7,124 providers, with 16,129 billable meters among them. 6,478 of those profiles are marked method: generated. Exactly one is marked provider-published. That ratio is the whole story of this artifact, and it is mostly our story.
What a FinOps profile is
Each profile maps a provider’s billing onto the FinOps Foundation Framework and the FOCUS cost-and-usage specification. It records a billing model (currency, frequency, pricing category, charge categories), a list of meters with an aggregation, a unit and the dimensions you would allocate cost by, and a set of FOCUS columns a cost team can drop into a report. Every profile that declares a FOCUS version declares 1.3, which is 2,822 of them. When it is right, a profile tells an integrator, or an agent with a budget, which actions actually cost money before the invoice shows up.
| Field | Profiles |
|---|---|
| method: generated | 6,478 |
| evidence_backed: true | 31 |
| has_sources: true | 2,969 |
| zero meters | 2,316 |
| primary_unit set | 98 |
| discount models listed | 8 |
Where the record is weak
Most of this collection came from API Evangelist bulk sweeps in May 2026. The provenance stamps say so: “written by the API Evangelist bulk sweep … not harvested from the provider.” 1,976 profiles carry reconciled: false in their source, against 976 marked reconciled. 321 describe themselves as placeholders. 2,316 define no meters at all. Only 31 are evidence-backed. Pricing category leans heavily toward Usage-Based (2,663), 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 it should not. A meter we inferred from a pricing page is a hypothesis about someone’s bill.
The one that shows why it matters
Nylas is the single provider-published profile, 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 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 on connected accounts and on Nylas-hosted Agent Account mailboxes, both aggregated as a maximum rather than a sum.
That is the failure mode of the whole collection in one paragraph. A generated profile counted the wrong thing (requests), aggregated it the wrong way (sum), and invented a meter (compute-seconds). A cost team that built allocation on it would have been allocating a bill that does not exist. 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.
Takeaway
The collection’s value is its shape, a FOCUS-aligned place to put a provider’s billing truth, more than its contents. What would move it is providers doing what Nylas did: publish a finops/ file in their own repo, or correct ours through the listing tools, and we flip it to provider-published. On our side, the 321 self-declared placeholders should be marked as such on the page, not presented as profiles.
Browse the collection at apis.io/finops/.