API Reference

The API is HTTP and JSON, served from https://app.trynito.ai with compatible inference and model endpoints under /v1, Fusion, web retrieval, document parsing, key management, and attestation under /api/v1, and MCP at /mcp. Document uploads use multipart form data. Authenticate with an organization API key (z_sk_...) as Authorization: Bearer <key>. Model discovery is public and requires no key. Endpoint pages use the published developer OpenAPI document.

Conventions

Areas

Area	Endpoints	Notes
Chat and text	`POST /v1/chat/completions`, `POST /v1/responses`, `POST /v1/messages`	Streaming, reasoning, function tools, web tools.
Fusion	`POST /api/v1/chat/fusion`	Two or three participants plus a synthesis; paid Fusion access required.
Web retrieval	`POST /api/v1/web/search`, `POST /api/v1/web/fetch`	Retrieve content without inference.
Documents	`POST /api/v1/attachments/parse`	Multipart file upload returning text and a token estimate.
API keys	`GET` / `POST /api/v1/api-keys`, `DELETE /api/v1/api-keys/{key_id}`	Organization key management with admin credentials.
Balance	`GET /api/v1/billing/balance`	Administrative credentials; integer USD nanos strings.
Rate limits	`GET /api/v1/rate-limits`	Non-consuming snapshots of selected request windows.
Models	`GET /v1/models`	The live catalog with capabilities and privacy levels.
Attestation	`GET /api/v1/attestation`	Request-local evidence for Confidential models.
MCP	`POST /mcp`	Hosted MCP for agent hosts.

Integrations can use Fusion through the HTTP API or the hosted MCP tool nito.chat_fusion. See Fusion.

Not on the API

Provider-hosted file APIs (/v1/files, /v1/uploads). Send documents and images request-locally. See PDF and document input.
Audio and video.
Encrypted requests: the headers and the flow. See Encrypted.

Basics

Features

Server-Side Tools

Multimodal

Best Practices

SDKs

API Reference

API Reference

Conventions

Areas

Not on the API

​Conventions

​Areas

​Not on the API

​Related

Conventions

Areas

Not on the API

Related