WEB DATA & EXTRACTION · FOR AI AGENTS
Financial Datasets
Retrieve market prices, filings and structured company financial data through API or MCP.
Use Financial Datasets for maintained financial evidence, with account-based access and a separate x402 payment route for selected endpoints.
Your integration checklist
- Capabilities
- What you need from your owner
- Create and fund an account for API access, or authorize a funded USDC wallet on Base for supported x402 requests. Check the intended use against the data licence before selecting a route.
- Authentication
- REST requests use X-API-KEY. Interactive MCP at https://mcp.financialdatasets.ai/ uses sign-in; programmatic MCP at https://mcp.financialdatasets.ai/api accepts X-API-KEY. Supported keyless REST calls can use x402.
- Your first task
- Retrieve one company’s recent statement for a specified period and retain currency, units, period and the supporting filing alongside each extracted value.
- Billing & payment
- Account plans include request allowances; premium endpoints consume multiples and eligible subscriptions permit billed overages. x402 charges per successful request, with each pagination page paid separately; read current terms before signing.
- Agent payment support
- Selected REST endpoints document keyless x402 payments with USDC on Base. Inspect PAYMENT-REQUIRED terms and retain PAYMENT-RESPONSE receipts. Endpoint, 365-day history and Non-Professional licence restrictions apply. Approved wallet funds are required; payment execution was not tested.
- Operational limits
- Coverage and history vary by endpoint and plan. The x402 route supports only selected endpoints, limits history to 365 days and is licensed for Non-Professional use. Professional use and broader history require an appropriate account plan.
ORIGINAL AI AGENT STORE INTEGRATION PLAYBOOK
Keep each financial value attached to its period and source
Editorial recommendation · Reviewed 2026-10-28
When to choose this service
Choose Financial Datasets when a research agent needs maintained financial records rather than recalled or inferred figures.
Continuously collecting and normalizing filings and licensing price feeds requires external data operations. An agent can calculate ratios, but cannot recreate missing current observations through reasoning.
Suggested workflow
- Resolve the company and reporting period before retrieval. Choose standardized or as-reported figures deliberately and preserve that choice.
- Keep currency, units, period and publication context with the data. Reconcile a material value against its source before using it in a conclusion.
- Choose account billing or a supported x402 call explicitly. Apply an approved per-request budget, including pagination, and retain payment receipts when used.
Acceptance checks before real work
- Treat an absent value as unknown rather than zero.
- Separate fiscal-period results from the date a filing became available.
- Confirm reuse rights before serving provider data to other users.
If the workflow fails
Inspect entitlement, date-window and rate-limit errors before retrying. After an uncertain paid response, reconcile the receipt and request outcome before authorizing another payment.