How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Every Talk At APIDays London, Mapped To The Kin Score

September 28th, 2026 · Kin Lane
Every Talk At APIDays London, Mapped To The Kin Score

APIDays London is this Wednesday and Thursday, 30 September and 1 October, at Convene Sancroft next to St. Paul’s. Before I go, I did what I always do with an agenda: I read every session. All 110 of them, across the Apidays, GenerationAI, GreenIO, OpenAPI, AsyncAPI and GraphQL tracks, and I mapped each one to the Kin Score facet it speaks to.

I wanted to see two things. What the people on stage are going to tell the room an API needs to be, and whether the rubric I use to measure APIs across the APIs.io catalog is looking at the same things. Mostly it is. Where it is not, the gap is interesting.

The short version. Agent Readiness dominates — it is the main subject of 33 talks and comes up in 61. MCP servers, machine-readable auth and rate-limit signalling are the three things speakers keep returning to. Contract Quality and Contract Governance are right behind, carried by the OpenAPI, AsyncAPI and GraphQL tracks. Accountability, a layer I do not score yet, is the main subject of 11 talks, which tells me it is time I did. And most of the GreenIO track sits outside the rubric entirely, pointing at a disclosure — energy, carbon, water — that no API provider publishes and I do not measure.

Each talk is listed once, under the facet it is mostly about, with its day and London start time. Many of them touch several. If you want to filter by facet, track or day, or see every facet a talk touches, the full mapping is at talks.apievangelist.com/events/apidays-london-2026/. Every talk and speaker below links to the APIDays agenda, which is where you should go to plan your two days — and if you do not have a ticket yet, you can still get one.

I am speaking too: OpenAPI Extensions Are Not a Mess, They Are a Map, Thursday at 09:55 on the OpenAPI track, where I walk through what 2,249 OpenAPI extensions say about the jobs the specification still does not do. Come find me.

Agent Readiness

A third of the primary talks at APIDays London are about one thing: whether an AI agent can drive an API without a human filling in the gaps. The speakers below will teach you what agents need from an API. Agent Readiness is the separate score I use to measure whether an API gives it to them: a published OpenAPI, an MCP server, machine-readable auth, idempotency, stable errors, rate-limit headers, agent skills, a well-known catalog, protected resource metadata, and bound rather than bearer credentials. How the Kin Score measures it on APIs.io.

Contract Quality

The contract is still the foundation, and London has a whole OpenAPI track, an AsyncAPI track and a GraphQL track making that case. Contract Quality is the largest facet of the Kin Score, a quarter of the composite, and it measures the depth of what a provider actually publishes: schemas, examples, descriptions and versions across OpenAPI, AsyncAPI, GraphQL and JSON Schema. How the Kin Score measures it on APIs.io.

Contract Governance

These are the talks about keeping contracts consistent as teams and agents multiply: rulesets, shared vocabulary, standards conformance, and governance that runs in the pipeline instead of in a meeting. Contract Governance measures the artifacts that constrain a contract — published rulesets, vocabulary, declared conformance, overlays. How the Kin Score measures it on APIs.io.

Access Clarity

What does it cost, what am I allowed to do, and how do I get in? These talks cover token spend, sovereignty, entitlements, and a surprising amount of finops from the GreenIO track. Access Clarity measures plans, pricing, sign-up, terms, privacy, a finops mapping, and trust and compliance. How the Kin Score measures it on APIs.io.

Accountability

Who answers for what an agent does? These talks are about ownership, judgement and responsibility once software starts acting on people’s behalf. Accountability is a standalone layer of the Kin Score that is not scored yet: whether an organisation publishes an AI policy that resolves, is versioned, names an owner and an accountable officer, and requires an impact assessment.

Developer Ergonomics

Getting started is still where most integrations are won or lost, and the audience now includes agents. Developer Ergonomics measures SDKs, CLI, a portal, getting-started guides, a sandbox or console, an MCP server, and clear auth documentation. How the Kin Score measures it on APIs.io.

Operational Transparency

How does the API behave in production, and does the provider tell you? These talks cover attacks at machine speed, observability, and thirty years of traffic management. Operational Transparency measures published rate limits, a status page, a change log, a deprecation policy and a security disclosure path. How the Kin Score measures it on APIs.io.

Regulatory Posture

London is a banking town and it shows. Regulatory Posture only applies to regulated industries, and it measures consent-scoped authorization, a published security posture, terms and privacy as a legal basis, and conformance to the industry’s data standard — ISO 20022, CAMARA, FAPI and the rest. How the Kin Score measures it on APIs.io.

Open Source Surface

Open Source Surface only applies where the product itself is open source. It measures the maintainership surface you need before you depend on it: a vulnerability disclosure path, a contribution route, a release history, a code of conduct. How the Kin Score measures it on APIs.io.

Discoverability

Discoverability measures whether an API can be found and understood from machine-readable metadata alone — apis.json, tags, identity signals. Plenty of talks touch it; one is about it. How the Kin Score measures it on APIs.io.

Outside the rubric

The GreenIO track keeps making a point I cannot measure yet: providers do not disclose the energy, carbon or water cost of what they serve. There is no Kin Score facet for that today. These talks are where I would start if I built one.

This is a mapping from titles and abstracts, not a score of anyone on stage — a reading of what each talk is about, against the facets of the Kin Score rubric. If I put your talk in the wrong place, tell me and I will move it. See you in London.