Stock Quotes APIs vs CVM Regulatory Filings API

Two layers of "financial data"

A quote tells you what the market paid yesterday. A DFP tells you what the company reported about assets, liabilities, and accounting policies. Both matter — neither replaces the other.

What quotes APIs provide

Typical capabilities (varies by vendor):

• Current and historical stock prices
• OHLCV candles for charting and backtests
• Dividends and corporate actions (vendor-dependent)
• Aggregated fundamentals derived from filings or third parties

Access pattern example (Brapi-style, external):

# Illustrative — quotes API, not apicvm
curl "https://brapi.dev/api/quote/PETR4?range=1mo&interval=1d"

Good for trading dashboards, price alerts, volatility models, and mark-to-market.

What apicvm provides

apicvm is a CVM regulatory filings API — not a quotes feed:

export APICVM_KEY='apicvm_...'
export APICVM_URL='https://apicvm.dev'

# List filings — not prices
curl -H "Authorization: Bearer $APICVM_KEY" \
  "$APICVM_URL/v1/documents?ticker=PETR4&type=DFP&year=2024&perPage=10"

Workflow:

resolve company → list documents → download PDF → optional async markdown extraction

apicvm does not provide quotes, price history, indices, or futures data.

When you need quotes

Choose a quotes or market data provider when you need:

• Live or historical stock prices for PETR4, VALE3, etc.
• Volume, bid/ask, or intraday bars for execution research
• Portfolio mark-to-market with daily closes
• Price-based signals (momentum, mean reversion, volatility)

For B3-specific licensing and exchange data nuances, see B3 market data vs CVM filings.

When you need regulatory filings

Choose apicvm (or equivalent CVM infrastructure) when you need:

• Audited financial statements from DFP/ITR PDFs
• Risk factor narrative from FRE documents
• Governance and related-party disclosures in regulatory text
• LLM/RAG over primary filing content with page citations
• Due diligence workflows tied to official CVM documents

Quotes APIs may expose simplified fundamentals; they do not replace full regulatory PDFs, footnotes, or FRE sections.

Combined workflows

Research stacks often join both layers:

Quotes API  →  prices, returns, market cap
apicvm      →  DFP/ITR/FRE text → fundamentals, NLP features

Example: compute P/E using market cap from a quotes API and net income from DFP text extraction via apicvm. Each API supplies a different input — you merge in your pipeline.

Quant teams building fundamental factors over Brazil often follow this pattern — see Brazil filings quant research pipelines.

# Conceptual — two APIs, one research job
price = quotes_client.get_close("PETR4", "2024-12-31")  # external quotes API
docs = apicvm_client.list_documents(ticker="PETR4", type="DFP", year=2024)
# download PDF → extract → parse net income from filing text

Analogy for US developers

If you already separate "price vendor" from "filings vendor" in US stacks, apply the same split in Brazil.

What apicvm explicitly does not provide

• Stock quotes, OHLCV, or index levels
• Real-time trading or market depth data
• Dividend calendars (unless you extract them from filing text)
• Analyst estimates or consensus forecasts
• Replacement for Bloomberg/Economatica-style market terminals

Stay precise in product copy and agent tool descriptions — do not ask apicvm for GET /quote/PETR4.

Current limitations (apicvm)

• Filings availability follows the ingestion pipeline — not tick-by-tick market sync.
• IPE (material facts) and some document categories are outside MVP scope.
• Extraction is async via callback; Pro plan required for markdown jobs.
• You need a separate provider for all market data — apicvm is filings-only.

Next steps

• Read the API docs
• Get an API key
• Download DFP and ITR filings in Brazil
• Brazil filings quant research pipelines

Related pages

• B3 market data vs CVM regulatory filings
• CVM open data vs apicvm API
• Getting started with the CVM filings API