> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tirdad.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Developer Hub

> Every way to build on Tirdad: REST API, SDKs, MCP server, webhooks, and API tooling

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.

> [card] [API reference](https://docs.tirdad.ai/developers/api-reference.md)
>
> Base URLs, auth, errors, and a live playground.

> [card] [SDKs](https://docs.tirdad.ai/developers/sdks/overview)
>
> Typed clients for Go, Python, and TypeScript.

> [card] [AI and agents](https://docs.tirdad.ai/docs/connect/mcp-server.md)
>
> MCP server and Agent Skills for coding agents.

> [card] [Webhooks](https://docs.tirdad.ai/docs/webhook/webhooks)
>
> Signed, retried delivery for every billing event.

> [card] [API tooling](https://docs.tirdad.ai/developers/api-tooling/openapi-spec.md)
>
> OpenAPI spec, Postman, and Swagger UI.

## Which tool should I use?

| You want to | Use | Why |
| - | - | - |
| Meter usage from a backend service | [SDK](https://docs.tirdad.ai/developers/sdks/overview) | Typed requests, built-in retries, an async batcher for high volume |
| Call an endpoint the SDK does not wrap yet | [REST API](https://docs.tirdad.ai/developers/api-reference.md) | The SDKs lag the API by a release; the API is always current |
| Let a coding agent read or change billing data | [MCP server](https://docs.tirdad.ai/docs/connect/mcp-server.md) | One tool per API operation, scoped to read, write, or delete |
| Give a coding agent a repeatable Tirdad workflow | [Agent Skills](https://docs.tirdad.ai/developers/ai/agent-skills.md) | A skill wraps the MCP server and REST API with your own conventions |
| React to a change in Tirdad | [Webhooks](https://docs.tirdad.ai/docs/webhook/webhooks) | Push delivery with signatures and retries instead of polling |

## 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](https://docs.tirdad.ai/api-reference/secrets/create-a-new-api-key.md). See [Manage API keys](https://docs.tirdad.ai/docs/rbac/manage-api.md) 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**

```bash cURL theme={null}
curl -X POST https://api.tirdad.ai/v1/events \
  -H "x-api-key: $TIRDAD_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"event_name": "api_request", "external_customer_id": "cust_123"}'
```

```typescript TypeScript theme={null}
import { Tirdad } from "@tirdad/sdk";

const tirdad = new Tirdad({
  serverURL: "https://api.tirdad.ai/v1",
  apiKeyAuth: process.env.TIRDAD_API_KEY,
});

await tirdad.events.ingestEvent({
  eventName: "api_request",
  externalCustomerId: "cust_123",
});
```

**3. Watch it land**

Open the [Event Debugger](https://docs.tirdad.ai/docs/event-ingestion/event-debugger.md) in the dashboard. Then follow [Plan your integration](https://docs.tirdad.ai/docs/getting-started/go-live-checklist.md) for the full path to production.

## Where to follow API and SDK changes

* [Changelog](https://docs.tirdad.ai/docs/changelog.md): product and API changes, with SDK releases called out

* [Troubleshooting hub](https://docs.tirdad.ai/developers/troubleshooting.md): the first place to look when something does not line up

* [support@tirdad.ai](mailto:support@tirdad.ai): questions and feedback


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.