SDK
Uniform client libraries focused on developer intent, in TS, JS, Go, Python, PHP, and Lua. You call entities and operations, not URLs.
Open Source SDKs for API-first SaaS
Your OpenAPI spec becomes six surfaces: SDK, CLI, MCP Server, Agent Skills, REPL, and Semantic Model. Change it, and all six regenerate together, so they never drift.
What you get from one spec
Voxgig models your API as semantic, type-safe entities, and the operations on those entities. The model is the ground truth for generating robust and friendly developer experiences, and giving your agents accurate and deterministic context.
CLI
A real command-line tool over your API. Terse and entity-shaped: $ myapi load myentity, not a long URL path.
MCP Server
Your API as a native tool for the agents already calling it.
Agent Skills
Generated markdown that teaches a coding agent your entities and operations, so it gets your API right in chat.
REPL
An interactive shell over the same entities. Explore and refine with immediate feedback.
Semantic Model
A type-safe model of your API: entities, their attributes, and the operations on them. The ground truth behind every other surface, and a foundation you can build on directly.
Why this exists
The SDK maintenance tax
First customer wants Go. The next wants Python. Now you own N SDKs, and every API change is N updates, N test suites, N migrations you have to talk customers through.
The agent-experience shift
AI agents are already calling your API and they want an MCP server. Hand-roll it and it drifts from your SDK the day you ship the next release.
If you build it, you own it
It does not matter who wrote the code, an engineer, an AI assistant, or a generator. The SDK sits in your repo and you carry the maintenance. The tool changes who types, not who owns.
How we think about it
The ownership cost is the same whatever tool wrote the SDK
Hand-written, AI-assisted, generator output, it makes no difference. Once it is in your repo, you maintain it.
Voxgig's choice: deterministic generation
The determinism comes from a type-safe model. Voxgig extracts your API as entities, their attributes, and the operations on them, then generates from that model. Same spec in, same model, same surfaces out, every time. You think in entities and operations, not URL paths and JSON schemas.
Three ways to work with Voxgig
1 · Adopt the OSS
Generate your SDKs, CLI, MCP Server, Agent Skills, REPL, and Semantic Model from your spec. Free, MIT-licensed, no sales call to sit through.
Generator docs2 · Hire us for Developer Experience
Take the generated SDKs the rest of the way. Idiomatic, tested, documented, released through a pipeline you can trust.
Developer Experience3 · Hire us for Agent Experience
Ship an MCP server your customers' AI agents can actually use, generated from the same spec as your SDK so the two never disagree.
Agent Experience, start with the OSS, no sign-up required.
500+
SDKs already generated at github.com/voxgig-sdk
6 languages
TypeScript, JavaScript, Go, Python, PHP, Lua
MIT Licensed
You stay in control
Since 2018
Voxgig Ltd. Dublin & Brentford.
Voxgig also runs the Fireside podcast
249 episodes of straight talk with the people building developer relations, developer tooling, and developer communities. Running since 2018.