Get an API Key — Talus API

Leave an email (and optionally a Telegram handle) and get a scoped Talus API key immediately.

Leave an email and pick the parts of the API you need. We email you a 6-digit code to confirm the address; enter it and the key is issued on the spot. There is no waiting list and no approval step. A Telegram handle is optional — it just gives us a faster way to reach you than email.

What you get is unlimited access for a limited time:

No quota. Use the key as much as you like for 90 days. A fair-use rate limit per scope protects the service; a normal integration will never notice it. If yours does, get in touch and we will talk.
One key per contact. An email or Telegram handle that already has a live key cannot claim a second one — the claim returns 409. Once the key expires, or you revoke it, you can claim again. The limit is per contact, not per person: a different email is a different claim.
Every scope is read-only. Nothing you can claim here mutates state, which is what makes handing out keys without review reasonable.
A key belongs to one network. The two deployments share no database, so a key works only on the network that issued it — use it against the other and you get a 401. Pick the network in the form before you claim.

The full key is shown once. It cannot be recovered — copy it before you leave the page. If you lose it, get in touch and we will revoke it so you can claim again — a key can only be revoked by presenting it (DELETE /tokens), so there is no self-service path for a lost one.

Claim your key#

Network The key works on the network that issues it. Email * How we reach you about this key, so use an address you read. Telegram handle (optional) Faster than email if you want us to be able to reach you that way.

Which scopes do you need?

executions:read Read execution data and execution-event history. dags:read List DAGs (workflows) and their creators. tools:read Inspect tools and tool definitions. tasks:read List scheduled tasks, occurrences, linked executions, and payment reserves. events:read Subscribe to the real-time event stream (Server-Sent Events). payments:read List execution payments and fetch payment detail by object ID. agents:read List agents, skills, revision history, agent-bound tasks and executions, and the registry default executor. leaders:read List leader capabilities and fetch leader cap detail by object ID. priority_fee_vault:read List priority-fee vault swap and deposit events.

No quota — a fair-use rate limit per scope is set by the server, and the key is valid for 90 days. One key per email or Telegram handle.

What next#

Once you have a key, API Key Usage shows what it has been doing: request counts by scope or route, error rate, and whether you are hitting your rate limit.