Need Agent-Writeable API Directory
API directories die when only humans can write to them; agents need to be first-class registrants so the directory's feedback loop stays alive at agent-web scale.
Take Control Of Your Signals — Become a Naftiko Design Partner Today!
Persona Story:
Nina has watched Reddit, Quora, and Stack Overflow decline — not because users stopped reading the answers, but because nobody is going to answer the questions. The feedback loops are broken. The same fate is waiting for any API directory that only accepts human-written registrations. For the agent web to function, agents themselves have to be able to write new API registrations into the directory and become a real part of the feedback loop.
Problem Context
- Public directories’ feedback loops collapse when only humans can write to them — the lesson from Reddit / Quora / Stack Overflow’s decline
- The agent web needs registries that agents can write into directly, not just read from
- An add-flow that accepts agent submissions must validate, classify, and publish without manual gatekeeping at every step
- This is a network-effect moat: an agent-writeable directory compounds in value once agents start writing
Problem Impact
- Read-only directories stop reflecting reality within months as new APIs ship faster than humans can register them
- Agents that discover new APIs cannot share that discovery back, so the directory falls behind the actual API landscape
- The directory becomes a curated museum instead of a living index
- The agent web fragments into private agent-side knowledge bases because the public commons isn’t writeable
Naftiko Today
- Executable YAML capability specs are a structured submission format agents can produce, so an agent’s “register this” action lands in a directory as auditable content
- JSON Schema validation gates agent-written submissions on structural conformance before they publish
- Spectral ruleset (15 rules) lets a directory enforce policy on agent-written entries the same way it enforces policy on human-written ones
- MCP exposure layer turns the directory itself into an agent surface that agents can call to add, search, and update entries
Naftiko Tomorrow
- Tool annotations (Second Alpha) will let the directory distinguish read-only discovery tools from write-back registration tools so agent permissions can be scoped accordingly
- MCP auth support (Second Alpha) will let the directory enforce identity on agent writers, keeping spam and bad-faith registrations out
- Webhook adapter (Second Alpha) will let downstream consumers subscribe to agent-written additions in real time, completing the feedback loop
- Fabric capability discovery (v1.1) will publish the directory as part of the enterprise capability fabric so agent-written entries propagate across the ecosystem