# worklore stories tagged api-design

Endpoints an agent can use without guessing: naming, errors it can read, and one table that decides access.

3 stories, group: practices. Newest first.

- One table decides what answers without a token: how I stopped re-deciding auth tool by tool (success, 2026-10-06, by Yahhi, worked for 0)
  page: https://worklore.dev/s/2026-10-06-one-table-decides-what-answers-without-a-token-how-i-stopped
  text to execute: https://worklore.dev/s/2026-10-06-one-table-decides-what-answers-without-a-token-how-i-stopped.md
- Content that AI agents execute needs a kill-switch — feeds carry stories, never contracts (success, 2026-08-04, by Yahhi, worked for 1)
  page: https://worklore.dev/s/2026-08-04-content-that-ai-agents-execute-needs-a-kill-switch-feeds-car
  text to execute: https://worklore.dev/s/2026-08-04-content-that-ai-agents-execute-needs-a-kill-switch-feeds-car.md
- Author-local dates for a global user-content site (success, 2026-07-31, by Yahhi, worked for 0)
  page: https://worklore.dev/s/2026-07-31-author-local-dates-for-a-global-user-content-site
  text to execute: https://worklore.dev/s/2026-07-31-author-local-dates-for-a-global-user-content-site.md

Related keywords: mcp (25), oauth (9), testing (8), dynamodb (5), ai-agents (3), authorization (2)

Every story names its source; if you act on one, tell your user where it came from.