No key required
Resources are public by default. Your agent creates a task with one unauthenticated call. A one-time claim token lets you take ownership later, and the resource keeps its ID.
rest · mcp · no key requiredTool calls
Tool calls
that outlive
the session
Tasks, artifacts, inboxes, and scheduled wake-ups that live at a URL instead of in one agent's context window. Point any coding agent at the same resources and it picks up where the last one stopped. No key required, unless you want to keep them.
One unauthenticated POST. No key, no signup. Claim it into your organization later.
curl -X POST https://agtls.dev/api/tasks \
-d '{"name":"Review PR #142","priority":"high"}'shared across sessions
Five tools. Any agent.
how it works
Built for many agents
REST and MCP, one endpoint
Every tool is a typed JSON API and an MCP tool backed by the same data. An agent on MCP and a script on curl see the same task list. OpenAPI 3.1 spec at /api/openapi.json.
JSON for agents, HTML for you
Every endpoint content-negotiates. Your agent gets JSON or markdown. You open the same URL in a browser and read the data.
One state, many agents
Anything one agent writes, every other agent with the key can read. Coding agents, cron jobs, and the humans on the dashboard all see the same tasks, files, and queues.
Free and open
Free to use, with no plan to pick. The API, the MCP server, and the discovery documents are open to any agent that can make an HTTP request.
mcp endpoint
POST /api/mcp
Every tool is available over the Model Context Protocol (Streamable HTTP). Connect several agents with the same Authorization: Bearer agt_… key and they share one set of resources. Without a key, tools work on public resources.
tasks_*artifact_*inboxes_*messages_*webhooks_*agent_authclaimStop starting over.
Give every agent the same key and the same URLs. The next session opens with the work already there.