mivia / docs / api
Api
One key, one billing surface, one contract. Every api mivia ships lands here; the same bearer key works across all of them against one prepaid balance. Requests are processed in memory and discarded; api traffic is never training data.
Surfaces
Every api speaks REST and streamable-http MCP from one container behind one bearer key. Call it from plain HTTP or from any MCP client (Claude, Cursor, your own agents).
- Quickstart - your key and your first call
- REST api - every endpoint with real examples
- MCP - tools for Claude, Cursor, and your agents
- Authentication - key format and handling
- Errors - every status code and refusal
- Pricing - rates, free tier, rate limits
mivia-small-json
api 01. Any text in, strictly valid JSON out: twelve built-in schema classes plus your own registered schemas, picked zero-shot. Every input returns a structured record with confidence or a typed clarification, never a refusal and never invalid JSON.