{ "data": { "a": { "slug": "nexscope", "name": "Nexscope", "vendor": "ECOCREATE TECHNOLOGY PTE. LTD.", "vendorUrl": "https://www.nexscope.ai", "kind": "platform", "category": "web-scrapers", "summary": "Nexscope is a hosted platform for ecommerce sellers with marketplace product, keyword and competitor data for Amazon, TikTok Shop, Walmart, Temu, 1688 and others, plus AI product images and video, through a web app, REST API and remote MCP server.", "url": "https://www.anchorterminal.com/tools/nexscope", "markdownUrl": "https://www.anchorterminal.com/tools/nexscope.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/nexscope.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/nexscope.json", "dns": "nexscope.grade.anchorterminal.com", "repo": "https://github.com/nexscope-ai/nexscope-ecommerce-api", "license": "Proprietary hosted service under the Nexscope terms (last updated 8 October 2026), whose contracting party is ECOCREATE TECHNOLOGY PTE. LTD. of Singapore. The OpenAPI file's licence is 'Proprietary API; use subject to Nexscope Terms'. In github.com/nexscope-ai/nexscope-ecommerce-api only the example clients, validation scripts, tests and workflow are MIT. The API documentation, catalogue, definitions and sample data stay copyright Nexscope", "transports": [ "streamable-http", "http" ], "remoteUrl": "https://api.nexscope.ai/mcp", "packages": [], "auth": "mixed", "authNotes": "The remote MCP server takes OAuth 2.1 (authorisation code with PKCE, scope `mcp:tools`) in clients that support it, or a Nexscope API key as `Authorization: Bearer nk-...`, which the tool pages call a compatibility option. The REST API takes the same key as a Bearer header. A person signs in and creates the key under API Access, API Keys. The full key is shown once, and keys can be expired, disabled or deleted, per the help page's troubleshooting. No key scopes, rotation rule or key-management API were found. Creative API key access needs an active subscription. Trial credits don't enable it. The OAuth metadata on api.nexscope.ai was not read (https://www.nexscope.ai/mcp-map/amazon-search, https://www.nexscope.ai/help/skills-external-access, https://github.com/nexscope-ai/nexscope-ecommerce-api, checked 2026-11-10).", "pricing": "paid", "pricingNotes": "Credits on a monthly subscription. A Free Trial gives 1,000 credits for 3 days with no card, at 1 API and 1 MCP request a second and 1 concurrent each, with no video API. Starter is $29 a month for 30,000 credits (3 requests a second, 2 concurrent), Growth $55 for 75,000 (5 and 4) and Pro $129 for 150,000 (10 and 8), each half price for the first period, with yearly billing and credits that reset monthly and don't roll over. Pay-as-you-go top-ups buy Data credits only, with no subscription. Each tool has its own credit cost, at least 10 for a Data API call. Amazon Search shows 'from 21 credits per call' and a recent average of 30. Refunds within 7 days if unused, per the terms. The home page listed Growth at $69 on the same day (https://www.nexscope.ai/pricing, https://www.nexscope.ai/mcp-map, https://www.nexscope.ai/terms, checked 2026-11-10).", "priceSummary": "$0.001 / credit", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the pricing page, the API quickstart, the MCP map, llms.txt, the visible part of the OpenAPI file or the GitHub repository on 2026-11-10. Credits come from a subscription or a Data top-up after a browser sign-in (https://www.nexscope.ai/pricing).", "endpoints": [] }, "toolCount": 382, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-10" }, "docsUrl": "https://www.nexscope.ai/api-docs", "llmsTxt": "https://www.nexscope.ai/llms.txt", "openapi": "https://api.nexscope.ai/openapi.json", "registryName": "io.github.nexscope/ecommerce", "capabilities": [ "web.extract", "shopping.search", "shopping.prices", "seo.keywords", "seo.backlinks", "search.serp", "image.generate", "image.edit", "video.generate", "video.image-to-video" ], "tags": [ "hosted", "official", "closed-source", "mcp", "remote-mcp", "oauth", "api-key", "openapi", "llms-txt", "marketplace", "shopping", "images", "video", "credits", "subscription", "free-trial", "no-card", "new" ], "lastRelease": "2026-11-09", "graded": true, "anchor": { "graded": true, "score": 46.2, "grade": "D", "agentReady": false, "rank": 1191, "ranked": true, "rankOf": 1520, "categoryRank": 28, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 44, "maintenance": 65, "payments": 35, "reliability": 39, "schema": 64, "security": 41, "transparency": 41 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-10" }, "negative": 0, "verdict": "An agent can reach Amazon, TikTok Shop, Temu, 1688 and other marketplace data, plus image and video models, on one credit balance through a remote MCP server with OAuth or a REST API with a public OpenAPI file. The connection loads 382 tools at once, and there is no status page, changelog or idempotency key.", "bestFor": "Agents that research ecommerce products, competitors, keywords, sourcing and patents across Amazon, TikTok Shop, Walmart, Temu, 1688 and other marketplaces, and that also make listing images and video, on one credit balance.", "strengths": [ "Marketplace product, keyword, competitor and sourcing data across more than ten marketplaces behind one key and one MCP endpoint", "OAuth 2.1 with PKCE and a `mcp:tools` scope on the MCP server, or a Bearer key shown once", "A public OpenAPI 3.1 file and a GitHub repository with request and response definitions, samples and standard-library clients for every documented API", "Per-plan API and MCP request limits published, and a 3-day trial of 1,000 credits with no card", "1688 order, payment-link, receipt and cancel calls each need an explicit JSON `true` confirmation field" ], "weaknesses": [ "The MCP connection advertises the full catalogue of 382 tools, with no toolsets or read-only subset", "No status page, SLA, public changelog or security.txt found", "No idempotency keys, and business errors answer HTTP 200 unless a header asks otherwise", "The privacy policy states no retention periods and names no hosting, AI or data suppliers", "Many Data definitions are field descriptors rather than JSON Schema, and the Amazon Search tool page omits the `keyword` argument its own examples pass" ], "agentNotes": [ "Check the outer `code` is 0 before reading `data`, or send `X-Nexscope-Http-Status: semantic` to get HTTP error statuses.", "Call an image or video tool once, keep the `taskId`, and poll `nexscope_media_task_result`. A second call bills a second job.", "Read the tool's credit cost before a call. Each tool costs at least 10 credits and some cost over 300.", "Before you set a 1688 confirmation field to `true`, show the user the preview and get approval.", "If the server returns 429 or 503, wait for `Retry-After` when present and back off." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 46.2 } ], "editorialScores": { "ergonomics": 44, "maintenance": 65, "payments": 35, "reliability": 39, "schema": 64, "security": 41, "transparency": 33 }, "provenanceScore": 48, "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": { "http": "curl --fail-with-body -X POST 'https://api.nexscope.ai/api/skill-api/v1/skills/amazon-search/run' \\\n -H \"Authorization: Bearer $NEXSCOPE_API_KEY\" \\\n -H 'Content-Type: application/json' \\\n -H 'X-Nexscope-Http-Status: semantic' \\\n -d '{\"keyword\":\"phone case\",\"page\":1}'", "config": { "mcpServers": { "nexscope": { "headers": { "Authorization": "Bearer YOUR_NEXSCOPE_API_KEY" }, "type": "streamableHttp", "url": "https://api.nexscope.ai/mcp" } } } }, "letme": { "capability": "https://letme.dev/web.extract", "tool": "https://letme.dev/nexscope" }, "area": "web-data", "unitPrices": [ { "item": "Nexscope credit (Starter)", "unit": "credit", "usd": 0.00097, "note": "$29 a month for 30,000 credits, half price in the first month. Credits reset monthly" }, { "item": "Nexscope credit (Pro)", "unit": "credit", "usd": 0.00086, "note": "$129 a month for 150,000 credits" }, { "item": "Amazon Search tool call (Starter)", "unit": "call", "usd": 0.029, "note": "A recent average of 30 credits, range 16 to 94, per the MCP tool page on 10 November 2026. About 20 results a page" }, { "item": "Starter plan", "unit": "month", "usd": 29, "note": "30,000 credits, 3 API and 3 MCP requests a second, 2 concurrent each" } ], "provenance": { "legalEntity": "ECOCREATE TECHNOLOGY PTE. LTD.", "domain": "nexscope.ai", "domainRegistered": "2026-03-04", "domainNote": "RDAP (Identity Digital) gives nexscope.ai a registration date of 4 March 2026 through GoDaddy, with the registrant behind Domains By Proxy. The terms and privacy policy name ECOCREATE TECHNOLOGY PTE. LTD., 'a company incorporated in Singapore', with no registration number or street address.", "endpointOnVendorDomain": true, "terms": "https://www.nexscope.ai/terms", "privacy": "https://www.nexscope.ai/privacy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-10", "notes": [ "The terms (last updated 8 October 2026) name ECOCREATE TECHNOLOGY PTE. LTD. under the laws of Singapore with SIAC arbitration seated in Singapore, cap liability at the amount paid in the six months before a claim, promise no availability, permit the official APIs and MCP integrations within plan limits, forbid bots and scrapers outside them, and give notice of material changes through the service or by email.", "The privacy policy (last updated 8 October 2026) names the same company, says uploaded materials are not used to train AI models, names Google Analytics, Microsoft Clarity, Ahrefs Analytics, Google Ads, X advertising and FirstPromoter, lists hosting, storage, AI processing, payment, email, support and authentication providers only by type, gives no retention periods ('this policy does not specify a single deletion deadline for all data') and mentions no DPA.", "https://www.nexscope.ai/.well-known/security.txt answered a client error. No status page or changelog is linked from the home page, llms.txt, the API quickstart or the MCP map.", "robots.txt on www.nexscope.ai gives `*` and twelve named crawlers, ClaudeBot among them, the same rules and disallows /api/ and /share/. Nothing there was fetched. api.nexscope.ai publishes no robots.txt (/robots.txt answers a JSON login error). Only /openapi.json and one GET to /mcp were sent there, per the batch. The MCP registry's /robots.txt answered a client error.", "firstReleased is 2026-08-07, the date on Nexscope's launch post ('Updated Aug 07, 2026', no earlier publication date shown), which names API, MCP and Skills as the ways to connect an agent and 1,000 free starting credits. The API repository dates its snapshot of an already public directory of 225 APIs to 10 September 2026, and the OpenAPI version label is 2026-08-28-public-catalog-v1. The domain dates from 4 March 2026 and the npm `nexscope` skills CLI from 20 March 2026, but neither reaches the API. lastRelease is 2026-11-09, when the 1688 procurement API contracts were synced as released." ], "score": 48 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/nexscope.json", "live": { "slug": "nexscope", "probe": { "target": "https://api.nexscope.ai/mcp", "method": "get", "lastAt": "2026-11-11T06:59:50.048088824Z", "lastOk": true, "lastStatus": 405, "lastMs": 305, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 271, "p95ms24h": 358, "samples24h": 43, "samples30d": 43, "days": [ { "date": "2026-11-11", "probes": 43, "ok": 43 } ], "since": "2026-11-11T02:53:20.057234625Z" }, "githubStars": 18, "updatedAt": "2026-11-11T06:59:50.048088824Z" }, "streak": { "days": 0, "from": "2026-11-11", "sinceWatching": true, "best": 0 } }, "answer": "Scrapewise scores 60 (C) on agent readiness against Nexscope's 46.2 (D), and leads in every scored category.", "b": { "slug": "scrapewise", "name": "Scrapewise", "vendor": "BEBOTECH OÜ", "vendorUrl": "https://scrapewise.ai", "kind": "http-api", "category": "web-scrapers", "summary": "Scrapewise is a hosted scraping service from BEBOTECH OÜ for product and price data. It has ready APIs for Amazon, Walmart and Google, AI scrapers for other sites, price cleaning and product matching, through REST and a remote MCP server.", "url": "https://www.anchorterminal.com/tools/scrapewise", "markdownUrl": "https://www.anchorterminal.com/tools/scrapewise.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/scrapewise.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/scrapewise.json", "dns": "scrapewise.grade.anchorterminal.com", "repo": "https://github.com/BEBOTECH-OU/scrapewise-mcp", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.scrapewise.ai/mcp", "packages": [ { "registry": "pypi", "name": "scrapewise" }, { "registry": "pypi", "name": "langchain-scrapewise" } ], "auth": "api-key", "authNotes": "Bearer API key (`sw_live_\u003cprefix\u003e.\u003csecret\u003e`) minted in the portal under Settings \u003e API Keys after a browser signup. Scopes are fixed at minting. USER keys reach the REST API only, LLM_READ keys read through MCP, LLM_FULL keys also run paid tools and change or delete data. Secrets are stored as hashes, revoked at once, and rotated by minting a new key and revoking the old. No expiry found.", "pricing": "usage", "pricingNotes": "€0.15 per 1,000 plain pages, prepaid from a euro wallet with no plan or subscription. Rendered pages €0.75, residential proxy €1.50, both €3.75 per 1,000. Data APIs €0.15 to €3.75 per 1,000 calls. MCP credits are €0.00015 each. Five free requests, no card. Top-ups €5 to €1,000, not refunded.", "priceSummary": "$0.17 / 1k pages", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the docs, OpenAPI specs, llms.txt or pricing.md (checked 2026-10-15). An empty wallet returns 402 with WALLET_INSUFFICIENT_BALANCE and no payment requirements; top-ups go through Stripe Checkout in a browser.", "endpoints": [] }, "toolCount": 113, "popularity": { "githubStars": 1, "npmWeekly": null, "pypiWeekly": 30, "asOf": "2026-10-15" }, "docsUrl": "https://docs.scrapewise.ai/", "llmsTxt": "https://scrapewise.ai/llms.txt", "openapi": "https://portal.scrapewise.ai/api/scraper-api/v3/api-docs", "registryName": "ai.scrapewise/scrapewise", "capabilities": [ "web.scrape", "web.extract", "scraping.js-render", "scraping.proxies", "web.crawl", "web.fetch", "web.search", "search.serp", "lead.search" ], "tags": [ "hosted", "usage", "prepaid", "no-card", "free-tier", "mcp", "remote-mcp", "mcp-registry", "llms-txt", "openapi", "proxies", "python", "eu" ], "lastRelease": "2026-10-23", "graded": true, "anchor": { "graded": true, "score": 60, "grade": "C", "agentReady": false, "rank": 676, "ranked": true, "rankOf": 1520, "categoryRank": 19, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 79, "payments": 40, "reliability": 45, "schema": 79, "security": 56, "transparency": 54 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-02" }, "negative": 0, "verdict": "Paid MCP tools each take a free `quote_only` price check and idempotency keys, keys are read-only or full-access, and euro prices start at €0.15 per 1,000 plain pages. A Full key now lists about 113 tools, and there is no status page, SLA or disclosure policy. The terms claim ownership of all scraped data.", "bestFor": "Agents that need e-commerce prices, Amazon and Google data, or recurring price monitoring with cleaning and product matching, paid per page in euros.", "strengths": [ "Every paid MCP tool takes `quote_only: true`, which returns the maximum price and wallet balance without spending, and each result reports its cost", "Separate key scopes (USER for REST, LLM_READ and LLM_FULL for MCP), hashed, revocable and listed with last-used time", "Public OpenAPI 3.1 at /v3/api-docs with an MCP subset, plus llms.txt, agents.md and pricing.md", "Prices per 1,000 pages published without login (€0.15 plain to €3.75 rendered with residential proxy), failed pages not charged, 5 free requests with no card", "Verified namespace `ai.scrapewise/scrapewise` in the official MCP registry since 6 October 2026" ], "weaknesses": [ "No status page, SLA, security.txt, disclosure policy or certification found", "Terms of 29 October 2025 say all collected and derived data is owned by Scrapewise, with a perpetual, sublicensable licence", "A Full key lists every tool, 113 in the catalogue, since 22 October 2026, with no toolset to narrow it", "Signup and every wallet top-up (Stripe Checkout, €5 to €1,000) need a person in a browser, and there is no machine payment protocol", "The prompt-injection contract relies on a `type: \"scraped\"` content block that the MCP specification does not define" ], "agentNotes": [ "Call each paid tool with `quote_only: true` first, then repeat with the same `idempotency_key` so a retry is charged once", "Expect about 113 tools from a Full key; use a Read key, which lists 48 read tools, when the task only reads saved rows or job results", "Use an LLM_READ key unless the task needs paid tools or writes, since LLM_FULL has no per-tool consent", "Treat 402 WALLET_INSUFFICIENT_BALANCE as final and ask the user to top up; on 429 wait for Retry-After, on 429 cost_exceeded wait for the next hour, and stop a run before deleting its scraper (409 SCRAPER_RUN_ACTIVE)", "Scrape many addresses with one `scrapewise_run_scraper_url_list` call (up to 5,000) and retry with the same name, never one scraper per address" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 60 } ], "editorialScores": { "ergonomics": 72, "maintenance": 79, "payments": 40, "reliability": 45, "schema": 79, "security": 56, "transparency": 38 }, "provenanceScore": 69, "checked": { "categories": { "ergonomics": "2026-11-02", "maintenance": "2026-11-02", "payments": "2026-11-02", "reliability": "2026-11-02", "schema": "2026-11-02", "security": "2026-11-02", "transparency": "2026-11-02" }, "last": "2026-11-02", "lastMoved": "2026-11-02", "oldest": "2026-11-02", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install scrapewise", "http": "curl -H \"Authorization: Bearer $SCRAPEWISE_KEY\" https://portal.scrapewise.ai/api/scraper-api/api/key/whoami", "claudeCode": "claude mcp add scrapewise --transport http https://mcp.scrapewise.ai/mcp --header 'Authorization: Bearer YOUR_SCRAPEWISE_API_KEY'", "config": { "mcpServers": { "scrapewise": { "headers": { "Authorization": "Bearer YOUR_SCRAPEWISE_API_KEY" }, "url": "https://mcp.scrapewise.ai/mcp" } } } }, "letme": { "capability": "https://letme.dev/web.scrape", "tool": "https://letme.dev/scrapewise" }, "area": "web-data", "unitPrices": [ { "item": "Plain page", "unit": "1k-pages", "usd": 0.17, "note": "€0.15, converted at the ECB rate of 15 October 2026 (1.1208)" }, { "item": "Rendered page", "unit": "1k-pages", "usd": 0.84, "note": "€0.75" }, { "item": "Residential proxy page", "unit": "1k-pages", "usd": 1.68, "note": "€1.50" }, { "item": "Rendered page with residential proxy", "unit": "1k-pages", "usd": 4.2, "note": "€3.75" }, { "item": "Google search", "unit": "1k-requests", "usd": 1.68, "note": "€1.50" }, { "item": "MCP credit", "unit": "credit", "usd": 0.000168, "note": "€0.00015, the price of one plain page" } ], "provenance": { "legalEntity": "BEBOTECH OÜ", "domain": "scrapewise.ai", "domainRegistered": "2025-05-19", "endpointOnVendorDomain": true, "terms": "https://scrapewise.ai/terms-of-service", "privacy": "https://scrapewise.ai/privacy-policy", "statusPage": "", "changelog": "https://docs.scrapewise.ai/changelog", "securityTxt": "none", "checked": "2026-10-15", "notes": [ "BEBOTECH OÜ is named as author in the PyPI metadata of scrapewise and langchain-scrapewise and in the scrapewise-python licence. The terms and privacy policy name only Scrapewise.ai, under Estonian law.", "Terms of service and privacy policy are both effective 29 October 2025. The terms contain no clause on automated access to the website.", "scrapewise.ai/robots.txt allows all crawlers and names ClaudeBot and anthropic-ai as allowed. docs.scrapewise.ai/robots.txt allows all.", "RDAP gives scrapewise.ai a registration date of 19 May 2025.", "/.well-known/security.txt and /security.txt return 404. No status page found." ], "score": 69 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/scrapewise.json", "live": { "slug": "scrapewise", "probe": { "target": "https://mcp.scrapewise.ai/mcp", "method": "get", "lastAt": "2026-11-11T06:59:59.708128288Z", "lastOk": true, "lastStatus": 401, "lastMs": 197, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 99.98, "p50ms24h": 175, "p95ms24h": 253, "samples24h": 244, "samples30d": 6386, "days": [ { "date": "2026-10-16", "probes": 151, "ok": 151 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 243, "ok": 242 }, { "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-10-16T00:00:00Z" }, "versions": [ { "registry": "mcp-registry", "name": "ai.scrapewise/scrapewise", "version": "0.1.3", "seenAt": "2026-11-10T19:22:02.357354042Z" }, { "registry": "pypi", "name": "langchain-scrapewise", "version": "0.1.0", "released": "2026-10-07", "seenAt": "2026-11-11T06:34:13.146545209Z" }, { "registry": "pypi", "name": "scrapewise", "version": "0.1.0", "released": "2026-10-07", "seenAt": "2026-11-11T06:34:12.933615727Z" } ], "githubStars": 1, "pypiWeekly": 5, "securityTxt": { "url": "https://scrapewise.ai/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-10T16:08:20.055172619Z" }, "llmsTxt": { "url": "https://scrapewise.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-10T15:44:33.401368619Z" }, "domain": { "domain": "scrapewise.ai", "registered": "2025-05-19", "source": "https://rdap.identitydigital.services/rdap/domain/scrapewise.ai", "checkedAt": "2026-11-08T15:04:20.63065253Z" }, "pages": [ { "url": "https://docs.scrapewise.ai/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-10T16:18:33.70315083Z", "changedAt": "2026-11-05T12:31:39.937978708Z", "fingerprint": "b3e50c597462" }, { "url": "https://scrapewise.ai/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-10T16:30:26.962028033Z", "changedAt": "2026-11-10T16:30:26.962028033Z", "fingerprint": "03b599d3009f" }, { "url": "https://scrapewise.ai/terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-11-10T16:30:29.252591902Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e020071fdbd3" } ], "mcpTools": { "url": "https://mcp.scrapewise.ai/mcp", "checkedAt": "2026-11-11T02:44:27.859768722Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-07T21:27:38.119254487Z" }, "github": { "repo": "bebotech-ou/scrapewise-mcp", "checkedAt": "2026-11-09T10:10:54.82288466Z", "stars": 1, "archived": false, "issuesEnabled": true, "pushedAt": "2026-10-13T07:52:25Z", "openIssues": 2, "openPRs": 0, "issuesOpened90d": 2, "issuesClosed90d": 0, "prsMerged90d": 2, "replies": { "sampled": 2, "unanswered": 2 } }, "updatedAt": "2026-11-11T06:59:59.708128288Z" }, "streak": { "days": 26, "from": "2026-10-16", "sinceWatching": true, "best": 26 } }, "edges": [ { "by": 28, "category": "ergonomics", "leads": "scrapewise", "name": "Agent ergonomics", "reasons": { "a": "Read on the MCP server, with the REST API where a line covers it. The MCP map lists 382 tools and says the category manifests 'narrow metadata for your integration; the MCP connection still advertises the full catalog'. That is more than 30 tools with no toolsets, dynamic loading or read-only subset found (5). Search tools page by `page` (about 20 results), with filters such as marketplace, category node, sort and device per tool, but no general pagination model or field selection, and output size depends on each tool (12 of 20). By default business errors answer HTTP 200 with an outer `code`. The `X-Nexscope-Http-Status: semantic` header maps them to HTTP statuses, the OpenAPI file names codes such as `DATA_IMAGE_DOWNLOAD_FAILED` and `CAPABILITY_BACKEND_UNAVAILABLE` in field text, and MCP errors aren't documented. SandBase earned 16 with typed bridge errors (11 of 20). Data calls only read. No idempotency keys and no readOnlyHint or destructiveHint documented. Async jobs return a `taskId` with a poll tool and a rule not to resubmit, and 1688 order, payment-link, receipt and cancel calls need an explicit JSON `true` confirmation (8 of 20). Few required parameters with defaults on most. No official SDK package, only standard-library clients in the repository for JavaScript and Python, which SoldFetch earned 8 for (8 of 15). 5+12+11+8+8 = 44.", "b": "Since 22 October 2026 a Full (LLM_FULL) key lists every tool, 113 in the tool catalogue and 114 operations in the MCP subset of the spec, and the `?toolsets=` address that kept the setup tools out of the default list is no longer documented, so more than 30 tools (5). A Read (LLM_READ) key lists only the read tools, a read-only subset of 48 (5 added back). Cursor pagination with `limit` up to 1,000, `q`, `sort`, `from` and `to` filters, and job results in pages of 100 (20). Error codes an agent can branch on, such as WALLET_INSUFFICIENT_BALANCE, scope_rejected, cost_exceeded, SCRAPER_RUN_ACTIVE and MCP_SHOP_LIMIT, with a troubleshooting table, though two envelope shapes are documented (16 of 20). Idempotency keys on paid tools and REST create and run, a same-name retry rule for list runs, and preview tokens before deletes. Annotations are documented but only some appear in the spec, and tools/list was not read (16 of 20). Few required fields and a free `quote_only` check, but only a Python SDK (10 of 15). 10 + 20 + 16 + 16 + 10 = 72." }, "scores": { "a": 44, "b": 72 } }, { "by": 15, "category": "schema", "leads": "scrapewise", "name": "Schema \u0026 documentation", "reasons": { "a": "A public OpenAPI 3.1 file at api.nexscope.ai/openapi.json, about 3.8 MB, linked from the quickstart. Visible request bodies are typed with required fields, patterns, enums and `additionalProperties: false`, but responses are open `data` objects and the components section, with the security scheme and the shared error response, wasn't reached. In the repository 166 of 252 request definitions are field descriptors rather than JSON Schema. The hosted tools/list wasn't read. SoldFetch took 17 with untyped responses and SandBase 22 with components unread (19 of 25). llms.txt on www.nexscope.ai and Markdown references for every API in the repository (10). MCP tool descriptions are one line ('Find Amazon products by keyword and marketplace. Results come back as structured JSON.'), with no when-not-to-use. The repository's references carry long trigger text ('trigger this skill whenever their need involves real-time Amazon search results'), not guidance on when to pick another tool (10 of 20). Tool pages list types, defaults, enums and length limits, but the Amazon Search page marks no argument required and omits the `keyword` its own examples pass, and many limits sit in prose (8 of 15). Every API has a request sample, a response fixture and cURL, JavaScript and Python clients, though most fixtures are labelled historical. Errors are an HTTP table, two named codes (11209, 12001) and a semantic error response whose schema wasn't read. MCP errors aren't documented (10 of 15). Path versioning under /v1, MCP v2 beside a legacy v1, and a dated OpenAPI version label, but no public changelog. SandBase earned 7 on the same pattern (7 of 15). 19+10+10+8+10+7 = 64.", "b": "Public OpenAPI 3.1 for the whole REST surface (247 operations on 2 November, 224 on 15 October) and an MCP subset (114 operations, 93 on 15 October), and MCP tools are generated from it with JSON Schema inputs (25). llms.txt, agents.md and pricing.md on scrapewise.ai, though docs.scrapewise.ai has no llms.txt (10). The data tools' descriptions say when to use each, what it returns, its price and that it is free or paid. Setup tools carry one-line descriptions (16 of 20). Required fields are marked and there are 55 enums in the MCP subset, but limits such as 1 to 20 results sit in prose, not as constraints, and paid tools wrap arguments in a `body` object (10 of 15). Request examples throughout, error codes listed with fixes, but the docs show two error envelope shapes and the MCP subset documents only 200, 204, 400 and 402 (10 of 15). A changelog with six entries, the newest items dated by day up to 23 October 2026, one evolving spec with no version prefix, and a one-release deprecation rule (8 of 15)." }, "scores": { "a": 64, "b": 79 } }, { "by": 15, "category": "security", "leads": "scrapewise", "name": "Security \u0026 auth", "reasons": { "a": "The MCP server takes OAuth 2.1 with PKCE and one scope, `mcp:tools`, per the tool pages, or a Bearer `nk-` API key. Keys are created by a person under API Access, shown once, and can be expired, disabled or deleted, with no scopes or rotation found. The OAuth metadata on api.nexscope.ai wasn't read. No query-string key option was found. Manifold earned 22 with OAuth and hashed keys whose storage it documents (20 of 30). Most tools read. Writes exist (1688 procurement on the user's own buyer account, Amazon Ads entity operations through an owned connection, paid generation jobs), and the 1688 calls need an explicit JSON `true` per action after a preview, with the guide saying to get the user's approval first. Credits cap spend. No read-only key or tool allowlist (12 of 20). Tools return third-party listings, reviews, social posts and web pages, and no prompt-injection guidance was found. Manifold, the closest marketing-data MCP, took 0 (0). The Account credits and Account usage APIs, `costToken` in data responses and credits charged on task results give per-call visibility. No key-level audit was found (9 of 15). security.txt answered a client error. No disclosure policy, bug bounty or certification found (0 of 20). 20+12+0+9+0 = 41.", "b": "Scoped keys (USER for REST, LLM_READ and LLM_FULL for MCP) stored as hashes, revocable at once, several per account with last-used time, rotated by mint and revoke. No expiry and no finer scopes (26 of 30). LLM_READ cannot run paid tools or write, and deletes need a preview token committed within 5 minutes. Since 22 October the setup and destructive tools are no longer opt-in for a Full key, and LLM_FULL has no per-tool consent (16 of 20). A documented prompt-injection contract and guidance, but it rests on a `type: \"scraped\"` content block that the MCP specification of 25 November 2025 does not define, and the docs' statement that Anthropic's clients honour it by default was not confirmed (8 of 15). Every call is logged with a correlation id and key prefix and the wallet ledger itemises charges, but the operator sees logs only through support (6 of 15). No security.txt, disclosure policy, bug bounty or certification found, security.txt still 404 on 2 November (0 of 20)." }, "scores": { "a": 41, "b": 56 } }, { "by": 14, "category": "maintenance", "leads": "scrapewise", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a closed service with a public documentation repository. The repository synced the released 1688 procurement contracts on 9 November 2026 and committed again on 10 November (30). No releases or changelog. The dated record is the registry's four versions on 14 and 16 October, repository commits on 8, 9, 20 and 29 October and 2, 9 and 10 November, and source notes dating WooCommerce (29 October) and design search (2 November) additions. SoldFetch earned 10 for dated commits without releases (10 of 20). No public changelog. Support is service@nexscope.ai, WhatsApp and a booked call, untested. The repository's one merged pull request came from the organisation itself, and GitHub's API refused us, so issues weren't read (5 of 15). The official MCP registry lists `io.github.nexscope/ecommerce`, active, latest 1.0.3 of 16 October 2026, read first-hand (15). A CI workflow runs offline catalogue validation and unit tests on standard-library clients with no dependencies. The run results weren't read (5 of 10). 30+10+5+15+5 = 65.", "b": "Read as a closed service. Changelog items dated 18, 20, 21, 22 and 23 October 2026 (30). At least three dated changes in 90 days, the September entry and the October items among them (20). A public changelog, a support address and site chat. Two outside issues on the MCP repository from 11 and 15 October had no reply per the 15 October check; GitHub's issue pages couldn't be read on 2 November (8 of 15). Verified namespace in the official MCP registry, version 0.1.1 still the latest on 2 November (15). The Python SDK has CI and trusted publishing at version 0.1.0, Beta, with no commit since 7 October (6 of 10). 30 + 20 + 8 + 15 + 6 = 79." }, "scores": { "a": 65, "b": 79 } }, { "by": 13, "category": "transparency", "leads": "scrapewise", "name": "Transparency \u0026 trust", "reasons": { "a": "The editorial half. The service is closed. The terms (8 October 2026) name ECOCREATE TECHNOLOGY PTE. LTD. under Singapore law with no registration number or address. The repository's MIT licence covers client code only, and the documentation and definitions stay copyright Nexscope. Scrapewise earned 15 for closed terms with MIT side code (15 of 30). The privacy policy (8 October 2026) says uploads are not used to train AI models and that connected selling-partner data is deleted or de-identified when no longer needed, but 'this policy does not specify a single deletion deadline for all data', and no DPA was found. SandBase took 12 with no retention periods (10 of 30). No deprecation policy or dated notices. The terms promise notice of material changes before they take effect where practicable, and the MCP map keeps a legacy v1 beside v2 (3 of 20). Analytics and advertising vendors are named (Google Analytics, Microsoft Clarity, Ahrefs, Google Ads, X, FirstPromoter), but hosting, AI processing and payment providers only by type, with no data locations. The repository's source notes say supplier references 'are presented as Nexscope', so the data suppliers go unnamed except LinkFox Agent for 1688 authorisation (5 of 20). 15+10+3+5 = 33. The provenance half is computed from the provenance block.", "b": "Closed service with terms under Estonian law, but the terms name no legal entity and claim ownership of all collected and derived data. The MCP manifest and Python SDK are MIT (15 of 30). The 90-day retention agrees across the terms, pricing.md and billing docs. The privacy policy still speaks of subscriptions and plan limits, calls service data confidential while the terms claim ownership of it, and no DPA or retention period for logs was found (10 of 30). The API reference states a one-release deprecation rule and the changelog records changed columns with old rows left as they were (8 of 20). Analytics tools on the website named, chat stored on Hetzner in Germany, Stripe and Firebase named in the docs, but no subprocessor list or data locations for the service (5 of 20)." }, "scores": { "a": 41, "b": 54 } }, { "by": 6, "category": "reliability", "leads": "scrapewise", "name": "Reliability", "reasons": { "a": "Hosted lines, graded on the remote MCP server and the REST API at api.nexscope.ai. No status page is linked from the home page, llms.txt, the API quickstart or the MCP map, and none was found (0). With no page there is no incident history to read (5). The pricing page publishes requests a second and concurrency per plan, the same for API and MCP, with 1 and 1 on the trial, 3 and 2 on Starter, 5 and 4 on Growth, 10 and 8 on Pro (15). The quickstart calls 429 an 'execution admission rate limit' and says to honour `Retry-After` on 429 and 503 when present. No idempotency key exists. The repository says 'Do not blindly retry POST requests' and to check whether a task was created before resubmitting, and the MCP tool pages say a reconnecting client should query existing async work rather than resubmit. SoldFetch earned 15 with idempotency keys and SandBase 11 with keys on some writes, so guidance without keys earns 9 (9 of 15). No SLA, and the terms say 'We cannot guarantee the Service will be available at all times' (0). No beta or preview label on the API or the MCP server (10). 0+5+15+9+0+10 = 39.", "b": "Read with the hosted lines. No status page found on scrapewise.ai, the docs, llms.txt or agents.md on 2 November 2026 (0). No readable incident history (5). Rate limits documented with numbers, per account per second and per day by plan (30 a second and 50,000 a day on STARTER up to 1,000 and 100,000,000 on BUSINESS, 2 a second unauthenticated), and 30 requests a second per key on the MCP gateway, plus an hourly cost ceiling there (15). 429 carries Retry-After and X-RateLimit-Remaining, Idempotency-Key is supported on scraper create and run, and paid MCP tools take an idempotency_key remembered for 24 hours (15). No SLA found (0). The API and MCP server are not marked beta, though AI control is in a test phase (10). 0 + 5 + 15 + 15 + 0 + 10 = 45." }, "scores": { "a": 39, "b": 45 } } ], "facts": [ { "a": "Platform", "b": "HTTP API", "name": "Kind" }, { "a": "ECOCREATE TECHNOLOGY PTE. LTD.", "b": "BEBOTECH OÜ", "name": "Vendor" }, { "a": "https://api.nexscope.ai/mcp", "b": "https://mcp.scrapewise.ai/mcp", "name": "Hosted endpoint" }, { "a": "Streamable HTTP, HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Paid", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary hosted service under the Nexscope terms (last updated 8 October 2026), whose contracting party is ECOCREATE TECHNOLOGY PTE. LTD. of Singapore. The OpenAPI file's licence is 'Proprietary API; use subject to Nexscope Terms'. In github.com/nexscope-ai/nexscope-ecommerce-api only the example clients, validation scripts, tests and workflow are MIT. The API documentation, catalogue, definitions and sample data stay copyright Nexscope", "b": "none", "name": "Licence" }, { "a": "382", "b": "113", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.github.nexscope/ecommerce", "b": "ai.scrapewise/scrapewise", "name": "MCP registry" }, { "a": "2026-11-09", "b": "2026-10-23", "name": "Last release" }, { "a": "not read yet", "b": "2025-10-29", "name": "Terms last updated" }, { "a": "not read yet", "b": "2025-10-29", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "1 stars, 30 PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Scrapewise scores 60 (C) on agent readiness against Nexscope's 46.2 (D), and leads in every scored category.", "question": "Which is better for AI agents, Nexscope or Scrapewise?" }, { "answer": "Yes. Nexscope has a hosted endpoint at https://api.nexscope.ai/mcp and Scrapewise at https://mcp.scrapewise.ai/mcp.", "question": "Can an agent call Nexscope and Scrapewise without installing anything?" } ], "goodFor": [ { "aheadOn": null, "also": null, "goodFor": "Agents that research ecommerce products, competitors, keywords, sourcing and patents across Amazon, TikTok Shop, Walmart, Temu, 1688 and other marketplaces, and that also make listing images and video, on one credit balance.", "slug": "nexscope", "watchFor": "The MCP connection advertises the full catalogue of 382 tools, with no toolsets or read-only subset" }, { "aheadOn": [ "Reliability, 45 against 39", "Schema \u0026 documentation, 79 against 64", "Agent ergonomics, 72 against 44", "Security \u0026 auth, 56 against 41", "Payments \u0026 pricing, 40 against 35", "Maintenance \u0026 community, 79 against 65", "Transparency \u0026 trust, 54 against 41" ], "also": null, "goodFor": "Agents that need e-commerce prices, Amazon and Google data, or recurring price monitoring with cleaning and product matching, paid per page in euros.", "slug": "scrapewise", "watchFor": "No status page, SLA, security.txt, disclosure policy or certification found" } ], "history": { "nexscope": null, "scrapewise": [ { "causes": [ "product" ], "date": "2026-11-02", "delta": -2.6, "from": 62.6, "fromGrade": "B", "to": 60, "toGrade": "C" }, { "causes": [ "evidence" ], "date": "2026-10-27", "delta": 0.1, "from": 62.5, "fromGrade": "B", "to": 62.6, "toGrade": "B" } ] }, "job": { "capability": "web.extract", "name": "Extraction" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bright-data-vs-scrapewise.json", "title": "Bright Data vs Scrapewise", "url": "https://www.anchorterminal.com/compare/bright-data-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/browseract-vs-scrapewise.json", "title": "BrowserAct vs Scrapewise", "url": "https://www.anchorterminal.com/compare/browseract-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/context-dev-vs-scrapewise.json", "title": "Context.dev vs Scrapewise", "url": "https://www.anchorterminal.com/compare/context-dev-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/crawl4ai-vs-scrapewise.json", "title": "Crawl4AI vs Scrapewise", "url": "https://www.anchorterminal.com/compare/crawl4ai-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-scrapewise.json", "title": "fastCRW vs Scrapewise", "url": "https://www.anchorterminal.com/compare/crw-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/decodo-vs-scrapewise.json", "title": "Decodo Web Data API vs Scrapewise", "url": "https://www.anchorterminal.com/compare/decodo-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/jina-reader-vs-scrapewise.json", "title": "Jina Reader vs Scrapewise", "url": "https://www.anchorterminal.com/compare/jina-reader-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/microlink-vs-scrapewise.json", "title": "Microlink vs Scrapewise", "url": "https://www.anchorterminal.com/compare/microlink-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/olostep-vs-scrapewise.json", "title": "Olostep vs Scrapewise", "url": "https://www.anchorterminal.com/compare/olostep-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapewise.json", "title": "Outcrawl vs Scrapewise", "url": "https://www.anchorterminal.com/compare/outcrawl-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapewise.json", "title": "Oxylabs Web Scraper API vs Scrapewise", "url": "https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/scrape-do-vs-scrapewise.json", "title": "Scrape.do vs Scrapewise", "url": "https://www.anchorterminal.com/compare/scrape-do-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapewise.json", "title": "ScrapeGraphAI vs Scrapewise", "url": "https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/scrapeless-vs-scrapewise.json", "title": "Scrapeless vs Scrapewise", "url": "https://www.anchorterminal.com/compare/scrapeless-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/scraperapi-vs-scrapewise.json", "title": "ScraperAPI vs Scrapewise", "url": "https://www.anchorterminal.com/compare/scraperapi-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/scrapewise-vs-scrapfly.json", "title": "Scrapewise vs Scrapfly", "url": "https://www.anchorterminal.com/compare/scrapewise-vs-scrapfly" }, { "json": "https://www.anchorterminal.com/compare/scrapewise-vs-scrapingant.json", "title": "Scrapewise vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/scrapewise-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/scrapewise-vs-scrapingbee.json", "title": "Scrapewise vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/scrapewise-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/scrapewise-vs-scrapingdog.json", "title": "Scrapewise vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/scrapewise-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/scrapewise-vs-spider-cloud.json", "title": "Scrapewise vs Spider", "url": "https://www.anchorterminal.com/compare/scrapewise-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/scrapewise-vs-webscraping-ai.json", "title": "Scrapewise vs WebScraping.AI", "url": "https://www.anchorterminal.com/compare/scrapewise-vs-webscraping-ai" }, { "json": "https://www.anchorterminal.com/compare/scrapewise-vs-zenrows.json", "title": "Scrapewise vs ZenRows", "url": "https://www.anchorterminal.com/compare/scrapewise-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/scrapewise-vs-zyte.json", "title": "Scrapewise vs Zyte API", "url": "https://www.anchorterminal.com/compare/scrapewise-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapewise.json", "title": "Firecrawl MCP vs Scrapewise", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/browseract-vs-nexscope.json", "title": "BrowserAct vs Nexscope", "url": "https://www.anchorterminal.com/compare/browseract-vs-nexscope" }, { "json": "https://www.anchorterminal.com/compare/context-dev-vs-nexscope.json", "title": "Context.dev vs Nexscope", "url": "https://www.anchorterminal.com/compare/context-dev-vs-nexscope" }, { "json": "https://www.anchorterminal.com/compare/crawl4ai-vs-nexscope.json", "title": "Crawl4AI vs Nexscope", "url": "https://www.anchorterminal.com/compare/crawl4ai-vs-nexscope" }, { "json": "https://www.anchorterminal.com/compare/crw-vs-nexscope.json", "title": "fastCRW vs Nexscope", "url": "https://www.anchorterminal.com/compare/crw-vs-nexscope" }, { "json": "https://www.anchorterminal.com/compare/decodo-vs-nexscope.json", "title": "Decodo Web Data API vs Nexscope", "url": "https://www.anchorterminal.com/compare/decodo-vs-nexscope" }, { "json": "https://www.anchorterminal.com/compare/diffbot-vs-nexscope.json", "title": "Diffbot vs Nexscope", "url": "https://www.anchorterminal.com/compare/diffbot-vs-nexscope" }, { "json": "https://www.anchorterminal.com/compare/diffbot-vs-scrapewise.json", "title": "Diffbot vs Scrapewise", "url": "https://www.anchorterminal.com/compare/diffbot-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-nexscope.json", "title": "Firecrawl MCP vs Nexscope", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-nexscope" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-nexscope.json", "title": "jevcrawl vs Nexscope", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-nexscope" }, { "json": "https://www.anchorterminal.com/compare/microlink-vs-nexscope.json", "title": "Microlink vs Nexscope", "url": "https://www.anchorterminal.com/compare/microlink-vs-nexscope" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-olostep.json", "title": "Nexscope vs Olostep", "url": "https://www.anchorterminal.com/compare/nexscope-vs-olostep" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-outcrawl.json", "title": "Nexscope vs Outcrawl", "url": "https://www.anchorterminal.com/compare/nexscope-vs-outcrawl" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-oxylabs-web-scraper.json", "title": "Nexscope vs Oxylabs Web Scraper API", "url": "https://www.anchorterminal.com/compare/nexscope-vs-oxylabs-web-scraper" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-printfriendly-mcp.json", "title": "Nexscope vs PrintFriendly MCP server", "url": "https://www.anchorterminal.com/compare/nexscope-vs-printfriendly-mcp" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-qovia.json", "title": "Nexscope vs Qovia", "url": "https://www.anchorterminal.com/compare/nexscope-vs-qovia" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-scrapeatlas.json", "title": "Nexscope vs ScrapeAtlas", "url": "https://www.anchorterminal.com/compare/nexscope-vs-scrapeatlas" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-scrapegraphai.json", "title": "Nexscope vs ScrapeGraphAI", "url": "https://www.anchorterminal.com/compare/nexscope-vs-scrapegraphai" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-scrapeops.json", "title": "Nexscope vs ScrapeOps Proxy API Aggregator", "url": "https://www.anchorterminal.com/compare/nexscope-vs-scrapeops" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-scraperapi.json", "title": "Nexscope vs ScraperAPI", "url": "https://www.anchorterminal.com/compare/nexscope-vs-scraperapi" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-scrapfly.json", "title": "Nexscope vs Scrapfly", "url": "https://www.anchorterminal.com/compare/nexscope-vs-scrapfly" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-scrapingant.json", "title": "Nexscope vs ScrapingAnt", "url": "https://www.anchorterminal.com/compare/nexscope-vs-scrapingant" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-scrapingbee.json", "title": "Nexscope vs ScrapingBee", "url": "https://www.anchorterminal.com/compare/nexscope-vs-scrapingbee" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-scrapingdog.json", "title": "Nexscope vs Scrapingdog", "url": "https://www.anchorterminal.com/compare/nexscope-vs-scrapingdog" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-soldfetch.json", "title": "Nexscope vs SoldFetch", "url": "https://www.anchorterminal.com/compare/nexscope-vs-soldfetch" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-spider-cloud.json", "title": "Nexscope vs Spider", "url": "https://www.anchorterminal.com/compare/nexscope-vs-spider-cloud" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-webscraping-ai.json", "title": "Nexscope vs WebScraping.AI", "url": "https://www.anchorterminal.com/compare/nexscope-vs-webscraping-ai" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-zenrows.json", "title": "Nexscope vs ZenRows", "url": "https://www.anchorterminal.com/compare/nexscope-vs-zenrows" }, { "json": "https://www.anchorterminal.com/compare/nexscope-vs-zyte.json", "title": "Nexscope vs Zyte API", "url": "https://www.anchorterminal.com/compare/nexscope-vs-zyte" }, { "json": "https://www.anchorterminal.com/compare/qovia-vs-scrapewise.json", "title": "Qovia vs Scrapewise", "url": "https://www.anchorterminal.com/compare/qovia-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapewise.json", "title": "ScrapeAtlas vs Scrapewise", "url": "https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/scrapewise-vs-soldfetch.json", "title": "Scrapewise vs SoldFetch", "url": "https://www.anchorterminal.com/compare/scrapewise-vs-soldfetch" }, { "json": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapewise.json", "title": "Apify MCP Server vs Scrapewise", "url": "https://www.anchorterminal.com/compare/apify-mcp-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapewise.json", "title": "jevcrawl vs Scrapewise", "url": "https://www.anchorterminal.com/compare/jevcrawl-vs-scrapewise" }, { "json": "https://www.anchorterminal.com/compare/scrapeops-vs-scrapewise.json", "title": "ScrapeOps Proxy API Aggregator vs Scrapewise", "url": "https://www.anchorterminal.com/compare/scrapeops-vs-scrapewise" } ], "panel": null, "scores": [ { "by": 6, "edge": "scrapewise", "key": "reliability", "name": "Reliability", "nexscope": 39, "scrapewise": 45, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 15, "edge": "scrapewise", "key": "schema", "name": "Schema \u0026 documentation", "nexscope": 64, "scrapewise": 79, "weight": 13 }, { "by": 28, "edge": "scrapewise", "key": "ergonomics", "name": "Agent ergonomics", "nexscope": 44, "scrapewise": 72, "weight": 13 }, { "by": 15, "edge": "scrapewise", "key": "security", "name": "Security \u0026 auth", "nexscope": 41, "scrapewise": 56, "weight": 14 }, { "by": 5, "edge": "scrapewise", "key": "payments", "name": "Payments \u0026 pricing", "nexscope": 35, "scrapewise": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 14, "edge": "scrapewise", "key": "maintenance", "name": "Maintenance \u0026 community", "nexscope": 65, "scrapewise": 79, "weight": 7 }, { "by": 13, "edge": "scrapewise", "key": "transparency", "name": "Transparency \u0026 trust", "nexscope": 41, "scrapewise": 54, "weight": 7 } ], "summary": "Scrapewise scores 60 (C) on agent readiness against Nexscope's 46.2 (D), and leads in every scored category. Both do extraction.", "tasks": null, "tutorials": [], "verdicts": { "nexscope": "An agent can reach Amazon, TikTok Shop, Temu, 1688 and other marketplace data, plus image and video models, on one credit balance through a remote MCP server with OAuth or a REST API with a public OpenAPI file. The connection loads 382 tools at once, and there is no status page, changelog or idempotency key.", "scrapewise": "Paid MCP tools each take a free `quote_only` price check and idempotency keys, keys are read-only or full-access, and euro prices start at €0.15 per 1,000 plain pages. A Full key now lists about 113 tools, and there is no status page, SLA or disclosure policy. The terms claim ownership of all scraped data." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/nexscope-vs-scrapewise", "json": "https://www.anchorterminal.com/compare/nexscope-vs-scrapewise.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/nexscope-vs-scrapewise.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/nexscope-vs-scrapewise.min.md" }, "markdown": "Scrapewise scores 60 (C) on agent readiness against Nexscope's 46.2 (D), and leads in every scored category. Both do extraction.\n\n- Nexscope: grade D, 46.2/100, rank #1191 of 1520. Markdown https://www.anchorterminal.com/tools/nexscope.md · JSON https://www.anchorterminal.com/api/v1/tools/nexscope.json\n- Scrapewise: grade C, 60/100, rank #676 of 1520. Markdown https://www.anchorterminal.com/tools/scrapewise.md · JSON https://www.anchorterminal.com/api/v1/tools/scrapewise.json\n- Best web scraping and crawling APIs for AI agents: https://www.anchorterminal.com/best/web-scrapers/index.md\n- All 533 scrapers comparisons: https://www.anchorterminal.com/compare/web-scrapers/index.md\n\n## Which one, for what\n\n### Nexscope (D)\n\nGood for: Agents that research ecommerce products, competitors, keywords, sourcing and patents across Amazon, TikTok Shop, Walmart, Temu, 1688 and other marketplaces, and that also make listing images and video, on one credit balance.\n\nWatch for: The MCP connection advertises the full catalogue of 382 tools, with no toolsets or read-only subset\n\n### Scrapewise (C)\n\nGood for: Agents that need e-commerce prices, Amazon and Google data, or recurring price monitoring with cleaning and product matching, paid per page in euros.\n\nAhead on:\n- Reliability, 45 against 39\n- Schema \u0026 documentation, 79 against 64\n- Agent ergonomics, 72 against 44\n- Security \u0026 auth, 56 against 41\n- Payments \u0026 pricing, 40 against 35\n- Maintenance \u0026 community, 79 against 65\n- Transparency \u0026 trust, 54 against 41\n\nWatch for: No status page, SLA, security.txt, disclosure policy or certification found\n\n\n## Why the edge\n\n### Agent ergonomics: Scrapewise +28\n\n- Nexscope (44): Read on the MCP server, with the REST API where a line covers it. The MCP map lists 382 tools and says the category manifests 'narrow metadata for your integration; the MCP connection still advertises the full catalog'. That is more than 30 tools with no toolsets, dynamic loading or read-only subset found (5). Search tools page by `page` (about 20 results), with filters such as marketplace, category node, sort and device per tool, but no general pagination model or field selection, and output size depends on each tool (12 of 20). By default business errors answer HTTP 200 with an outer `code`. The `X-Nexscope-Http-Status: semantic` header maps them to HTTP statuses, the OpenAPI file names codes such as `DATA_IMAGE_DOWNLOAD_FAILED` and `CAPABILITY_BACKEND_UNAVAILABLE` in field text, and MCP errors aren't documented. SandBase earned 16 with typed bridge errors (11 of 20). Data calls only read. No idempotency keys and no readOnlyHint or destructiveHint documented. Async jobs return a `taskId` with a poll tool and a rule not to resubmit, and 1688 order, payment-link, receipt and cancel calls need an explicit JSON `true` confirmation (8 of 20). Few required parameters with defaults on most. No official SDK package, only standard-library clients in the repository for JavaScript and Python, which SoldFetch earned 8 for (8 of 15). 5+12+11+8+8 = 44.\n- Scrapewise (72): Since 22 October 2026 a Full (LLM_FULL) key lists every tool, 113 in the tool catalogue and 114 operations in the MCP subset of the spec, and the `?toolsets=` address that kept the setup tools out of the default list is no longer documented, so more than 30 tools (5). A Read (LLM_READ) key lists only the read tools, a read-only subset of 48 (5 added back). Cursor pagination with `limit` up to 1,000, `q`, `sort`, `from` and `to` filters, and job results in pages of 100 (20). Error codes an agent can branch on, such as WALLET_INSUFFICIENT_BALANCE, scope_rejected, cost_exceeded, SCRAPER_RUN_ACTIVE and MCP_SHOP_LIMIT, with a troubleshooting table, though two envelope shapes are documented (16 of 20). Idempotency keys on paid tools and REST create and run, a same-name retry rule for list runs, and preview tokens before deletes. Annotations are documented but only some appear in the spec, and tools/list was not read (16 of 20). Few required fields and a free `quote_only` check, but only a Python SDK (10 of 15). 10 + 20 + 16 + 16 + 10 = 72.\n\n### Schema \u0026 documentation: Scrapewise +15\n\n- Nexscope (64): A public OpenAPI 3.1 file at api.nexscope.ai/openapi.json, about 3.8 MB, linked from the quickstart. Visible request bodies are typed with required fields, patterns, enums and `additionalProperties: false`, but responses are open `data` objects and the components section, with the security scheme and the shared error response, wasn't reached. In the repository 166 of 252 request definitions are field descriptors rather than JSON Schema. The hosted tools/list wasn't read. SoldFetch took 17 with untyped responses and SandBase 22 with components unread (19 of 25). llms.txt on www.nexscope.ai and Markdown references for every API in the repository (10). MCP tool descriptions are one line ('Find Amazon products by keyword and marketplace. Results come back as structured JSON.'), with no when-not-to-use. The repository's references carry long trigger text ('trigger this skill whenever their need involves real-time Amazon search results'), not guidance on when to pick another tool (10 of 20). Tool pages list types, defaults, enums and length limits, but the Amazon Search page marks no argument required and omits the `keyword` its own examples pass, and many limits sit in prose (8 of 15). Every API has a request sample, a response fixture and cURL, JavaScript and Python clients, though most fixtures are labelled historical. Errors are an HTTP table, two named codes (11209, 12001) and a semantic error response whose schema wasn't read. MCP errors aren't documented (10 of 15). Path versioning under /v1, MCP v2 beside a legacy v1, and a dated OpenAPI version label, but no public changelog. SandBase earned 7 on the same pattern (7 of 15). 19+10+10+8+10+7 = 64.\n- Scrapewise (79): Public OpenAPI 3.1 for the whole REST surface (247 operations on 2 November, 224 on 15 October) and an MCP subset (114 operations, 93 on 15 October), and MCP tools are generated from it with JSON Schema inputs (25). llms.txt, agents.md and pricing.md on scrapewise.ai, though docs.scrapewise.ai has no llms.txt (10). The data tools' descriptions say when to use each, what it returns, its price and that it is free or paid. Setup tools carry one-line descriptions (16 of 20). Required fields are marked and there are 55 enums in the MCP subset, but limits such as 1 to 20 results sit in prose, not as constraints, and paid tools wrap arguments in a `body` object (10 of 15). Request examples throughout, error codes listed with fixes, but the docs show two error envelope shapes and the MCP subset documents only 200, 204, 400 and 402 (10 of 15). A changelog with six entries, the newest items dated by day up to 23 October 2026, one evolving spec with no version prefix, and a one-release deprecation rule (8 of 15).\n\n### Security \u0026 auth: Scrapewise +15\n\n- Nexscope (41): The MCP server takes OAuth 2.1 with PKCE and one scope, `mcp:tools`, per the tool pages, or a Bearer `nk-` API key. Keys are created by a person under API Access, shown once, and can be expired, disabled or deleted, with no scopes or rotation found. The OAuth metadata on api.nexscope.ai wasn't read. No query-string key option was found. Manifold earned 22 with OAuth and hashed keys whose storage it documents (20 of 30). Most tools read. Writes exist (1688 procurement on the user's own buyer account, Amazon Ads entity operations through an owned connection, paid generation jobs), and the 1688 calls need an explicit JSON `true` per action after a preview, with the guide saying to get the user's approval first. Credits cap spend. No read-only key or tool allowlist (12 of 20). Tools return third-party listings, reviews, social posts and web pages, and no prompt-injection guidance was found. Manifold, the closest marketing-data MCP, took 0 (0). The Account credits and Account usage APIs, `costToken` in data responses and credits charged on task results give per-call visibility. No key-level audit was found (9 of 15). security.txt answered a client error. No disclosure policy, bug bounty or certification found (0 of 20). 20+12+0+9+0 = 41.\n- Scrapewise (56): Scoped keys (USER for REST, LLM_READ and LLM_FULL for MCP) stored as hashes, revocable at once, several per account with last-used time, rotated by mint and revoke. No expiry and no finer scopes (26 of 30). LLM_READ cannot run paid tools or write, and deletes need a preview token committed within 5 minutes. Since 22 October the setup and destructive tools are no longer opt-in for a Full key, and LLM_FULL has no per-tool consent (16 of 20). A documented prompt-injection contract and guidance, but it rests on a `type: \"scraped\"` content block that the MCP specification of 25 November 2025 does not define, and the docs' statement that Anthropic's clients honour it by default was not confirmed (8 of 15). Every call is logged with a correlation id and key prefix and the wallet ledger itemises charges, but the operator sees logs only through support (6 of 15). No security.txt, disclosure policy, bug bounty or certification found, security.txt still 404 on 2 November (0 of 20).\n\n### Maintenance \u0026 community: Scrapewise +14\n\n- Nexscope (65): Read as a closed service with a public documentation repository. The repository synced the released 1688 procurement contracts on 9 November 2026 and committed again on 10 November (30). No releases or changelog. The dated record is the registry's four versions on 14 and 16 October, repository commits on 8, 9, 20 and 29 October and 2, 9 and 10 November, and source notes dating WooCommerce (29 October) and design search (2 November) additions. SoldFetch earned 10 for dated commits without releases (10 of 20). No public changelog. Support is service@nexscope.ai, WhatsApp and a booked call, untested. The repository's one merged pull request came from the organisation itself, and GitHub's API refused us, so issues weren't read (5 of 15). The official MCP registry lists `io.github.nexscope/ecommerce`, active, latest 1.0.3 of 16 October 2026, read first-hand (15). A CI workflow runs offline catalogue validation and unit tests on standard-library clients with no dependencies. The run results weren't read (5 of 10). 30+10+5+15+5 = 65.\n- Scrapewise (79): Read as a closed service. Changelog items dated 18, 20, 21, 22 and 23 October 2026 (30). At least three dated changes in 90 days, the September entry and the October items among them (20). A public changelog, a support address and site chat. Two outside issues on the MCP repository from 11 and 15 October had no reply per the 15 October check; GitHub's issue pages couldn't be read on 2 November (8 of 15). Verified namespace in the official MCP registry, version 0.1.1 still the latest on 2 November (15). The Python SDK has CI and trusted publishing at version 0.1.0, Beta, with no commit since 7 October (6 of 10). 30 + 20 + 8 + 15 + 6 = 79.\n\n### Transparency \u0026 trust: Scrapewise +13\n\n- Nexscope (41): The editorial half. The service is closed. The terms (8 October 2026) name ECOCREATE TECHNOLOGY PTE. LTD. under Singapore law with no registration number or address. The repository's MIT licence covers client code only, and the documentation and definitions stay copyright Nexscope. Scrapewise earned 15 for closed terms with MIT side code (15 of 30). The privacy policy (8 October 2026) says uploads are not used to train AI models and that connected selling-partner data is deleted or de-identified when no longer needed, but 'this policy does not specify a single deletion deadline for all data', and no DPA was found. SandBase took 12 with no retention periods (10 of 30). No deprecation policy or dated notices. The terms promise notice of material changes before they take effect where practicable, and the MCP map keeps a legacy v1 beside v2 (3 of 20). Analytics and advertising vendors are named (Google Analytics, Microsoft Clarity, Ahrefs, Google Ads, X, FirstPromoter), but hosting, AI processing and payment providers only by type, with no data locations. The repository's source notes say supplier references 'are presented as Nexscope', so the data suppliers go unnamed except LinkFox Agent for 1688 authorisation (5 of 20). 15+10+3+5 = 33. The provenance half is computed from the provenance block.\n- Scrapewise (54): Closed service with terms under Estonian law, but the terms name no legal entity and claim ownership of all collected and derived data. The MCP manifest and Python SDK are MIT (15 of 30). The 90-day retention agrees across the terms, pricing.md and billing docs. The privacy policy still speaks of subscriptions and plan limits, calls service data confidential while the terms claim ownership of it, and no DPA or retention period for logs was found (10 of 30). The API reference states a one-release deprecation rule and the changelog records changed columns with old rows left as they were (8 of 20). Analytics tools on the website named, chat stored on Hetzner in Germany, Stripe and Firebase named in the docs, but no subprocessor list or data locations for the service (5 of 20).\n\n### Reliability: Scrapewise +6\n\n- Nexscope (39): Hosted lines, graded on the remote MCP server and the REST API at api.nexscope.ai. No status page is linked from the home page, llms.txt, the API quickstart or the MCP map, and none was found (0). With no page there is no incident history to read (5). The pricing page publishes requests a second and concurrency per plan, the same for API and MCP, with 1 and 1 on the trial, 3 and 2 on Starter, 5 and 4 on Growth, 10 and 8 on Pro (15). The quickstart calls 429 an 'execution admission rate limit' and says to honour `Retry-After` on 429 and 503 when present. No idempotency key exists. The repository says 'Do not blindly retry POST requests' and to check whether a task was created before resubmitting, and the MCP tool pages say a reconnecting client should query existing async work rather than resubmit. SoldFetch earned 15 with idempotency keys and SandBase 11 with keys on some writes, so guidance without keys earns 9 (9 of 15). No SLA, and the terms say 'We cannot guarantee the Service will be available at all times' (0). No beta or preview label on the API or the MCP server (10). 0+5+15+9+0+10 = 39.\n- Scrapewise (45): Read with the hosted lines. No status page found on scrapewise.ai, the docs, llms.txt or agents.md on 2 November 2026 (0). No readable incident history (5). Rate limits documented with numbers, per account per second and per day by plan (30 a second and 50,000 a day on STARTER up to 1,000 and 100,000,000 on BUSINESS, 2 a second unauthenticated), and 30 requests a second per key on the MCP gateway, plus an hourly cost ceiling there (15). 429 carries Retry-After and X-RateLimit-Remaining, Idempotency-Key is supported on scraper create and run, and paid MCP tools take an idempotency_key remembered for 24 hours (15). No SLA found (0). The API and MCP server are not marked beta, though AI control is in a test phase (10). 0 + 5 + 15 + 15 + 0 + 10 = 45.\n\n## Score by category\n\n| Category | Weight | Nexscope | Scrapewise | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 39 | 45 | Scrapewise +6 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 64 | 79 | Scrapewise +15 |\n| Agent ergonomics | 13% (16.2 this run) | 44 | 72 | Scrapewise +28 |\n| Security \u0026 auth | 14% (17.5 this run) | 41 | 56 | Scrapewise +15 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 40 | Scrapewise +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 65 | 79 | Scrapewise +14 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 41 | 54 | Scrapewise +13 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **46.2 · D** | **60 · C** | |\n\n## Facts side by side\n\n| Fact | Nexscope | Scrapewise |\n| --- | --- | --- |\n| Kind | Platform | HTTP API |\n| Vendor | ECOCREATE TECHNOLOGY PTE. LTD. | BEBOTECH OÜ |\n| Hosted endpoint | `https://api.nexscope.ai/mcp` | `https://mcp.scrapewise.ai/mcp` |\n| Transports | Streamable HTTP, HTTP | Streamable HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Paid | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary hosted service under the Nexscope terms (last updated 8 October 2026), whose contracting party is ECOCREATE TECHNOLOGY PTE. LTD. of Singapore. The OpenAPI file's licence is 'Proprietary API; use subject to Nexscope Terms'. In github.com/nexscope-ai/nexscope-ecommerce-api only the example clients, validation scripts, tests and workflow are MIT. The API documentation, catalogue, definitions and sample data stay copyright Nexscope | none |\n| Tools exposed | 382 | 113 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.nexscope/ecommerce` | `ai.scrapewise/scrapewise` |\n| Last release | 2026-11-09 | 2026-10-23 |\n| Terms last updated | not read yet | 2025-10-29 |\n| Privacy policy last updated | not read yet | 2025-10-29 |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | not found in the text |\n| Terms restrict benchmarking | not read yet | not found in the text |\n| Terms or service can change without notice | not read yet | not found in the text |\n| Arbitration or class-action waiver | not read yet | not found in the text |\n| Popularity | none | 1 stars, 30 PyPI/wk |\n| Agent reviews | none | 3/5 (4) |\n\n## How the scores have moved\n\n### Nexscope\n\nNo score change since it was listed.\n\n### Scrapewise\n\n- -2.6 on 2 November 2026 (B to C): product\n- +0.1 on 27 October 2026: new evidence\n\n## Verdicts\n\n**Nexscope.** An agent can reach Amazon, TikTok Shop, Temu, 1688 and other marketplace data, plus image and video models, on one credit balance through a remote MCP server with OAuth or a REST API with a public OpenAPI file. The connection loads 382 tools at once, and there is no status page, changelog or idempotency key.\n\n**Scrapewise.** Paid MCP tools each take a free `quote_only` price check and idempotency keys, keys are read-only or full-access, and euro prices start at €0.15 per 1,000 plain pages. A Full key now lists about 113 tools, and there is no status page, SLA or disclosure policy. The terms claim ownership of all scraped data.\n\n## Before you call either\n\n### Nexscope\n\n1. Check the outer `code` is 0 before reading `data`, or send `X-Nexscope-Http-Status: semantic` to get HTTP error statuses.\n2. Call an image or video tool once, keep the `taskId`, and poll `nexscope_media_task_result`. A second call bills a second job.\n3. Read the tool's credit cost before a call. Each tool costs at least 10 credits and some cost over 300.\n4. Before you set a 1688 confirmation field to `true`, show the user the preview and get approval.\n5. If the server returns 429 or 503, wait for `Retry-After` when present and back off.\n\n### Scrapewise\n\n1. Call each paid tool with `quote_only: true` first, then repeat with the same `idempotency_key` so a retry is charged once\n2. Expect about 113 tools from a Full key; use a Read key, which lists 48 read tools, when the task only reads saved rows or job results\n3. Use an LLM_READ key unless the task needs paid tools or writes, since LLM_FULL has no per-tool consent\n4. Treat 402 WALLET_INSUFFICIENT_BALANCE as final and ask the user to top up; on 429 wait for Retry-After, on 429 cost_exceeded wait for the next hour, and stop a run before deleting its scraper (409 SCRAPER_RUN_ACTIVE)\n5. Scrape many addresses with one `scrapewise_run_scraper_url_list` call (up to 5,000) and retry with the same name, never one scraper per address\n\n## Questions\n\n### Which is better for AI agents, Nexscope or Scrapewise?\n\nScrapewise scores 60 (C) on agent readiness against Nexscope's 46.2 (D), and leads in every scored category.\n\n### Can an agent call Nexscope and Scrapewise without installing anything?\n\nYes. Nexscope has a hosted endpoint at https://api.nexscope.ai/mcp and Scrapewise at https://mcp.scrapewise.ai/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/nexscope-vs-scrapewise.json, and with the fewest tokens: https://www.anchorterminal.com/compare/nexscope-vs-scrapewise.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"nexscope\", \"b\": \"scrapewise\"}`. From a terminal: `anchor compare nexscope scrapewise`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/nexscope.json and https://www.anchorterminal.com/api/v1/tools/scrapewise.json\n\n## Other comparisons with Nexscope or Scrapewise\n\n- [Bright Data vs Scrapewise](https://www.anchorterminal.com/compare/bright-data-vs-scrapewise.md)\n- [BrowserAct vs Scrapewise](https://www.anchorterminal.com/compare/browseract-vs-scrapewise.md)\n- [Context.dev vs Scrapewise](https://www.anchorterminal.com/compare/context-dev-vs-scrapewise.md)\n- [Crawl4AI vs Scrapewise](https://www.anchorterminal.com/compare/crawl4ai-vs-scrapewise.md)\n- [fastCRW vs Scrapewise](https://www.anchorterminal.com/compare/crw-vs-scrapewise.md)\n- [Decodo Web Data API vs Scrapewise](https://www.anchorterminal.com/compare/decodo-vs-scrapewise.md)\n- [Jina Reader vs Scrapewise](https://www.anchorterminal.com/compare/jina-reader-vs-scrapewise.md)\n- [Microlink vs Scrapewise](https://www.anchorterminal.com/compare/microlink-vs-scrapewise.md)\n- [Olostep vs Scrapewise](https://www.anchorterminal.com/compare/olostep-vs-scrapewise.md)\n- [Outcrawl vs Scrapewise](https://www.anchorterminal.com/compare/outcrawl-vs-scrapewise.md)\n- [Oxylabs Web Scraper API vs Scrapewise](https://www.anchorterminal.com/compare/oxylabs-web-scraper-vs-scrapewise.md)\n- [Scrape.do vs Scrapewise](https://www.anchorterminal.com/compare/scrape-do-vs-scrapewise.md)\n- [ScrapeGraphAI vs Scrapewise](https://www.anchorterminal.com/compare/scrapegraphai-vs-scrapewise.md)\n- [Scrapeless vs Scrapewise](https://www.anchorterminal.com/compare/scrapeless-vs-scrapewise.md)\n- [ScraperAPI vs Scrapewise](https://www.anchorterminal.com/compare/scraperapi-vs-scrapewise.md)\n- [Scrapewise vs Scrapfly](https://www.anchorterminal.com/compare/scrapewise-vs-scrapfly.md)\n- [Scrapewise vs ScrapingAnt](https://www.anchorterminal.com/compare/scrapewise-vs-scrapingant.md)\n- [Scrapewise vs ScrapingBee](https://www.anchorterminal.com/compare/scrapewise-vs-scrapingbee.md)\n- [Scrapewise vs Scrapingdog](https://www.anchorterminal.com/compare/scrapewise-vs-scrapingdog.md)\n- [Scrapewise vs Spider](https://www.anchorterminal.com/compare/scrapewise-vs-spider-cloud.md)\n- [Scrapewise vs WebScraping.AI](https://www.anchorterminal.com/compare/scrapewise-vs-webscraping-ai.md)\n- [Scrapewise vs ZenRows](https://www.anchorterminal.com/compare/scrapewise-vs-zenrows.md)\n- [Scrapewise vs Zyte API](https://www.anchorterminal.com/compare/scrapewise-vs-zyte.md)\n- [Firecrawl MCP vs Scrapewise](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-scrapewise.md)\n- [BrowserAct vs Nexscope](https://www.anchorterminal.com/compare/browseract-vs-nexscope.md)\n- [Context.dev vs Nexscope](https://www.anchorterminal.com/compare/context-dev-vs-nexscope.md)\n- [Crawl4AI vs Nexscope](https://www.anchorterminal.com/compare/crawl4ai-vs-nexscope.md)\n- [fastCRW vs Nexscope](https://www.anchorterminal.com/compare/crw-vs-nexscope.md)\n- [Decodo Web Data API vs Nexscope](https://www.anchorterminal.com/compare/decodo-vs-nexscope.md)\n- [Diffbot vs Nexscope](https://www.anchorterminal.com/compare/diffbot-vs-nexscope.md)\n- [Diffbot vs Scrapewise](https://www.anchorterminal.com/compare/diffbot-vs-scrapewise.md)\n- [Firecrawl MCP vs Nexscope](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-nexscope.md)\n- [jevcrawl vs Nexscope](https://www.anchorterminal.com/compare/jevcrawl-vs-nexscope.md)\n- [Microlink vs Nexscope](https://www.anchorterminal.com/compare/microlink-vs-nexscope.md)\n- [Nexscope vs Olostep](https://www.anchorterminal.com/compare/nexscope-vs-olostep.md)\n- [Nexscope vs Outcrawl](https://www.anchorterminal.com/compare/nexscope-vs-outcrawl.md)\n- [Nexscope vs Oxylabs Web Scraper API](https://www.anchorterminal.com/compare/nexscope-vs-oxylabs-web-scraper.md)\n- [Nexscope vs PrintFriendly MCP server](https://www.anchorterminal.com/compare/nexscope-vs-printfriendly-mcp.md)\n- [Nexscope vs Qovia](https://www.anchorterminal.com/compare/nexscope-vs-qovia.md)\n- [Nexscope vs ScrapeAtlas](https://www.anchorterminal.com/compare/nexscope-vs-scrapeatlas.md)\n- [Nexscope vs ScrapeGraphAI](https://www.anchorterminal.com/compare/nexscope-vs-scrapegraphai.md)\n- [Nexscope vs ScrapeOps Proxy API Aggregator](https://www.anchorterminal.com/compare/nexscope-vs-scrapeops.md)\n- [Nexscope vs ScraperAPI](https://www.anchorterminal.com/compare/nexscope-vs-scraperapi.md)\n- [Nexscope vs Scrapfly](https://www.anchorterminal.com/compare/nexscope-vs-scrapfly.md)\n- [Nexscope vs ScrapingAnt](https://www.anchorterminal.com/compare/nexscope-vs-scrapingant.md)\n- [Nexscope vs ScrapingBee](https://www.anchorterminal.com/compare/nexscope-vs-scrapingbee.md)\n- [Nexscope vs Scrapingdog](https://www.anchorterminal.com/compare/nexscope-vs-scrapingdog.md)\n- [Nexscope vs SoldFetch](https://www.anchorterminal.com/compare/nexscope-vs-soldfetch.md)\n- [Nexscope vs Spider](https://www.anchorterminal.com/compare/nexscope-vs-spider-cloud.md)\n- [Nexscope vs WebScraping.AI](https://www.anchorterminal.com/compare/nexscope-vs-webscraping-ai.md)\n- [Nexscope vs ZenRows](https://www.anchorterminal.com/compare/nexscope-vs-zenrows.md)\n- [Nexscope vs Zyte API](https://www.anchorterminal.com/compare/nexscope-vs-zyte.md)\n- [Qovia vs Scrapewise](https://www.anchorterminal.com/compare/qovia-vs-scrapewise.md)\n- [ScrapeAtlas vs Scrapewise](https://www.anchorterminal.com/compare/scrapeatlas-vs-scrapewise.md)\n- [Scrapewise vs SoldFetch](https://www.anchorterminal.com/compare/scrapewise-vs-soldfetch.md)\n- [Apify MCP Server vs Scrapewise](https://www.anchorterminal.com/compare/apify-mcp-vs-scrapewise.md)\n- [jevcrawl vs Scrapewise](https://www.anchorterminal.com/compare/jevcrawl-vs-scrapewise.md)\n- [ScrapeOps Proxy API Aggregator vs Scrapewise](https://www.anchorterminal.com/compare/scrapeops-vs-scrapewise.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": "Nexscope vs Scrapewise", "url": "" } ], "description": "Scrapewise scores 60 (C) to Nexscope's 46.2 (D) for extraction. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Nexscope D 46.2", "Scrapewise C 60", "scores" ], "h1": "Nexscope vs Scrapewise", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/nexscope-vs-scrapewise", "published": "2026-10-01", "section": "tools", "title": "Nexscope vs Scrapewise for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-11", "url": "https://www.anchorterminal.com/compare/nexscope-vs-scrapewise" }, "tokens": { "markdown": 6750, "slim": 1230 }, "version": 1 }