Eulerpool Financial Data API vs Financial Datasets

Eulerpool Financial Data API 40

No x402, MPP or L402 (0). Plan prices and overage per 1,000 requests are public (20). 100,000 free requests a month with no card, non-commercial (20). A person registers in a browser (0). 0+20+20+0 = 40.

Financial Datasets 75

x402 on the vendor's own endpoints for every documented GET data endpoint, 36 of them, with the last 365 days only and a Non-Professional licence; full history, the market snapshot, filing items and the POST endpoints need a key (35 of 40). Plan prices and overage rates are public, and each x402 endpoint quotes its price in the 402 header, $0.02 on /earnings (20). No free tier or trial found; data calls return 402 until an account holds credits, from $20 (0). An agent can pay by x402 with no account, or open an account with POST /agent/signup and have the owner fund it (20). Total 75.

Eulerpool Financial Data API 53

An OpenAPI 3.0 document is linked at api.eulerpool.com/api/1/documentation/yaml, but that host's robots.txt disallows every path, so it was not read; partial credit for a linked contract we couldn't check (10 of 25). llms.txt, a 449-entry endpoint index and a 13,904-line llms-full.txt (10). Endpoint descriptions say what each returns, with the same marketing sentence repeated in every section and little on when not to use one (10 of 20). Parameter typing not visible in the llms files read (7 of 15). Response examples throughout; the errors page was not read (8 of 15). /api/1 paths and a dated changelog that mixes API changes with tutorial posts (8 of 15). 10+10+10+7+8+8 = 53.

Financial Datasets 80

OpenAPI 3.0.1 at financialdatasets.ai/openapi.json, 68 operations with 13 response codes and one security scheme, named the source of truth by the docs (25). llms.txt and a Markdown twin of every page (10). Every operation has a description, and the 402 terms carry a resource description that says when an agent should use the endpoint (17 of 20). 330 parameters, 36 with enums, 32 required, no free-form blobs (12 of 15). Code samples in Python, JavaScript and curl, x402 error values documented, but response examples on only six operations in the spec (11 of 15). No API version and no changelog; the news page has four dated posts in 2026 (5 of 15). Total 80.

Eulerpool Financial Data API 48

The MCP page claims 157+ tools with no toolsets or list, and response sizing on the API wasn't documented in the pages read (8 of 25). Filtering and pagination not documented in the pages read (8 of 20). Error codes not documented in the pages read (5 of 20). The data endpoints are reads (12 of 20). Official SDKs in Python, JavaScript, Node.js and Go (15). 8+8+5+12+15 = 48.

Financial Datasets 73

limit and period on the data endpoints, as_reported flags and snapshot variants, with no field selection (15 of 25). next_page_url cursors and ticker, CIK, market and date filters (18 of 20). A 402 body says what to do next, x402 errors carry named values, and the spec lists 400, 401, 403, 404, 409, 422, 429, 502 and 503 (16 of 20). Data calls are GETs, payment settles only after a successful response, and a replayed x402 signature is refused; no readOnlyHint found for the MCP tools and no idempotency key for the POST endpoints (14 of 20). Few required parameters, 28 compact MCP tools, but the only package, financial-datasets on PyPI, is at 0.1.18 from 26 May 2024 (10 of 15). Total 73.

Eulerpool Financial Data API 35

One API key per account, revocability not stated (20), less 10 because ?token= in the URL is documented as the first option (10 of 30). Read-only data (15 of 20). News, earnings-call transcripts and AI-generated SWOT text are returned with no prompt-injection guidance (5 of 15). Quota headers on each response; no usage log found (5 of 15). No security.txt check, disclosure policy, bug bounty or certification found (0 of 20). 10+15+5+5+0 = 35.

Financial Datasets 49

A plain account key in the X-API-KEY header only, revoked from the dashboard, with no scopes, rotation or expiry; the MCP server adds OAuth 2 with PKCE (plain and S256), dynamic client registration, a revocation endpoint and one scope (20 of 30). Every data endpoint is a read; the x402 route and agent signup don't change the account beyond funding it (15 of 20). Filing text, filing items and news are third-party content, with no guidance on treating them as untrusted (5 of 15). The privacy policy says requests and responses are logged for up to three years; no per-call log is shown to the key holder (5 of 15). security.txt returns 404 and no bounty, SOC 2 or ISO 27001 was found; the terms ask for prompt notice of a compromised key and a subprocessor list is published (4 of 20). Total 49.

Eulerpool Financial Data API 70

Closed service. The changelog's newest entry is dated 6 November 2026 (30), with daily entries through October, though many are tutorials rather than API changes (20). Contact by email; no public tracker or community found (5 of 15). Official SDKs in four languages, published 13 September 2026 (12 of 15). Package health not checked (3 of 10). 30+20+5+12+3 = 70.

Financial Datasets 56

UK fundamentals went live on 26 October 2026, India on 23 October, with Japan and South Korea dated for November on the coverage page (30). Dated changes in the last 90 days are x402 on 23 October, UK fundamentals on 26 October, terms and subprocessor list on 29 October, privacy policy on 20 August, with no changelog as such (12 of 20). Contact is a form and the dashboard; no support email, Discord or forum was found, and the GitHub organisation's four repositories couldn't be read because the GitHub API rate limit was reached (6 of 15). The PyPI package is 0.1.18 of 26 May 2024 by the founder, and the docs point to the OpenAPI file and the MCP server rather than an SDK (5 of 15). Package health unknown, dependencies not checked (3 of 10). Total 56.

Eulerpool Financial Data API 52

Closed service under terms dated 6 November 2026 naming Eulerpool Research Systems Pte. Ltd. of Singapore (15 of 30). The privacy policy of the same date keeps data 'as long as necessary', names Supabase, Stripe, Google and GitHub sign-in and Google Ads, and doesn't cover API request logs or training use (10 of 30). No deprecation policy or notices found (0 of 20). Some processors named; hosting location not stated (8 of 20). 15+10+0+8 = 33.

Financial Datasets 63

A closed service under terms dated 29 October 2026 that name Financial Datasets, Inc., set New York law, and state the licence per plan (15 of 30). The privacy policy of 20 August 2026 gives retention periods (accounts up to seven years after closure, API and MCP logs up to three years, backups 90 days), says inputs aren't used for training, and links a subprocessor list; no DPA text was found (24 of 30). No deprecation policy; the terms say the Services may be discontinued and material changes get reasonable notice (3 of 20). Subprocessors (AWS, Heroku, Stripe, Google sign-in, Vercel) and the United States as hosting location are disclosed (18 of 20). Total 60.