The scorecards
Reports
One report per product. A fixed five-task battery, a fixed three-model panel, and a verified receipt behind every quote.
Category
Showing 93 of 93 reports.
Recover from a 429 landed PARTIAL: A complete 429 remedy exists only for LLM Gateway; on the transcription side the error table lists 429 with no fix while the rate-limits page states the HTTP ceiling returns 403, so a 429 on /v2/transcript has no documented cause or correction.
Find the exact limits landed PARTIAL: Rate limits are exact, but the Organizations guide scopes 50 MROs to development while pricing states 100 per application.
Find the exact limits landed PARTIAL: Service, warehouse, organization, and API rate limits are all stated with exact numbers, but a knowledge-base page gives 100000 parts per service where the usage-limits and cloud-compatibility pages both give 10k.
Find the exact limits landed PARTIAL: The plan tables give per-region caps, but they state 50 pre-recorded requests where the pre-recorded guide states 100.
Recover from a 429 landed PARTIAL: The headers provide a limit number and retry timing, but they do not identify the triggering scope or request bucket.
Find the exact limits landed SPLIT: The docs omit purchase thresholds and exact per-endpoint quotas, while the FAQ says excess requests queue but the concurrency guide documents raw-HTTP 429s.
Recover from a RATELIMITED error landed PARTIAL: The page shows separate limit headers, but it does not map a generic error to one limiter or state a complete retry procedure.
Find the exact limits landed PASS: All quotas and rate limits documented on a single page with consistent values across concurrency, API, LLM, STT, TTS, and observability categories.
Use the Python SDK landed PARTIAL: The generated reference states the two input options but leaves the upload step to a separate page.
Find the exact limits landed FAIL: The platform API says rate limits are unpublished, while the environments page says the environment allowance depends on the plan without stating a number.
Find the exact limits landed PARTIAL: One exact global number is stated in a single sentence on a page titled for status codes, but no plan quotas, per-endpoint limits, or dedicated rate-limit page exist, and the OpenAPI spec and the API reference pages never mention the limit at all.
Find the exact limits landed PARTIAL: API and pricing values agree, but the organization-wide cap and Data burst sizes remain unquantified.
Find the exact limits landed PARTIAL: Numeric API ceilings are clear, but scope is undefined and plan quotas differ between credit-based and legacy accounts.
Find the exact limits landed PARTIAL: The page gives exact per-connection and listed size limits, but omits numeric shared-workspace and child-depth limits.
Find the exact limits landed PARTIAL: The page omits numeric Router limits, and the FAQ contradicts its API-specific tier and limiter rules.
Find the exact limits landed PARTIAL: The guide names all six headers and directs readers to environment-specific values, but its 300 default conflicts with the API reference’s 3003 example.
Find the exact limits landed PARTIAL: Plaid lists Sandbox and Production defaults by Item and client, and Billing states a 10-Item Trial quota, but the table disclaims completeness and customer uniformity.
Find the exact limits landed PARTIAL: The numeric rate and pricing tables agree, but the linked monthly query allowance has no amount or matching section on the query page.
Find the exact limits landed PARTIAL: The values require overview, pricing, and endpoint pages, and the per-user scope conflicts with support's public-IP explanation.
Find the exact limits landed FAIL: The API page gives headers but no numeric endpoint limits; pricing gives paid baselines but omits the Developer plan quota.
Verify a webhook landed PARTIAL: Creation and the INSERT payload shape are documented, but no page states how a delivery is authenticated: there is no signing secret, signature header, or verification procedure, and the Dashboard steps stop at selecting events without reaching the URL or headers fields.
Find the exact limits landed PARTIAL: The docs retire plan tiers and describe dynamic factors, but one page promises limit headers on every request while another says successful responses omit them.
Find the exact limits landed PARTIAL: The rate-limit table gives plan values and scopes, but the general table says Enterprise deployments per day are Custom rather than 24000.
Find the exact limits landed PARTIAL: General (6,000 requests per 60 seconds per API key) and AuthKit (1,000 reads and 500 writes per 10 seconds per environment) are exact and scoped, but the default email provider's sending limits are stated only qualitatively, with no number an agent can plan against.
Recover from error 42910 landed PARTIAL: The page gives complete recovery guidance; an older FAQ contradicts its scope, and a legacy markdown URL returned 404.
Find the exact limits landed PARTIAL: The pages define every requested rule, but possible extra subscription usage has no formula or exact ceiling.
Use the Python SDK landed PARTIAL: The SDK lacks runnable Python deployment code, and two Qwen deployment guides require different builder GPU counts.
Find the exact limits landed PARTIAL: Resource, cache, concurrency, and platform limits are exact, but the runner and pricing pages disagree on per-minute savings.
Find the exact limits landed PARTIAL: The $9.99/month price and the per-1M-token reference rates are exact, but the three ClinePass quota windows are defined circularly with no magnitude, and no page in the API reference states a numeric Cline API rate limit.
Find the exact limits landed PARTIAL: The plans page gives 10 trial reviews per hour for Pro+, while the FAQ gives 3 for the default Pro+ trial.
Find the exact limits landed FAIL: The page names all five limit categories but omits a complete per-plan matrix, and the linked dashboard returned only an app shell.
Verify an inference webhook landed PARTIAL: The page documents submission and success or failure payloads, but it gives no callback-authenticity verification method.
Find the exact limits landed PARTIAL: The limits page says 512MB, while the builds reference says 768MB by default and 4GB on Pro.
Find the exact limits landed PARTIAL: The 429 page gives unscoped plan concurrency values, while Models adds doubled Flash limits; two alternative concurrency URLs failed.
Find the exact limits landed PARTIAL: The docs give credits, prices, and Enterprise differences, but rate-limits says 10 QPS while Starter pricing says 5 QPS.
Find the exact limits landed PARTIAL: No page under docs.expo.dev states per-plan MAU, bandwidth, storage, or concurrency counts; the numbers exist only on the marketing site at expo.dev/pricing and its pricing.md mirror.
Recover from a tool error landed PARTIAL: The page documents ToolError and is_error handling, but it gives no corrective retry rule or example.
Find the exact limits landed PARTIAL: Realtime timeout (120s) and parallel ceilings (max_workers default 32, max 1000; worker_concurrency default 1; max_retry default 2) are stated precisely, but the realtime RAM ceiling is given as ~10GB on the realtime and fused-run pages and as ~4GB twice on the scaling-out page, and no plan or account quota carries a number anywhere in the docs.
Find the exact limits landed PARTIAL: Hermes-owned limits are stated exactly but only on the page that owns each subsystem, API server max_concurrent_runs default 10, webhook 30 requests per minute per route, webhook body 1 MB, delegation max_concurrent_children default 3, max_concurrent_sessions null, while no page gives a single numeric model-provider plan quota, so the provider half of the question is answered only by "upgrade your provider plan".
Verify an agent webhook trigger landed PARTIAL: Definition, pushing, verification, and tracking are documented, but signature formatting is missing and invocation endpoints conflict.
Find the exact limits landed PARTIAL: Agent caps and API-plan charges are exact (Free "limited to 3 stateful agents", Pro "Up to 20 stateful agents", API Plan "$20 /month", "$0.10 / active agent / mo", "$0.00015 / sec tool execution"), but no page anywhere states a numeric Letta Auto quota, the FAQ restates the free cap as an unquantified "limited number of total agents", and spending limits are only referenced as an email notification with no documented place to set one.
Configure an access token landed PARTIAL: The guides cover least-privilege scopes, URL rules, 401, and 403, but troubleshooting also recommends all public scopes.
Find the exact limits landed PARTIAL: No request limit appears anywhere under /docs/; the four values are only reachable in one knowledge-base article that also states "While we do not have a specific rate limit" alongside the 5-per-minute free-tier cap and the 100-requests-per-second ceiling, while plan-specific data access lives separately on each endpoint page as "Included in all Stocks plans".
Find the exact limits landed FAIL: No page gives all requested limits by plan; the attempted pricing and rate-limit pages returned no content.
Find the exact limits landed PARTIAL: The three tier values match across HRIS and ATS, but the overview neither lists nor links the 1-request-per-10-seconds async polling exception.
Find the exact rate limits landed PARTIAL: The table gives modality values, but Token Plan throttling is dynamic and most modality tables omit TPM or concurrency.
Use the Python SDK landed PARTIAL: The Python landing page extraction failed, while direct guides supplied the SDK path but disagreed on whether a database name is required.
Find the exact limits landed PARTIAL: The values require Docs, Pricing, and Support, and Pro retention conflicts at 30 days versus 14 days.
Find the exact limits landed PARTIAL: Official pages disagree on Free graph and backup limits, omit exact Free RAM and storage, and differ on paid maxima.
Verify an Auth webhook landed PARTIAL: The reference covers configuration, payloads, and verification, but it never defines NEON_AUTH_URL; the linked walkthrough uses NEON_AUTH_BASE_URL.
Start the first coding session landed PARTIAL: The introduction documents provider connection and project initialization, but prerequisites and setup span multiple sections.
Find the exact limits landed PARTIAL: Task scope and rate-limit zero behavior are documented, but concurrentExecLimit=0 behavior is not stated.
Find the exact limits landed PARTIAL: New and legacy values differ by declared policy, but exact thresholds, shared counters, and 429 handling span four resources.
Find the exact access limits landed PASS: The client page fixes order, formats, and whole-type behavior; the cloud-sources table lists six themes and 15 types.
Find the exact limits landed PARTIAL: Track's hourly and daily values are unstated; fixed plan quotas are absent, and radar.com/pricing.md returned Not Found.
Find the exact limits landed PARTIAL: Create is 120/min/workspace, list is 60/min/workspace, and scheduled concurrency is unlimited, but ad-hoc concurrency is workspace-specific versus 30.
Find the exact data limits landed PARTIAL: Key and memory scopes are clear; element pages differ by one, and the list page exceeded the 5MB fetch limit.
Recover from throttling landed PARTIAL: The rate-limit page maps each 429 body to a fix, but the agent guide incorrectly describes 429 as concurrent-request throttling.
Find the exact limits landed PARTIAL: Public has 15 credits, 10 projects, and 2 members; Core starts at 30 credits, 20 projects, and 3 members, while Hosted API capacity depends on shared credit use.
Find the exact limits landed PARTIAL: The docs give all requested scopes, but sync retention appears as both one minute and up to five minutes.
Find the exact limits landed SPLIT: The page states no hard rate limits and recommends 2-4 requests, but it gives no numeric queue capacity.
Verify a transcription notification landed PARTIAL: The page covers configuration, authentication, allowlists, 2xx acknowledgement, ordering, and failures, but gives no retry timeout value.
Find the exact limits landed PARTIAL: Both limit pages agree on Connect 10,000, Send Message 1,000, and 60 user requests per endpoint and platform.
Find the exact limits landed PARTIAL: The page supplies both quotas and identifiers, but its second-to-day intervals conflict with its universal “top of the hour” rule.
Find the exact limits landed PARTIAL: HTTP limits agree, but Free memory conflicts: 512 MB in instance docs versus 1 GB on pricing.
Find the exact limits landed PASS: Rate Limits covers every requested scope, while Credits & Pricing covers all plan quotas and endpoint costs without conflicts.
Find the exact limits landed FAIL: It documents $100 for six months but omits storage rates and API quotas; the pricing link shows deployment pricing.
Find the exact limits landed PARTIAL: The values are 250 per IP per region and 20, 100, and 200 per workspace, but pricing says all limits are organization-wide.
Find the exact limits landed PARTIAL: The limits page covers every category, but Triggering conflicts on payload and output caps.
Find the exact limits landed PARTIAL: The docs define six units, first-match order, and monthly plan quotas, but state no numeric default limit when no custom rule exists.
Verify a workflow webhook landed PARTIAL: The sender is documented, but receiver token checking appears only in a separate webhook app example with different semantics.
Transform a document landed PARTIAL: The quickstart gives a complete flow, but the create-job reference appends /api/v1 to a variable that already ends with /api/v1.
Verify a server event landed SPLIT: The docs configure HMAC credentials but never define signed bytes, signature encoding, timestamp handling, or receiver verification code.
Find the exact limits landed FAIL: The trial page states one credit allocation but sends paid-plan details to a marketing pricing page; no exact paid quotas appear in the docs.
Find the exact limits landed PARTIAL: Plan values are findable, but two pages disagree on whether auto-reload fires at or below 100 credits.
Find the exact limits landed PARTIAL: The account window is one minute; Flex lists 600 RPM and Flex Plus 1,000, while Free, Flex under load, and Enterprise vary.
Find the exact limits landed PARTIAL: The docs give collection, partition, and insert limits but omit Free DDL and conflict on load rates; /docs/limits-and-restrictions did not load.
Find the exact limits landed PARTIAL: The limits page lists all numbers, but /platform/next/ returned 404 and the workspace page excludes Plus.
Find the exact limits landed FAIL: The docs mention shared provider limits but give no exact API or plan numbers, and llms-full.txt returned 404.
Find the exact limits landed PARTIAL: The docs give matching per-IP ceilings and annual API weights, but they publish only a 35-300 monthly M2M range and no numeric API Access Token entitlement by plan.
Use the Python SDK landed PARTIAL: The Python SDK reference executes composio.tools.execute() without the required version or opt-in flag, while the agent quickstart uses current sessions.
Verify a log webhook landed PARTIAL: The page documents setup and events, but its verifier parses the request before reading the bytes that it verifies.
Find the exact limits landed PARTIAL: The limits page publishes tier resource pools and three per-minute request columns; the agents reduced the task because resource numbers differ across live pages.
Find the exact limits landed PARTIAL: Defaults are 80% RAM, 1000, and 4 GB; temporary storage conflicts as unlimited versus 90% free disk.
Recover from a 429 landed FAIL: The reference names the cause but provides no retry timing, response-header guidance, backoff, or limit-remediation steps.
Find the exact limits landed SPLIT: The guide states 300 requests per minute per IP, but gives no numeric plan threshold and references 429 inconsistently.
Verify a crawl webhook landed PARTIAL: The configuration, payload, and HMAC steps are complete, but Overview omits failed from Crawl while the Crawl page lists crawl.failed.
Find the exact limits landed PARTIAL: The LangSmith tracing path documents exact endpoint limits, plan-tier event limits, data-ingest limits, and monthly trace quotas with scopes and windows.
Find the exact limits landed PARTIAL: Both tables are findable, but the API page defines X-RateLimit-Limit as daily beside hourly limits.
A perfect agent surface and a clean quickstart, but the free plan allows either one or three concurrent sessions depending on the page.
Strong quickstart, one concrete rate-limit number in 144 pages, and it lives under Metrics.
Ships .md mirrors, llms.txt, and an MCP server, and its two webhook pages name the same parameter two different ways.
The docs give instructions to the reading agent itself, and the classic quickstart path graded PARTIAL partly because of it.
Subscribe by RSS (opens in a new tab) or nominate a docs site. Every score in one table.