The surface where developers and agents meet your API

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

Three practices

We work on the surface of your company that developers actually touch. The practices overlap, and most engagements start in one and bleed into the next.

Developer Experience (DX)

Treat your SDK as infrastructure, not a side project. Reproducible, idiomatic in each language, tested, documented, on a release pipeline. We make generated SDKs production-grade, ours or anyone else's.

Developer Experience

Agent Experience (AX)

Your API as an AI agent sees it: MCP servers, tool schemas, error semantics an agent can act on. The practice barely has a name yet, two years old as a category.

Agent Experience

Developer Relations (DevRel)

Where Voxgig started. Community programs, Developer Advocate roles, technical content strategy, Fractional CTO.

Developer Relations

How we engage

We're a consultancy, not a SaaS. No per-seat pricing, no annual lock-in. Engagements tend to take one of three shapes:

Retainer

When you need us in the room while the decisions get made. Fractional CTO seat, DevRel program lead, an MCP rollout already in flight.

Fixed-price

When the scope is clean and you want a number up front. A production-readiness sprint for a generated SDK, a first MCP server, a documentation audit.

Time & materials

When the work is exploratory and nobody can honestly scope it yet.

Pricing follows discovery, not a rate card. After a 30-minute call you'll know what the engagement looks like and what it costs. No surprises later.

Where the practices meet

DX, AX, and DevRel are three different briefs with one question under all of them: can a human, and now an agent, actually 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 us 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 quietly depends on. Larger companies hire us across all three and let us run their developer-facing surface as the lead consultancy. The practices are separate. The work rarely is.

Some of our work

Published case study

A non-technical CEO, a technical company. Voxgig's Fractional CTO and Developer Management work helped a non-technical founder secure investment and win high-value contracts. The full story.

Read the case study

In progress · 2026

An API-first SaaS SDK and MCP engagement, the first production roll-out of the SDK Generator alongside the AX practice. We publish once the client has signed off, not before.

In progress · 2026

A DevRel program from a standing start, cold start to first-90-days operations for a seed-stage developer-tools company. We publish once the numbers say something real.

Richard Rodger founded Voxgig in 2018. The team is small, small enough that the people you talk to are the people doing the work. Offices in Dublin and Brentford.

Since 2018
doing Developer Relations, and recording Fireside.
249+ episodes
of Fireside, the podcast we actually run on the work.
500+ SDKs
shipped through the open-source generator (@voxgig/sdkgen).

Start with a 30-minute call

Free, no scope, no slide deck. We talk about what you're trying to ship and what we'd do first, whether or not we end up being the ones to do it.

Get the Voxgig dispatch

Short notes on building SDKs, CLIs, REPLs, and MCPs for API-first teams, plus the occasional Fireside episode pick.

By signing up you agree to our Terms and Conditions.