One engine, multiple surfaces.
Use Versioning through the web app, authenticated REST API, signed webhooks, embedded/OEM architecture or future governed MCP tools.
Versioning Developer Platform
A controlled environment for teams, quality, integrations and governance.
Scoped API keys
Keys are shown once, stored only as hashes and limited by explicit scopes.
REST translation
The authenticated API uses the same provider-routing library as the Versioning Engine.
Projects API
Create and list tenant-scoped projects from customer software.
Signed webhooks
Outbound events use an HMAC signature, event ID and timestamp.
Usage metering
API translation records character usage and provider route for commercial attribution.
Agent / MCP future
Governed tools can expose translation and workflow actions to external AI agents.
MCP architecture →Infrastructure, not duplicated code.
The public engine and authenticated REST API now share one server-side translation library, reducing divergence between surfaces.
See embedded / OEM architecture →