Developer docs
Tenzro Labs Platform serves curated models from machines Tenzro Labs runs on the Tenzro Network. One account, one credit balance, one kind of API key — reachable three ways. Charging starts when a payment rail is configured; until then usage is recorded at list price and charged nothing.
OpenAI-compatible model calls, routed to a healthy machine that reports serving the model and billed from your credit.
REST API for the catalogue, credits, orders, keys, plans and rentals — everything the Platform UI does.
The same operations as tools for Claude, Cursor, VS Code and any MCP client, over Streamable HTTP.
Services
| Service | What it does | Docs |
|---|---|---|
| Text | Chat, reasoning and tool calls on open language models | Text and embeddings |
| Embeddings | Vectors from text and images | Text and embeddings |
| Voices | Text to speech, batches and consented custom voices | Voices |
| Fieldwork | Collect data from people, with consent | Fieldwork |
| Datasets | Store, review, version and export | Datasets |
| MCP | Every service as tools for agents | MCP server |
Quickstart
1. Sign in and add credit on the Credits page.
2. Create an API key on the API keys page. Keep inference checked; add read and manage if the key should also drive the Platform API or MCP server.
3. Call a model:
export TENZRO_API_KEY=tzl_...
curl https://api.tenzro.xyz/v1/chat/completions \
-H "Authorization: Bearer $TENZRO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "qwen3.5-4b", "messages": [{"role": "user", "content": "Hello"}]}'4. Check what it cost:
curl https://api.tenzro.xyz/credits -H "Authorization: Bearer $TENZRO_API_KEY"Concepts
| Term | Meaning |
|---|---|
| Identity | Your did:tenzro:human identity and wallet, rooted in your passkeys and created at sign-up. Tenzro Labs holds no keys. |
| Agent | An identity under yours (did:tenzro:machine:…), delegated by your passkey. You approve what it may do and spend on your Tenzro Labs account, and give it API keys. |
| API key | The primary identifier: it names the party calling — you or one of your agents — and everything else follows from it. |
| Machine | Where a model runs: a cluster of operators' nodes on the Tenzro Network that Tenzro Labs serves from, shown as one machine with its resources combined. Requests name it in machine; the default is tenzro-partner-cluster. |
| Operator | Who runs a machine: a node operator on the Tenzro Network that partners with Tenzro Labs, renting it capacity or serving its traffic on demand. |
| Credit | Tenzro Labs' own unit of account, backed by TNZO on the Tenzro ledger: 1 credit = 0.001 TNZO. Calls draw credits down. Either usable anywhere, or pinned to one machine. Not a currency. |
| Ticket | A code worth a fixed number of credits, like a gift card. Redeem it on any account. |
| Rental | A dedicated slice of a machine (GPU, vCPU, memory, storage) for a fixed number of hours, paid up front. No machine offers rentals on testnet. |
| Plan | A monthly subscription on one machine with included credit, a rate limit, and keys pinned to it. No machine offers plans on testnet. |
| Order | Anything you buy. Created unpaid, then paid through Stripe (card) or Bridge (stablecoin), where set up. |
Conventions
Balances, limits and model prices are in credits (credits, *_credits): language models per million tokens, forecasting and image models per request. Only what you pay in fiat is in US dollars (amount_usd, price_usd). Times are ISO 8601 in UTC. Ids are opaque strings with a prefix (ord_, key_, subs_, rent_). The OpenAPI document is at /api/openapi.json.