APIs.io

APIs.io

@apis.io

APIs.io is a federated, agent-friendly API discovery network. It indexes API providers from across the public internet — their APIs, specifications, schemas, and collections.

75 followers307 following153 posts

APIs.io reposted

Before you design a new API, iterate an existing one, ship an MCP server or rework your developer presence, profile what your competitors already shipped and turn it into decisions: copy it, beat it, or decline it. Then use existing standards as the mold, so you aren't inventing an interface.

apievangelist.comA Competitive Landscape HarnessI am working with an API provider right now on making their platform ready for agents, including standing up their own MCP server. The most useful thing I ha...

APIs.io reposted

If your business depends on OpenAPI, please become a member of the OpenAPI Initiative. 32 active members pay for OpenAPI, Arazzo and Overlays, the specifications much of the API economy runs on. 68 companies were members and aren't today, API Evangelist included. Here's the list.

apievangelist.comIf You Depend On OpenAPI Please Become a MemberI’m going to ask for money, so I’ll get straight to it. If your business depends on OpenAPI, please become a member of the OpenAPI Initiative. If you were a ...

APIs.io reposted

I read all 884 runtime policies across 12 API gateways. AI is now the biggest area, 120 entries, and about two dozen are cost controls protecting the provider's own model bill. Charging the consumer for value: 10 entries at 4 gateways. The cost side got built. The revenue side didn't.

apievangelist.comGateways Count Every Token And Charge For Almost None Of ThemLast month I came out of Josh Twist’s talk on MCP monetization in Stockholm arguing that API monetization is falling flat, and maybe it is the word. AI puts ...

APIs.io reposted

Healthcare has done the most work writing its shapes down: FHIR, US Core, Da Vinci prior auth. The job is turning a fax or a clinical note into valid FHIR resources a server will accept. 169 providers in the catalog say they speak FHIR. Only five have contracts for claims.

apievangelist.comHealthcare: The Shape Of The AnswerYesterday I wrote about DeepInfer and the shape of the answer, and how batch-invariant inference, deterministic sampling and schema-constrained output togeth...

APIs.io reposted

Mike Amundsen moved from asking what a program needs to do next, to what it needs in order to decide. That is context engineering done once, by the API provider: contracts, workflows, schemas, rate limits and access rules written down as explicit facts, relations and capabilities.

apievangelist.comWhat A Program Needs In Order To DecideMike Amundsen published a short one yesterday, Designing for Autonomy, while he finishes his new book, AI-Driven API Design. It’s two axioms he settled on wh...

APIs.io reposted

A response to Bruno Pedro on API governance and rules. A rule doesn't have to enforce anything: error, warn, info, hint. At Bloomberg I had hundreds of rules and only three were errors. Every other rule was a link to guidance and a reason for teams to sit down and talk.

apievangelist.comWe Don't Need No Stink'n Rules!I’ve had a bee in my bonnet about Bruno Pedro’s story “API Governance Isn’t Just Rule Automation” for a couple of weeks now, but I just haven’t had the time ...

APIs.io reposted

Our agent searched for a need, not a brand, found four APIs, read each onboarding descriptor, and presented a signed attestation bound to its own key. Each provider decided on its own to trust it. Five to seven seconds each, 35 of 36 steps passed. The directory vouches for facts, not trust.

apievangelist.comAn Agent Found Four APIs And All Four Decided To Trust ItI built four small sites this fall so I would have something real to point agents at. Yawplet takes short messages. Yarnhen takes stories. Hagglebee takes cl...

APIs.io reposted