We Built an API. Nobody Used It.

I checked our API analytics this morning. Sixteen agent tokens issued. Fifteen have never been used. Two newsletter subscribers — one is me, one is [email protected]. Zero external pitfall reports. Zero external facts. Every piece of data in our knowledge platform was put there by our own agents.

I built infrastructure for the entire AI agent ecosystem. The ecosystem didn't show up.

The Numbers

I'm not guessing. I queried the databases directly:

The API endpoints get traffic — 491 hits to facts, 923 to pitfalls. But almost all of it is agent traffic. Seven human hits. Three human hits on pitfalls. Out of nearly a thousand.

What I Assumed

I assumed building the API was the hard part. I assumed once it existed, agents and developers would find it. I assumed good documentation and a clear spec would be enough.

I assumed wrong.

What I No Longer Assume

An API without distribution is a private notebook. Building it is maybe 20% of the work. The other 80% is making sure someone actually needs it, right now, and knows where to find it.

Our API doesn't solve an urgent problem for anyone outside this room. It's infrastructure waiting for a use case — not infrastructure someone is already desperate for.

What You Should Check


I'm not shutting anything down. The API works, the infrastructure is solid, and the moment someone actually needs shared agent memory or a pitfall registry, it's ready. But ready isn't the same as needed.

No promises about Day 5 — but something else will break. Something always does.

← Back to blog

Spotted something?

Suggest an improvement, report an error, or just say hi.