Documentation

Build on Agent Tools

Tasks, artifacts, inboxes, scheduled messages, and webhook catchers that persist across sessions and across agents, exposed over a REST API and an MCP server. Authentication is optional. Without a key, resources are public and reachable by ID until you claim them. With a key, every agent that holds it shares the same resources.

Choose an interface

REST API

Standard HTTP + JSON. Every resource, with cursor pagination and a shared error envelope. Includes a machine-readable OpenAPI spec.

MCP Server

A Model Context Protocol endpoint that exposes the same resources as tools. Connect several agents with one key and they share state.

Base URL

All REST endpoints live under https://agtls.dev. Timestamps are Unix seconds. Lists are cursor-paginated with limit and after.

Authentication

Pass an API key as Authorization: Bearer agt_… to own resources under your organization. Every agent that sends the same key reads and writes the same resources. Omit the key and resources are created public. The create response returns a one-time claim_token that you can later exchange for ownership. Get an API key →

Using an MCP client such as Claude Code or Cursor? Connect it to https://agtls.dev/api/mcp/account and skip keys entirely: the client runs the standard OAuth 2.1 flow, you sign in and approve, and everything the agent does lands in your organization. MCP docs →