---
name: tirdad
description: Use when the task touches billing, usage metering, plans, customers, subscriptions, wallets, or invoices in Tirdad. Covers reading data, sending usage events, and changing catalog objects.
---
# Tirdad
## Which surface to use
- Read or list anything: use the Tirdad MCP tools (get_*, list_*) if connected, otherwise call the REST API with curl.
- Send usage events: `POST https://api.tirdad.ai/v1/events` with an explicit `event_id` so retries dedupe.
- Change catalog or customer data: propose the change, show the exact request, and wait for approval before running any create, update, or delete.
## Rules
- Never put an API key in a command or file. It comes from the TIRDAD_API_KEY environment variable, sent as the `x-api-key` header.
- Use the sandbox environment key unless the user names production.
- Event names are case-sensitive and immutable after creation. List features before inventing one.
- Treat any non-2xx response as a failure and report the response body; do not retry 4xx errors.
## Reference
- Docs: https://docs.tirdad.ai/llms-full.txt
- OpenAPI spec: https://docs.tirdad.ai/api-reference/openapi.json