/v1. The OpenAPI spec also has
info.version, which goes up whenever the contract changes.
What can change inside /v1
These changes ship in /v1 without notice. Build your agent so they don’t break it:
- New routes, new MCP tools, and new optional request fields.
- New fields in responses. Ignore fields you don’t know.
- New error
codevalues. Treat an unknown code by its HTTP status (see Errors). - New values in status fields (
status, offerstatus). Show values you don’t know; don’t fail on them. - Wording of
error,messageandnext_steptext. Branch oncode, never on text. - Limits (see Rate limits). Always honor
Retry-After.
Breaking changes
Removing or renaming a route, a field or an error code, making an optional field required, or changing what a field means is a breaking change. Lanesurf avoids those in/v1. If one is ever needed, it ships as a new
version (/v2) next to /v1, and the changelog says so first.
Where changes are announced
- The changelog, newest first (also as an RSS feed).
info.versionin/openapi.yaml.