# Bitvore

> Bitvore Corp. runs Cellenus, an AI/NLP platform that reads unstructured public text — global news,
> press releases, SEC filings, earnings-call transcripts — and turns it into structured material business
> events, signals, sentiment, growth and risk scores for corporate entities and municipal bond issuers.
> The platform surveils 500,000+ companies across 60,000+ sources and is sold as two separately licensed
> datasets: Cellenus Corporate Intelligence and Cellenus Municipal (Muni News), with an ESG signal layer.
> Bitvore's fixed-income data-analytics unit was acquired by BondWave in November 2024; bitvore.com now
> redirects to bondwave.com/muni-news/, while developer.bitvore.com and api.bitvore.com remain live.

Generated by API Evangelist. This file is an independent third-party summary, not published by Bitvore.
generated: 2026-08-07
method: generated
source: apis.yml + repo artifacts (no /llms.txt is served on any bitvore.com host — 404)

## APIs

- [Cellenus Corporate API](https://developer.bitvore.com/v2/docs/overview/corp): Corporate news, economic
  news, organizations, financial filings, sentiment scores, portfolios and dataset/changeset exports.
  Base URL https://api.bitvore.com/v2/corp/. 28 paths / 37 operations.
- [Cellenus Municipal API](https://developer.bitvore.com/v2/docs/overview/muni): Municipal bond news by
  CUSIP, location, FIPS, sector and portfolio, plus CUSIP portfolio management.
  Base URL https://api.bitvore.com/v2/muni/. 12 paths / 21 operations.
- [Bitvore OAuth 2.0 Token API](https://developer.bitvore.com/v2/docs/security): Exchanges a registered
  client id + API key for a client-credentials bearer token. POST https://api.bitvore.com/oauth/accesstoken.
- [Bitvore Legacy (v1) API](https://developer.bitvore.com/v1/docs/overview): The pre-2021 unprefixed
  surface — /corpnews, /muninews, /econnews, /entityapi, /idapi, /financialfiling, /portfolioapi,
  /sentimentscores. Still served. 22 paths / 33 operations.

## Specs

Bitvore publishes Swagger 2.0 (springfox), enumerated at https://api.bitvore.com/swagger-resources.
No OpenAPI 3.x document is published.

- https://api.bitvore.com/v2/api-docs?group=v2-Corp
- https://api.bitvore.com/v2/api-docs?group=v2-Muni
- https://api.bitvore.com/v2/api-docs?group=Security
- https://api.bitvore.com/v2/api-docs?group=Legacy
- https://api.bitvore.com/v2/api-docs?group=z-Custom%20API%20I.T. (marked "Deprecated 2019")
- https://api.bitvore.com/v2/api-docs?group=z-Custom%20API%20L. (marked "Deprecated 2019")

## Docs

- [Developer portal](https://developer.bitvore.com/)
- [Getting started](https://developer.bitvore.com/v2/getting-started)
- [API reference](https://developer.bitvore.com/v2/docs/api-reference)
- [Security / authentication](https://developer.bitvore.com/v2/docs/security)
- [Signal glossary](https://developer.bitvore.com/v2/docs/api-reference/signals)
- [Release notes and v1 to v2 upgrade guide](https://developer.bitvore.com/v2/release)
- [Sample portfolios](https://developer.bitvore.com/v2/docs/api-reference/portfolios)
- [Dataset exports](https://developer.bitvore.com/v1/docs/dataset-exports)
- [Request access](https://developer.bitvore.com/get-access)

## Authentication

Three accepted forms, all keyed on a licensed API key:

1. Query parameter `key=<apikey>` — GET requests and dataset exports only.
2. HTTP header `X-BV-APIKEY: <apikey>` — GET and POST; REQUIRED for POST.
3. OAuth 2.0 bearer token (RFC 6750) — `POST /oauth/accesstoken` with
   `grant_type=client_credentials&client_id=<username>&client_secret=<apikey>`.
   No refresh token is issued; request a new token on expiry.

The API key carries product scope: Corporate and Municipal are separately licensed and issue separate keys.
Keys are not self-serve — a trial key comes from products@bitvore.com, a licensed key from sales@bitvore.com.

## Conventions

- Every response is wrapped: `{ success, response, returned, total }` on success,
  `{ success: false, reason, reasonSupport, response }` on failure.
- Pagination is page-number: `pageNo` + `pageSize`, with `returned` and `total` in the envelope.
- Date ranges use required `startDate`/`endDate` ISO 8601 values plus optional `dateType` and `tz`.
- Multi-value parameters are plural (`bvIds`, `signals`) as of v2.
- Primary identifier is `bvId`; CUSIP, ISIN, SEDOL and FIGI are licensed alternates.
- No idempotency key, no request-id header, no published rate limit, no RFC 9457 problem details.

## What Bitvore does not publish

Recorded so an agent does not go looking: no /llms.txt, no /.well-known/ documents on any host,
no A2A agent card, no MCP server, no client SDKs on npm/PyPI/RubyGems, no public GitHub repos,
no status page, no public Postman collection, no security.txt, no trust center, and no rate-limit
documentation. The release-notes page has not been updated since 2023-09-01.

## API Evangelist artifacts

- openapi/ — the six harvested Swagger 2.0 documents (verbatim in openapi/_original/)
- authentication/bitvore-authentication.yml
- scopes/bitvore-scopes.yml
- conventions/bitvore-conventions.yml
- errors/bitvore-problem-types.yml
- lifecycle/bitvore-lifecycle.yml
- changelog/bitvore-changelog.yml
- conformance/bitvore-conformance.yml
- data-model/bitvore-data-model.yml
- security/bitvore-domain-security.yml
- well-known/bitvore-well-known.yml
- mcp/bitvore-mcp.yml (candidate tool surface derived from real operationIds — not served by Bitvore)
- skills/ — packaged Agent Skills grounded in real operationIds