Polygon.io vs Brazil CVM Filings API
Polygon vs CVM filings API compares different products. Polygon.io focuses on market data APIs (aggregates, trades, and related datasets). apicvm focuses on CVM regulatory filings over HTTP. Complementary — never "replace Polygon.io".
Side-by-side
| Capability | Polygon.io | apicvm |
|---|---|---|
| Quotes / market data | Core product focus | No |
| CVM DFP/ITR/FRE PDF by document ID | Not the product shape | Yes |
| Resolve by Brazilian ticker / CNPJ for filings | Not a filings API | Yes |
| Async page markdown extraction | No | Yes (Pro) |
Developer shape
import os, requests
BASE = os.environ["APICVM_URL"]
H = {"Authorization": f"Bearer {os.environ['APICVM_KEY']}"}
company = requests.get(
f"{BASE}/v1/companies/resolve",
headers=H,
params={"query": "PETR4", "by": "ticker"},
).json()Pair Polygon.io (or any quotes API) with apicvm when models need the filing PDF. See Quotes APIs vs filings.
When apicvm is the better fit
- Regulatory document archives for Brazil
- Agent tools that must cite CVM document UUIDs
- FRE section retrieval
When Polygon.io is the better fit
- US-centric or multi-venue market-data pipelines
- Tick/aggregate workloads without a filings archive need
- Teams already licensed for Polygon market data
Current limitations
- apicvm does not ship OHLCV endpoints
- We do not document Polygon.io's entitlements or symbol coverage
- Filings availability follows ingestion, not tick prints
Next steps
Ready to integrate?
Get an API key and start querying Brazilian CVM filings programmatically.