Developer documentation

Find your starting point.

Integrate the UDS Evidence API or connect an AI assistant to local WinOLS map-definition and Ghidra firmware-analysis tools.

Tuning catalogueOpenAPI 3.1

Tuning Files API

Explore software releases, immutable file versions and verified associations. Staff publish reviewed files with explicit download policies.

Read the tuning overview

OpenAPI contract

Accounts, catalogue, staff workflows and raw downloads.

JSON

Integration guide

Cookies, CSRF, immutable provenance and safe retries.

MD

01 / HTTP APIOpenAPI 3.1.2

UDS Evidence API

Ingest diagnostic observations with original bytes, source provenance, and explicit handling of unknown context.

Read the UDS overview

Create your first source, session, and observation.

OpenAPI contract

Operations, request bodies, and responses.

JSON Schemas

Resource and request validation contracts.

Runnable examples

curl, Node.js, and synthetic fixtures.

AI client guide

Evidence rules, permissions, and retry behavior.

02 / LOCAL MCPFree · MIT

WinOLS MCP

Inspect, validate, and create map definitions through a Rust MCP server and a Lua bridge for WinOLS.

Read the WinOLS MCP overview

Build & try it

Start with the included mock backend.

Tool reference

Seven tools for byte inspection and map definitions.

Connect WinOLS

Requirements, Lua bridge, and local setup.

Machine-readable guide

Setup and capabilities in plain Markdown.

Source & contributions

Code, examples, and the MIT license on GitHub.

03 / LOCAL MCP Free · MIT

Ghidra MCP

Trace graphs and SSA data flow, define native types, compare functions, and test explicit inputs in isolated emulation through local Ghidra.

Read the Ghidra MCP overview

Build & connect

Set up Ghidra, Java, and the local bridge.

Tool reference

85 tools; 84 supported headlessly, with bounded native contracts.

Connect CodeBrowser

Install the GUI extension and start its bridge.

Machine-readable guide

Setup, capabilities, and limits in Markdown.

Source & contributions

Rust server, Java adapter, and MIT license.

Choose your workflow

A tool for each part of the work.

Product	Use it for	Connection
UDS Evidence API	Store diagnostic observations with bytes, provenance, and review context.	Hosted HTTP API; dataset operations require a scoped credential.
WinOLS MCP	Read Original/current bytes and validate or create map definitions.	Local stdio server and Lua bridge; licensed WinOLS and OLS530, or a mock backend.
Ghidra MCP	Inspect graphs and data flow, refine types, compare candidates, and save evidence.	Local stdio server and Java adapter; background Ghidra or its GUI extension.

Moving findings from Ghidra into WinOLS requires checking source identity, file offsets, live bytes, and map semantics. Follow the WinOLS handoff guide.

For developers & AI clients

Start with the source of truth.

These documents are public and readable without a login. API data access uses scoped credentials; both MCP servers run locally.

UDS evidence semantics

Payloads, timestamps, provenance, and uncertainty.

Errors & retries

Respond to validation errors and interrupted requests.

UDS contract changelog

Version history and compatibility notes.

A readable entry point

Give your assistant the docs.

Our plain-text resource index points to all three products and their authoritative setup guides.

Read https://api.redlineautohaus.com/llms.txt.
Choose the guide for my task, inspect the
contract, and explain the required setup.

Open llms.txt

UDS stores evidence. WinOLS MCP creates map metadata. Ghidra MCP supports firmware analysis. See each guide for operations and requirements.