generated: '2026-08-13'
method: searched
source: >
  https://newsapi.ai/plans (server-prerendered, read 2026-08-13),
  https://github.com/EventRegistry/event-registry-api (the provider's API changelog),
  https://github.com/EventRegistry/newsapi-mcp/blob/main/CHANGELOG.md, plus DNS/HTTP probes
  for a status page, and the OpenAPI definitions under openapi/.
name: Event Registry API Lifecycle
description: >
  Versioning, deprecation, support and availability posture for the Event Registry
  (NewsAPI.ai) API. Event Registry publishes support tiers and a plan-level uptime
  commitment, but no versioning policy, no deprecation policy, and no status page.
versioning:
  scheme: url-path
  current: v1
  base_url: https://eventregistry.org/api/v1
  version_header: null
  date_pinning: false
  policy_published: false
  policy_note: >
    The `v1` segment has been in place since at least 2017 and has never been incremented.
    There is no published statement of what constitutes a breaking change, how a v2 would be
    announced, or how long v1 would be supported alongside it. Breaking changes have instead
    been shipped in place — the 2017-06-14 changelog entry renamed three query flags and
    altered two returned data models under the same v1 path.
deprecation:
  policy_published: false
  sunset_header: false
  deprecation_header: false
  rfc8594: false
  deprecated_operations: []
  deprecated_operations_note: >
    No operation in any of the five OpenAPI definitions carries `deprecated: true`.
  historical_notices:
    - date: '2017-06-14'
      subject: articlesSortBy value `sourceImportance`
      replacement: sourceImportanceRank
      migration_note: >
        The replacement is the reverse of the deprecated value, so callers must also negate
        their existing sortByAsc value.
      source: https://github.com/EventRegistry/event-registry-api
      note: >
        The only deprecation notice Event Registry has ever published. Nine years old, in an
        abandoned repository. The deprecated value is still listed as accepted in the
        provider's own current MCP error handler, so it appears never to have been removed.
  finding: >
    No RFC 8594 Sunset or Deprecation response headers, no deprecation window, no published
    policy. An agent calling this API has no runtime signal that an operation or parameter is
    going away.
availability:
  sla_published: true
  sla: 99.99% uptime
  sla_scope: Paid plans (recorded from the plans page; see plans/event-registry-plans-pricing.yml).
  status_page: null
  status_page_probes:
    - url: https://status.newsapi.ai
      status: 000
      result: miss
      note: No DNS resolution.
    - url: https://status.eventregistry.org
      status: 000
      result: miss
      note: No DNS resolution.
    - url: https://eventregistry.statuspage.io
      status: 200
      result: miss
      note: >
        Redirects to https://www.atlassian.com/software/statuspage — the Statuspage marketing
        site, not a tenant page. Event Registry has no Statuspage tenant.
    - url: https://newsapi.ai/status
      status: 200
      result: miss
      note: >
        Byte-identical to the SPA shell served for a known-nonexistent path
        (/definitely-not-a-real-page-xyz123), so this is a soft 200, not a status page.
  incident_history: not published
  finding: >
    A 99.99% uptime commitment is sold on the pricing page but there is no status page, no
    incident history and no uptime reporting against which a customer could verify it.
support:
  tiers:
    - name: Limited Support
      plans: [Free / lowest tier]
      description: No direct support. Documentation and the sandbox environment only.
    - name: Basic Support
      description: Basic tech support via email or chat, plus documentation and sandbox.
    - name: Enhanced Support
      description: Email support with the option for Zoom calls on technical issues.
    - name: Advanced Support
      description: Access to a dedicated technical team.
    - name: Premium Support
      description: Personal account manager and connection to all company resources.
  source: https://newsapi.ai/plans
  contact_email: info@eventregistry.org
  contact_source: openapi/_original/openapi.yml info.contact
  demo: Book a demo (linked from the plans page navigation).
data_lifecycle:
  archive_start: '2014'
  free_tier_window: last 30 days only
  paid_window: current data plus historical data from 2014
  note: >
    Data retention is a plan entitlement, not a lifecycle policy — historical depth is what
    the pricing tiers are actually selling.
change_communication:
  changelog: changelog/event-registry-changelog.yml
  api_changelog_status: abandoned since 2017-06-14
  mcp_changelog_status: current through 2026-03-18
  mailing_list: not published
  breaking_change_notice_period: not published
sdk_lifecycle:
  note: >
    The two general-purpose SDKs have not been republished in years (Python 9.1 on
    2023-06-23, Node 9.1.1 on 2024-11-14) while the API gained parameters through 2026. The
    MCP server, released 2026-03-18, is the only first-party client tracking the current
    surface. See packages/event-registry-packages.yml.