The Vrtmv API

The Vrtmv API (vrtmv-api) is the authenticated service the client talks to. It is the only thing that connects to the Translation Index, and it is the account, licensing, and metering boundary.

Authentication

Every protected endpoint requires Authorization: Bearer <token>. Tokens are issued per account and are stored server-side only as a SHA-256 hash — the plaintext is never persisted. An account can hold multiple tokens, and each request is attributed to the token that authenticated it. See Authentication for the client side.

Request shape

• Requests and responses are JSON.
• Batch endpoints (resolve, translate, config-paths) accept up to 1000 items per call.
• Request bodies are size-limited and requests are time-bounded; a burst cannot exhaust the connection pool.

What the client sends

Only identifiers: package names, canonical slugs, a (source, target) release pair, and — for metering — a depersonalized VM fingerprint. Image contents and configuration never reach the API.

See Endpoints for the routes and Accounts, quota & billing for the commercial model.