Skip to main content
Tirdad exposes one REST API, and every other developer surface is a wrapper around it. Pick the surface that fits where your code runs, then move between them freely: an object you create with the SDK shows up in the dashboard, and a webhook fires no matter which client made the change.

API reference

Base URLs, auth, errors, and a live playground.

SDKs

Typed clients for Go, Python, and TypeScript.

AI and agents

MCP server and Agent Skills for coding agents.

Webhooks

Signed, retried delivery for every billing event.

API tooling

OpenAPI spec, Postman, and Swagger UI.

Which tool should I use?

What every Tirdad surface shares

One API key, one environment. An API key belongs to a single environment (sandbox or production). The SDKs read the same key and never need an environment flag. The MCP server takes the same key. Create keys in the dashboard under Developers, or with the API keys endpoint. See Manage API keys for roles and scopes. One base URL. Every client is pointed at https://api.tirdad.ai/v1, including the /v1 suffix and no trailing slash.

Start building in five minutes

1

Create an API key

In the dashboard, open Developers, click Add, and choose Read & Write. Copy the key when it is shown; it is not displayed again.
2

Send one usage event

3

Watch it land

Open the Event Debugger in the dashboard. Then follow Plan your integration for the full path to production.

Where to follow API and SDK changes