Using Pinswap with AI

Pinswap is built to be read by machines: a public read API, an OpenAPI spec, an MCP endpoint, and an llms.txt file.

1 · llms.txt

Crawlers and agents can start at https://pinswap.app/llms.txt for a concise index, or https://pinswap.app/llms-full.txt for the full guide (data model, source policy, API, file formats).

2 · Public read API

Everything the public site can read is available as unauthenticated JSON. List endpoints for vehicles, engines, ECUs, the vehicle×ECU fit table, harnesses, parts and sources; per-harness endpoints for full state and export. The complete machine-readable description is at https://pinswap.app/api/openapi.json (OpenAPI 3.0.3).

/api/vehicles · /api/engines · /api/ecus
/api/fit · /api/car/{code}/compare · /api/harnesses · /api/parts
/api/sources — the citation behind every fact
/api/harness/{id}/state · /api/harness/{id}/export/export.json

All read endpoints are cached (~5 min) and per-IP rate limited. Writes require a session or the MCP token.

3 · MCP (tool use)

An MCP endpoint at /api/mcp exposes editing and inspection tools — list_harnesses, get_harness_state, validate, pin_map, apply_ops, undo/redo, snapshot, export, search_parts, plugin_compare. It requires a shared token and is tool-only.

4 · Honesty rule

Pinswap is a wiki run like Wikipedia: every value has a citation, and nothing is guessed. A pin number, function or part number without a source is left not found. Agents reading or contributing to Pinswap should preserve that rule — state the source alongside every fact, and prefer "not found" to a plausible guess.

Data is CC BY-SA. See Sources & citations and Terms.