|
I spent this week in Stockholm at the
Nordic APIs Platform Summit, where I closed the event on Wednesday with a talk
called
The Agent Hype is at Odds with Your API Foundation. Before I went, I read the agenda and
mapped all sixty-four talks against the keynote, and the agenda lined up with it.
Back home, the blog pull read
12,552 posts from 2,743 provider blogs
this week, against 13,318 from 2,880 the week before — now
that the wider set of sources has settled, a like-for-like
week, a little quieter. From that pile three things stood
out, and none of them was MCP on its own. Models that make
decisions instead of writing text became something you
route, govern and meter. The agent payment rail got
measured by people who did not build it. And the remote
MCP servers I have been watching move from experiment to
general availability did exactly that.
|
|
A dark neon junction where a single stream of
light-vessels arrives at a glowing switch that
splits it cleanly into three lit channels, a small
meter glowing beside each channel.
|
Decision Models Became Plumbing
"Decision" showed up in 56 titles this week.
Plenty of those are the ordinary word, but a striking
share are the new category of models that return a yes or
no, a pick from a list, or a score — with probabilities —
instead of a paragraph. I wrote on Monday that
decision models agreed on the questions, not the
contract: eleven providers ask the same three kinds of question,
and publish eleven different request shapes. The rest of
the industry spent the week building the layer that hides
that.
What I find interesting is where the work is landing. A
month ago these were model launches. This week they were
gateway features, proxy routes and deployment guides — the
same path MCP took, compressed into a few weeks. The
decision is becoming an API call you govern, which means
it needs a contract, and right now it has eleven.
|
|
A dark neon toll plaza where a long row of glowing
toll booths stands across a luminous road, most
booths dim and closed, a few lit and passing small
light-vessels through, and a scanning beam passing
along the row counting them.
|
x402 Got Measured
The agent payment rail had its first week of honest
measurement, and the numbers point in two directions at
once.
I spent part of the week on the provider's side of
the same rail.
Five MCP servers put a price in the tool, in four
different shapes: there is no price field in the MCP specification, so
the cost lives in the payment handshake, on the tool
definition, in the description text, or nowhere an agent
can see it before it pays. And
nobody is forecasting the transactional API economy
— which, given a hundred and thirty-eight million
transactions, someone should.
|
|
A dark neon harbour where a long pier of glowing
docking bays stretches out over dark water, each bay
newly lit and holding a small moored vessel, the
lights coming on one after another down the length
of the pier.
|
From the research: Making API Governance Conversational
Your Spectral ruleset reaches the IDE and the pipeline. It
does not reach the conversation — which is now where APIs
actually get designed. Wrapping the governance engine in a
small MCP server makes it conversational for copilots and
reachable by agents.
Read the paper
Remote MCP Went Generally Available
The pattern I have been tracking for two months — local
MCP server you run yourself, then a hosted one you just
point at — completed at several big platforms in the same
week.
How a company advertises those servers got
settled the same week, and it is the piece I would read
first.
Two front doors for agents in one week: MCP finalized
Server Cards
and deliberately pointed discovery at an
AI Catalog
under
/.well-known/, while the new Personal Agent Protocol defined its own
well-known document the same day.
The well-known folder is filling up, and somebody is going to have to keep it tidy.
|
|
A dark neon checkpoint where a small angular
light-vessel holds up a glowing credential toward
four separate gates in a row, and each gate's
light turns from amber to clear green as it reads
the same credential.
|
An Agent Found Four APIs, and All Four Trusted It
Agent identity kept coming up in other people's work:
Token Security on what an agent identity lifecycle
looks like, from discovery and ownership through rotation and
retirement, and
Nudge Security on why delegation is the real control
point
— agents do not get their own identities, they act on the
keys and grants people hand them.
I wanted to see the other side of that work end to end, so
I built it. This fall I stood up four small sites, each an
API first and a website second, so I would have providers
I control completely. On Thursday I pointed our own agent
at all four with nobody in the room: it searched APIs.io,
read each site's onboarding descriptor, asked APIs.io
to vouch for it, and presented that to each site.
An agent found four APIs, and all four decided to trust
it
— five to seven seconds from first search to a trust
decision, and 35 of 36 steps passing. That is Know Your
Agent working outside a slide.
|
|
A dark neon cartographer's table seen from
above where a single luminous blueprint lies
unrolled, a bright chain of linked nodes running
from one corner across the map to a glowing
marketplace at the far edge.
|
From My Desk: The Market, the Rules, and the Standards
Nobody Ratified
-
The Kin Score is getting a third dimension.
For a year it has measured what a provider publishes
and how ready that is for agents — both the provider
looking at itself.
Now it gets a Market layer, built from a deterministic chain: operation → tag →
business capability → workflow → integration → market.
It is the first part of the score that says what an
API is worth to the businesses depending on it.
-
Two new sections on APIs.io.
Ninety-five companies publish their API design
rules, and APIs.io lists them first. And
six standards nobody ratified, measured against
what the industry built
— the S3 interface, the OpenAI API, CKAN, Ethereum
JSON-RPC and others that became standards by being
copied.
-
From Stockholm. Bill Doerrfeld opened
the summit with a definition of an agent, and I wrote
about the one word in it that matters:
driven or enabled.
-
The numbers.
102 companies hiring for MCP, and the enterprises
are ahead.
Twenty-five thousand overlays, and none of them are
yours yet.
-
And the rest.
fx is a coding agent that tells you which parts of
MCP it does not do
— I wish more tools did.
The wires are crossed: slop for humans, structure
for agents. And
Commune has an API, and Substack does not
— which is also how this week's new subscribers
got onto this list.
Across 12,552 posts, OpenAPI appeared in two titles. One
of them was
Scalar on generating it from NestJS. The other was a hands-on post about building an API
reference from a single OpenAPI file. The specification
layer stays quiet in the titles and load-bearing
everywhere else.
I closed my talk in Stockholm on the same point I want to
close on here. Decision models, payment rails and remote
MCP servers are all, underneath, an API call with a
contract — and this week each of them showed up with more
than one contract for the same job. The hype is about what
agents can do. The foundation is whether the thing they
are calling says, in a way a machine can read, what it
does, what it costs and who is allowed to call it.
See you next week.
🔌 APIs.io — Rules and Standards
— Two new sections this week.
Rules
lists the companies that publish the API design rules
their APIs are held to, as rulesets anyone can read and
reuse.
Standards
measures the de facto standards — S3, the OpenAI API and
the rest — against who actually implements them. If you
are deciding how to design your next API, or what
"compatible" should commit you to, start there.
Also on the shelf: Explicit Agent Boundaries
Every team I talk to has an agent editing their codebase
and a folder of Markdown nobody reviews. That Markdown is
the new configuration layer. Govern it like configuration.
Read the paper
You are receiving this because you subscribed to this
newsletter.
Unsubscribe
606 W 57th New York, NY 10019
|
