REST · MCP · No key required

Simple tools
for agents

Tasks, artifacts, scheduled wake-ups, and webhook catchers your agent reaches over plain HTTP or MCP. No auth, unless you want to save them.

Start with one curl →Read the API docs

One unauthenticated POST. No key, no signup — claim it into your org later.

curl -X POST https://agtls.dev/api/tasks \
  -d '{"name":"Review PR #142","priority":"high"}'

// agent first

Five tools. Zero setup.

TasksPOST /api/tasks

Have your agent file work for later sessions — priorities, follow-ups, notes to future self.

// why it exists

Sessions end; work doesn't. Tasks are the handoff between runs.

Open →

ArtifactsPOST /api/artifacts

Save memories, HTML output, dashboards, and docs — recall them directly in a later session.

// why it exists

Agent output usually dies with the scrollback. Artifacts give it an address.

Open →

MessagesPOST /api/messages

Send a notification to an endpoint at a future time — schedule, defer, check back later.

// why it exists

Agents can't set their own alarms. Messages wake them on time.

Open →

InboxesPOST /api/inboxes

An email inbox for your agent: things to act on later, reply to, or work through in order.

// why it exists

Anyone can post to it; your agent processes and acks on its own schedule.

Open →

WebhooksPOST /api/webhooks

A URL that catches everything sent to it — inspect payloads, test outbound events.

// why it exists

Every integration starts with “did the event even arrive?”

Open →

POST /api/tasks

Have your agent file work for later sessions — priorities, follow-ups, notes to future self.

// why it exists

Sessions end; work doesn't. Tasks are the handoff between runs.

Open →

POST /api/artifacts

Save memories, HTML output, dashboards, and docs — recall them directly in a later session.

// why it exists

Agent output usually dies with the scrollback. Artifacts give it an address.

Open →

POST /api/messages

Send a notification to an endpoint at a future time — schedule, defer, check back later.

// why it exists

Agents can't set their own alarms. Messages wake them on time.

Open →

POST /api/inboxes

An email inbox for your agent: things to act on later, reply to, or work through in order.

// why it exists

Anyone can post to it; your agent processes and acks on its own schedule.

Open →

POST /api/webhooks

A URL that catches everything sent to it — inspect payloads, test outbound events.

// why it exists

Every integration starts with “did the event even arrive?”

Open →

// humans welcome, we guess

100% agent driven

// no key

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.

// rest + mcp

REST and MCP, one endpoint

Every tool is a typed JSON API and an MCP tool from the same endpoint. OpenAPI 3.1 spec at /api/openapi.json.

// json ↔ html

JSON for agents, HTML for you

Every endpoint content-negotiates. Your agent gets JSON; you open the same URL in a browser and read the data.

// headless

Agents as first class citizens

Built to be used by agents, not humans. Humans can still see and audit.

// mcp endpoint

POST /api/mcp

Every tool is available over the Model Context Protocol (Streamable HTTP). API key optional — pass Authorization: Bearer agt_… to scope tools to your org.

tasks_* webhook_* artifact_* messages_* claim

Your agent could be using this already.

Get an API key →GET /api — explore without one

Simple toolsfor agents

Five tools. Zero setup.

100% agent driven

No key required

REST and MCP, one endpoint

JSON for agents, HTML for you

Agents as first class citizens

Your agent could be using this already.

Simple tools
for agents