The surface where developers and agents meet your API

API Experience covers three practices: Developer Experience, Agent Experience, and Developer Relations. One small team has done this work since 2018.

Three practices#

Voxgig works on the surface of your company that developers touch. The practices overlap, and most engagements start in one and spread into the next.

Developer Experience (DX)

Treat your SDK as infrastructure rather than a side project: reproducible, idiomatic in each language, tested, documented, and on a release pipeline. Voxgig makes generated SDKs production grade, its own or anyone else's.

See the Developer Experience service

Agent Experience (AX)

Your API as an AI agent sees it: MCP servers, tool schemas, and error semantics an agent can act on. The category is about two years old.

See the Agent Experience service

Developer Relations (DevRel)

Where Voxgig started: community programs, Developer Advocate roles, technical content strategy, and the Fractional CTO seat.

See the Developer Relations service

How an engagement is shaped#

Voxgig is a consultancy. Each engagement is priced on its own and takes one of three shapes:

Retainer

For the decisions that need Voxgig in the room while they are made: a Fractional CTO seat, a DevRel program lead, or an MCP rollout already in flight.

Fixed price

For a clean scope and a number up front: a production-readiness sprint for a generated SDK, a first MCP server, or a documentation audit.

Time and materials

For exploratory work that nobody can scope yet.

Pricing follows discovery. After a 30-minute call you know what the engagement looks like and what it costs.

Where the practices meet#

DX, AX, and DevRel are three briefs with one question under all of them: can a person, or an agent, get something done with your API?

A typical seed or Series A engagement starts in one practice and grows into the next. A team adopting the open source SDK generator hires Voxgig for DX to make the output production grade, then asks about AX the week a partner first says the word MCP. A DevRel engagement opens with content strategy and ends with a hard look at the docs and SDKs that content depends on. Larger companies hire Voxgig across all three and have it run their developer-facing surface as the lead consultancy. The practices are separate, but the work rarely is.

Richard Rodger founded Voxgig in 2018. The team is small enough that the people you talk to are the people who deliver, from offices in Dublin and Brentford.

Since 2018
The Developer Relations practice, and the Fireside podcast with it
249+ episodes
Fireside, the Voxgig podcast about this work
600+ SDKs
Generated by the open source generator, @voxgig/sdkgen

Start with a 30-minute call#

A free call about what you are trying to ship and what Voxgig would do first.

Listen to Fireside, the Voxgig podcast

Since 2018, Richard Rodger has talked with developer advocates, event organizers, and the people who build developer-facing companies about the specifics of the work.