Private · API-first · ECU tuning

Tune by API.
Ship maps at machine speed.

A headless tuning platform where every mappack, project and map version is created over a REST API — so your AI agent writes safe maps as fast as you can review them.

agent · POST /v1/projects/:id/versions
bash
$ curl -X POST https://api.stagemod.dev/v1/projects/prj_8f3a/versions \
    -H "Authorization: Bearer sk_live_••••••••••••" \
    -H "Content-Type: application/json" \
    -d '{ "stage": 2, "notes": "+18% boost, lambda held 0.86" }'

▸ 201  version v4 created · checksum OK · within limits ✓
1900+Control units
6.8MCatalogued maps
<200msMedian API write
The platform

The stack for headless tuning

Everything a tuning agent needs, exposed as a clean, scoped, snake-case REST API.

API-first mutations

Every create, upload and version lands over REST. Drive the whole platform from Claude Code or any agent.

Shared catalogue

Mappacks indexed by ECU and engine, shared across the group. Reference, never re-derive.

Versioned projects

Original file → an immutable version timeline with notes, diffs and a full safety verdict per write.

Logs & DTCs

Attach datalogs and fault codes to any version. RPM, boost, lambda, EGT and knock, in context.

Safety catalogue

Machine-readable lambda, boost and timing limits the AI reads before it tunes — gasoline and diesel.

Closed group

Invite-only. First login becomes admin. Per-user, scoped API keys — no public signup, no marketplace.

The loop

From token to shipped map

Three steps. The agent does the typing; you keep the judgment.

  1. 01

    Get an API key

    An admin invites you; mint a scoped token from the dashboard. Treat it like a password — it authenticates your headless agent.

  2. 02

    Point your agent

    "Write a stage-2 mappack for this ECU." It calls the API, reads the catalogue limits, and stays inside the safe envelope.

  3. 03

    Review & ship

    Versions, logs and DTCs land in the dashboard with checksum and within-limits verdicts, ready for your sign-off.

Tuning depth

Stages, color-coded and bounded

Each stage is a contract: what it touches, and the limits it must respect.

Stage 1+15–25%

What it touches

Boost, fuelling and timing tuned on the stock hardware envelope.

Limits respected

Lambda windows and knock margin held; no mechanical changes assumed.

Stage 2+25–35%

What it touches

Optimised for bolt-ons — downpipe, intake, intercooler.

Limits respected

Higher boost targets, EGT ceilings respected per the diesel/gas catalogue.

Stage 3+35–60%

What it touches

Hybrid turbo and hardware-supported maps with reworked load tables.

Limits respected

Driveline strain caps enforced; flagged for human review before ship.

CustomBespoke

What it touches

Per-vehicle goals — economy, race fuel, methanol, transmission logic.

Limits respected

Constraints set explicitly; the agent tunes only within them.

Safety catalogue

The AI reads the rules before it tunes

Our info-catalogue is machine-readable: lambda and AFR windows, timing ceilings, boost and driveline strain limits — for both gasoline and diesel. Agents fetch limits via /v1/catalogue and stay inside the safe envelope. Every version write is checked against it.

catalogue.jsonjson
GET /v1/catalogue

{
  "object": "catalogue",
  "gasoline": {
    "lambda_min_wot": 0.78,
    "knock_margin_deg": 2,
    "boost_max_bar": 1.8,
    "egt_max_c": 950
  },
  "diesel": {
    "egt_max_c": 780,
    "boost_max_bar": 2.6,
    "rail_pressure_max_bar": 2200
  }
}
Closed group

Built for one workshop and its tuners. Not a marketplace — a private toolchain.

No vanity logos, no leaderboard. Just a tight group of tuners and the agents they trust, sharing one catalogue and one API.

Per-project ownership & scoping
Invite-only no public signup
Scoped keys per agent, revocable
Get started

Ready to tune headless?

Access is invite-only. Ask your admin for a seat, or request one — then point your agent at the API and start shipping versions.