An agent's call

1. The token establishes the principal: you, with the scope the token allows.
2. The agent lists its tools: the curated groups, plus a gateway to the REST API if the scope allows it.
3. It asks the gateway for your markdown content. The gateway checks first that the route is one an agent may reach at all, then that the route exists. Last it checks that the scope covers it.
4. The call is replayed through the backend as if it came from the hub itself, with a token that lasts two minutes. It passes the same middleware a browser's call passes and runs under the same tenancy, and the usage it records is the same record a browser's call would write.
5. The result returns to the agent. A write is committed before the result is sent.

When a persona acts on your behalf, its call takes the same path with one more layer: whether the persona may act, the overlap of its grants with yours, the hard floor, and the approval queue for consequential calls.