{ "data": { "a": { "slug": "benzinga", "name": "Benzinga", "vendor": "Benzinga", "vendorUrl": "https://www.benzinga.com", "kind": "http-api", "category": "market-data", "summary": "Benzinga is a financial news and data company whose licensed APIs serve news, earnings and ratings calendars, analyst insights, transcripts, SEC filings, fundamentals and options signals over REST, websockets and webhooks, for firms that hold a content licence.", "url": "https://www.anchorterminal.com/tools/benzinga", "markdownUrl": "https://www.anchorterminal.com/tools/benzinga.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/benzinga.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/benzinga.json", "dns": "benzinga.grade.anchorterminal.com", "repo": "https://github.com/Benzinga/benzinga-docs", "transports": [ "http" ], "remoteUrl": "https://api.benzinga.com", "packages": [ { "registry": "pypi", "name": "benzinga" } ], "auth": "api-key", "authNotes": "API token generated in the Benzinga console and sent as the `token` query parameter on every request, which the docs call Bearer authentication. No header option, scopes, rotation or expiry were found in the docs or the OpenAPI specs.", "pricing": "paid", "pricingNotes": "No prices are published. The docs say to email licensing@benzinga.com or call to get started, and the registration page is on www.benzinga.com, which answered 403 to our reader. The FAQ says each subscription carries its own rate limits and that a trial or sandbox is often available, without terms.", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, llms.txt or the 11 OpenAPI specs (checked 2026-11-03).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 34, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://docs.benzinga.com/", "llmsTxt": "https://docs.benzinga.com/llms.txt", "openapi": "https://github.com/Benzinga/benzinga-docs/tree/main/openapi", "capabilities": [ "market.news", "market.fundamentals", "market.filings", "market.prices", "data.markets", "data.company" ], "tags": [ "official", "hosted", "paid", "sales-led", "openapi", "llms-txt", "status-page", "webhooks", "python", "closed-source" ], "lastRelease": "2026-11-03", "graded": true, "anchor": { "graded": true, "score": 49.2, "grade": "D", "agentReady": false, "rank": 1110, "ranked": true, "rankOf": 1520, "categoryRank": 8, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 65, "maintenance": 56, "payments": 0, "reliability": 60, "schema": 71, "security": 36, "transparency": 44 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-03" }, "negative": 0, "verdict": "Benzinga's news, calendar and transcript APIs are documented from 11 public OpenAPI specs with an llms.txt and a Statuspage. The token travels in the query string, no prices or rate limit numbers are published, the Python client was last released in February 2021, and the vendor's main site refused our reader, so its terms and privacy policy are unread.", "bestFor": "A licensed firm's agent that needs Benzinga's own newswire, calendars, analyst ratings and transcripts as structured data with deltas.", "strengths": [ "11 OpenAPI specs in a public GitHub repository, 80 operations, with enums on the calendar and news parameters and example responses", "llms.txt and a Markdown twin of every docs page at docs.benzinga.com", "`displayOutput` sizes news responses to headline, abstract or full text, and `updatedSince` deltas avoid re-reading history", "Statuspage with seven API components and no incident since 14 September 2023", "security.txt names security@benzinga.com and a disclosure policy" ], "weaknesses": [ "The API token is sent only as the `token` query parameter, with no header option, scopes or rotation found", "No prices, rate limit numbers, 429 guidance or SLA are published; sales is by email or phone", "www.benzinga.com returned 403 on every page, so the terms, privacy policy, registration and pricing were not read", "The Python client's last release is 1.21 from 8 February 2021 and the JavaScript client's last push is from 2023; the docs' SDK page is template text", "The changelog pages are empty, and the error responses in the specs don't match the examples (401 and 404 appear in examples only)" ], "agentNotes": [ "Keep the token out of logs; it can only travel as `?token=`, so strip query strings before recording request URLs", "Page through news with `page` and `pageSize` (max 100) and narrow by `tickers`, `dateFrom` or `channels`; a query can't pass 10,000 items", "Poll with `updatedSince` (news) or `parameters[updated]` (calendar, signals) rather than re-reading history", "An unknown or unentitled news node ID returns 200 with an empty array, not 404; treat empty as not found", "Don't plan on a free key; access starts with licensing@benzinga.com and a contract" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 49.2 } ], "editorialScores": { "ergonomics": 65, "maintenance": 56, "payments": 0, "reliability": 60, "schema": 71, "security": 36, "transparency": 13 }, "provenanceScore": 75, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install benzinga", "http": "curl -H 'accept: application/json' \"https://api.benzinga.com/api/v2/news?token=$BENZINGA_TOKEN\u0026tickers=AAPL\u0026pageSize=5\"" }, "letme": { "capability": "https://letme.dev/market.news", "tool": "https://letme.dev/benzinga" }, "area": "domain-data", "provenance": { "legalEntity": "Benzinga", "domain": "benzinga.com", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://www.benzinga.com/terms-and-conditions", "privacy": "https://www.benzinga.com/page/privacy", "statusPage": "https://benzinga1.statuspage.io", "changelog": "https://docs.benzinga.com/changelog/overview", "securityTxt": "expired", "checked": "2026-11-03", "notes": [ "The legal entity's full name was not read. The terms and privacy pages on www.benzinga.com, linked from the docs footer, answered 403 to our reader, as did every other page on that host. The docs name Benzinga and the GitHub organisation is Benzinga.", "www.benzinga.com/robots.txt (version 11 September 2026) allows /apis/ and the terms and privacy paths for all crawlers; the 403 is a bot check, not a robots rule. docs.benzinga.com/robots.txt allows everything except /cdn-cgi/ and /_next/, with Content-Signal ai-train=yes, search=yes, ai-input=yes.", "security.txt at www.benzinga.com/.well-known/security.txt names security@benzinga.com, a policy at /.well-known/security-policy.md and Expires 2025-06-01T00:00:00.000Z, so it is expired.", "The status page is an Atlassian Statuspage at benzinga1.statuspage.io; the docs link it as API Status.", "RDAP for benzinga.com was refused (403 from rdap.org), so the registration date is unchecked.", "No terms clause on automated access could be read." ], "score": 75 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/benzinga.json", "live": { "slug": "benzinga", "probe": { "target": "https://api.benzinga.com", "method": "get", "lastAt": "2026-11-11T06:59:26.856971574Z", "lastOk": true, "lastStatus": 403, "lastMs": 130, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 88, "p95ms24h": 206, "samples24h": 244, "samples30d": 1558, "days": [ { "date": "2026-11-04", "probes": 87, "ok": 87 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 243, "ok": 243 }, { "date": "2026-11-08", "probes": 243, "ok": 243 }, { "date": "2026-11-09", "probes": 243, "ok": 243 }, { "date": "2026-11-10", "probes": 244, "ok": 244 }, { "date": "2026-11-11", "probes": 72, "ok": 72 } ], "since": "2026-11-04T00:00:00Z" }, "vendorStatus": { "page": "https://benzinga1.statuspage.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-11T06:54:24.635719706Z" }, "versions": [ { "registry": "pypi", "name": "benzinga", "version": "1.21", "released": "2021-02-08", "seenAt": "2026-11-11T05:41:59.06382679Z" } ], "githubStars": 2, "pypiWeekly": 4353, "securityTxt": { "url": "https://benzinga.com/.well-known/security.txt", "state": "expired", "expires": "2025-06-01T00:00:00.000Z", "checkedAt": "2026-11-10T16:07:34.112958493Z" }, "llmsTxt": { "url": "https://docs.benzinga.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-10T15:42:17.563071451Z" }, "domain": { "domain": "benzinga.com", "registered": "2009-05-18", "source": "https://rdap.verisign.com/com/v1/domain/benzinga.com", "checkedAt": "2026-11-08T14:50:53.506670312Z" }, "pages": [ { "url": "https://docs.benzinga.com/changelog/overview", "kind": "changelog", "status": 200, "checkedAt": "2026-11-10T16:15:49.870491728Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "8483546bdd23" }, { "url": "https://www.benzinga.com/page/privacy", "kind": "privacy", "status": 403, "checkedAt": "2026-11-10T16:36:52.002119578Z", "changedAt": "0001-01-01T00:00:00Z" }, { "url": "https://www.benzinga.com/terms-and-conditions", "kind": "terms", "status": 403, "checkedAt": "2026-11-10T16:36:54.040292777Z", "changedAt": "0001-01-01T00:00:00Z" } ], "github": { "repo": "benzinga/benzinga-docs", "checkedAt": "2026-11-09T09:42:22.932259955Z", "stars": 2, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-06T10:38:57Z", "openIssues": 1, "openPRs": 6, "issuesOpened90d": 1, "issuesClosed90d": 0, "prsMerged90d": 5, "ci": { "branch": "main", "runs": 50, "success": 49, "failure": 1, "other": 0, "latest": "success", "latestAt": "2026-11-06T09:13:37Z" }, "replies": { "sampled": 1, "unanswered": 1 } }, "updatedAt": "2026-11-11T06:59:26.856971574Z" }, "streak": { "days": 7, "from": "2026-11-04", "sinceWatching": true, "best": 7 } }, "answer": "TickerLayer scores 71.5 (BB) on agent readiness against Benzinga's 49.2 (D), and leads in 6 of 7 scored categories. Benzinga leads on transparency \u0026 trust.", "b": { "slug": "tickerlayer", "name": "TickerLayer", "vendor": "TickerLayer", "vendorUrl": "https://tickerlayer.com", "kind": "http-api", "category": "market-data", "summary": "TickerLayer is a market data API for stocks, forex, crypto, indices, ETFs, commodities, bond yields and perpetual futures, over REST and WebSocket with an API key, a hosted MCP server and pay-per-call x402 access in USDC on Base.", "url": "https://www.anchorterminal.com/tools/tickerlayer", "markdownUrl": "https://www.anchorterminal.com/tools/tickerlayer.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/tickerlayer.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/tickerlayer.json", "dns": "tickerlayer.grade.anchorterminal.com", "repo": "https://github.com/tickerlayer/agent-plugin", "license": "Proprietary hosted service under the TickerLayer terms of use, user agreement and market data disclaimer (all effective 3 November 2026), which name no legal entity or governing law. Free and Individual plans are for internal use, Business adds use inside the customer's own product, and redistribution needs a written Enterprise agreement. The agent plugin (github.com/tickerlayer/agent-plugin) and the npm client are MIT", "transports": [ "http", "streamable-http", "websocket" ], "remoteUrl": "https://mcp.tickerlayer.com/mcp", "packages": [ { "registry": "npm", "name": "tickerlayer" }, { "registry": "pypi", "name": "tickerlayer" } ], "auth": "mixed", "authNotes": "REST takes an API key in the `x-api-key` header. The OpenAPI file also defines `ApiKeyQuery`, an `apiKey` query parameter described as a 'compatibility fallback' that 'keeps the key in logged URLs', and the WebSocket at wss://stream.tickerlayer.com takes the key only in the URL as `apiKey`. A person creates the key in the dashboard after a browser signup. It is shown once and has no scopes, and regenerating it invalidates the previous key. The hosted MCP server takes the key as `x-api-key` or `Authorization: Bearer`, or OAuth 2.1 against https://api.tickerlayer.com (authorisation code with PKCE S256, dynamic client registration, refresh tokens, a revocation endpoint and one scope, `market.read`). The x402 gateway at https://x402.tickerlayer.com needs no account or key (https://tickerlayer.com/llms.txt, https://tickerlayer.com/openapi.json, https://tickerlayer.com/docs/mcp, https://api.tickerlayer.com/.well-known/oauth-authorization-server, https://tickerlayer.com/terms-of-use, checked 2026-11-10).", "pricing": "freemium", "pricingNotes": "Free plan at 0 USD with no card, per llms.txt, covering crypto, forex and US stocks over REST, 3,000 calls every 30 days, 10 requests a second, no WebSocket, internal use only. Individual plans are priced per feed, 49 USD a month for crypto, commodities or indices, 59 USD for forex or ETFs and 59 to 99 USD per stock market (United States 99 USD), each with 250,000 REST calls a month, 1 WebSocket connection and 10 symbols. Business runs 449 to 999 USD per feed with 25 million calls and 100 requests a second, for use inside the customer's own product. Perpetuals 179 or 799 USD, Futures CFDs 219 or 849 USD, add-ons (overnight session, SignalPoint, Fundamentals, Bonds) 39 to 449 USD. Yearly billing is 20 per cent lower. Enterprise is custom, with redistribution and an SLA. Without an account, x402 charges 0.01 to 0.10 USDC a call on Base and settles only after a valid response (https://tickerlayer.com/pricing, https://tickerlayer.com/llms.txt, https://tickerlayer.com/ai/x402.md, checked 2026-11-10).", "priceSummary": "$0.01 / call", "where": "hosted", "x402": { "level": "yes", "evidence": "Production gateway https://x402.tickerlayer.com on Base mainnet (`eip155:8453`) in USDC, with a sandbox at https://x402-testnet.tickerlayer.com on Base Sepolia. The catalogue lists 41 GET resources, scheme exact, protocol version 2, facilitator `coinbase-cdp-mainnet`, accountRequired false. Six routes each for stocks, forex, crypto, indices, ETFs and commodities, plus bond yields and four market-calendar routes. Perpetuals, Futures CFDs, the add-ons and WebSocket are not covered. Settlement only after a valid response, and payment identifiers bound to the request (https://x402.tickerlayer.com/catalog, https://tickerlayer.com/ai/x402.md, checked 2026-11-10).", "endpoints": [ { "url": "https://x402.tickerlayer.com/v1/stocks/quote/{symbol}", "priceUsd": 0.01, "network": "eip155:8453" }, { "url": "https://x402.tickerlayer.com/v1/crypto/snapshot/{symbol}", "priceUsd": 0.02, "network": "eip155:8453" }, { "url": "https://x402.tickerlayer.com/v1/forex/agg/{symbol}/{multiplier}/{timespan}/{from}/{to}", "priceUsd": 0.03, "network": "eip155:8453" }, { "url": "https://x402.tickerlayer.com/v1/bond/last/{symbol}", "priceUsd": 0.01, "network": "eip155:8453" }, { "url": "https://x402.tickerlayer.com/v1/markets/status", "priceUsd": 0.01, "network": "eip155:8453" } ] }, "toolCount": 12, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-10" }, "docsUrl": "https://tickerlayer.com/docs", "llmsTxt": "https://tickerlayer.com/llms.txt", "openapi": "https://tickerlayer.com/openapi.json", "registryName": "com.tickerlayer/market-data", "capabilities": [ "market.prices", "market.history", "market.crypto", "market.indices", "market.fundamentals", "data.markets" ], "tags": [ "official", "hosted", "x402", "freemium", "free-tier", "no-card", "openapi", "llms-txt", "mcp", "remote-mcp", "mcp-registry", "oauth", "api-key", "websocket", "streaming", "status-page", "closed-source", "python", "typescript", "agent-skills", "pre-1.0", "new" ], "lastRelease": "2026-11-06", "graded": true, "anchor": { "graded": true, "score": 71.5, "grade": "BB", "agentReady": true, "rank": 160, "ranked": true, "rankOf": 1520, "categoryRank": 2, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 79, "maintenance": 79, "payments": 92, "reliability": 70, "schema": 88, "security": 49, "transparency": 38 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-10" }, "negative": 0, "verdict": "An agent can read quotes, bars and market hours across eight asset classes through a documented REST API, 12 MCP tools or 41 x402 resources with no account, and 429s carry Retry-After. The data is derived from unnamed non-exchange sources, no operator is named, and the status history couldn't be read.", "bestFor": "An agent that needs latest prices, bars and market hours across stocks, forex, crypto, indices, ETFs, commodities, bond yields and perpetual futures from one schema, and wants to pay per call without an account.", "strengths": [ "x402 on its own gateway for 41 routes across six asset classes, bond yields and market hours, from 0.01 USDC, settled only after a valid response", "OpenAPI 3.1 with enums, examples and one error schema carrying `retryAfterMs`, `resetsAt` and the missing product, plus `Retry-After` and `X-RateLimit-*` headers", "llms.txt, llms-full.txt, a Markdown twin of every docs page and a skill that says which MCP tool to use for which question", "A dated changelog of 50 entries from 8 September to 6 November 2026", "MCP server under OAuth 2.1 with PKCE, dynamic registration, revocation and one read scope, listed in the official registry as `com.tickerlayer/market-data`" ], "weaknesses": [ "The data is derived and indicative from unnamed non-exchange sources, and no page says it is licensed from an exchange", "No legal entity, address or governing law in the terms, user agreement or privacy policy", "The REST key can travel as an `apiKey` query parameter, and the WebSocket takes it only in the URL", "The privacy policy names no subprocessors and gives no period for request logs", "No security.txt, bug bounty or certification found, and the status page's history loads from a path robots.txt disallows" ], "agentNotes": [ "Write stocks as `COUNTRY:TICKER`, such as `US:KO`, and always pass `asset_class` to the data tools.", "If a 429 carries `REST_QUOTA_EXCEEDED`, stop and tell the user. Waiting doesn't reset the monthly quota.", "Present prices as indicative TickerLayer values, never as official exchange prices.", "Call `get_market_status` before you report a quiet symbol as missing data.", "Send the key in the `x-api-key` header, never as the `apiKey` query parameter." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 71.5 } ], "editorialScores": { "ergonomics": 79, "maintenance": 79, "payments": 92, "reliability": 70, "schema": 88, "security": 49, "transparency": 30 }, "provenanceScore": 46, "checked": { "categories": { "ergonomics": "2026-11-10", "maintenance": "2026-11-10", "payments": "2026-11-10", "reliability": "2026-11-10", "schema": "2026-11-10", "security": "2026-11-10", "transparency": "2026-11-10" }, "last": "2026-11-10", "oldest": "2026-11-10", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install tickerlayer", "http": "curl -H \"x-api-key: $TICKERLAYER_API_KEY\" \"https://api.tickerlayer.com/stocks/quote/US:KO\"", "claudeCode": "claude mcp add --transport http tickerlayer https://mcp.tickerlayer.com/mcp", "config": { "mcpServers": { "tickerlayer": { "type": "http", "url": "https://mcp.tickerlayer.com/mcp" } } }, "x402": "curl -i \"https://x402.tickerlayer.com/v1/stocks/quote/US:KO\"" }, "letme": { "capability": "https://letme.dev/market.prices", "tool": "https://letme.dev/tickerlayer" }, "area": "domain-data", "unitPrices": [ { "item": "x402 quote, last trade or previous close", "unit": "call", "usd": 0.01, "note": "USDC on Base, no account, with snapshot and symbol lists at 0.02" }, { "item": "x402 historical bars, up to 100", "unit": "call", "usd": 0.03, "note": "0.05 for up to 500 bars and 0.10 for up to 1,000" }, { "item": "Individual crypto, commodities or indices feed", "unit": "month", "usd": 49, "note": "250,000 REST calls a month, 10 requests a second, internal use only" }, { "item": "Individual US stocks feed", "unit": "month", "usd": 99, "note": "other stock markets 59 to 99 USD each, internal use only" }, { "item": "Business crypto, commodities or indices feed", "unit": "month", "usd": 449, "note": "25 million REST calls a month, 100 requests a second, use inside the customer's own product" } ], "provenance": { "legalEntity": "", "domain": "tickerlayer.com", "domainRegistered": "2026-04-29", "domainNote": "RDAP (Verisign) gives tickerlayer.com a registration date of 29 April 2026 through Cloudflare, last changed 5 October 2026. No page read names a company, registration number, address or country.", "endpointOnVendorDomain": true, "terms": "https://tickerlayer.com/terms-of-use", "privacy": "https://tickerlayer.com/privacy-policy", "statusPage": "https://status.tickerlayer.com", "changelog": "https://tickerlayer.com/docs/changelog", "securityTxt": "none", "checked": "2026-11-10", "notes": [ "No legal entity is named anywhere read. The terms of use, the user agreement and the privacy policy (all effective 3 November 2026), the about page and the pricing footer name only 'TickerLayer' or 'the operator of TickerLayer', with no company, registration number, address, country or governing law. Their contact addresses are obfuscated and weren't read. The plugin README gives info@tickerlayer.com.", "The terms say the Services come 'AS IS', promise no uptime, cap liability at the greater of 12 months' fees or US$100, and allow MCP tools to change 'with reasonable notice where practical'. The user agreement makes payments non-refundable, refunds at TickerLayer's discretion. The terms ban scraping public pages at a volume that interferes with the Services. A handful of pages were read at a person's pace.", "The privacy policy keeps WebSocket connection records for 7 days and request and tool-call logs for 'a limited operational window', names subprocessor categories but no vendors, and says nothing on model training or transfer mechanisms.", "robots.txt on tickerlayer.com disallows ia_archiver and archive.org_bot entirely and, for `*`, /dashboard, /admin, /login, /signup, /auth, /oauth, /api, /billing, /profile, the market pages and /cdn-cgi/, with no Content-Signal. x402.tickerlayer.com disallows /v1/ and status.tickerlayer.com disallows /api/. robots.txt on mcp.tickerlayer.com and api.tickerlayer.com answered a client error, read as no rules. Only their OAuth metadata and one unauthenticated GET to /mcp (client error) were sent there.", "/.well-known/security.txt answered a client error.", "firstReleased is 2026-08-07, the first commit of tickerlayer/agent-plugin ('Release v0.1.0'), whose changelog names the hosted MCP server. The about page says the API opened in 'Early 2026' with no day. lastRelease is 2026-11-06, the newest changelog entry." ], "score": 46 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/tickerlayer.json", "live": { "slug": "tickerlayer", "probe": { "target": "https://mcp.tickerlayer.com/mcp", "method": "get", "lastAt": "2026-11-11T07:00:06.406304915Z", "lastOk": true, "lastStatus": 405, "lastMs": 160, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 150, "p95ms24h": 222, "samples24h": 43, "samples30d": 43, "days": [ { "date": "2026-11-11", "probes": 43, "ok": 43 } ], "since": "2026-11-11T02:53:34.214194678Z" }, "vendorStatus": { "page": "https://status.tickerlayer.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-11T05:35:55.448183455Z" }, "versions": [ { "registry": "npm", "name": "tickerlayer", "version": "0.1.0", "seenAt": "2026-11-11T06:42:09.859295043Z" }, { "registry": "pypi", "name": "tickerlayer", "version": "0.1.0", "released": "2026-10-20", "seenAt": "2026-11-11T06:42:10.714909327Z" } ], "githubStars": 0, "npmWeekly": 6, "pypiWeekly": 5, "updatedAt": "2026-11-11T07:00:06.406304915Z" }, "streak": { "days": 0, "from": "2026-11-11", "sinceWatching": true, "best": 0 } }, "edges": [ { "by": 92, "category": "payments", "leads": "tickerlayer", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). No prices are published anywhere we could read; the docs say to email or call licensing and the APIs page on www.benzinga.com answered 403 (0). The FAQ says a trial or sandbox is often available, with no terms, length or card condition, and the registration page was unread (0). A person registers in a browser or by email (0). Total 0, with pricing and registration recorded as unchecked.", "b": "x402 on the vendor's own gateway, x402.tickerlayer.com, for 41 GET routes. That is six routes for each of stocks, forex, crypto, indices, ETFs and commodities, plus bond yields and four market-calendar routes. Perpetuals, Futures CFDs, the add-ons, the symbol catalogue and WebSocket need a key. Between massive's 30 for US stock routes only and financial-datasets' 35 for every documented data endpoint (32 of 40). Per-call x402 prices from 0.01 to 0.10 USDC in the catalogue and docs, and plan prices per feed on the pricing page, all without a login (20). A Free plan of 3,000 REST calls every 30 days with 'no card', per llms.txt (20). An agent with a funded Base wallet pays per call with no account or key (20). 32+20+20+20 = 92." }, "scores": { "a": 0, "b": 92 } }, { "by": 23, "category": "maintenance", "leads": "tickerlayer", "name": "Maintenance \u0026 community", "reasons": { "a": "The docs repository had commits on 2 and 3 November 2026 moving OpenAPI specs from GitLab, and the robots.txt is versioned 11 September 2026 (30). Eight commit days between 23 October and 3 November 2026, all spec transfers, with no dated changelog entry anywhere (12 of 20). Support is licensing@benzinga.com, partners@benzinga.com and a phone line, with a status page; GitHub issue responsiveness was not read (6 of 15). The Python client's last PyPI release is 1.21 of 8 February 2021 and the JavaScript client was last pushed in July 2023, so no current official SDK (5 of 15). The Python client repository was pushed in March 2026 with no release; CI not checked (3 of 10). Total 56.", "b": "Read as a closed service. The newest changelog entry is 6 November 2026, a bond yield curve endpoint (30). 50 dated changelog entries from 8 September to 6 November 2026 (20). A public changelog, a consultation form, info@tickerlayer.com and a support chat, all untested, with no community channel and no issues on the plugin repository read. Massive and twelve-data took 10 (9 of 15). Official clients for JavaScript or TypeScript (npm) and Python (PyPI), both 0.1.0 from 20 October 2026, and an MCP registry entry under the verified namespace `com.tickerlayer` (15). The npm package has no dependencies or install hooks but no repository field, the clients' source isn't public and no CI is visible (5 of 10). 30+20+9+15+5 = 79." }, "scores": { "a": 56, "b": 79 } }, { "by": 17, "category": "schema", "leads": "tickerlayer", "name": "Schema \u0026 documentation", "reasons": { "a": "The docs are generated from 11 OpenAPI 3 specs in the public Benzinga/benzinga-docs repository, 80 operations, and the raw YAML is linked from the welcome page (25). llms.txt and a Markdown twin of every page (10). Operations carry a summary and a sentence or two on scope, with little on when not to use a call (12 of 20). Typed query parameters with enums on the calendar (50) and news (9) specs, and the token as a query parameter (10 of 15). Examples on most operations, but the error responses in the specs are thin, 400, 499 and 500 on news, with the 401 and 404 bodies shown only as examples (9 of 15). Versioned paths (/api/v2) and three changelog pages that are empty templates (5 of 15). Total 71.", "b": "OpenAPI 3.1 at tickerlayer.com/openapi.json (TickerLayer Market Data API 1.0.0, about 386,000 characters), read in its first 100,000 and last 96,000 characters, with summaries, descriptions, tags and examples on the operations read and shared 400, 401, 403, 404, 429 and 503 responses. The WebSocket is described in prose only and the hosted MCP tool schemas weren't read (23 of 25). llms.txt, llms-full.txt and a Markdown twin of every docs page (10). Operation descriptions state purpose and plan gating, and the vendor's skill says which MCP tool to use for each question and when not to, such as `get_quote` not being the tool for a price. Financial-datasets took 17 (17 of 20). Enums on `interval`, `multiplier`, `timespan` and `sort`, `format: date` on dates, bounded `limit`, required path parameters, as for massive (13 of 15). Examples on most parameters and responses, one Error schema with ten fields and documented codes, but the codes appear only as example values with no enum or table (13 of 15). A dated changelog of the last 50 changes, 8 September to 6 November 2026, but no version in the REST paths ('no /v1/') and the spec at 1.0.0. Above twelve-data's 10 for monthly updates and below massive's 15 for versioned paths (12 of 15). 23+10+17+13+13+12 = 88." }, "scores": { "a": 71, "b": 88 } }, { "by": 14, "category": "ergonomics", "leads": "tickerlayer", "name": "Agent ergonomics", "reasons": { "a": "`displayOutput` of headline, abstract or full sizes a news response, and `pageSize` runs to 100 (18 of 25). `page` and `pageSize`, ticker, channel, date and `updatedSince` filters, with a 10,000-item cap per query that the docs explain how to work round (18 of 20). Error bodies carry a code, an id and a message in the examples, but an unknown node ID returns 200 with an empty array and the spec's response list doesn't match the examples (10 of 20). Every data call is a read, with no safe-retry guidance; the webhook API registers endpoints (12 of 20). Few required parameters, but the Python client is from 2021, the JavaScript client from 2023 and the docs' SDK page is template text (7 of 15). Total 65.", "b": "Read on the REST API, with the MCP server where a line covers it. Responses are sized by `limit` (bars up to 5,000, catalogue up to 1,000), `sort`, date ranges and batch calls for futures quotes and market status, with no field selection. The MCP server has 12 tools, 11 shown to the model. Massive and financial-datasets took 15 (15 of 25). `limit`, `offset` and `next_offset`, cursors on fundamentals and economic events, `total_count` on bars, `search` on symbols and `updated_since` on signals (18 of 20). Errors carry `statusCode`, `message`, a code, `retryAfterMs`, `resetsAt`, `limitRps`, `plansUrl` and the missing `product` or `market`, and the skill gives an action per status. Above financial-datasets' 16 (17 of 20). Every data call is a GET, and x402 settles only after a valid response with payment identifiers bound to the request, but no readOnlyHint or other annotation was found for the MCP tools. Financial-datasets took 14 without annotations (15 of 20). Data tools need only `asset_class` and `symbol`, with defaults for limit and sort, and official clients exist for JavaScript or TypeScript and Python, both at 0.1.0 from 20 October 2026. Stocks need the `COUNTRY:TICKER` form (14 of 15). 15+18+17+15+14 = 79." }, "scores": { "a": 65, "b": 79 } }, { "by": 13, "category": "security", "leads": "tickerlayer", "name": "Security \u0026 auth", "reasons": { "a": "One token per account with no scopes, sent only as the `token` query parameter, generated in the console; no rotation or expiry found (20 less 10 for the query string, so 10). Every data endpoint is a read (15 of 20). News, press releases and transcripts are third-party text, with no guidance on treating them as untrusted (5 of 15). No usage log or per-call record for the token holder was found (0 of 15). security.txt names security@benzinga.com and a policy page, with an Expires date of 1 June 2025, and the policy itself is on the host that refused our reader; no bounty, SOC 2 or ISO 27001 was found in the docs (6 of 20). Total 36.", "b": "A plain account key with no scopes, shown once and replaced by regenerating it in the dashboard (20). The OpenAPI file defines an `apiKey` query parameter as a 'compatibility fallback', and the WebSocket takes the key only in its URL, so 10 off. The MCP server adds OAuth 2.1 with PKCE S256, dynamic registration, refresh tokens, a revocation endpoint and one scope, `market.read`. Twelve-data took 18 on the same pattern, one less here because the WebSocket has no header option (17 of 30). Every operation reads data, and the OAuth scope is read-only, as for twelve-data and financial-datasets (15 of 20). Responses are prices, bars, symbols, calendars and yields. There is no news feed, and SignalPoint signals are structured fields, so no untrusted text reaches the agent (10 of 15). Rate-limit headers on every response, quota 429s that state the limit and when it renews, and a dashboard list of WebSocket connections with source IP, key and how each ended (24 October 2026). No per-call REST log for the key holder was found, though the privacy policy says request logs are kept (7 of 15). security.txt answered a client error, and no disclosure policy, bug bounty, SOC 2 or ISO 27001 was found (0 of 20). 17+15+10+7+0 = 49." }, "scores": { "a": 36, "b": 49 } }, { "by": 10, "category": "reliability", "leads": "tickerlayer", "name": "Reliability", "reasons": { "a": "Graded as a hosted service. Atlassian Statuspage at benzinga1.statuspage.io with seven API components (20). The incident feed holds 14 incidents, the newest on 14 September 2023, so the 90 days to 3 November 2026 are clean (30). No rate limit numbers are published; the FAQ says limits depend on the API and the subscription tier (0 of 15). No 429, Retry-After or backoff guidance was found in the docs or the specs (0 of 15). No SLA was found; the architecture page cites a 99.9 per cent availability figure as a claim, and the terms were unread (0). The APIs are generally available (10). Total 60.", "b": "Read with the hosted lines, on the REST API. status.tickerlayer.com is an UptimeRobot page linked from the site header (20). Its monitors and history load by script from /api/, which its robots.txt disallows, so no incident record was read, as for eodhd and apitemplate-io (5). Limits are published with numbers, 10 requests a second per account on Free and Individual, 100 on Business, and monthly call quotas per feed (15). The OpenAPI file's 429 carries `Retry-After` and a body with `retryAfterMs`, `resetsAt` and a code that separates the per-second limit from the monthly quota, and every response has carried `X-RateLimit-Limit` and `X-RateLimit-Remaining` since 14 September 2026. Every data operation is a GET, and x402 retries with the same payment identifier return the stored response (15). An SLA is named only for Enterprise under a written agreement and as 'partially available' on Business, with no published terms or figure, and the terms of use promise no uptime. Financial-datasets took 10 for SLAs listed on a self-serve plan, so this is half (5 of 10). No beta or preview label on the REST API, the MCP server or the x402 gateway (10). 20+5+15+15+5+10 = 70." }, "scores": { "a": 60, "b": 70 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Benzinga", "b": "TickerLayer", "name": "Vendor" }, { "a": "https://api.benzinga.com", "b": "https://mcp.tickerlayer.com/mcp", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP, websocket", "name": "Transports" }, { "a": "API key", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "yes, from $0.01/call", "name": "x402" }, { "a": "none", "b": "Proprietary hosted service under the TickerLayer terms of use, user agreement and market data disclaimer (all effective 3 November 2026), which name no legal entity or governing law. Free and Individual plans are for internal use, Business adds use inside the customer's own product, and redistribution needs a written Enterprise agreement. The agent plugin (github.com/tickerlayer/agent-plugin) and the npm client are MIT", "name": "Licence" }, { "a": "none", "b": "12", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "com.tickerlayer/market-data", "name": "MCP registry" }, { "a": "2026-11-03", "b": "2026-11-06", "name": "Last release" }, { "a": "couldn't be read", "b": "not read yet", "name": "Terms last updated" }, { "a": "couldn't be read", "b": "not read yet", "name": "Privacy policy last updated" }, { "a": "couldn't be read", "b": "not read yet", "name": "Customer content may train models" }, { "a": "couldn't be read", "b": "not read yet", "name": "Terms restrict automated access" }, { "a": "couldn't be read", "b": "not read yet", "name": "Terms restrict benchmarking" }, { "a": "couldn't be read", "b": "not read yet", "name": "Terms or service can change without notice" }, { "a": "couldn't be read", "b": "not read yet", "name": "Arbitration or class-action waiver" }, { "a": "34 stars", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "TickerLayer scores 71.5 (BB) on agent readiness against Benzinga's 49.2 (D), and leads in 6 of 7 scored categories. Benzinga leads on transparency \u0026 trust.", "question": "Which is better for AI agents, Benzinga or TickerLayer?" }, { "answer": "Benzinga needs an API key. TickerLayer takes an API key or an OAuth sign-in. An agent can also pay TickerLayer per call over x402, with no account.", "question": "Do Benzinga and TickerLayer need an API key?" }, { "answer": "Yes. Benzinga has a hosted endpoint at https://api.benzinga.com and TickerLayer at https://mcp.tickerlayer.com/mcp.", "question": "Can an agent call Benzinga and TickerLayer without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Transparency \u0026 trust, 44 against 38" ], "also": null, "goodFor": "A licensed firm's agent that needs Benzinga's own newswire, calendars, analyst ratings and transcripts as structured data with deltas.", "slug": "benzinga", "watchFor": "The API token is sent only as the `token` query parameter, with no header option, scopes or rotation found" }, { "aheadOn": [ "Reliability, 70 against 60", "Schema \u0026 documentation, 88 against 71", "Agent ergonomics, 79 against 65", "Security \u0026 auth, 49 against 36", "Payments \u0026 pricing, 92 against 0", "Maintenance \u0026 community, 79 against 56" ], "also": [ "Agent-ready, a grade of BB or better", "An agent can pay per call over x402, with no account", "Free to start without a card" ], "goodFor": "An agent that needs latest prices, bars and market hours across stocks, forex, crypto, indices, ETFs, commodities, bond yields and perpetual futures from one schema, and wants to pay per call without an account.", "slug": "tickerlayer", "watchFor": "The data is derived and indicative from unnamed non-exchange sources, and no page says it is licensed from an exchange" } ], "history": null, "job": { "capability": "market.prices", "name": "Market prices" }, "others": [ { "json": "https://www.anchorterminal.com/compare/alpha-vantage-vs-benzinga.json", "title": "Alpha Vantage vs Benzinga", "url": "https://www.anchorterminal.com/compare/alpha-vantage-vs-benzinga" }, { "json": "https://www.anchorterminal.com/compare/alpha-vantage-vs-tickerlayer.json", "title": "Alpha Vantage vs TickerLayer", "url": "https://www.anchorterminal.com/compare/alpha-vantage-vs-tickerlayer" }, { "json": "https://www.anchorterminal.com/compare/benzinga-vs-databento.json", "title": "Benzinga vs Databento", "url": "https://www.anchorterminal.com/compare/benzinga-vs-databento" }, { "json": "https://www.anchorterminal.com/compare/benzinga-vs-massive.json", "title": "Benzinga vs Massive (formerly Polygon.io)", "url": "https://www.anchorterminal.com/compare/benzinga-vs-massive" }, { "json": "https://www.anchorterminal.com/compare/databento-vs-tickerlayer.json", "title": "Databento vs TickerLayer", "url": "https://www.anchorterminal.com/compare/databento-vs-tickerlayer" }, { "json": "https://www.anchorterminal.com/compare/finnhub-vs-tickerlayer.json", "title": "Finnhub vs TickerLayer", "url": "https://www.anchorterminal.com/compare/finnhub-vs-tickerlayer" }, { "json": "https://www.anchorterminal.com/compare/intrinio-vs-tickerlayer.json", "title": "Intrinio vs TickerLayer", "url": "https://www.anchorterminal.com/compare/intrinio-vs-tickerlayer" }, { "json": "https://www.anchorterminal.com/compare/massive-vs-tickerlayer.json", "title": "Massive (formerly Polygon.io) vs TickerLayer", "url": "https://www.anchorterminal.com/compare/massive-vs-tickerlayer" }, { "json": "https://www.anchorterminal.com/compare/tickerlayer-vs-tiingo.json", "title": "TickerLayer vs Tiingo", "url": "https://www.anchorterminal.com/compare/tickerlayer-vs-tiingo" }, { "json": "https://www.anchorterminal.com/compare/tickerlayer-vs-twelve-data.json", "title": "TickerLayer vs Twelve Data", "url": "https://www.anchorterminal.com/compare/tickerlayer-vs-twelve-data" }, { "json": "https://www.anchorterminal.com/compare/eulerpool-vs-tickerlayer.json", "title": "Eulerpool Financial Data API vs TickerLayer", "url": "https://www.anchorterminal.com/compare/eulerpool-vs-tickerlayer" }, { "json": "https://www.anchorterminal.com/compare/financial-datasets-vs-tickerlayer.json", "title": "Financial Datasets vs TickerLayer", "url": "https://www.anchorterminal.com/compare/financial-datasets-vs-tickerlayer" }, { "json": "https://www.anchorterminal.com/compare/financial-modeling-prep-vs-tickerlayer.json", "title": "Financial Modeling Prep vs TickerLayer", "url": "https://www.anchorterminal.com/compare/financial-modeling-prep-vs-tickerlayer" }, { "json": "https://www.anchorterminal.com/compare/eodhd-vs-tickerlayer.json", "title": "EODHD vs TickerLayer", "url": "https://www.anchorterminal.com/compare/eodhd-vs-tickerlayer" }, { "json": "https://www.anchorterminal.com/compare/benzinga-vs-eodhd.json", "title": "Benzinga vs EODHD", "url": "https://www.anchorterminal.com/compare/benzinga-vs-eodhd" }, { "json": "https://www.anchorterminal.com/compare/benzinga-vs-eulerpool.json", "title": "Benzinga vs Eulerpool Financial Data API", "url": "https://www.anchorterminal.com/compare/benzinga-vs-eulerpool" }, { "json": "https://www.anchorterminal.com/compare/benzinga-vs-financial-datasets.json", "title": "Benzinga vs Financial Datasets", "url": "https://www.anchorterminal.com/compare/benzinga-vs-financial-datasets" }, { "json": "https://www.anchorterminal.com/compare/benzinga-vs-financial-modeling-prep.json", "title": "Benzinga vs Financial Modeling Prep", "url": "https://www.anchorterminal.com/compare/benzinga-vs-financial-modeling-prep" }, { "json": "https://www.anchorterminal.com/compare/benzinga-vs-finnhub.json", "title": "Benzinga vs Finnhub", "url": "https://www.anchorterminal.com/compare/benzinga-vs-finnhub" }, { "json": "https://www.anchorterminal.com/compare/benzinga-vs-intrinio.json", "title": "Benzinga vs Intrinio", "url": "https://www.anchorterminal.com/compare/benzinga-vs-intrinio" }, { "json": "https://www.anchorterminal.com/compare/benzinga-vs-tiingo.json", "title": "Benzinga vs Tiingo", "url": "https://www.anchorterminal.com/compare/benzinga-vs-tiingo" }, { "json": "https://www.anchorterminal.com/compare/benzinga-vs-twelve-data.json", "title": "Benzinga vs Twelve Data", "url": "https://www.anchorterminal.com/compare/benzinga-vs-twelve-data" } ], "panel": null, "scores": [ { "benzinga": 60, "by": 10, "edge": "tickerlayer", "key": "reliability", "name": "Reliability", "tickerlayer": 70, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "benzinga": 71, "by": 17, "edge": "tickerlayer", "key": "schema", "name": "Schema \u0026 documentation", "tickerlayer": 88, "weight": 13 }, { "benzinga": 65, "by": 14, "edge": "tickerlayer", "key": "ergonomics", "name": "Agent ergonomics", "tickerlayer": 79, "weight": 13 }, { "benzinga": 36, "by": 13, "edge": "tickerlayer", "key": "security", "name": "Security \u0026 auth", "tickerlayer": 49, "weight": 14 }, { "benzinga": 0, "by": 92, "edge": "tickerlayer", "key": "payments", "name": "Payments \u0026 pricing", "tickerlayer": 92, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "benzinga": 56, "by": 23, "edge": "tickerlayer", "key": "maintenance", "name": "Maintenance \u0026 community", "tickerlayer": 79, "weight": 7 }, { "benzinga": 44, "by": 6, "edge": "benzinga", "key": "transparency", "name": "Transparency \u0026 trust", "tickerlayer": 38, "weight": 7 } ], "summary": "TickerLayer scores 71.5 (BB) on agent readiness against Benzinga's 49.2 (D), and leads in 6 of 7 scored categories. Benzinga leads on transparency \u0026 trust. Both do market prices. TickerLayer accepts x402. Benzinga doesn't.", "tasks": null, "tutorials": [], "verdicts": { "benzinga": "Benzinga's news, calendar and transcript APIs are documented from 11 public OpenAPI specs with an llms.txt and a Statuspage. The token travels in the query string, no prices or rate limit numbers are published, the Python client was last released in February 2021, and the vendor's main site refused our reader, so its terms and privacy policy are unread.", "tickerlayer": "An agent can read quotes, bars and market hours across eight asset classes through a documented REST API, 12 MCP tools or 41 x402 resources with no account, and 429s carry Retry-After. The data is derived from unnamed non-exchange sources, no operator is named, and the status history couldn't be read." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/benzinga-vs-tickerlayer", "json": "https://www.anchorterminal.com/compare/benzinga-vs-tickerlayer.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/benzinga-vs-tickerlayer.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/benzinga-vs-tickerlayer.min.md" }, "markdown": "TickerLayer scores 71.5 (BB) on agent readiness against Benzinga's 49.2 (D), and leads in 6 of 7 scored categories. Benzinga leads on transparency \u0026 trust. Both do market prices. TickerLayer accepts x402. Benzinga doesn't.\n\n- Benzinga: grade D, 49.2/100, rank #1110 of 1520. Markdown https://www.anchorterminal.com/tools/benzinga.md · JSON https://www.anchorterminal.com/api/v1/tools/benzinga.json\n- TickerLayer: grade BB, 71.5/100, rank #160 of 1520. Markdown https://www.anchorterminal.com/tools/tickerlayer.md · JSON https://www.anchorterminal.com/api/v1/tools/tickerlayer.json\n- Best financial market data APIs for AI agents: https://www.anchorterminal.com/best/market-data/index.md\n- All 78 markets comparisons: https://www.anchorterminal.com/compare/market-data/index.md\n\n## Which one, for what\n\n### Benzinga (D)\n\nGood for: A licensed firm's agent that needs Benzinga's own newswire, calendars, analyst ratings and transcripts as structured data with deltas.\n\nAhead on:\n- Transparency \u0026 trust, 44 against 38\n\nWatch for: The API token is sent only as the `token` query parameter, with no header option, scopes or rotation found\n\n### TickerLayer (BB)\n\nGood for: An agent that needs latest prices, bars and market hours across stocks, forex, crypto, indices, ETFs, commodities, bond yields and perpetual futures from one schema, and wants to pay per call without an account.\n\nAhead on:\n- Reliability, 70 against 60\n- Schema \u0026 documentation, 88 against 71\n- Agent ergonomics, 79 against 65\n- Security \u0026 auth, 49 against 36\n- Payments \u0026 pricing, 92 against 0\n- Maintenance \u0026 community, 79 against 56\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n- An agent can pay per call over x402, with no account\n- Free to start without a card\n\nWatch for: The data is derived and indicative from unnamed non-exchange sources, and no page says it is licensed from an exchange\n\n\n## Why the edge\n\n### Payments \u0026 pricing: TickerLayer +92\n\n- Benzinga (0): No x402, MPP or L402 (0). No prices are published anywhere we could read; the docs say to email or call licensing and the APIs page on www.benzinga.com answered 403 (0). The FAQ says a trial or sandbox is often available, with no terms, length or card condition, and the registration page was unread (0). A person registers in a browser or by email (0). Total 0, with pricing and registration recorded as unchecked.\n- TickerLayer (92): x402 on the vendor's own gateway, x402.tickerlayer.com, for 41 GET routes. That is six routes for each of stocks, forex, crypto, indices, ETFs and commodities, plus bond yields and four market-calendar routes. Perpetuals, Futures CFDs, the add-ons, the symbol catalogue and WebSocket need a key. Between massive's 30 for US stock routes only and financial-datasets' 35 for every documented data endpoint (32 of 40). Per-call x402 prices from 0.01 to 0.10 USDC in the catalogue and docs, and plan prices per feed on the pricing page, all without a login (20). A Free plan of 3,000 REST calls every 30 days with 'no card', per llms.txt (20). An agent with a funded Base wallet pays per call with no account or key (20). 32+20+20+20 = 92.\n\n### Maintenance \u0026 community: TickerLayer +23\n\n- Benzinga (56): The docs repository had commits on 2 and 3 November 2026 moving OpenAPI specs from GitLab, and the robots.txt is versioned 11 September 2026 (30). Eight commit days between 23 October and 3 November 2026, all spec transfers, with no dated changelog entry anywhere (12 of 20). Support is licensing@benzinga.com, partners@benzinga.com and a phone line, with a status page; GitHub issue responsiveness was not read (6 of 15). The Python client's last PyPI release is 1.21 of 8 February 2021 and the JavaScript client was last pushed in July 2023, so no current official SDK (5 of 15). The Python client repository was pushed in March 2026 with no release; CI not checked (3 of 10). Total 56.\n- TickerLayer (79): Read as a closed service. The newest changelog entry is 6 November 2026, a bond yield curve endpoint (30). 50 dated changelog entries from 8 September to 6 November 2026 (20). A public changelog, a consultation form, info@tickerlayer.com and a support chat, all untested, with no community channel and no issues on the plugin repository read. Massive and twelve-data took 10 (9 of 15). Official clients for JavaScript or TypeScript (npm) and Python (PyPI), both 0.1.0 from 20 October 2026, and an MCP registry entry under the verified namespace `com.tickerlayer` (15). The npm package has no dependencies or install hooks but no repository field, the clients' source isn't public and no CI is visible (5 of 10). 30+20+9+15+5 = 79.\n\n### Schema \u0026 documentation: TickerLayer +17\n\n- Benzinga (71): The docs are generated from 11 OpenAPI 3 specs in the public Benzinga/benzinga-docs repository, 80 operations, and the raw YAML is linked from the welcome page (25). llms.txt and a Markdown twin of every page (10). Operations carry a summary and a sentence or two on scope, with little on when not to use a call (12 of 20). Typed query parameters with enums on the calendar (50) and news (9) specs, and the token as a query parameter (10 of 15). Examples on most operations, but the error responses in the specs are thin, 400, 499 and 500 on news, with the 401 and 404 bodies shown only as examples (9 of 15). Versioned paths (/api/v2) and three changelog pages that are empty templates (5 of 15). Total 71.\n- TickerLayer (88): OpenAPI 3.1 at tickerlayer.com/openapi.json (TickerLayer Market Data API 1.0.0, about 386,000 characters), read in its first 100,000 and last 96,000 characters, with summaries, descriptions, tags and examples on the operations read and shared 400, 401, 403, 404, 429 and 503 responses. The WebSocket is described in prose only and the hosted MCP tool schemas weren't read (23 of 25). llms.txt, llms-full.txt and a Markdown twin of every docs page (10). Operation descriptions state purpose and plan gating, and the vendor's skill says which MCP tool to use for each question and when not to, such as `get_quote` not being the tool for a price. Financial-datasets took 17 (17 of 20). Enums on `interval`, `multiplier`, `timespan` and `sort`, `format: date` on dates, bounded `limit`, required path parameters, as for massive (13 of 15). Examples on most parameters and responses, one Error schema with ten fields and documented codes, but the codes appear only as example values with no enum or table (13 of 15). A dated changelog of the last 50 changes, 8 September to 6 November 2026, but no version in the REST paths ('no /v1/') and the spec at 1.0.0. Above twelve-data's 10 for monthly updates and below massive's 15 for versioned paths (12 of 15). 23+10+17+13+13+12 = 88.\n\n### Agent ergonomics: TickerLayer +14\n\n- Benzinga (65): `displayOutput` of headline, abstract or full sizes a news response, and `pageSize` runs to 100 (18 of 25). `page` and `pageSize`, ticker, channel, date and `updatedSince` filters, with a 10,000-item cap per query that the docs explain how to work round (18 of 20). Error bodies carry a code, an id and a message in the examples, but an unknown node ID returns 200 with an empty array and the spec's response list doesn't match the examples (10 of 20). Every data call is a read, with no safe-retry guidance; the webhook API registers endpoints (12 of 20). Few required parameters, but the Python client is from 2021, the JavaScript client from 2023 and the docs' SDK page is template text (7 of 15). Total 65.\n- TickerLayer (79): Read on the REST API, with the MCP server where a line covers it. Responses are sized by `limit` (bars up to 5,000, catalogue up to 1,000), `sort`, date ranges and batch calls for futures quotes and market status, with no field selection. The MCP server has 12 tools, 11 shown to the model. Massive and financial-datasets took 15 (15 of 25). `limit`, `offset` and `next_offset`, cursors on fundamentals and economic events, `total_count` on bars, `search` on symbols and `updated_since` on signals (18 of 20). Errors carry `statusCode`, `message`, a code, `retryAfterMs`, `resetsAt`, `limitRps`, `plansUrl` and the missing `product` or `market`, and the skill gives an action per status. Above financial-datasets' 16 (17 of 20). Every data call is a GET, and x402 settles only after a valid response with payment identifiers bound to the request, but no readOnlyHint or other annotation was found for the MCP tools. Financial-datasets took 14 without annotations (15 of 20). Data tools need only `asset_class` and `symbol`, with defaults for limit and sort, and official clients exist for JavaScript or TypeScript and Python, both at 0.1.0 from 20 October 2026. Stocks need the `COUNTRY:TICKER` form (14 of 15). 15+18+17+15+14 = 79.\n\n### Security \u0026 auth: TickerLayer +13\n\n- Benzinga (36): One token per account with no scopes, sent only as the `token` query parameter, generated in the console; no rotation or expiry found (20 less 10 for the query string, so 10). Every data endpoint is a read (15 of 20). News, press releases and transcripts are third-party text, with no guidance on treating them as untrusted (5 of 15). No usage log or per-call record for the token holder was found (0 of 15). security.txt names security@benzinga.com and a policy page, with an Expires date of 1 June 2025, and the policy itself is on the host that refused our reader; no bounty, SOC 2 or ISO 27001 was found in the docs (6 of 20). Total 36.\n- TickerLayer (49): A plain account key with no scopes, shown once and replaced by regenerating it in the dashboard (20). The OpenAPI file defines an `apiKey` query parameter as a 'compatibility fallback', and the WebSocket takes the key only in its URL, so 10 off. The MCP server adds OAuth 2.1 with PKCE S256, dynamic registration, refresh tokens, a revocation endpoint and one scope, `market.read`. Twelve-data took 18 on the same pattern, one less here because the WebSocket has no header option (17 of 30). Every operation reads data, and the OAuth scope is read-only, as for twelve-data and financial-datasets (15 of 20). Responses are prices, bars, symbols, calendars and yields. There is no news feed, and SignalPoint signals are structured fields, so no untrusted text reaches the agent (10 of 15). Rate-limit headers on every response, quota 429s that state the limit and when it renews, and a dashboard list of WebSocket connections with source IP, key and how each ended (24 October 2026). No per-call REST log for the key holder was found, though the privacy policy says request logs are kept (7 of 15). security.txt answered a client error, and no disclosure policy, bug bounty, SOC 2 or ISO 27001 was found (0 of 20). 17+15+10+7+0 = 49.\n\n### Reliability: TickerLayer +10\n\n- Benzinga (60): Graded as a hosted service. Atlassian Statuspage at benzinga1.statuspage.io with seven API components (20). The incident feed holds 14 incidents, the newest on 14 September 2023, so the 90 days to 3 November 2026 are clean (30). No rate limit numbers are published; the FAQ says limits depend on the API and the subscription tier (0 of 15). No 429, Retry-After or backoff guidance was found in the docs or the specs (0 of 15). No SLA was found; the architecture page cites a 99.9 per cent availability figure as a claim, and the terms were unread (0). The APIs are generally available (10). Total 60.\n- TickerLayer (70): Read with the hosted lines, on the REST API. status.tickerlayer.com is an UptimeRobot page linked from the site header (20). Its monitors and history load by script from /api/, which its robots.txt disallows, so no incident record was read, as for eodhd and apitemplate-io (5). Limits are published with numbers, 10 requests a second per account on Free and Individual, 100 on Business, and monthly call quotas per feed (15). The OpenAPI file's 429 carries `Retry-After` and a body with `retryAfterMs`, `resetsAt` and a code that separates the per-second limit from the monthly quota, and every response has carried `X-RateLimit-Limit` and `X-RateLimit-Remaining` since 14 September 2026. Every data operation is a GET, and x402 retries with the same payment identifier return the stored response (15). An SLA is named only for Enterprise under a written agreement and as 'partially available' on Business, with no published terms or figure, and the terms of use promise no uptime. Financial-datasets took 10 for SLAs listed on a self-serve plan, so this is half (5 of 10). No beta or preview label on the REST API, the MCP server or the x402 gateway (10). 20+5+15+15+5+10 = 70.\n\n## Score by category\n\n| Category | Weight | Benzinga | TickerLayer | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 60 | 70 | TickerLayer +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 71 | 88 | TickerLayer +17 |\n| Agent ergonomics | 13% (16.2 this run) | 65 | 79 | TickerLayer +14 |\n| Security \u0026 auth | 14% (17.5 this run) | 36 | 49 | TickerLayer +13 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 0 | 92 | TickerLayer +92 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 56 | 79 | TickerLayer +23 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 44 | 38 | Benzinga +6 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **49.2 · D** | **71.5 · BB** | |\n\n## Facts side by side\n\n| Fact | Benzinga | TickerLayer |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Benzinga | TickerLayer |\n| Hosted endpoint | `https://api.benzinga.com` | `https://mcp.tickerlayer.com/mcp` |\n| Transports | HTTP | HTTP, Streamable HTTP, websocket |\n| Auth | API key | OAuth or key |\n| Pricing | Paid | Freemium |\n| x402 | no | yes, from $0.01/call |\n| Licence | none | Proprietary hosted service under the TickerLayer terms of use, user agreement and market data disclaimer (all effective 3 November 2026), which name no legal entity or governing law. Free and Individual plans are for internal use, Business adds use inside the customer's own product, and redistribution needs a written Enterprise agreement. The agent plugin (github.com/tickerlayer/agent-plugin) and the npm client are MIT |\n| Tools exposed | none | 12 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `com.tickerlayer/market-data` |\n| Last release | 2026-11-03 | 2026-11-06 |\n| Terms last updated | couldn't be read | not read yet |\n| Privacy policy last updated | couldn't be read | not read yet |\n| Customer content may train models | couldn't be read | not read yet |\n| Terms restrict automated access | couldn't be read | not read yet |\n| Terms restrict benchmarking | couldn't be read | not read yet |\n| Terms or service can change without notice | couldn't be read | not read yet |\n| Arbitration or class-action waiver | couldn't be read | not read yet |\n| Popularity | 34 stars | none |\n\n## Verdicts\n\n**Benzinga.** Benzinga's news, calendar and transcript APIs are documented from 11 public OpenAPI specs with an llms.txt and a Statuspage. The token travels in the query string, no prices or rate limit numbers are published, the Python client was last released in February 2021, and the vendor's main site refused our reader, so its terms and privacy policy are unread.\n\n**TickerLayer.** An agent can read quotes, bars and market hours across eight asset classes through a documented REST API, 12 MCP tools or 41 x402 resources with no account, and 429s carry Retry-After. The data is derived from unnamed non-exchange sources, no operator is named, and the status history couldn't be read.\n\n## Before you call either\n\n### Benzinga\n\n1. Keep the token out of logs; it can only travel as `?token=`, so strip query strings before recording request URLs\n2. Page through news with `page` and `pageSize` (max 100) and narrow by `tickers`, `dateFrom` or `channels`; a query can't pass 10,000 items\n3. Poll with `updatedSince` (news) or `parameters[updated]` (calendar, signals) rather than re-reading history\n4. An unknown or unentitled news node ID returns 200 with an empty array, not 404; treat empty as not found\n5. Don't plan on a free key; access starts with licensing@benzinga.com and a contract\n\n### TickerLayer\n\n1. Write stocks as `COUNTRY:TICKER`, such as `US:KO`, and always pass `asset_class` to the data tools.\n2. If a 429 carries `REST_QUOTA_EXCEEDED`, stop and tell the user. Waiting doesn't reset the monthly quota.\n3. Present prices as indicative TickerLayer values, never as official exchange prices.\n4. Call `get_market_status` before you report a quiet symbol as missing data.\n5. Send the key in the `x-api-key` header, never as the `apiKey` query parameter.\n\n## Questions\n\n### Which is better for AI agents, Benzinga or TickerLayer?\n\nTickerLayer scores 71.5 (BB) on agent readiness against Benzinga's 49.2 (D), and leads in 6 of 7 scored categories. Benzinga leads on transparency \u0026 trust.\n\n### Do Benzinga and TickerLayer need an API key?\n\nBenzinga needs an API key. TickerLayer takes an API key or an OAuth sign-in. An agent can also pay TickerLayer per call over x402, with no account.\n\n### Can an agent call Benzinga and TickerLayer without installing anything?\n\nYes. Benzinga has a hosted endpoint at https://api.benzinga.com and TickerLayer at https://mcp.tickerlayer.com/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/benzinga-vs-tickerlayer.json, and with the fewest tokens: https://www.anchorterminal.com/compare/benzinga-vs-tickerlayer.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"benzinga\", \"b\": \"tickerlayer\"}`. From a terminal: `anchor compare benzinga tickerlayer`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/benzinga.json and https://www.anchorterminal.com/api/v1/tools/tickerlayer.json\n\n## Other comparisons with Benzinga or TickerLayer\n\n- [Alpha Vantage vs Benzinga](https://www.anchorterminal.com/compare/alpha-vantage-vs-benzinga.md)\n- [Alpha Vantage vs TickerLayer](https://www.anchorterminal.com/compare/alpha-vantage-vs-tickerlayer.md)\n- [Benzinga vs Databento](https://www.anchorterminal.com/compare/benzinga-vs-databento.md)\n- [Benzinga vs Massive (formerly Polygon.io)](https://www.anchorterminal.com/compare/benzinga-vs-massive.md)\n- [Databento vs TickerLayer](https://www.anchorterminal.com/compare/databento-vs-tickerlayer.md)\n- [Finnhub vs TickerLayer](https://www.anchorterminal.com/compare/finnhub-vs-tickerlayer.md)\n- [Intrinio vs TickerLayer](https://www.anchorterminal.com/compare/intrinio-vs-tickerlayer.md)\n- [Massive (formerly Polygon.io) vs TickerLayer](https://www.anchorterminal.com/compare/massive-vs-tickerlayer.md)\n- [TickerLayer vs Tiingo](https://www.anchorterminal.com/compare/tickerlayer-vs-tiingo.md)\n- [TickerLayer vs Twelve Data](https://www.anchorterminal.com/compare/tickerlayer-vs-twelve-data.md)\n- [Eulerpool Financial Data API vs TickerLayer](https://www.anchorterminal.com/compare/eulerpool-vs-tickerlayer.md)\n- [Financial Datasets vs TickerLayer](https://www.anchorterminal.com/compare/financial-datasets-vs-tickerlayer.md)\n- [Financial Modeling Prep vs TickerLayer](https://www.anchorterminal.com/compare/financial-modeling-prep-vs-tickerlayer.md)\n- [EODHD vs TickerLayer](https://www.anchorterminal.com/compare/eodhd-vs-tickerlayer.md)\n- [Benzinga vs EODHD](https://www.anchorterminal.com/compare/benzinga-vs-eodhd.md)\n- [Benzinga vs Eulerpool Financial Data API](https://www.anchorterminal.com/compare/benzinga-vs-eulerpool.md)\n- [Benzinga vs Financial Datasets](https://www.anchorterminal.com/compare/benzinga-vs-financial-datasets.md)\n- [Benzinga vs Financial Modeling Prep](https://www.anchorterminal.com/compare/benzinga-vs-financial-modeling-prep.md)\n- [Benzinga vs Finnhub](https://www.anchorterminal.com/compare/benzinga-vs-finnhub.md)\n- [Benzinga vs Intrinio](https://www.anchorterminal.com/compare/benzinga-vs-intrinio.md)\n- [Benzinga vs Tiingo](https://www.anchorterminal.com/compare/benzinga-vs-tiingo.md)\n- [Benzinga vs Twelve Data](https://www.anchorterminal.com/compare/benzinga-vs-twelve-data.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-11", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Benzinga vs TickerLayer", "url": "" } ], "description": "TickerLayer scores 71.5 (BB) to Benzinga's 49.2 (D) for market prices. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Benzinga D 49.2", "TickerLayer BB 71.5", "scores" ], "h1": "Benzinga vs TickerLayer", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/benzinga-vs-tickerlayer", "published": "2026-10-01", "section": "tools", "title": "Benzinga vs TickerLayer for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-11", "url": "https://www.anchorterminal.com/compare/benzinga-vs-tickerlayer" }, "tokens": { "markdown": 5200, "slim": 1280 }, "version": 1 }