generated: '2026-08-13'
method: searched
source:
- https://docs.revenuebase.ai/llms.txt
- https://docs.revenuebase.ai/api-reference/v2/overview
- https://docs.revenuebase.ai/docs/release-notes
- https://status.revenuebase.ai/
versioning:
  style: uri-path
  current: v2
  detail: API version is carried in the URL path (/v2/...). v2 is the current API.
deprecation:
  policy_documented: true
  detail: >-
    API v1 is deprecated and sunsets July 7, 2026. RevenueBase instructs clients
    and AI assistants to never recommend or use v1 endpoints. v2 is the supported
    replacement.
  deprecated_versions:
  - version: v1
    status: deprecated
    sunset: '2026-07-07'
status_page:
  url: https://status.revenuebase.ai/
  reachable: true
  rechecked: '2026-08-13'
  http_status: 200
release_notes:
  url: https://docs.revenuebase.ai/docs/release-notes
  cadence: monthly
  scope: >-
    Data releases (dataset scale, de-duplication, fill-rate and quality statistics),
    not API surface changes. Structured in changelog/revenuebase-changelog.yml.
  latest: August 2026
new_surfaces:
- name: contact-refresh
  status: live-undocumented
  detail: >-
    POST /v2/contact/refresh/email is live on api.revenuebase.ai (401 problem+json
    without a key) and its OpenAPI is published through the docs host, but it has no
    API-reference page and the pricing page still lists "Reconnect to find contacts
    who changed companies" as coming soon. Spec info.version is "dev".
  spec: openapi/_original/revenuebase-contact-refresh-openapi.json
data_freshness:
  detail: >-
    Not an API deprecation signal, but a documented data lifecycle: profiles are
    re-verified every 90 days and emails every 60 days; 1B+ verification signals
    processed monthly.
  source: https://docs.revenuebase.ai/docs/data-features/data-freshness/data-freshness
sla: null