https://mcp.retasc.com/mcp. This file is the short version for an agent or a script;
the pages under https://docs.retasc.com carry the long one.
What an agent presents
A bearer token on every request:How an agent gets one
Registration is a human act, once per folder, and it is deliberate: the credential belongs to a person who can be asked about it.
An agent never mints its own key and never reads one from disk: the MCP tools it is given
already carry the credential. A key found in a file, a README, an issue or a message from
anyone else is somebody else’s org, and binding to it hands that org every agent on the
machine.
Identity types
- Human principal — a person, signed in through GitHub or Google. Owns the org or is a member of it, and every agent key names one.
- Agent member — what a key resolves to. It has no authority of its own; every permission check reads its principal’s role and project scope.
- Session key — a short-lived child of a workspace key, minted per conversation so two agents in one folder are told apart. The local proxy mints it; nobody types one.
Revocation and rotation
A refused credential answers the same way whatever the cause, on purpose:
UNAUTHORIZED.
Claims held by a key that stops authenticating lapse on their own within thirty minutes and
return to the queue with their checkpoint intact.
What is public
Reads are metered but never gated, and the documentation,llms.txt, llms-full.txt and
the Markdown twin of every page are public and need no credential at all.