Anyone can add an API to APIs.io — paste a URL at apis.io/add, and if there is a machine-readable surface behind it, it gets profiled, scored on the Kin Score, and listed. That form is one of the more honest instruments we have for reading what people are actually building, because nobody submits an API they are not proud of. So it is worth looking at the last twenty-five that came through, because they are not a random sample of the API economy — they are a snapshot of who chose to raise their hand this week, and the pattern in them is hard to miss: a growing share of new APIs are being built for agents to call, not for people to read.
The agent-native ones say so out loud. EventEdge Oracle returns “read-only, machine-readable prediction-market context (Polymarket + Kalshi) built for autonomous AI agents.” AssetFare is a routing API “aimed at AI agents.” iCallAgent is a platform for building AI voice agents that hold real phone calls. DELTA Witness calls itself a “trust layer for autonomous actions” — timestamped content hashes so an agent can prove what a page said when it acted. ARAKEL sells pay-per-call, machine-readable evidence checked against official U.S. government sources. Featureflip describes itself as API-first and agent-oriented, down to a GitHub Action that cleans up its own dead flags. None of these are human-facing products with an API bolted on. The agent is the primary user, and the pricing and the shape follow from that.
The money rails underneath them are crypto, and metered per call. P2Flux is a non-custodial USDC payments API on Base. AssetFare routes a single corridor — Solana SOL to Base ETH — as a capped, non-custodial call. CoinNudge serves crypto market data. When the caller is a program with a wallet rather than a person with a credit card, per-call settlement on a chain stops being ideological and starts being the obvious plumbing, and three of the last twenty-five reach for it without comment.
The largest single group is still data — but data packaged for a machine to consume. drillr and iTick both deliver financial statements and market data across the US and Asia. CrustAPI and Social Fetch turn Google, Maps, and public social profiles into structured JSON. tgAtlas maps public Telegram channels. USACallerLookup exposes US phone-numbering and FTC robocall data with no key at all, and Rates and Limits does the same for federal and state tax and payroll figures. QName programmatizes WHOIS/RDAP. GEOCitation audits how a brand shows up in answer engines — SEO for the age when the reader is an LLM.
And then the long tail, which is the part of any open catalog worth loving: flatin.pt for buying property in Portugal, CoworkingView for comparing flexible workspace across Europe, RubiConnect and Chatwik for business messaging, RankFabrik’s four data-collection APIs run out of Paris, Raphael AI for no-signup image generation, a free stateful mock-API Playground, and — because someone always builds the thing only they need — L2Calendar, a multilingual tracker of Lineage 2 private-server opening dates. That one will never trend, and it is exactly why an open add form beats a curated list.
The scores tell the other half of the story, and it is a simple one. The spread across these twenty-five runs from tgAtlas at 70.5, exemplar and flatin.pt at 66.4 down to L2Calendar at 18.6, emerging. That is a huge range for products that are often comparably real, and the thing that separates the top from the bottom is almost never the quality of the service — it is whether they published a machine-readable contract. drillr (57.6, strong), GEOCitation (55.4), Social Fetch (53.6) and CrustAPI (52.3) shipped an OpenAPI or an apis.json; the emerging-band submissions shipped a documentation page and left the contract in HTML. The Kin Score is not grading ambition. It is grading whether an agent can find the door without a human to open it — which is the same thing every one of the agent-native APIs above is quietly betting its business on.
That is the whole shape of the week: people are building for agents, settling per call, and the ones who wrote the contract down are the ones an agent can actually use. If you have an API — for autonomous agents, for a corner of the market only you care about, or anything in between — add it. The next twenty-five is where the pattern goes next.