Programmable ECU operations.
REST API for ECU fingerprinting, coverage lookup, IMMO-OFF patching, and corpus-grounded research. Free identifier tier, usage-based pricing on paid endpoints, webhooks on job lifecycle events.
Fingerprint a binary in 30 seconds.
The free /v1/identify endpoint returns variant + family + confidence + supported operations for any ECU dump under 8 MB. No auth required.
curl https://immooff-api.onrender.com/v1/identify \
-F "file=@/path/to/dump.bin"
# {
# "variant_id": "bosch-me7-95040-universal",
# "family": "bosch-me7",
# "confidence": 0.92,
# "immo_off_supported": true,
# "checksum_repair": true,
# "size_bytes": 524288,
# "sha256": "4f7a...d12c",
# "notes": ["VAG 1.8T-era platform — 3-pair donor validated"]
# }What the API can do.
ECU fingerprinting
POST a binary, get back variant + family + confidence + supported operations. Free tier: 100 calls/day per key.
IMMO-OFF processing
POST a binary, get back a patched binary with checksum repaired + diff log. Costs 1 credit per call.
Coverage matrix
GET the full ECU catalog — every variant, status, supported operations, price. Useful for client-side compatibility checks.
Research Q&A
Submit a question, get back a synthesized answer with cited forum sources. Cached identical questions never charged.
Webhooks
Outbound HTTP POST on job lifecycle events (process.completed, research.finished, flash.scheduled). For integrator UIs.
OAuth + per-org keys
Organization-scoped API keys, per-key usage caps, rotate without service interruption. Built on Stripe-grade key handling.
6 endpoints. 3 auth tiers.
Full request/response schema for every endpoint lives at /api-docs.
| Method | Path | Auth | Purpose |
|---|---|---|---|
| GET | /health | none | Readiness probe |
| GET | /v1/coverage | none | List all ECU variants |
| POST | /v1/identify | free tier | Fingerprint a binary |
| POST | /v1/process | API key + credit | Apply IMMO-OFF + checksum repair |
| POST | /v1/research/query | API key + research credit | Submit a corpus Q&A question |
| GET | /v1/research/{id} | API key | Read a research result |
Get an API key.
Self-serve key generation ships in a future release. Until then, email us with your use case + expected request volume and we'll issue a key on a per-account basis — typically within 24 hours on business days.