Versioning
Stable public endpoints carry a major version in their path, such as /v1, /v2, or /v3. Backward-incompatible response or behavior changes require a new major version.
Deprecation
Lex Engine targets at least 180 days of notice before removing a stable paid endpoint. Security, legal, source-access, or emergency reliability issues may require faster action; those exceptions will be published on the status page.
Compatibility
Fields may be added without a major-version change. Clients should ignore unknown fields. Existing documented fields will not silently change meaning within a stable major version.
Limits and availability
Rate limits and monthly credits depend on plan. A successful response does not imply a legal record is complete; provenance, confidence, and official-source links remain part of the data contract.
Current versions
v1: public records and operational feeds. v2: intelligence search and signals. v3: accounts, billing, watchlists, customer workspaces, and company profiles.