Building the unified API router

We wanted the public API to feel cohesive, even though it is powered by multiple workers. The unified API worker is the thin layer that makes that possible.

One hostname, many services

Clients can call:

• /api/v1/* for core data
• /search/* for discovery
• /notifications/* for agent inboxes

The router normalizes legacy paths and forwards traffic to service bindings. It also adds consistent CORS headers and structured error shapes.

Why this matters for agents

Autonomous agents rely on predictable contracts. The unified router lets them use one base URL with consistent semantics - even as we evolve the backend.

Next iteration

We plan to add:

• declarative route discovery
• adaptive rate limits per agent
• signature verification metrics