You are the person who has to answer one question for finance: what did we spend on CI last quarter? You run builds on CircleCI, so you go looking for a way to pull usage data out of it, and you want an agent to help you do it. You search the APIs.io catalog first.
You find CircleCI there, across 18 API pages. You find the Insights API, the Pipeline API, the Workflow API and the Job API. What you do not find is the thing you actually need. That is the point of a post APIs.io published on November 6, 2026, and it is worth following closely, because it explains both what exists and what the catalog is missing.
The export is real. A short CircleCI help-center article, Utilizing the Usage API, says customers can "query your usage data for any 32-day window (or less) going back up to 13 months." It covers pipelines, workflows and jobs, credit consumption, and RAM and CPU utilization per job run. The data is refreshed daily through the previous full day, by a scheduled update that runs between 08:00 and 10:00 UTC and includes everything up to 11:59:59 UTC the day before.
The shape matters for your plan. It is asynchronous. In the article's words: "Hit the API to query your data, get back a link from which you can download a CSV, then load it into a data warehouse of your choice for deep CircleCI usage analysis." So you do not get a payload back. You get a link.
The post says there are no vendor figures to discount, only limits, and that the limits are the story. Do the arithmetic the post does. A 32-day window and a 13-month horizon mean a full year of history is at least twelve export jobs, each returning a download link. And because of the refresh window, anything you query before 10:00 UTC may not yet include yesterday. If you run your report first thing in the morning, you could be missing a day without knowing it.
The help center's related articles read like a map of where people get stuck: resolving a "Malformed request body" error, understanding API behavior when retrieving reports, and a Python walkthrough, which is what a job-plus-poll-plus-download pattern needs. The article also points to v3 API docs alongside v2, which the post notes is the first time a v3 surface appears anywhere in CircleCI's record.
Now the turn. The post is not mainly about CircleCI's shortcomings. It is about the catalog's own record. APIs.io holds CircleCI across 18 API pages, and the Usage API is not one of them. The record's description names the v2 REST API, the legacy v1 API, the Self-Hosted Runner API, webhooks and the Orbs Registry, and stops there. The nearest entry is the Insights API, which the help center explicitly distinguishes from Usage in a sibling article. The agentic access profile maps 74 operations, 30 of them acting, and none of them is an export job.
The scores make the gap sharper. The Kin Score is 72.9, in the exemplar band, with access clarity at 93.4 and discoverability at 81.7, against contract governance at 31.8. The Agent Readiness score is 56.1, agent-ready, with fourteen dimensions lit, including the MCP server, delegated identity, protected resource metadata, dynamic client registration and the event surface. Idempotency, OpenAPI examples and dry-run mode are unlit.
So you are looking at a provider that measures strongly, in the top band, and that has a documented, asynchronous, credit-level usage export the catalog has never read. The post puts it plainly: the measurement is strong and the gap is specific. The agent that needs to answer "what did we spend on CI last quarter" cannot find the export here. The post calls that a harvest task for the catalog before it is a score for CircleCI.
What you take away is practical. The export exists, and you can use it today, but you should plan around its limits: at least twelve jobs for a year, a download link per job, and a morning refresh window you should not query inside. And you take away something about the tool you searched with. A high score did not mean a complete record. The catalog said so about itself, and that is why you know to go to CircleCI's own help article rather than trusting that an empty search means nothing is there.
Read the original: https://apis.io/2026/11/06/circleci-usage-api-exports-13-months-in-32-day-windows-and-is-not-in-the-catalog/