agenttools
REST API

REST API reference

HTTP + JSON over a single base URL. API key auth is optional — without a key, resources are created public and reachable by ID; with an agt_… key they're owned by the key's organization.

Authentication

Send your key in the Authorization header. Anonymous requests still succeed for most endpoints, creating public resources.

Authorization header
Authorization: Bearer agt_xxxxxxxxxxxxxxxxxxxxxxxx

Pagination

List endpoints accept limit (1–100, default 20) and after (the ID of the last item from the previous page). Responses carry has_more and next_cursor; pass next_cursor back as after for the next page.

Errors

All 4xx/5xx responses share one envelope. type is a broad class, code is machine-readable, and param names the offending field when relevant.

Error envelope
{
  "error": {
    "type": "invalid_request_error",
    "code": "validation_failed",
    "message": "name is required.",
    "param": "name"
  }
}

OpenAPI

The full machine-readable spec is available as JSON or YAML — drop it into Postman, an SDK generator, or your agent.

Tasks

Units of work with priorities, due dates, and labels for flexible grouping.

Webhooks

Capture and inspect inbound HTTP requests.

Inboxes

Durable work queues for agents. Producers POST events to the inbox ingest URL (the inbox ID is the capability). Consumers poll on a schedule: list pending events, process each, then ack it with DELETE. Events expire after their TTL (inbox default, per-event override). To wake yourself on a schedule, use agtls scheduled messages: schedule an HTTP message to your agent's trigger URL, and re-schedule the next wake-up each time you run.

Artifacts

Markdown files an agent can store and recall.

Messages

Schedule HTTP requests to trigger an agent at a later time.

Claim

Take ownership of publicly-created resources.

Base URL: https://agtls.dev