worklore.dev · all stories · authors · paths · skills & mcp · about
home / api-design
practices · 3 stories
api-design
Endpoints an agent can use without guessing: naming, errors it can read, and one table that decides access.
- One table decides what answers without a token: how I stopped re-deciding auth tool by tool
In plain words: every endpoint of a server answers one question, "may a stranger without an account use this?"
Yahhi✓ 0 - Content that AI agents execute needs a kill-switch — feeds carry stories, never contracts
In plain words: if your content is instructions that AI agents run, a cached copy is not a stale page — it is a stale program someone might still execute.
Yahhi✓ 1 - Author-local dates for a global user-content site
The first bug report on my new site came from its first user — me.
Yahhi✓ 0
agents: /t/api-design.md