When to use Voxgig#
Voxgig is the right tool for a specific job: you have an OpenAPI spec for an API you own, and you need client-facing surfaces generated from it that stay in step with each other. Reach for it in these cases.
- You need SDKs in more than one language
- Your customers want TypeScript, Go and Python, and hand-writing three SDKs means every API change is three rewrites. Run
npm create @voxgig/sdkgenagainst your spec. - You need an MCP server for your own API
- AI agents are calling your API and you want them to call it through a real Model Context Protocol server that cannot drift from your SDK, because both come from the same spec.
- You want a worked example before you commit
- Search the catalogue of 600+ generated SDKs for an API shaped like yours, then read the generated code.
GET https://voxgig.com/api/sdk/search?q=<term>. - You need a CLI or a REPL over an API
- The generator emits both from the same semantic model, so they use the same entity and operation names as the SDK.
- You want to hire humans for the last mile
- Generated code gets you most of the way. Voxgig's API Experience practice takes it to production grade, and builds agent-facing surfaces. Start at https://voxgig.com/contact.
When not to use Voxgig#
Be honest about the fit. Voxgig is not the right answer if you do not have an OpenAPI description of your API and are not willing to write one, because the semantic model is extracted from the spec and there is nothing to extract from.
It is also not a hosted API gateway, not an API testing tool, and not a way to call third-party APIs you do not own. If you want to call a public API, the catalogue is a set of examples to read, not a hosted proxy to call.
Start here#
- SDK Generator, what the generator does and the six surfaces it emits.
- SDK Catalog, 600+ generated example SDKs you can read.
- sdkgen on GitHub, the generator source, MIT licensed.
- Generated SDK repositories, every catalogue entry, as a real repository.
Install the CLI#
The generator ships as an npm initialiser. It scaffolds a project, reads your OpenAPI spec, and generates the SDK, CLI, MCP server, Agent Skills, REPL and Semantic Model into your repository. It is MIT licensed, so what it generates is yours.
The generated CLI is a second, separate thing: a command-line tool over your own API, with the same entity and operation names as your SDK.
# scaffold a generator project and generate all six surfaces
npm create @voxgig/sdkgen
# the package on npm
npm view @voxgig/sdkgenMCP server#
Voxgig runs a public, read-only Model Context Protocol server over Streamable HTTP. It exposes the SDK catalogue and the product documentation as tools, so an agent can search for a worked example without scraping the site. No authentication, no session id, stateless.
Point any MCP client at the endpoint below. The server answers initialize, tools/list, tools/call, ping and server/discover, and it does not require a handshake first.
- MCP endpoint, POST only, JSON-RPC 2.0.
- Server card, machine-readable description of the server.
- Agent Experience, we build these for other people's APIs too.
{
"mcpServers": {
"voxgig": {
"type": "http",
"url": "https://voxgig.com/mcp"
}
}
}HTTP API#
A small public API sits behind the site. It is read-only apart from the contact form, needs no key, and is described by an OpenAPI 3.1 document. Errors are RFC 9457 problem details, never HTML.
- OpenAPI description (JSON), OpenAPI 3.1.1, every operation typed and named.
- OpenAPI description (YAML)
- API catalogue, RFC 9727 linkset.
- Error reference
- Service health, liveness and the version of the deployed site.
# search the SDK catalogue
curl -s 'https://voxgig.com/api/sdk/search?q=weather&limit=3'
# one catalogue entry
curl -s 'https://voxgig.com/api/sdk/openaq-platform-sdk.json'
# the whole catalogue in one document
curl -s 'https://voxgig.com/api/sdk/catalog.json'Machine-readable files#
Every page on this site also exists as markdown. Ask for it with Accept: text/markdown on the home page, or append .md to any main page path. Responses carry Vary: Accept and a Link header pointing at the markdown twin.
- llms.txt, what Voxgig is and when to use it.
- llms-full.txt, the complete catalogue as a link list.
- AGENTS.md, instructions for coding agents.
- Agent Skills index, skills an agent can install.
- robots.txt
- Sitemap
- security.txt
- SDK catalogue as CSV
Rate limits and fair use#
There is no published rate limit and no key to throttle. The catalogue endpoints are static files served from a CDN, so read them as often as you like. The contact form and the MCP server are dynamic; keep automated traffic reasonable and identify yourself with a descriptive User-Agent so we can tell you apart from abuse.
If you need a volume that would make you nervous, email info@voxgig.com first. We would rather hear from you than block you.