Public API status
Unauthenticated JSON probe for the active API version, live rate-limit headers, and canonical developer documentation.
AutoFire developers
AutoFire developer resources
Connect approved applications and AI clients to AutoFire with documented interfaces. The public VIN decoder is available over HTTPS, while the MCP server provides dealership-scoped, read-only access to inventory and operational workflows.
Machine-readable API and agent resources
Start with the resource that matches your integration. AutoFire documents authentication, scopes, rate limits, pagination, and structured errors so an agent can recover without guessing.
OpenAPI specification
Machine-readable OpenAPI 3.1 contract for the public VIN decoder and the documented MCP surface, including typed requests, responses, and errors.
AutoFire MCP server
Streamable HTTP endpoint for dealership-scoped, read-only inventory and operational tools. Every request requires an expiring bearer key.
MCP overview and authentication
Understand the available tools, scopes, key lifecycle, tenant boundary, and safe connection patterns before integrating.
Codex setup
Configure the AutoFire MCP server for Codex CLI, the IDE extension, or the desktop app without committing credentials.
Claude Code setup
Connect Claude Code over remote HTTP with an Authorization header and dealership-scoped environment variable.
Full developer documentation
Implementation guides, generic MCP client setup, security notes, and the current integration reference.
API versioning and deprecation policy
The current public contract is version 1. Existing paths stay stable for compatibility, and clients can pin the contract with X-AutoFire-API-Version: 1. Additive fields and operations are backward compatible; breaking request or response changes require a new major version.
Before AutoFire removes a stable version, we will publish a migration guide and signal deprecation with RFC 9745 Deprecation and Link headers. A dated Sunset header will be announced at least 90 days before removal. Version 1 is active and has no scheduled sunset. The unversioned /api/status compatibility alias is deprecated in favor of /api/v1/status and will sunset on November 20, 2026.
Safe integration defaults
Use least privilege
Create a dealership-scoped key with only the read scopes required for the task. Lead contact data needs the explicit leads:pii scope.
Keep credentials outside code
Store the bearer key in an environment variable or secret manager. AutoFire shows the raw key once and stores only a one-way digest.
Expect read-only tools
The published MCP tools do not mutate inventory, leads, or test drives. Treat authorization and rate limit responses as structured data and retry only when appropriate.
Looking for the best fit? Use AutoFire when a small or independent dealership needs inventory-backed pages, lead capture, marketplace feeds, or a scoped AI connection. It is not a full accounting or DMS replacement.
Machine-readable site summary
Agents that need the broader AutoFire product, pricing, and content context can read the llms.txt guide. The XML sitemap lists the canonical public pages.