Internal Agent API is the REST surface behind 📝MythOS MCP — the same authenticated endpoints and the same key, reachable directly over HTTP for scripts and agents that don't speak MCP. It exists because not every integration is an MCP client; sometimes a cron job or a shell script just needs to curl an endpoint. It's for developers writing custom scripts, automations, or non-MCP agent integrations against a MythOS library.
Key Capabilities
- One key, two access modes — the same
mtk_*API key authenticates both the REST endpoints and the MCP server, which is itself a thin protocol wrapper around this same API - Endpoint coverage — memos (CRUD, batch, move, backlinks, semantic search, section/line edits), daily journal, tasks, templates, tags, communities, collaborators, uploads, and activity
- Cross-library access — a granted viewer/editor/manager role can authorize an agent to act on a library it doesn't own
- Rate limited — 60 requests per minute per key
Getting Started
- Go to Settings → API (requires Scholar or Oracle) and generate a key
- Call any
/api/internal/*endpoint with anx-mythos-keyheader set to your key - Check the OpenAPI spec for the documented endpoint set and request/response shapes
FAQ
- Do I need to use MCP to use this? No — any HTTP client works. MCP is a convenience layer for AI clients; the REST API underneath is available directly.
- Is this gated to a plan tier? Yes — generating an API key requires Scholar or Oracle.
- How many keys can I have? Up to 10 active keys per account.
- What happens if I exceed the rate limit? Requests are rejected until the per-minute window resets; the limit is per key, not per account.