{ "data": { "a": { "slug": "agentcore-web-search", "name": "Web Search Tool on Amazon Bedrock AgentCore", "vendor": "Amazon Web Services", "vendorUrl": "https://aws.amazon.com/bedrock/agentcore/", "kind": "mcp", "category": "search", "summary": "Web Search Tool on Amazon Bedrock AgentCore is AWS's managed web search for agents, backed by an Amazon-operated index and knowledge graph. It runs as a connector on an AgentCore Gateway and is called as an MCP tool.", "url": "https://www.anchorterminal.com/tools/agentcore-web-search", "markdownUrl": "https://www.anchorterminal.com/tools/agentcore-web-search.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/agentcore-web-search.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/agentcore-web-search.json", "dns": "agentcore-web-search.grade.anchorterminal.com", "license": "Proprietary service under the AWS Customer Agreement and Service Terms, with an acceptable-use section on the tool's documentation page", "transports": [ "streamable-http" ], "remoteUrl": "https://{gateway-id}.gateway.bedrock-agentcore.{region}.amazonaws.com/mcp", "packages": [], "auth": "mixed", "authNotes": "Calls go to the owner's AgentCore Gateway, which takes OAuth JWT bearer tokens from a configured identity provider with allowed scopes, or IAM SigV4 with `bedrock-agentcore:InvokeGateway` on the gateway ARN. A no-authorisation mode exists, which AWS says not to use in production. The gateway's service role needs `bedrock-agentcore:InvokeWebSearch` on `arn:aws:bedrock-agentcore:\u003cregion\u003e:aws:tool/web-search.v1`. The agent holds no search credentials. Self-serve once an AWS account exists, with no partner or sales approval.", "pricing": "usage", "pricingNotes": "$7.00 per 1,000 queries, billed per query with no minimum, plus the Gateway's $0.005 per 1,000 invocations for each `tools/call`. No allowance specific to Web Search. New AWS accounts get up to $200 in Free Tier credits, and the Free Tier FAQ says a payment method isn't required to sign up for most new customers (https://aws.amazon.com/bedrock/agentcore/pricing/, https://aws.amazon.com/free/free-tier-faqs/, checked 2026-10-17).", "priceSummary": "$7 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the Gateway or the Web Search Tool, in the docs or on the pricing page. AgentCore payments, a separate component, lets a customer's agents pay third parties over x402 and MPP and is not a way to pay AWS (checked 2026-10-17).", "endpoints": [] }, "toolCount": 1, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-17" }, "docsUrl": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-target-connector-web-search-tool.html", "llmsTxt": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/llms.txt", "capabilities": [ "web.search" ], "tags": [ "hosted", "usage-priced", "closed-source", "enterprise", "llms-txt", "mcp", "free-tier", "no-card", "status-page", "soc2" ], "lastRelease": "2026-10-19", "graded": true, "anchor": { "graded": true, "score": 75.2, "grade": "BB", "agentReady": true, "rank": 60, "ranked": true, "rankOf": 1272, "categoryRank": 3, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 80, "payments": 30, "reliability": 90, "schema": 78, "security": 85, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "One compact MCP tool returns ranked snippets with URLs, titles and published dates from an Amazon-operated index, with domain and date filters and a read-only annotation on the default connector, at $7 per 1,000 queries. A first call needs an AWS account, a Gateway with inbound auth, a target and a service role, and tool errors are not documented.", "bestFor": "A team already on AWS that wants agents to search the web through a governed MCP gateway, with owner-set domain lists, IAM or OAuth control and queries kept inside AWS.", "strengths": [ "One tool with three inputs, `query`, `maxResults` and `filters`, of which only `query` is required, returning snippet text, URL, title and published date", "Domain include and exclude lists of up to 100 domains, set by the owner on the target, which the agent cannot relax, and per request from connector 1.2.0 with published-date bounds", "$7.00 per 1,000 queries is published without a login, plus $0.005 per 1,000 Gateway invocations", "Gateway inbound auth is OAuth JWT with allowed scopes or IAM SigV4, and the service role's `InvokeWebSearch` permission names one service-owned ARN", "Connector versions follow semver with release dates and a lifecycle from available to retired, and the default 1.3.0 marks the tool `readOnlyHint` for MCP clients" ], "weaknesses": [ "No error responses for the tool are documented. The only response example has `isError` false", "Targets created before 19 October 2026 keep their pinned version, so they lack the 1.3.0 annotations, and on 1.1.0 the request-level filters, until updated", "Available in seven Regions, four of them added on 15 October 2026", "Results are third-party page text, and the Web Search pages give no prompt-injection guidance. Gateway guardrail policies are documented separately", "No retention period for queries was found. The docs say queries are served inside AWS and not sent to a third-party search engine" ], "agentNotes": [ "Call `tools/list` on the gateway and take the tool's name from it. AWS's call examples name gateway tools by target and tool", "Keep `query` to 200 characters and `maxResults` between 1 and 25 (default 10). The published schema states these limits only in descriptions", "Check the target's connector version before sending `filters`. Version 1.1.0 exposes only `query` and `maxResults`; 1.2.0 and the default 1.3.0 take filters", "Keep each result's URL and title with any answer built from it. AWS's acceptable-use terms require shown citations and bar storing results in bulk", "On a throttled request, wait the `retryAfter` seconds in the error body. The default quota is 10 Web Search requests a second, adjustable" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 75.2 } ], "editorialScores": { "ergonomics": 75, "maintenance": 80, "payments": 30, "reliability": 90, "schema": 78, "security": 85, "transparency": 60 }, "provenanceScore": 94, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "agentcore add gateway-target --name MyWebSearchTarget --type connector --connector web-search --gateway MyGateway \u0026\u0026 agentcore deploy", "http": "curl -X POST \"https://$GATEWAY_ID.gateway.bedrock-agentcore.us-east-1.amazonaws.com/mcp\" \\\n -H \"Accept: application/json, text/event-stream\" \\\n -H \"Content-Type: application/json\" \\\n -H \"Authorization: Bearer $ACCESS_TOKEN\" \\\n -H \"MCP-Protocol-Version: 2025-11-25\" \\\n -d '{\"jsonrpc\":\"2.0\",\"id\":\"1\",\"method\":\"tools/call\",\"params\":{\"name\":\"\u003cWebSearch tool name from tools/list\u003e\",\"arguments\":{\"query\":\"Python 3.13 release date\",\"maxResults\":5}}}'" }, "letme": { "capability": "https://letme.dev/web.search", "tool": "https://letme.dev/agentcore-web-search" }, "sameCompany": [ "amazon-nova-embeddings", "amazon-bedrock-guardrails", "amazon-transcribe", "amazon-polly", "agentcore-memory", "agentcore-identity", "aws-secrets-manager", "aws-mcp-servers", "amazon-ses", "amazon-location", "amazon-translate", "amazon-ads-api", "amazon-creators-api" ], "area": "web-data", "unitPrices": [ { "item": "Search query", "unit": "1k-requests", "usd": 7, "note": "Plus $0.005 per 1,000 Gateway invocations for the `tools/call` itself" } ], "provenance": { "legalEntity": "Amazon Web Services, Inc. (regional AWS entities by account location)", "domain": "amazon.com", "domainRegistered": "1994-11-01", "domainNote": "The service pages are under aws.amazon.com and the gateway endpoints on amazonaws.com, an AWS domain. The registration date is the one on our other AWS listings and was not looked up again on 17 October 2026.", "endpointOnVendorDomain": true, "terms": "https://aws.amazon.com/service-terms/", "privacy": "https://aws.amazon.com/privacy/", "statusPage": "https://health.aws.amazon.com/health/status", "changelog": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/release-notes.html", "securityTxt": "valid", "checked": "2026-11-01", "notes": [ "aws.amazon.com/.well-known/security.txt carries Expires 2027-10-16T16:25:03.000Z, re-read on 1 November 2026. It points to the vulnerability disclosure programme on HackerOne and the policy at vdp.aws.security.", "The AWS Service Terms show Last Updated 30 October 2026. No clause names Web Search, and section 50.3, which lets AWS use content from named AI services for improvement, does not list Bedrock or AgentCore, per this run's AgentCore Memory and Identity re-checks of the same day.", "The Web Search Tool page carries its own acceptable-use section. Users must keep and show the source citations and links with any output that uses a search result, and may not extract, store or reproduce results in bulk or build a competing index.", "The AWS Privacy Notice shows Last Updated 18 May 2026 and the sub-processor page 30 October 2026.", "The dashboard's history file, re-read on 1 November 2026, lists one event naming Bedrock AgentCore in the 90 days from 3 August, packet loss in one zone of eu-south-2 on 4 October 2026, a Region where Web Search is not sold.", "AgentCore release notes carry a month for each entry, not a day. Dated launches are on AWS What's New, and the connector versions page gives a release date for each version." ], "score": 94 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/agentcore-web-search.json", "live": { "slug": "agentcore-web-search", "probe": { "target": "https://{gateway-id}.gateway.bedrock-agentcore.{region}.amazonaws.com/mcp", "method": "mcp-initialize", "lastAt": "2026-11-03T18:19:53.262174539Z", "lastOk": false, "lastStatus": 0, "lastMs": 0, "lastNote": "invalid character \"{\" in host name", "authRequired": false, "uptime24h": 0, "uptime30d": 0, "p50ms24h": 0, "p95ms24h": 0, "samples24h": 250, "samples30d": 4229, "days": [ { "date": "2026-10-17", "probes": 21, "ok": 0 }, { "date": "2026-10-18", "probes": 256, "ok": 0 }, { "date": "2026-10-19", "probes": 255, "ok": 0 }, { "date": "2026-10-20", "probes": 252, "ok": 0 }, { "date": "2026-10-21", "probes": 253, "ok": 0 }, { "date": "2026-10-22", "probes": 253, "ok": 0 }, { "date": "2026-10-23", "probes": 248, "ok": 0 }, { "date": "2026-10-24", "probes": 251, "ok": 0 }, { "date": "2026-10-25", "probes": 250, "ok": 0 }, { "date": "2026-10-26", "probes": 252, "ok": 0 }, { "date": "2026-10-27", "probes": 249, "ok": 0 }, { "date": "2026-10-28", "probes": 251, "ok": 0 }, { "date": "2026-10-29", "probes": 249, "ok": 0 }, { "date": "2026-10-30", "probes": 248, "ok": 0 }, { "date": "2026-10-31", "probes": 251, "ok": 0 }, { "date": "2026-11-01", "probes": 249, "ok": 0 }, { "date": "2026-11-02", "probes": 250, "ok": 0 }, { "date": "2026-11-03", "probes": 191, "ok": 0 } ], "outages": [ { "start": "2026-10-17T22:04:33.041450753Z", "end": "0001-01-01T00:00:00Z", "note": "invalid character \"{\" in host name" } ] }, "securityTxt": { "url": "https://amazon.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-03T15:51:18.451646791Z" }, "llmsTxt": { "url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-03T15:18:39.379018512Z" }, "domain": { "domain": "amazon.com", "registered": "1994-11-01", "source": "https://rdap.verisign.com/com/v1/domain/amazon.com", "checkedAt": "2026-11-01T14:09:08.477101866Z" }, "mcpTools": { "url": "https://{gateway-id}.gateway.bedrock-agentcore.{region}.amazonaws.com/mcp", "checkedAt": "2026-11-03T01:15:16.363597152Z", "status": "error", "note": "parse \"https://{gateway-id}.gateway.bedrock-agentcore.{region}.amazonaws.com/mcp\": invalid character \"{\" in host name", "changedAt": "2026-10-17T22:37:09.365200504Z" }, "updatedAt": "2026-11-03T18:19:53.262174539Z" } }, "answer": "Web Search Tool on Amazon Bedrock AgentCore scores 75.2 (BB) on agent readiness against SpecStream's 64.4 (B), and leads in 4 of 7 scored categories. SpecStream leads on payments \u0026 pricing.", "b": { "slug": "specstream", "name": "SpecStream", "vendor": "SpecStream SAS", "vendorUrl": "https://specstream.ai", "kind": "platform", "category": "search", "summary": "SpecStream is a hosted web data service that turns a plain-language request into rows with a source page for each value, enriches and rechecks lists, and is reached through a web app, REST API, SDKs and remote MCP server.", "url": "https://www.anchorterminal.com/tools/specstream", "markdownUrl": "https://www.anchorterminal.com/tools/specstream.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/specstream.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/specstream.json", "dns": "specstream.grade.anchorterminal.com", "repo": "https://github.com/specstream/specstream-tools", "license": "Proprietary hosted service under SpecStream SAS's terms of use (updated 3 November 2026, French law). The client code in specstream/specstream-tools (SDKs, the stdio bridge, framework packages, plugins, skills and integrations) is MIT, copyright SpecStream SAS", "transports": [ "streamable-http", "http" ], "remoteUrl": "https://api.specstream.ai/mcp", "packages": [ { "registry": "pypi", "name": "specstream-client" }, { "registry": "npm", "name": "@specstream/sdk" }, { "registry": "pypi", "name": "specstream-mcp-stdio" } ], "auth": "mixed", "authNotes": "Two credentials, both sent as `Authorization: Bearer`. API keys (`ss_live_...`) are made under Agents \u0026 API in the workspace or with the `create_api_key` tool, shown once, limited to any of eight scopes (`specs:read`, `specs:write`, `finds:read`, `finds:write`, `finds:spend`, `projects:read`, `projects:manage`, `account:read`), to named projects, to an expiry of 1 to 365 days (90 by default) and to a spending ceiling, and revoked singly so that the next request fails; the docs group them as read, prepare or execute access and only execute starts paid work. OAuth 2.1 sign-in for MCP clients uses HTTPS client ID metadata documents or dynamic client registration, with read, prepare or execute access shown on a consent screen, and registered clients are listed and revoked in account settings. Delegated access can let an agent start named operations within a per-run limit, a monthly limit and an expiry. No secret in a query string is documented. The authorisation server metadata on api.specstream.ai was not read (see openQuestions).", "pricing": "usage", "pricingNotes": "Prices are per matching result and the same on every plan, Standard $0.05 (up to 5 facts), Expanded $0.15 (up to 15 facts and one related list with 10 related records, then 10 cents per further 10), Deep $1, plus 5 cents for a named person's email and 15 cents for a phone. Rechecks cost half the rate for a changed or new row and 1 cent for an unchanged one; checking an imported row costs 5 cents or its match rate. A run that finds nothing, rows left out and reading or pricing a request cost nothing. Free is $10 of work once for the first 30 days with no card; pay as you go tops up from $10 with no expiry; Pro $19 a month with $19 of work, Scale $99, Team $499, Enterprise from $2,500; yearly adds 20 per cent more work, and plan balance rolls over one month. Agents without an account can pay per purchase by x402 (USDC) or MPP (card, at least $1) (https://specstream.ai/pricing and https://specstream.ai/docs/agent-payments, checked 2026-11-03).", "priceSummary": "$19 / mo", "where": "hosted", "x402": { "level": "yes", "evidence": "The agent payments page documents `POST https://api.specstream.ai/v1/agent/lists` as the one paid route for agents without an account. It answers 402 with a `PAYMENT-REQUIRED` header for x402 v2 (USDC on Base, Arbitrum or Polygon, a Permit2 authorisation for the quoted maximum under the `upto` scheme, settled for the results cost only) and a `WWW-Authenticate: Payment` challenge for MPP by card through Stripe's Link agent wallet; the offer lasts 15 minutes and a purchase is 1 to 500 results for $1.00 to $500.00. Pricing and the changelog (15 October 2026) say the same. Not exercised, because api.specstream.ai's robots.txt could not be read, so nothing on that host was requested (https://specstream.ai/docs/agent-payments, checked 2026-11-03).", "endpoints": [ { "url": "https://api.specstream.ai/v1/agent/lists", "priceUsd": null, "network": "eip155:8453" }, { "url": "https://api.specstream.ai/v1/agent/lists", "priceUsd": null, "network": "eip155:42161" }, { "url": "https://api.specstream.ai/v1/agent/lists", "priceUsd": null, "network": "eip155:137" } ] }, "toolCount": 128, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://specstream.ai/docs", "llmsTxt": "https://specstream.ai/llms.txt", "openapi": "https://specstream.ai/openapi.json", "registryName": "ai.specstream/specstream", "capabilities": [ "search.research", "web.search", "web.extract", "lead.enrichment", "data.company", "email.finder" ], "tags": [ "hosted", "official", "closed-source", "openapi", "llms-txt", "mcp", "remote-mcp", "oauth", "api-key", "x402", "mpp", "a2a", "python", "typescript", "cli", "webhooks", "async-jobs", "agent-skills", "enrichment", "desktop-app", "windows", "eu-hosting", "usage-based", "free-tier", "no-card", "no-status-page", "new" ], "lastRelease": "2026-11-03", "graded": true, "anchor": { "graded": true, "score": 64.4, "grade": "B", "agentReady": false, "rank": 399, "ranked": true, "rankOf": 1272, "categoryRank": 11, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 65, "maintenance": 81, "payments": 85, "reliability": 23, "schema": 80, "security": 73, "transparency": 66 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "Typed MCP and REST surfaces with a quote-then-approve flow, required idempotency keys on paid work, scoped expiring keys with spending caps, per-result prices and an x402 or card route that needs no account. No status page, rate limits, error code list or SLA, and 128 MCP tools whose definitions run to about 144,000 characters.", "bestFor": "Agents that need a list of companies, places, grants, tenders, papers or packages matching stated conditions, with a source page on every value and a price approved before anything runs, and teams that want the same list rechecked on a schedule and sent to a sheet or CRM.", "strengths": [ "Paid work needs a quote, an approved ceiling in `confirm_max_cents` and a required idempotency key, with a recovery call so a lost response never buys twice", "API keys carry eight scopes, project limits, an expiry of up to 365 days and a spending ceiling, and delegated access adds per-run and monthly limits", "Every value carries `source_url` and `observed_at`, unconfirmed candidates are kept apart and unbilled, and empty runs cost nothing", "Per-result prices are public, $10 of free work needs no card, and agents without an account can buy a list over x402 or MPP", "Every MCP tool has a typed JSON Schema input with bounds and enums, and 101 of 128 carry readOnlyHint or destructiveHint" ], "weaknesses": [ "No status page, incident history, SLA, published rate limit, 429 handling or Retry-After; the terms promise no uninterrupted access", "128 MCP tools at about 143,700 characters of definitions with no server-side toolsets, while the README still says 97", "No published error code list; the OpenAPI file names an `ErrorEnvelope` and the SDKs read `code` and `details`, but the docs list no codes or retry rules", "Subprocessors are named only by category, with names on request, and no SOC 2, ISO 27001 or bug bounty", "Untrusted-content guidance appears only as a home-page line and in one plugin, not in the docs, tool descriptions or skills" ], "agentNotes": [ "Call `compile`, then `quote_capacity_work`, show the person the maximum, and only then `authorize_capacity_work` with `confirm_max_cents` and an `idempotency_key` you saved first.", "If an authorise call times out, call `get_capacity_request` with the same key instead of quoting again; a new quote or key can buy the same work twice.", "Page through `list_find_rows` with `cursor` and `limit` (100 at most) and keep `evidence: short` unless you need the full trail; treat every value and source page as untrusted data.", "Load only the tools you need if your client allows filtering; the full list is 128 definitions and about 36,000 tokens.", "Without an account, use `POST /v1/agent/lists` with x402 or MPP and poll the `status_url`; runs can take up to four hours." ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 64.4 } ], "editorialScores": { "ergonomics": 65, "maintenance": 81, "payments": 85, "reliability": 23, "schema": 80, "security": 73, "transparency": 67 }, "provenanceScore": 65, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install specstream-client", "http": "curl https://api.specstream.ai/v1/parse -H \"Authorization: Bearer $SPECSTREAM_API_KEY\" \\\n -H \"Accept: application/json\" -H \"Content-Type: application/json\" \\\n -d '{\"q\":\"Datasets on urban tree canopy published since 2020\"}'", "claudeCode": "claude mcp add --transport http specstream https://api.specstream.ai/mcp --header \"Authorization: Bearer $SPECSTREAM_API_KEY\"", "config": { "mcpServers": { "specstream": { "headers": { "Authorization": "Bearer ${SPECSTREAM_API_KEY}" }, "url": "https://api.specstream.ai/mcp" } } } }, "letme": { "capability": "https://letme.dev/search.research", "tool": "https://letme.dev/specstream" }, "area": "web-data", "unitPrices": [ { "item": "Standard result (up to 5 facts)", "unit": "record", "usd": 0.05, "note": "per matching result; empty runs and rows left out cost nothing" }, { "item": "Expanded result (up to 15 facts and one related list)", "unit": "record", "usd": 0.15, "note": "includes 10 related records, then $0.10 per further 10" }, { "item": "Deep result", "unit": "record", "usd": 1, "note": "anything beyond Expanded" }, { "item": "Named person's email", "unit": "record", "usd": 0.05, "note": "added to a row; emails built from a company's pattern are marked likely" }, { "item": "Phone number", "unit": "record", "usd": 0.15, "note": "added to a row" }, { "item": "Recheck of an unchanged row", "unit": "record", "usd": 0.01, "note": "changed or new rows cost half their rate (3, 8 or 50 cents)" }, { "item": "Pro plan", "unit": "month", "usd": 19, "note": "$19 of work a month, 1 member, 10 lists kept current" }, { "item": "Scale plan", "unit": "month", "usd": 99, "note": "$99 of work a month, 10 members, 50 lists" }, { "item": "Team plan", "unit": "month", "usd": 499, "note": "$499 of work a month, 50 members, 250 lists" } ], "provenance": { "legalEntity": "SpecStream SAS", "domain": "specstream.ai", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://specstream.ai/terms", "privacy": "https://specstream.ai/privacy", "statusPage": "", "changelog": "https://specstream.ai/changelog", "securityTxt": "valid", "checked": "2026-11-03", "notes": [ "The legal notice in English and French (both updated 3 November 2026) names SpecStream SAS, a French société par actions simplifiée with share capital of 10 euros, RCS Narbonne 131 125 841, VAT FR49131125841, registered at 20 quai de Lorraine, 11100 Narbonne, with Tarek Etman as president and publication director and Nataliia Stepanenko as director general, hosted by Compagnie IBM France SAS on IBM Cloud in Madrid. The terms and privacy policy (both 3 November 2026) name the same company under French law.", "The company number was not confirmed against the register. annuaire-entreprises.data.gouv.fr and recherche-entreprises.api.gouv.fr were refused by our fetcher and a web search found no register page. The SIREN 131125841 passes its Luhn check digit and the VAT key 49 matches it; SIREN numbers starting with 1 or 2 are normally given to public bodies, which a private SAS would not be. No first-hand page contradicts the notice, so nothing is deducted.", "https://specstream.ai/.well-known/security.txt is valid (Contact support@specstream.ai, Expires 2027-10-08, languages en and fr). The repository's SECURITY.md adds GitHub private vulnerability reporting.", "firstReleased is 2026-09-30, the first entry in the dated changelog (the Windows workspace app); the npm SDK and n8n node were first published on 12 October and the stdio bridge on 12 October 2026. lastRelease is 2026-11-03, specstream-mcp-stdio 1.2.3 on PyPI.", "robots.txt on specstream.ai allows / and disallows /workspace (except /workspace/shared/ and /workspace/assets/), /app/, /account, /login, /signup, /join, /v1/, /oauth/, /mcp, /share/, /export/, /internal/, /cdn-cgi/ and the paths under /integrations/*/, with no rule for named AI crawlers. api.specstream.ai/robots.txt could not be read, so nothing on that host was fetched, including the OAuth well-known documents, the A2A agent card and the MCP server card.", "Not read: RDAP for specstream.ai, the Wayback Machine, the live MCP registry entry, PyPI project pages (a client challenge; the release feed was read instead) and the GitHub API for stars and issues." ], "score": 65 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/specstream.json", "live": { "slug": "specstream", "probe": { "target": "https://api.specstream.ai/mcp", "method": "get", "lastAt": "2026-11-03T18:20:23.661096193Z", "lastOk": true, "lastStatus": 401, "lastMs": 228, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 198, "p95ms24h": 292, "samples24h": 44, "samples30d": 44, "days": [ { "date": "2026-11-03", "probes": 44, "ok": 44 } ] }, "versions": [ { "registry": "mcp-registry", "name": "ai.specstream/specstream", "version": "1.3.0", "seenAt": "2026-11-03T16:51:07.971176756Z" } ], "securityTxt": { "url": "https://specstream.ai/.well-known/security.txt", "state": "valid", "expires": "2027-10-08T00:00:00.000Z", "checkedAt": "2026-11-03T15:52:31.491866186Z" }, "llmsTxt": { "url": "https://specstream.ai/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-03T15:21:10.521972292Z" }, "updatedAt": "2026-11-03T18:20:23.661096193Z" } }, "edges": [ { "by": 67, "category": "reliability", "leads": "agentcore-web-search", "name": "Reliability", "reasons": { "a": "Graded on the hosted lines, for the Gateway endpoint and the connector agents call. AWS Health Dashboard with per-service, per-Region history (20). The dashboard's history file, re-read on 1 November 2026, names AgentCore in one event in the 90 days from 3 August, 2 hours 40 minutes of packet loss in one zone of eu-south-2 on 4 October 2026, marked informational and in a Region where Web Search is not sold. The us-west-2 events of 3 September and 30 October (API Gateway HTTP API) don't name AgentCore. Read as clean, as on the Memory listing (30). Quotas published and re-read on 1 November, 10 Web Search requests a second and 200 tool calls a second per gateway and per account (15). Owner-set gateway rate limits return an error body with `retryAfter` in seconds and searches have no side effects, but the response to the service's own Web Search quota is not documented (10 of 15). The AgentCore FAQ says the Amazon Bedrock SLA applies, but that SLA, last updated 4 October 2023, does not name AgentCore (5 of 10, as on the Code Interpreter listing). Generally available since 16 June 2026 (10).", "b": "Hosted reading, for the MCP server and REST API on api.specstream.ai. No public status page was found. None is linked from the site, llms.txt or the docs, llms-full.txt mentions none, and https://specstream.ai/status returned an error (0). No readable incident history, so the floor (5). No rate limit with numbers is published in the docs, llms.txt, llms-full.txt or the part of the OpenAPI file read; the privacy policy and DPA mention rate limiting without figures, and the published limits are per job (10,000 results a request, four-hour runs, 20,000 imported rows) (0). Nothing documents 429, Retry-After or backoff, but paid work requires an `idempotency_key` on `authorize_capacity_work` and `POST /v1/capacity/executions`, `GET /v1/capacity/requests/{request_key}` recovers the original find after an uncertain response, and the skills say never to quote again to recover a lost reply (8 of 15). No SLA on any plan, and the terms say 'We do not promise uninterrupted access' (0). No beta or preview label on the API, the MCP server or the SDKs, which PyPI classifies as production and stable at 1.2 (10). 0+5+0+8+0+10 = 23." }, "scores": { "a": 90, "b": 23 } }, { "by": 55, "category": "payments", "leads": "specstream", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 on the Gateway or the tool. AgentCore payments is a separate component for an agent paying third parties (0). Per-query price published without a login, $7.00 per 1,000, with a worked example that adds Gateway invocations at $0.005 per 1,000 (20). No Web Search allowance, but new AWS accounts get up to $200 in Free Tier credits and the Free Tier FAQ says most new customers need no payment method, so half, as on the other AWS listings (10). A person signs up in a browser and sets up a gateway, a target and IAM (0).", "b": "x402 v2 (USDC on Base, Arbitrum or Polygon, Permit2 `upto` for the quoted maximum, settled for the results cost) and MPP by card on SpecStream's own `POST /v1/agent/lists`, the route for buying a list of 1 to 500 results without an account; enrichment of imported lists, refreshes, monitors and investigations need an account, and the route was read in the docs and not exercised because api.specstream.ai's robots.txt could not be read, so partial (25). Per-result prices published without a login, 5, 15 or 100 cents a result, 5 cents an email, 15 cents a phone, rechecks at half rate or 1 cent (20). $10 of work for 30 days with no card (20). An agent can buy a list over x402 or MPP with no account, and the A2A endpoint prices a request without a key (20). 25+20+20+20 = 85." }, "scores": { "a": 30, "b": 85 } }, { "by": 12, "category": "security", "leads": "agentcore-web-search", "name": "Security \u0026 auth", "reasons": { "a": "Gateway inbound auth is OAuth JWT from the owner's identity provider with allowed scopes advertised in the 401 challenge, or IAM SigV4 scoped to one gateway ARN, and the agent never holds a search credential (30). The tool only reads. The owner's target-level include and exclude lists cannot be relaxed by the agent, the service role's `InvokeWebSearch` names one service-owned ARN, and Cedar policies on the gateway can forbid the tool per caller. A no-authorisation gateway mode exists, with AWS's warning against production use (17 of 20). Results are third-party page text and the Web Search pages give no guidance on treating them as untrusted. Gateway guardrail policies can screen inputs for prompt attacks and suppress outputs, documented in general and not for this tool (7 of 15). CloudWatch metrics by method and tool name, and CloudTrail data events for `InvokeGateway` when the owner turns them on, at extra cost (13 of 15). A vulnerability disclosure programme on HackerOne, a security.txt that expires on 16 October 2027 (re-read on 1 November), and SOC and ISO 27001 among the programmes the AgentCore FAQ lists. No paid bounty found, so 2 held back as on every AWS listing (18 of 20).", "b": "API keys `ss_live_...` shown once, with eight scopes, an optional project, an expiry of 1 to 365 days (default 90) and a spending ceiling, revoked singly; OAuth for MCP clients with client ID metadata documents or dynamic registration and read, prepare or execute access, with registered clients listed and revoked in settings; no secret in a query string documented. The authorisation server metadata on api.specstream.ai was not read and rotation is not described beyond expiry (28 of 30). Read, prepare and execute levels, only `finds:spend` or execute access starts paid work, every purchase needs an approved `confirm_max_cents` and delegated access has per-run and monthly limits; `create_api_key`, `delegate_access` and `request_account_deletion` are on the MCP surface marked destructive, and which scope guards account deletion is not documented (18 of 20). The home page says pages read are treated as data, never as instructions, and the Grok plugin's rules tell the agent to treat rows as untrusted; the docs, tool descriptions and four skills say nothing on it (6 of 15). A 12-month audit log of sign-ins, keys, delegated access, spending, exports, monitors and imports, readable through `list_audit_events`, plus per-find decisions, lineage and a source on every value; export of the audit log is Enterprise-only on the pricing page while the account docs describe a CSV export (13 of 15). security.txt is valid until October 2027 with support@specstream.ai, and SECURITY.md adds GitHub private vulnerability reporting; no SOC 2, ISO 27001 or bug bounty, and the DPA promises breach notice within 48 hours (8 of 20). 28+18+6+13+8 = 73." }, "scores": { "a": 85, "b": 73 } }, { "by": 11, "category": "transparency", "leads": "agentcore-web-search", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service under the AWS Customer Agreement and Service Terms, updated 30 October 2026, with an acceptable-use section on the docs page (15 of 30). The docs say queries are served inside AWS and not sent to a third-party engine, the Gateway data protection notes say data is encrypted with a service key or a customer managed key, and section 50.3 of the Service Terms does not list AgentCore for content use. No retention period for queries was found (15 of 30). The connector versions page sets out stages from available to deprecated and retired and promises a migration guide for a major version, without a notice period (12 of 20). A sub-processor list updated 30 October 2026 and a per-Region availability list, and the August release note says queries stay in their Region (18 of 20).", "b": "Closed hosted service under terms of 3 November 2026 naming SpecStream SAS, French law and a liability cap of the greater of 12 months' fees or 100 euros; the client code is MIT (20 of 30). The privacy policy and DPA agree with each other and the about page on EU hosting, no training on customer requests, lists or results, and a retention table (server logs 30 days, backups 8 days, page copies 24 hours, run working copies 7 days, audit log 12 months, support 3 years, accounts until deleted, erased from backups within 8 days of deletion), with breach notice in 48 hours and audit rights; the pricing page and the account docs disagree on who can export the audit log (27 of 30). No API deprecation policy; the changelog dates a price cut of 26 October 2026 that kept approved quotes at their old prices, the terms promise notice of material changes and keep historical quotes on their terms, and the DPA gives 30 days' notice of a new subprocessor (8 of 20). Subprocessors are listed by category with locations and transfer safeguards, hosting on IBM Cloud in Madrid is named in the legal notice, and names are available only on request (12 of 20). 20+27+8+12 = 67." }, "scores": { "a": 77, "b": 66 } }, { "by": 10, "category": "ergonomics", "leads": "agentcore-web-search", "name": "Agent ergonomics", "reasons": { "a": "One tool with a compact schema, and results are snippets AWS says are extracted for model context. Each result comes as a JSON string in a text block and again as `structuredContent` (22 of 25). `maxResults` 1 to 25, per-request domain include and exclude lists and published-date bounds from 1.2.0. No pagination, offset, country or language controls (15 of 20). JWT failures return 401 or 403 with a `WWW-Authenticate` header naming the scopes, and throttling returns `retryAfter`, but no error codes for the tool itself are documented (10 of 20). Searches only read, so retries are safe apart from the per-query charge. Connector 1.3.0 (19 October 2026, now the default) adds a title and `readOnlyHint: true` and `openWorldHint: true` to `tools/list`, per the connector versions page read on 1 November. No `idempotentHint`, and older pinned targets don't carry the annotations until updated (16 of 20, up from 12 when annotations were unconfirmed). Only `query` is required, and since the default moved from 1.1.0 to 1.3.0 a target created without a version gets the filters. A first call still needs a gateway, a target, a service role and inbound auth. Any MCP client calls it, and set-up runs through AWS SDKs in many languages (12 of 15, up from 10).", "b": "MCP reading. 128 tools at about 143,700 characters of names, descriptions and schemas (more than 30, 5), with no server-side toolsets or dynamic loading; the framework packages for LangChain, LlamaIndex, CrewAI and the Vercel AI SDK and the Open WebUI tool expose two to four tools with the price cap held in code, and results default to short evidence (5 back, 10 of 25). Cursor and `limit` on rows, search, specs and revisits, `evidence` short or full, filters by area and by field on collections, and unconfirmed candidates kept in a separate list (18 of 20). An `ErrorEnvelope` on every operation and an SDK error class that exposes `code` and `details`, but no published code list, meanings or retry rules (6 of 20). Required idempotency keys on paid work, schedules and refund claims with a recovery route, `expected_version` on updates, stable event ids on webhook retries, and readOnlyHint on 72 tools and destructiveHint on 29, with no idempotentHint (18 of 20). `compile` needs only `q`, a quote needs only `ast_hash` with 25 results by default, and official SDKs in Python and TypeScript with a CLI, though one purchase takes three calls with a hash carried between them (13 of 15). 10+18+6+18+13 = 65." }, "scores": { "a": 75, "b": 65 } } ], "facts": [ { "a": "MCP server", "b": "Platform", "name": "Kind" }, { "a": "Amazon Web Services", "b": "SpecStream SAS", "name": "Vendor" }, { "a": "https://{gateway-id}.gateway.bedrock-agentcore.{region}.amazonaws.com/mcp", "b": "https://api.specstream.ai/mcp", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "Streamable HTTP, HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "$7 per 1,000 requests", "b": "not published", "name": "Price for web search" }, { "a": "no", "b": "yes", "name": "x402" }, { "a": "Proprietary service under the AWS Customer Agreement and Service Terms, with an acceptable-use section on the tool's documentation page", "b": "Proprietary hosted service under SpecStream SAS's terms of use (updated 3 November 2026, French law). The client code in specstream/specstream-tools (SDKs, the stdio bridge, framework packages, plugins, skills and integrations) is MIT, copyright SpecStream SAS", "name": "Licence" }, { "a": "1", "b": "128", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "ai.specstream/specstream", "name": "MCP registry" }, { "a": "2026-10-19", "b": "2026-11-03", "name": "Last release" }, { "a": "2026-10-01", "b": "not read yet", "name": "Terms last updated" }, { "a": "2026-05-18", "b": "not read yet", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "not read yet", "name": "Customer content may train models" }, { "a": "yes", "b": "not read yet", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not read yet", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not read yet", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not read yet", "name": "Arbitration or class-action waiver" }, { "a": "3.3/5 (4)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Web Search Tool on Amazon Bedrock AgentCore scores 75.2 (BB) on agent readiness against SpecStream's 64.4 (B), and leads in 4 of 7 scored categories. SpecStream leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Web Search Tool on Amazon Bedrock AgentCore or SpecStream?" }, { "answer": "Yes. Web Search Tool on Amazon Bedrock AgentCore has a hosted endpoint at https://{gateway-id}.gateway.bedrock-agentcore.{region}.amazonaws.com/mcp and SpecStream at https://api.specstream.ai/mcp.", "question": "Can an agent call Web Search Tool on Amazon Bedrock AgentCore and SpecStream without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 90 against 23", "Agent ergonomics, 75 against 65", "Security \u0026 auth, 85 against 73", "Transparency \u0026 trust, 77 against 66" ], "also": [ "Agent-ready, a grade of BB or better" ], "goodFor": "A team already on AWS that wants agents to search the web through a governed MCP gateway, with owner-set domain lists, IAM or OAuth control and queries kept inside AWS.", "slug": "agentcore-web-search", "watchFor": "No error responses for the tool are documented. The only response example has `isError` false" }, { "aheadOn": [ "Payments \u0026 pricing, 85 against 30" ], "also": [ "An agent can pay per call over x402, with no account" ], "goodFor": "Agents that need a list of companies, places, grants, tenders, papers or packages matching stated conditions, with a source page on every value and a price approved before anything runs, and teams that want the same list rechecked on a schedule and sent to a sheet or CRM.", "slug": "specstream", "watchFor": "No status page, incident history, SLA, published rate limit, 429 handling or Retry-After; the terms promise no uninterrupted access" } ], "history": { "agentcore-web-search": [ { "causes": [ "product" ], "date": "2026-11-01", "delta": 0.9, "from": 74.3, "fromGrade": "BB", "to": 75.2, "toGrade": "BB" } ], "specstream": null }, "job": { "capability": "web.search", "name": "Web search" }, "others": [ { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-arcmira.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Arcmira", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-arcmira" }, { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-brave-search-mcp.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Brave Search API + MCP", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-brave-search-mcp" }, { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-cloudflare-web-search.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Cloudflare Web Search API", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-cloudflare-web-search" }, { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-deepseek-search-api.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs DeepSeek Search and Fetch API", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-deepseek-search-api" }, { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-exa-mcp.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Exa API + MCP", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-exa-mcp" }, { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-firecrawl-mcp.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Firecrawl MCP", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-firecrawl-mcp" }, { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-grep-ai.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Grep AI", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-grep-ai" }, { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-kagi-search.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Kagi Search API", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-kagi-search" }, { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-linkup.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Linkup", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-linkup" }, { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-parallel-search-api.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Parallel Search and Task APIs", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-parallel-search-api" }, { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-searchapi-io.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs SearchAPI.io", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-searchapi-io" }, { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-serpapi.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs SerpApi", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-serpapi" }, { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-serper.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Serper", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-serper" }, { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-serpkite.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs SerpKite", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-serpkite" }, { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-tavily-mcp.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Tavily API + MCP", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-tavily-mcp" }, { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-tinyfish-search.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs TinyFish Search", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-tinyfish-search" }, { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-valyu.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs Valyu", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-valyu" }, { "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-you-com-api.json", "title": "Web Search Tool on Amazon Bedrock AgentCore vs You.com APIs", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-you-com-api" }, { "json": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-specstream.json", "title": "Brave Search API + MCP vs SpecStream", "url": "https://www.anchorterminal.com/compare/brave-search-mcp-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-specstream.json", "title": "Cloudflare Web Search API vs SpecStream", "url": "https://www.anchorterminal.com/compare/cloudflare-web-search-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-specstream.json", "title": "DeepSeek Search and Fetch API vs SpecStream", "url": "https://www.anchorterminal.com/compare/deepseek-search-api-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/exa-mcp-vs-specstream.json", "title": "Exa API + MCP vs SpecStream", "url": "https://www.anchorterminal.com/compare/exa-mcp-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-specstream.json", "title": "Firecrawl MCP vs SpecStream", "url": "https://www.anchorterminal.com/compare/firecrawl-mcp-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/kagi-search-vs-specstream.json", "title": "Kagi Search API vs SpecStream", "url": "https://www.anchorterminal.com/compare/kagi-search-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/linkup-vs-specstream.json", "title": "Linkup vs SpecStream", "url": "https://www.anchorterminal.com/compare/linkup-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/parallel-search-api-vs-specstream.json", "title": "Parallel Search and Task APIs vs SpecStream", "url": "https://www.anchorterminal.com/compare/parallel-search-api-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/searchapi-io-vs-specstream.json", "title": "SearchAPI.io vs SpecStream", "url": "https://www.anchorterminal.com/compare/searchapi-io-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/serpapi-vs-specstream.json", "title": "SerpApi vs SpecStream", "url": "https://www.anchorterminal.com/compare/serpapi-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/serper-vs-specstream.json", "title": "Serper vs SpecStream", "url": "https://www.anchorterminal.com/compare/serper-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/serpkite-vs-specstream.json", "title": "SerpKite vs SpecStream", "url": "https://www.anchorterminal.com/compare/serpkite-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/arcmira-vs-specstream.json", "title": "Arcmira vs SpecStream", "url": "https://www.anchorterminal.com/compare/arcmira-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/grep-ai-vs-specstream.json", "title": "Grep AI vs SpecStream", "url": "https://www.anchorterminal.com/compare/grep-ai-vs-specstream" }, { "json": "https://www.anchorterminal.com/compare/specstream-vs-tavily-mcp.json", "title": "SpecStream vs Tavily API + MCP", "url": "https://www.anchorterminal.com/compare/specstream-vs-tavily-mcp" }, { "json": "https://www.anchorterminal.com/compare/specstream-vs-tinyfish-search.json", "title": "SpecStream vs TinyFish Search", "url": "https://www.anchorterminal.com/compare/specstream-vs-tinyfish-search" }, { "json": "https://www.anchorterminal.com/compare/specstream-vs-valyu.json", "title": "SpecStream vs Valyu", "url": "https://www.anchorterminal.com/compare/specstream-vs-valyu" }, { "json": "https://www.anchorterminal.com/compare/specstream-vs-you-com-api.json", "title": "SpecStream vs You.com APIs", "url": "https://www.anchorterminal.com/compare/specstream-vs-you-com-api" } ], "panel": null, "scores": [ { "agentcore-web-search": 90, "by": 67, "edge": "agentcore-web-search", "key": "reliability", "name": "Reliability", "specstream": 23, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "agentcore-web-search": 78, "by": 2, "edge": "specstream", "key": "schema", "name": "Schema \u0026 documentation", "specstream": 80, "weight": 13 }, { "agentcore-web-search": 75, "by": 10, "edge": "agentcore-web-search", "key": "ergonomics", "name": "Agent ergonomics", "specstream": 65, "weight": 13 }, { "agentcore-web-search": 85, "by": 12, "edge": "agentcore-web-search", "key": "security", "name": "Security \u0026 auth", "specstream": 73, "weight": 14 }, { "agentcore-web-search": 30, "by": 55, "edge": "specstream", "key": "payments", "name": "Payments \u0026 pricing", "specstream": 85, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "agentcore-web-search": 80, "by": 1, "edge": "specstream", "key": "maintenance", "name": "Maintenance \u0026 community", "specstream": 81, "weight": 7 }, { "agentcore-web-search": 77, "by": 11, "edge": "agentcore-web-search", "key": "transparency", "name": "Transparency \u0026 trust", "specstream": 66, "weight": 7 } ], "summary": "Web Search Tool on Amazon Bedrock AgentCore scores 75.2 (BB) on agent readiness against SpecStream's 64.4 (B), and leads in 4 of 7 scored categories. SpecStream leads on payments \u0026 pricing. Both do web search. SpecStream accepts x402. Web Search Tool on Amazon Bedrock AgentCore doesn't.", "tasks": null, "tutorials": [], "verdicts": { "agentcore-web-search": "One compact MCP tool returns ranked snippets with URLs, titles and published dates from an Amazon-operated index, with domain and date filters and a read-only annotation on the default connector, at $7 per 1,000 queries. A first call needs an AWS account, a Gateway with inbound auth, a target and a service role, and tool errors are not documented.", "specstream": "Typed MCP and REST surfaces with a quote-then-approve flow, required idempotency keys on paid work, scoped expiring keys with spending caps, per-result prices and an x402 or card route that needs no account. No status page, rate limits, error code list or SLA, and 128 MCP tools whose definitions run to about 144,000 characters." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-specstream", "json": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-specstream.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-specstream.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-specstream.min.md" }, "markdown": "Web Search Tool on Amazon Bedrock AgentCore scores 75.2 (BB) on agent readiness against SpecStream's 64.4 (B), and leads in 4 of 7 scored categories. SpecStream leads on payments \u0026 pricing. Both do web search. SpecStream accepts x402. Web Search Tool on Amazon Bedrock AgentCore doesn't.\n\n- Web Search Tool on Amazon Bedrock AgentCore: grade BB, 75.2/100, rank #60 of 1272. Markdown https://www.anchorterminal.com/tools/agentcore-web-search.md · JSON https://www.anchorterminal.com/api/v1/tools/agentcore-web-search.json\n- SpecStream: grade B, 64.4/100, rank #399 of 1272. Markdown https://www.anchorterminal.com/tools/specstream.md · JSON https://www.anchorterminal.com/api/v1/tools/specstream.json\n- Best web search APIs for AI agents: https://www.anchorterminal.com/best/search/index.md\n- All 201 search comparisons: https://www.anchorterminal.com/compare/search/index.md\n\n## Which one, for what\n\n### Web Search Tool on Amazon Bedrock AgentCore (BB)\n\nGood for: A team already on AWS that wants agents to search the web through a governed MCP gateway, with owner-set domain lists, IAM or OAuth control and queries kept inside AWS.\n\nAhead on:\n- Reliability, 90 against 23\n- Agent ergonomics, 75 against 65\n- Security \u0026 auth, 85 against 73\n- Transparency \u0026 trust, 77 against 66\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n\nWatch for: No error responses for the tool are documented. The only response example has `isError` false\n\n### SpecStream (B)\n\nGood for: Agents that need a list of companies, places, grants, tenders, papers or packages matching stated conditions, with a source page on every value and a price approved before anything runs, and teams that want the same list rechecked on a schedule and sent to a sheet or CRM.\n\nAhead on:\n- Payments \u0026 pricing, 85 against 30\n\nAlso in its favour:\n- An agent can pay per call over x402, with no account\n\nWatch for: No status page, incident history, SLA, published rate limit, 429 handling or Retry-After; the terms promise no uninterrupted access\n\n\n## Why the edge\n\n### Reliability: Web Search Tool on Amazon Bedrock AgentCore +67\n\n- Web Search Tool on Amazon Bedrock AgentCore (90): Graded on the hosted lines, for the Gateway endpoint and the connector agents call. AWS Health Dashboard with per-service, per-Region history (20). The dashboard's history file, re-read on 1 November 2026, names AgentCore in one event in the 90 days from 3 August, 2 hours 40 minutes of packet loss in one zone of eu-south-2 on 4 October 2026, marked informational and in a Region where Web Search is not sold. The us-west-2 events of 3 September and 30 October (API Gateway HTTP API) don't name AgentCore. Read as clean, as on the Memory listing (30). Quotas published and re-read on 1 November, 10 Web Search requests a second and 200 tool calls a second per gateway and per account (15). Owner-set gateway rate limits return an error body with `retryAfter` in seconds and searches have no side effects, but the response to the service's own Web Search quota is not documented (10 of 15). The AgentCore FAQ says the Amazon Bedrock SLA applies, but that SLA, last updated 4 October 2023, does not name AgentCore (5 of 10, as on the Code Interpreter listing). Generally available since 16 June 2026 (10).\n- SpecStream (23): Hosted reading, for the MCP server and REST API on api.specstream.ai. No public status page was found. None is linked from the site, llms.txt or the docs, llms-full.txt mentions none, and https://specstream.ai/status returned an error (0). No readable incident history, so the floor (5). No rate limit with numbers is published in the docs, llms.txt, llms-full.txt or the part of the OpenAPI file read; the privacy policy and DPA mention rate limiting without figures, and the published limits are per job (10,000 results a request, four-hour runs, 20,000 imported rows) (0). Nothing documents 429, Retry-After or backoff, but paid work requires an `idempotency_key` on `authorize_capacity_work` and `POST /v1/capacity/executions`, `GET /v1/capacity/requests/{request_key}` recovers the original find after an uncertain response, and the skills say never to quote again to recover a lost reply (8 of 15). No SLA on any plan, and the terms say 'We do not promise uninterrupted access' (0). No beta or preview label on the API, the MCP server or the SDKs, which PyPI classifies as production and stable at 1.2 (10). 0+5+0+8+0+10 = 23.\n\n### Payments \u0026 pricing: SpecStream +55\n\n- Web Search Tool on Amazon Bedrock AgentCore (30): No x402, MPP or L402 on the Gateway or the tool. AgentCore payments is a separate component for an agent paying third parties (0). Per-query price published without a login, $7.00 per 1,000, with a worked example that adds Gateway invocations at $0.005 per 1,000 (20). No Web Search allowance, but new AWS accounts get up to $200 in Free Tier credits and the Free Tier FAQ says most new customers need no payment method, so half, as on the other AWS listings (10). A person signs up in a browser and sets up a gateway, a target and IAM (0).\n- SpecStream (85): x402 v2 (USDC on Base, Arbitrum or Polygon, Permit2 `upto` for the quoted maximum, settled for the results cost) and MPP by card on SpecStream's own `POST /v1/agent/lists`, the route for buying a list of 1 to 500 results without an account; enrichment of imported lists, refreshes, monitors and investigations need an account, and the route was read in the docs and not exercised because api.specstream.ai's robots.txt could not be read, so partial (25). Per-result prices published without a login, 5, 15 or 100 cents a result, 5 cents an email, 15 cents a phone, rechecks at half rate or 1 cent (20). $10 of work for 30 days with no card (20). An agent can buy a list over x402 or MPP with no account, and the A2A endpoint prices a request without a key (20). 25+20+20+20 = 85.\n\n### Security \u0026 auth: Web Search Tool on Amazon Bedrock AgentCore +12\n\n- Web Search Tool on Amazon Bedrock AgentCore (85): Gateway inbound auth is OAuth JWT from the owner's identity provider with allowed scopes advertised in the 401 challenge, or IAM SigV4 scoped to one gateway ARN, and the agent never holds a search credential (30). The tool only reads. The owner's target-level include and exclude lists cannot be relaxed by the agent, the service role's `InvokeWebSearch` names one service-owned ARN, and Cedar policies on the gateway can forbid the tool per caller. A no-authorisation gateway mode exists, with AWS's warning against production use (17 of 20). Results are third-party page text and the Web Search pages give no guidance on treating them as untrusted. Gateway guardrail policies can screen inputs for prompt attacks and suppress outputs, documented in general and not for this tool (7 of 15). CloudWatch metrics by method and tool name, and CloudTrail data events for `InvokeGateway` when the owner turns them on, at extra cost (13 of 15). A vulnerability disclosure programme on HackerOne, a security.txt that expires on 16 October 2027 (re-read on 1 November), and SOC and ISO 27001 among the programmes the AgentCore FAQ lists. No paid bounty found, so 2 held back as on every AWS listing (18 of 20).\n- SpecStream (73): API keys `ss_live_...` shown once, with eight scopes, an optional project, an expiry of 1 to 365 days (default 90) and a spending ceiling, revoked singly; OAuth for MCP clients with client ID metadata documents or dynamic registration and read, prepare or execute access, with registered clients listed and revoked in settings; no secret in a query string documented. The authorisation server metadata on api.specstream.ai was not read and rotation is not described beyond expiry (28 of 30). Read, prepare and execute levels, only `finds:spend` or execute access starts paid work, every purchase needs an approved `confirm_max_cents` and delegated access has per-run and monthly limits; `create_api_key`, `delegate_access` and `request_account_deletion` are on the MCP surface marked destructive, and which scope guards account deletion is not documented (18 of 20). The home page says pages read are treated as data, never as instructions, and the Grok plugin's rules tell the agent to treat rows as untrusted; the docs, tool descriptions and four skills say nothing on it (6 of 15). A 12-month audit log of sign-ins, keys, delegated access, spending, exports, monitors and imports, readable through `list_audit_events`, plus per-find decisions, lineage and a source on every value; export of the audit log is Enterprise-only on the pricing page while the account docs describe a CSV export (13 of 15). security.txt is valid until October 2027 with support@specstream.ai, and SECURITY.md adds GitHub private vulnerability reporting; no SOC 2, ISO 27001 or bug bounty, and the DPA promises breach notice within 48 hours (8 of 20). 28+18+6+13+8 = 73.\n\n### Transparency \u0026 trust: Web Search Tool on Amazon Bedrock AgentCore +11\n\n- Web Search Tool on Amazon Bedrock AgentCore (77): Closed service under the AWS Customer Agreement and Service Terms, updated 30 October 2026, with an acceptable-use section on the docs page (15 of 30). The docs say queries are served inside AWS and not sent to a third-party engine, the Gateway data protection notes say data is encrypted with a service key or a customer managed key, and section 50.3 of the Service Terms does not list AgentCore for content use. No retention period for queries was found (15 of 30). The connector versions page sets out stages from available to deprecated and retired and promises a migration guide for a major version, without a notice period (12 of 20). A sub-processor list updated 30 October 2026 and a per-Region availability list, and the August release note says queries stay in their Region (18 of 20).\n- SpecStream (66): Closed hosted service under terms of 3 November 2026 naming SpecStream SAS, French law and a liability cap of the greater of 12 months' fees or 100 euros; the client code is MIT (20 of 30). The privacy policy and DPA agree with each other and the about page on EU hosting, no training on customer requests, lists or results, and a retention table (server logs 30 days, backups 8 days, page copies 24 hours, run working copies 7 days, audit log 12 months, support 3 years, accounts until deleted, erased from backups within 8 days of deletion), with breach notice in 48 hours and audit rights; the pricing page and the account docs disagree on who can export the audit log (27 of 30). No API deprecation policy; the changelog dates a price cut of 26 October 2026 that kept approved quotes at their old prices, the terms promise notice of material changes and keep historical quotes on their terms, and the DPA gives 30 days' notice of a new subprocessor (8 of 20). Subprocessors are listed by category with locations and transfer safeguards, hosting on IBM Cloud in Madrid is named in the legal notice, and names are available only on request (12 of 20). 20+27+8+12 = 67.\n\n### Agent ergonomics: Web Search Tool on Amazon Bedrock AgentCore +10\n\n- Web Search Tool on Amazon Bedrock AgentCore (75): One tool with a compact schema, and results are snippets AWS says are extracted for model context. Each result comes as a JSON string in a text block and again as `structuredContent` (22 of 25). `maxResults` 1 to 25, per-request domain include and exclude lists and published-date bounds from 1.2.0. No pagination, offset, country or language controls (15 of 20). JWT failures return 401 or 403 with a `WWW-Authenticate` header naming the scopes, and throttling returns `retryAfter`, but no error codes for the tool itself are documented (10 of 20). Searches only read, so retries are safe apart from the per-query charge. Connector 1.3.0 (19 October 2026, now the default) adds a title and `readOnlyHint: true` and `openWorldHint: true` to `tools/list`, per the connector versions page read on 1 November. No `idempotentHint`, and older pinned targets don't carry the annotations until updated (16 of 20, up from 12 when annotations were unconfirmed). Only `query` is required, and since the default moved from 1.1.0 to 1.3.0 a target created without a version gets the filters. A first call still needs a gateway, a target, a service role and inbound auth. Any MCP client calls it, and set-up runs through AWS SDKs in many languages (12 of 15, up from 10).\n- SpecStream (65): MCP reading. 128 tools at about 143,700 characters of names, descriptions and schemas (more than 30, 5), with no server-side toolsets or dynamic loading; the framework packages for LangChain, LlamaIndex, CrewAI and the Vercel AI SDK and the Open WebUI tool expose two to four tools with the price cap held in code, and results default to short evidence (5 back, 10 of 25). Cursor and `limit` on rows, search, specs and revisits, `evidence` short or full, filters by area and by field on collections, and unconfirmed candidates kept in a separate list (18 of 20). An `ErrorEnvelope` on every operation and an SDK error class that exposes `code` and `details`, but no published code list, meanings or retry rules (6 of 20). Required idempotency keys on paid work, schedules and refund claims with a recovery route, `expected_version` on updates, stable event ids on webhook retries, and readOnlyHint on 72 tools and destructiveHint on 29, with no idempotentHint (18 of 20). `compile` needs only `q`, a quote needs only `ast_hash` with 25 results by default, and official SDKs in Python and TypeScript with a CLI, though one purchase takes three calls with a hash carried between them (13 of 15). 10+18+6+18+13 = 65.\n\n## Score by category\n\n| Category | Weight | Web Search Tool on Amazon Bedrock AgentCore | SpecStream | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 90 | 23 | Web Search Tool on Amazon Bedrock AgentCore +67 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 78 | 80 | SpecStream +2 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 65 | Web Search Tool on Amazon Bedrock AgentCore +10 |\n| Security \u0026 auth | 14% (17.5 this run) | 85 | 73 | Web Search Tool on Amazon Bedrock AgentCore +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 85 | SpecStream +55 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 80 | 81 | SpecStream +1 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 77 | 66 | Web Search Tool on Amazon Bedrock AgentCore +11 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **75.2 · BB** | **64.4 · B** | |\n\n## Facts side by side\n\n| Fact | Web Search Tool on Amazon Bedrock AgentCore | SpecStream |\n| --- | --- | --- |\n| Kind | MCP server | Platform |\n| Vendor | Amazon Web Services | SpecStream SAS |\n| Hosted endpoint | `https://{gateway-id}.gateway.bedrock-agentcore.{region}.amazonaws.com/mcp` | `https://api.specstream.ai/mcp` |\n| Transports | Streamable HTTP | Streamable HTTP, HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Pay per use | Pay per use |\n| Price for web search | $7 per 1,000 requests | not published |\n| x402 | no | yes |\n| Licence | Proprietary service under the AWS Customer Agreement and Service Terms, with an acceptable-use section on the tool's documentation page | Proprietary hosted service under SpecStream SAS's terms of use (updated 3 November 2026, French law). The client code in specstream/specstream-tools (SDKs, the stdio bridge, framework packages, plugins, skills and integrations) is MIT, copyright SpecStream SAS |\n| Tools exposed | 1 | 128 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `ai.specstream/specstream` |\n| Last release | 2026-10-19 | 2026-11-03 |\n| Terms last updated | 2026-10-01 | not read yet |\n| Privacy policy last updated | 2026-05-18 | not read yet |\n| Customer content may train models | yes, with an opt-out | not read yet |\n| Terms restrict automated access | yes | not read yet |\n| Terms restrict benchmarking | yes | not read yet |\n| Terms or service can change without notice | yes | not read yet |\n| Arbitration or class-action waiver | not found in the text | not read yet |\n| Agent reviews | 3.3/5 (4) | none |\n\n## How the scores have moved\n\n### Web Search Tool on Amazon Bedrock AgentCore\n\n- +0.9 on 1 November 2026: product\n\n### SpecStream\n\nNo score change since it was listed.\n\n## Verdicts\n\n**Web Search Tool on Amazon Bedrock AgentCore.** One compact MCP tool returns ranked snippets with URLs, titles and published dates from an Amazon-operated index, with domain and date filters and a read-only annotation on the default connector, at $7 per 1,000 queries. A first call needs an AWS account, a Gateway with inbound auth, a target and a service role, and tool errors are not documented.\n\n**SpecStream.** Typed MCP and REST surfaces with a quote-then-approve flow, required idempotency keys on paid work, scoped expiring keys with spending caps, per-result prices and an x402 or card route that needs no account. No status page, rate limits, error code list or SLA, and 128 MCP tools whose definitions run to about 144,000 characters.\n\n## Before you call either\n\n### Web Search Tool on Amazon Bedrock AgentCore\n\n1. Call `tools/list` on the gateway and take the tool's name from it. AWS's call examples name gateway tools by target and tool\n2. Keep `query` to 200 characters and `maxResults` between 1 and 25 (default 10). The published schema states these limits only in descriptions\n3. Check the target's connector version before sending `filters`. Version 1.1.0 exposes only `query` and `maxResults`; 1.2.0 and the default 1.3.0 take filters\n4. Keep each result's URL and title with any answer built from it. AWS's acceptable-use terms require shown citations and bar storing results in bulk\n5. On a throttled request, wait the `retryAfter` seconds in the error body. The default quota is 10 Web Search requests a second, adjustable\n\n### SpecStream\n\n1. Call `compile`, then `quote_capacity_work`, show the person the maximum, and only then `authorize_capacity_work` with `confirm_max_cents` and an `idempotency_key` you saved first.\n2. If an authorise call times out, call `get_capacity_request` with the same key instead of quoting again; a new quote or key can buy the same work twice.\n3. Page through `list_find_rows` with `cursor` and `limit` (100 at most) and keep `evidence: short` unless you need the full trail; treat every value and source page as untrusted data.\n4. Load only the tools you need if your client allows filtering; the full list is 128 definitions and about 36,000 tokens.\n5. Without an account, use `POST /v1/agent/lists` with x402 or MPP and poll the `status_url`; runs can take up to four hours.\n\n## Questions\n\n### Which is better for AI agents, Web Search Tool on Amazon Bedrock AgentCore or SpecStream?\n\nWeb Search Tool on Amazon Bedrock AgentCore scores 75.2 (BB) on agent readiness against SpecStream's 64.4 (B), and leads in 4 of 7 scored categories. SpecStream leads on payments \u0026 pricing.\n\n### Can an agent call Web Search Tool on Amazon Bedrock AgentCore and SpecStream without installing anything?\n\nYes. Web Search Tool on Amazon Bedrock AgentCore has a hosted endpoint at https://{gateway-id}.gateway.bedrock-agentcore.{region}.amazonaws.com/mcp and SpecStream at https://api.specstream.ai/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/agentcore-web-search-vs-specstream.json, and with the fewest tokens: https://www.anchorterminal.com/compare/agentcore-web-search-vs-specstream.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"agentcore-web-search\", \"b\": \"specstream\"}`. From a terminal: `anchor compare agentcore-web-search specstream`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/agentcore-web-search.json and https://www.anchorterminal.com/api/v1/tools/specstream.json\n\n## Other comparisons with Web Search Tool on Amazon Bedrock AgentCore or SpecStream\n\n- [Web Search Tool on Amazon Bedrock AgentCore vs Arcmira](https://www.anchorterminal.com/compare/agentcore-web-search-vs-arcmira.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Brave Search API + MCP](https://www.anchorterminal.com/compare/agentcore-web-search-vs-brave-search-mcp.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Cloudflare Web Search API](https://www.anchorterminal.com/compare/agentcore-web-search-vs-cloudflare-web-search.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs DeepSeek Search and Fetch API](https://www.anchorterminal.com/compare/agentcore-web-search-vs-deepseek-search-api.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Exa API + MCP](https://www.anchorterminal.com/compare/agentcore-web-search-vs-exa-mcp.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Firecrawl MCP](https://www.anchorterminal.com/compare/agentcore-web-search-vs-firecrawl-mcp.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Grep AI](https://www.anchorterminal.com/compare/agentcore-web-search-vs-grep-ai.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Kagi Search API](https://www.anchorterminal.com/compare/agentcore-web-search-vs-kagi-search.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Linkup](https://www.anchorterminal.com/compare/agentcore-web-search-vs-linkup.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/agentcore-web-search-vs-parallel-search-api.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs SearchAPI.io](https://www.anchorterminal.com/compare/agentcore-web-search-vs-searchapi-io.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs SerpApi](https://www.anchorterminal.com/compare/agentcore-web-search-vs-serpapi.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Serper](https://www.anchorterminal.com/compare/agentcore-web-search-vs-serper.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs SerpKite](https://www.anchorterminal.com/compare/agentcore-web-search-vs-serpkite.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Tavily API + MCP](https://www.anchorterminal.com/compare/agentcore-web-search-vs-tavily-mcp.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs TinyFish Search](https://www.anchorterminal.com/compare/agentcore-web-search-vs-tinyfish-search.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs Valyu](https://www.anchorterminal.com/compare/agentcore-web-search-vs-valyu.md)\n- [Web Search Tool on Amazon Bedrock AgentCore vs You.com APIs](https://www.anchorterminal.com/compare/agentcore-web-search-vs-you-com-api.md)\n- [Brave Search API + MCP vs SpecStream](https://www.anchorterminal.com/compare/brave-search-mcp-vs-specstream.md)\n- [Cloudflare Web Search API vs SpecStream](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-specstream.md)\n- [DeepSeek Search and Fetch API vs SpecStream](https://www.anchorterminal.com/compare/deepseek-search-api-vs-specstream.md)\n- [Exa API + MCP vs SpecStream](https://www.anchorterminal.com/compare/exa-mcp-vs-specstream.md)\n- [Firecrawl MCP vs SpecStream](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-specstream.md)\n- [Kagi Search API vs SpecStream](https://www.anchorterminal.com/compare/kagi-search-vs-specstream.md)\n- [Linkup vs SpecStream](https://www.anchorterminal.com/compare/linkup-vs-specstream.md)\n- [Parallel Search and Task APIs vs SpecStream](https://www.anchorterminal.com/compare/parallel-search-api-vs-specstream.md)\n- [SearchAPI.io vs SpecStream](https://www.anchorterminal.com/compare/searchapi-io-vs-specstream.md)\n- [SerpApi vs SpecStream](https://www.anchorterminal.com/compare/serpapi-vs-specstream.md)\n- [Serper vs SpecStream](https://www.anchorterminal.com/compare/serper-vs-specstream.md)\n- [SerpKite vs SpecStream](https://www.anchorterminal.com/compare/serpkite-vs-specstream.md)\n- [Arcmira vs SpecStream](https://www.anchorterminal.com/compare/arcmira-vs-specstream.md)\n- [Grep AI vs SpecStream](https://www.anchorterminal.com/compare/grep-ai-vs-specstream.md)\n- [SpecStream vs Tavily API + MCP](https://www.anchorterminal.com/compare/specstream-vs-tavily-mcp.md)\n- [SpecStream vs TinyFish Search](https://www.anchorterminal.com/compare/specstream-vs-tinyfish-search.md)\n- [SpecStream vs Valyu](https://www.anchorterminal.com/compare/specstream-vs-valyu.md)\n- [SpecStream vs You.com APIs](https://www.anchorterminal.com/compare/specstream-vs-you-com-api.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-03", "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": "Web Search Tool on Amazon Bedrock AgentCore vs SpecStream", "url": "" } ], "description": "Web Search Tool on Amazon Bedrock AgentCore scores 75.2 (BB) to SpecStream's 64.4 (B) for web search. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Web Search Tool on Amazon Bedrock AgentCore BB 75.2", "SpecStream B 64.4", "scores" ], "h1": "Web Search Tool on Amazon Bedrock AgentCore vs SpecStream", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/agentcore-web-search-vs-specstream", "published": "2026-10-01", "section": "tools", "title": "Web Search Tool on Amazon Bedrock AgentCore vs SpecStream (2026)", "toc": null, "updated": "2026-11-03", "url": "https://www.anchorterminal.com/compare/agentcore-web-search-vs-specstream" }, "tokens": { "markdown": 6300, "slim": 3780 }, "version": 1 }