RemapdbRemapdb

For software and product teams

Add vehicle tuning data to your software platform

Connect your software to the Remapdb vehicle tuning database through the REST API. Retrieve vehicle records, engine information, and reference tuning figures while keeping customer accounts and business logic in your own system.

Explore the APICompare API plans

REST API and MCP access require API or Max. The Free widget plan does not include developer API access.

How Remapdb fits

Build your product around structured vehicle records

Your application may need a vehicle selector, an internal lookup screen, or tuning context beside an enquiry. Remapdb provides the catalog and documented data endpoints. Your developers decide how to present the records and connect them to the workflows that make your product useful.

Vehicle hierarchy and search

Browse by vehicle type, manufacturer, model, generation, and engine, or use search. Test relevant records and handle empty results.

A catalog that fits your account

API reads use the shared catalog on the API plan. On Max, API v2 can return your added records, edits, and visibility choices managed in the app.

A choice of interface

Build a custom UI with REST access, embed the ready-made widget, or connect a supported AI client through MCP. Each approach has its own setup requirements.

Your setup

Validate the integration before expanding it

  1. Confirm data and access

    Review coverage, returned fields, and API or Max plan access. Check the current API reference and usage limits.

    Video tutorialWatch API access and credentialsStarts at 0:18 · 3:23 total

  2. Build and test on your backend

    Store credentials securely, handle errors and missing values, and keep account-specific catalog responses separate in your cache.

    Video tutorialWatch secure configuration and access checksStarts at 0:35 · 3:23 total

  3. Connect your product workflow

    Pass the selected vehicle into your own quoting, ordering, or support process. Test that the displayed information and subsequent action remain consistent.

    Video tutorialWatch the backend-to-browser connectionStarts at 1:28 · 3:23 total

Before you choose

A vehicle-data service with a defined scope

Remapdb does not provide vehicle diagnostics, ECU flashing, calibration-file generation, payment processing, or a complete multi-user dealer portal. Your software may provide those functions independently. Reference tuning figures also do not establish the suitability of a calibration or hardware product for an individual vehicle.

Choose by the features you need

  • API. Read the shared vehicle catalog through REST and supported MCP tools.
  • Max. Combine catalog editing with API v2 access to your account catalog, plus advanced widget features.
  • Request volume. Review the documented usage limits and your expected traffic before choosing a plan.
Compare plans and limits

FAQ

Questions before you start

Does Remapdb build the platform for us?

No. Your technical team implements the application and integration. Remapdb provides product documentation and support for access, configuration, and API behavior.

Does the API write changes to our catalog?

Catalog editing happens in the Remapdb app. REST API v2 reads the account catalog. Customizations and API access together are included on Max.

Can we start with the widget instead?

Yes, when your application can embed it and the website is allowed by your plan. Use the API when you need your own interface and application logic.

Can AI assistants query the same data?

API and Max include MCP access for supported AI clients. These tools retrieve vehicle information; they do not perform autonomous tuning or create ECU files.

Explore the features

Explore the relevant product details

See how each feature works, what it includes, and which plan gives you access.

API capabilities and examples

Review the vehicle tuning data API, returned fields, credentials, and documented integration examples.

Explore API

MCP vehicle-data tools

Connect a supported AI client to retrieve vehicle records using the access included on API and Max.

Explore AI integrations

Customized catalog on Max

Understand how account-specific edits and visibility settings relate to the records API v2 returns.

Explore customizations

Your next step

Define the vehicle data your product needs

Start with the documented records and usage limits, then plan the interface and business workflow your developers will build.

Explore the APIDiscuss your setup

REST API and MCP access require API or Max. The Free widget plan does not include developer API access.