Changelog

Vehicles as AutoUncle Vehicle Schema documents

Every result that describes a vehicle now returns it as an AutoUncle Vehicle Schema (AVS) 0.3 document, with its catalogue identification, candidates and per-value provenance beside it in identification. A returned vehicle can be posted back unchanged, and the attributes you send today still work. This is a breaking change for anyone reading vehicle fields.

Response schemas, a valuation ID header and clearer warnings

Catalogue and account responses now have complete schemas in the OpenAPI contract. Valuation results carry their ID in an X-Valuation-Id header, the countries list marks each market's availability, a missing country returns country_required, unsupported vehicle flags produce a warning, and the MCP account and read-back tools share the REST rate limit.

Concurrency limits and retry delays

Valuations now run with limited concurrency per workspace, per market and across the platform. A request that cannot get a slot is rejected before anything is reserved or charged, with concurrency_limited or engine_busy and a retry_after delay, and can be retried with the same idempotency key.

Notes, data-source attributions and provenance basis

Every valuation, catalogue and account result now carries notes and attributions. Attributions list only the data sources that contributed, with licence references and any required attribution text. Field provenance gains a basis, and AI-interpreted values are no longer labelled as imputed assumptions.

Valuations, catalogue and a workspace for your team

The first platform preview brings together API keys, credit controls, a valuation playground, request logs, documentation and agent integration tools.

The OpenAPI contract is the current reference for supported request fields and responses.