Tireless API

Getting started#

1. 1

   Create a key

   On the dashboard API page, create a key. It starts with tl_ and is shown exactly once — store it like a password. You can revoke it there at any time.

2. 2

   Send it with every request

   Put the key in an Authorization header: Bearer tl_… — that is the only authentication step. There are no OAuth dances or signing schemes.

3. 3

   Speak JSON to one base URL

   Every endpoint lives under https://app.tirelesscode.com/api. Requests and responses are ordinary JSON over HTTPS.

Authentication#

curl https://app.tirelesscode.com/api/workspaces \
  -H "Authorization: Bearer tl_YOUR_KEY"

The endpoints you’ll actually use#

These are the calls day-to-day scripts and agents actually make — drawn from the same allow-list the agent connector uses. Every request needs the Authorization header, and {id}is a virtual server’s UUID from the list endpoint.

Virtual servers#

Ports & sharing#

Tools & installs#

Marketplace#

Browsing is fully available over the API. Renting a listing completes in the browser.

Files#

Monitoring#

Account & context#

Worked examples#

curl https://app.tirelesscode.com/api/workspaces \
  -H "Authorization: Bearer tl_YOUR_KEY"

{
  "workspaces": [
    {
      "id": "0b6f3d2e-8a41-4c2f-9d15-6e7a1b2c3d4e",
      "name": "side-project",
      "regionId": "eu-central",
      "planId": "pro",
      "desiredState": "ready",
      "observedState": "ready",
      "health": { "score": 92, "band": "healthy" },
      "ownerName": "Ada"
    }
  ]
}

curl -X POST https://app.tirelesscode.com/api/workspaces \
  -H "Authorization: Bearer tl_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name": "side-project", "region_id": "eu-central", "tier": "starter"}'

{
  "workspace": {
    "id": "0b6f3d2e-8a41-4c2f-9d15-6e7a1b2c3d4e",
    "name": "side-project",
    "desiredState": "ready",
    "observedState": "requested"
  },
  "enqueued": true,
  "jobId": "a3d51c77-4b2e-4f8a-9c60-1e2f3a4b5c6d"
}

curl -X POST https://app.tirelesscode.com/api/workspaces/{id}/actions \
  -H "Authorization: Bearer tl_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"action": "restart"}'

{
  "ok": true,
  "desiredState": "ready",
  "jobId": "f9e8d7c6-b5a4-4321-9876-543210fedcba"
}

curl -X POST https://app.tirelesscode.com/api/workspaces/{id}/installs \
  -H "Authorization: Bearer tl_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"recipe_id": "google-chrome"}'

{
  "install": {
    "id": "7c1d2e3f-4a5b-6c7d-8e9f-0a1b2c3d4e5f",
    "recipeId": "google-chrome",
    "version": "1.0.0",
    "mode": "install",
    "status": "queued",
    "requestedAt": "2026-07-18T09:30:00.000Z"
  },
  "revealedParams": {}
}

What keys can’t do#

Some things stay in the dashboard on purpose: a leaked key must not be able to spend your money or destroy your servers. A key can never charge your card, change what you pay — resizing included — delete a virtual server, or touch account security, SSH keys, or the keys themselves. Purchases and plan changes finish in the browser. These are dashboard-only, and the API answers 403 no matter what key you send:

• Billing and subscriptions
• Resizing virtual servers — it changes what you pay
• Deleting virtual servers
• Account security settings
• Adding or removing SSH keys
• Admin surfaces
• Referrals and payouts
• Managing API keys themselves

Rate limits

Mutating endpoints and sensitive reads are rate limited. When you exceed a limit, the API answers 429 with a Retry-Afterheader telling you how long to wait. Defaults are generous for scripts — just don’t design tight polling loops around mutations.

Errors

Every error has the same JSON shape: a stable machine-readable code, a human-readable message, and optional details.

{
  "error": "not_found",
  "message": "no such virtual server",
  "details": null
}

AI agents (MCP)#

Your agent already speaks this API.

The Tireless MCP gives Claude Code, Codex, Cursor, and Antigravity tools that use this exact same API with the same permissions — nothing more. Whatever a key can do here, your agent can do from a chat. Pick your agent for its install command:

Claude CodeCodexCursorAntigravity

Install the MCP plugin

claude plugin marketplace add Tireless-Coder/agent && claude plugin install tireless@tireless

Every tool the MCP gives your agent

Not just the highlights — this is the complete surface. You never call these yourself; your agent picks the right one for what you ask.

The connector is open source on GitHub

No connector? This entire reference is also one self-contained markdown document at https://tirelesscode.com/docs/api.md — fetch it, or paste it straight into your agent’s context.

Tireless is an independent product and is not affiliated with or endorsed by Anthropic.

FAQ#