# Fix list: ScrapingAnt From Anchor Terminal's listing at https://www.anchorterminal.com/tools/scrapingant, the October 2026 research run, assessed 1 October 2026. Grade F, 35.9 out of 100. This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public. For a coding agent working on ScrapingAnt: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published. ## 1. Security & auth, 10 out of 100, up to 15.8 more on the total Why it scored 10: One account API key with no scopes, and we found no documented rotation or revocation (10). API Basics tells you to send x-api-key as a query parameter, a documented option, so less 10 (0 of 30). The header form works and the SDKs use it. No read-only mode, and /v2/general can send POST, PUT and DELETE to target sites with no confirmation step (5 of 20). No prompt-injection guidance found for the HTML, Markdown or text it returns (0 of 15). The Ant-credits-cost header and a subscription status endpoint show spend per call. No request log found (5 of 15). No security.txt, disclosure policy, bug bounty or certification found (0 of 20). The checklist (https://www.anchorterminal.com/benchmark/#checklist-security): - 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option. - 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions. - 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10. - 0 to 15, audit logs or per-call visibility for the operator. - 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public. Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing. ## 2. Reliability, 30 out of 100, up to 14 more on the total Why it scored 30: No status page linked from the site or docs (0). No readable incident history (5). The free plan allows 1 concurrent request and paid plans have no concurrency cap, with timeout settable from 5 to 60 seconds. No per-minute limits published (8 of 15). The errors page documents 409 for the concurrency limit and 423 for anti-bot detection with advice to retry or change settings. No 429, Retry-After or backoff guidance (7 of 15). No SLA found (0). The API is generally available (10). The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability): Hosted APIs, MCP servers, models and platforms. - 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own). - 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so. - 15, rate limits documented with numbers. - 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved. - 10, an SLA published for any paid tier. - 10, the surface agents use is generally available, not beta or preview. Local packages, SDKs, frameworks and stdio MCP servers. - 20, installs from an official package with supported runtimes stated. - 25, a public CI and test suite, passing on the default branch. - 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered). - 15, semver discipline and breaking changes called out in a changelog. - 15, version 1.0 or later, or declared stable. Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors. ## 3. Schema & documentation, 43 out of 100, up to 9.3 more on the total Why it scored 43: No OpenAPI or Swagger spec found. The MCP docs give a typed parameter table for the 3 tools (8 of 25). docs.scrapingant.com/llms.txt returns 404 and no Markdown twins were found (0). MCP descriptions are one line each, such as Fetch a URL and return raw HTML content, with no when-to-use guidance (8 of 20). Few parameters, typed, with proxy_type as an enum of `datacenter` or `residential` (10 of 15). Request examples on every docs page and an errors page with 8 status codes and their meanings (12 of 15). Versioned paths (v1 and v2) and no changelog (5 of 15). The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema): APIs and MCP servers. - 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool). - 10, llms.txt or Markdown docs served for agents. - 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference. - 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs. - 0 to 15, examples and documented error responses. - 15, versioning and a public changelog. Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference. ## 4. Maintenance & community, 5 out of 100, up to 8.3 more on the total Why it scored 5: No changelog or dated API change found, and the newest SDK release is Python 2.1.0 on 2024-07-16 (0). No releases in the last 90 days (0). No public changelog. Support by email (3 of 15). The JavaScript client was last released 2022-05-06, the MCP server isn't in the official registry, and the only registry entry is a third-party wrapper (0). The Python client has a code-check workflow, but neither SDK has moved in over two years (2 of 10). The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance): - 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older. - 20, at least three releases or dated changelog entries in the last 90 days. - 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15. - 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models). - 10, package health, current dependencies and CI. Models are read for deprecation notice periods and model churn rather than release counts. ## 5. Payments & pricing, 40 out of 100, up to 7.5 more on the total Why it scored 40: No x402, MPP or L402 (0). Credit costs per request type (1 to 125) and plan prices are public (20). 10,000 free credits a month, no card (20). A person signs up in a browser (0). The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments): The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/). - 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which. - 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login. - 20, a free tier or trial that doesn't need a card. - 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API). Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied. Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol. ## 6. Agent ergonomics, 66 out of 100, up to 5.5 more on the total Why it scored 66: 3 compact MCP tools (25). Markdown and text endpoints, AI extraction, wait-for-selector and a JSON extended response, but no output-size limit on the MCP tools (12 of 20). 8 documented status codes, and 422 returns a detail field (14 of 20). Requests are reads of third-party pages and failures aren't billed, but there are no tool annotations or retry guidance beyond 423 (5 of 20). Only url is required, though browser defaults to true at 10 credits. Python and JavaScript clients exist but are stale (10 of 15). The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics): - 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries). - 20, pagination, filtering and output-size controls. - 20, actionable, documented error responses, codes and messages an agent can recover from. - 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations. - 15, sensible defaults, few required parameters, and official SDKs in at least two languages. Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs. ## 7. Transparency & trust, 57 out of 100, up to 3.8 more on the total Made of editorial 48, provenance 66. Why it scored 57: Closed service with terms naming DATAANT SP. Z O.O., registered in Poland (KRS 0000848755). The SDKs are Apache 2.0 (15 of 30). The privacy policy, last updated 3 November 2020, gives 12-month retention after an account closes, names processors and mentions DPAs with clients. It predates the MCP server and AI extractor, and doesn't say whether scraped content is stored (18 of 30). No deprecation policy or dated notices found (0). Processors and locations named, Sendgrid in Ireland, Paddle in the UK, Google Analytics and Amazon hosting in the USA (15 of 20). The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency): - 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms. - 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors). - 0 to 20, a deprecation policy or notices with dates. - 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted). The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two. Provenance checks not met in full (half of this category, computed from checked facts): - Domain age: scrapingant.com, registered 2020-03-31 (6 years) (11 of 15) - Status page: not found (0 of 10) - Changelog: not found (0 of 10) - security.txt: not found (0 of 10) ## What we couldn't check What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it. - unchecked: whether api.scrapingant.com serves an OpenAPI document. Our reader was blocked from the API domain - Whether API keys can be rotated or revoked from the dashboard. Not found in the docs - When the hosted MCP server launched and whether it's versioned - Whether ScrapingAnt stores the content of scraped pages, and for how long ## Weaknesses - API Basics puts the key in the query string, so it lands in logs - No status page, changelog, security.txt, llms.txt or OpenAPI spec - SDKs are stale. JavaScript last released 2022-05-06, Python 2024-07-16 - No prompt-injection guidance for the pages it returns - Privacy policy last updated 3 November 2020 ## What costs an agent a turn today The notes we give agents before they call it. Each one is a workaround an agent shouldn't need. - Send the key in the `x-api-key` header rather than the query string - Use `/v2/markdown` for LLM input, and set `browser=false` on static pages to pay 1 credit instead of 10 - Switch to `proxy_type=residential` only after a 423 (anti-bot) response. It raises a browser request from 10 to 125 credits - On the free plan a second concurrent request gets 409. Wait for the first to finish - Google, Bing and Yandex result pages come back as raw HTML through `/v2/general`, so you parse them yourself ## What the review panel asked for - default to the 1-credit request - an output size limit - llms.txt ## When it's done Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.