stocks.team

Issuer-specific SEC data availability

Native MCP & REST for AI Agents

Beta Plans from $9.99/mo billed annually

Point-in-Time 10-K & 10-Q Provenance

A financial answer you can check.

Start with a question. Keep the value, reporting period and original evidence together.

Historic source example · Apple FY2024

What was Apple's revenue in fiscal 2024?

$391.035 billion

Reported as 391,035 USD millions in total net sales.

This historic example demonstrates how to check a source. Live availability and the evidence fields returned by the API vary by issuer, filing, and metric.

Period

Fiscal year ended September 28, 2024

Source

Apple 2024 Form 10-K

Find the number

Consolidated Statements of Operations, page 29, total net sales

Read the original SEC filing (new tab) Filing identifiers and source check

CIK: 0000320193
Accession: 0000320193-24-000123

Source checked September 5, 2026.

Apple's accompanying financial statements (PDF, new tab)

For your research

Check the period and unit before comparing companies. Follow the filing link to review the number in context.

Explore Apple's data availability

For your agent

Use structured evidence in your workflow. Have the agent retain source references and inspect availability before drawing a conclusion.

Show the latest reported revenue for AAPL and the filing that supports it.

Illustrative agent previewEvidence linkedIllustrative preview

Illustrative preview: an authenticated response returns the exact value, reporting period, acceptance timestamp, accession number, and SEC source locator. The agent should verify those fields before presenting the result.

Illustrative UI only · live values require an authenticated request

Stop burning tokens on raw SEC filings. Give your AI agents structured financial evidence.

Instead of asking an agent to parse an entire filing, stocks.team exposes structured SEC facts through MCP and REST. The response keeps periods, provenance, quality states, and missing evidence visible so a downstream model can show its work.

• ✕ Unbounded filing context Sending an entire 10-K or 10-Q to a model increases context size and makes period selection harder to audit.

• ✕ Slow, variable retrieval Document retrieval, OCR, and multi-pass reading add work before an agent can answer a narrow financial question.

• ✕ Hard-to-audit answers Dense tables can hide fiscal-year, amendment, unit, and GAAP versus non-GAAP mistakes.

• ✕ Fragile custom scrapers Every team must separately maintain SEC pacing, retries, parsing, and provenance handling.

• ✓ Structured tool payloads Focused JSON gives an agent the requested facts and the metadata needed to verify them.

• ✓ Measured edge delivery Responses are served through the deployed edge path. Latency varies by route, cache state, region, and database work.

• ✓ Deterministic calculations with evidence Returned calculations expose their inputs, periods, quality state, and SEC source coordinates. Unmaterialized metrics fail closed.

• ✓ MCP adapter and point-in-time guardrails Use the documented contract from Claude, Cursor, or a custom agent while preserving publication timestamp fences.

Structured Tool-ready responses

Measured Per-route performance

Explicit Point-in-time fences

Linked SEC source coordinates

Built from the ground up for agentic workflows.

stocks.team replaces slow scraping and ambiguous third-party summaries with a deterministic, point-in-time financial layer engineered specifically for LLMs and quants.

01 Agent Native

Native MCP Server & REST API for AI Agents

Connect Claude, Cursor, and autonomous AI agents in seconds using our official Model Context Protocol (MCP) server or REST API. Query published SEC facts with explicit periods and source references.

02 Temporal Boundaries

Point-in-Time Financial Statements & Backtesting

Point-in-time queries respect publication and observation boundaries. Inspect each response’s availability and source evidence before using it in a backtest.

03 Proprietary Metrics

Financial Reality & GAAP Normalization

Normalized financial facts and documented Financial Reality formulas. Coverage varies by issuer, filing, metric, and the available source evidence.

04 SEC Provenance

Cryptographic SEC EDGAR Source Citations

Inspect filing identifiers, periods, taxonomy concepts, source URLs, and quality status where available. Derived metrics expose their supporting components.

Built for speed, accuracy, and developer value.

12 guided examples cover discovery, facts, statements, core metrics, Financial Reality diagnostics, filings, strict trailing-twelve-months values, and current curated changes.

Starts with the stable API identity, SEC-only scope, and machine-readable contract link.

GET /api

$ curl "https://stocks.team/api"

Read the OpenAPI contract

Official beta execution API key required

Authenticated REST and MCP data requests are open for beta accounts. Create an API key in the dashboard, keep it server-side, and use the documented quota and provenance fields on every request.

Issuers mapped to SEC filings.

The company universe is configured at runtime and grows with customer demand. Every issuer still passes the same SEC identity, ingestion, quality, and quota gates before it becomes available. The tickers below are regression examples, not a product limit.

AAPL MSFT NVDA AMZN GOOGL META TSLA AVGO AMD ORCL BRK-B JPM BAC GS V MA WMT COST KO PG

Audit Standard

Institutional Data Integrity

Guaranteed

Point-in-time queries Inspect filing acceptance and source observation boundaries

Explicit fences

SEC EDGAR evidence Source references and quality status accompany supported results

Source-linked

Financial Reality availability A documented formula does not guarantee indexed evidence for every issuer

Issuer-specific

API delivery Response time depends on the endpoint, query, and cache state

Cloudflare Workers

Make SEC evidence usable. Built natively for AI agents.

Legacy data products vary widely in price, licensing, and source transparency. stocks.team focuses on a documented SEC evidence contract for Claude, Cursor, Grok, and custom agents, with beta plans from $9.99 per month when billed annually.

Capability	stocks.team	Legacy Financial APIs	Terminal Feeds
Starting Price	$9.99 / mo billed annually; $11.99 billed monthly	$50 – $300 / mo	$2,000+ / mo
AI agent / MCP integration	Native MCP (Cursor, Claude, Cline) & OpenAPI	Complex REST only; manual wrappers required	Proprietary desktop software only
Financial Reality	Documented formulas; issuer-specific evidence coverage	Opaque calculations; inconsistent formulas	Proprietary vendor adjustments
Direct SEC Audit Trail	Supported facts retain accession & EDGAR source references	Black-box third-party aggregations	Closed vendor proprietary calculations
Point-in-Time Honest Backtesting	Publication and observation fences with explicit availability	Vulnerable to survivorship & restatement leaks	High-cost specialized historical add-ons
Edge Latency	Cloudflare Workers; latency varies by request	Variable centralized server latency	Heavy client-side application overhead
US Stock Coverage	Check each issuer’s published data and collection status	Tiered plan gates based on universe size	Broad coverage locked behind enterprise contracts

Lock your rate before the public price rises.

These are launch-window beta prices, shown as a monthly equivalent for annual prepayment. Join now and your rate stays fixed while the subscription remains active, even after public pricing changes.

Plus

$9.99 /mo, billed yearly

$119.88 billed yearly

A focused starting point for developers and AI agent builders.

100,000 requests / month 3,500 requests / day

• Runtime SEC issuer coverage
• MCP and OpenAPI access
• Point-in-time facts & metrics
• CSV data export
• Standard email support Join with Plus

Ultra

$49.99 /mo, billed yearly

$599.88 billed yearly

Maximum beta capacity for demanding applications and teams.

10,000,000 requests / month 350,000 requests / day

• Everything in Pro
• 10x higher request quota
• Priority ingestion and support
• Built for multi-agent workloads Join with Ultra

Daily caps reset at midnight UTC. Monthly allowances reset on the first day of each UTC calendar month. Instant API key activation · Cancel anytime · Early beta rates locked for life.

What this product is, and is not.

01Why is stocks.team built specifically for AI models and agents?

LLMs can produce unsupported numbers when reading unstructured PDFs or third-party summaries. stocks.team provides structured, point-in-time SEC facts with evidence fields and EDGAR URLs, plus documented Model Context Protocol (MCP) integration.

02How should I compare beta pricing with other financial data providers?

Compare the data you need, commercial-use terms, request allowances, and daily caps. stocks.team is a focused SEC evidence product, not a market-price feed or a replacement for every financial dataset. Annual-equivalent and monthly-billed prices are shown separately below.

03What does point-in-time mean for AI and backtesting?

An as-of query filters by the filing acceptance timestamp, not only the period the number describes. An amendment filed in June is not selected for a query about what was public in March, subject to the coverage and quality state returned with the response.

04How fast can I connect stocks.team to my AI tools?

Follow the MCP installation guide to download the local adapter, or integrate directly via REST and OpenAPI. Setup requires an active API key. Hosted remote MCP and npm registry installation are not currently available.

05Where does the financial data come from?

Directly from SEC EDGAR filings (10-K, 10-Q, 8-K, and amendments). Original filing documents are retained with immutable hashes, while normalized facts preserve their accession number, taxonomy concept, unit, and period.

06Does AI normalize the financial statements?

Extraction, XBRL mapping, and Financial Reality formulas use deterministic rules. Inspect quality status, missing evidence, periods, and source references; deterministic processing does not remove the need to validate a result.

Trace the fact. Then build.

Create a beta account, activate a plan, and generate a server-side API key for REST or MCP access. Every data request remains authenticated, quota-controlled, and tied to the published evidence contract.