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 athttps://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
- Changelog: product and API changes, with SDK releases called out
- Troubleshooting hub: the first place to look when something does not line up
- support@tirdad.ai: questions and feedback