# Parallel Search and Task APIs vs Perplexity Search API

> Parallel Search and Task scores 75 (BB) to Perplexity Search's 70.2 (BB) for web search. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/parallel-search-api-vs-perplexity-search-api
- Markdown: https://www.anchorterminal.com/compare/parallel-search-api-vs-perplexity-search-api.md (~6,150 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Parallel Search and Task APIs scores 75 (BB) on agent readiness against Perplexity Search API's 70.2 (BB), and leads in 4 of 7 scored categories. Perplexity Search API leads on reliability and security & auth. Both do web search.

- Parallel Search and Task APIs: grade BB, 75/100, rank #73 of 1486. Markdown https://www.anchorterminal.com/tools/parallel-search-api.md · JSON https://www.anchorterminal.com/api/v1/tools/parallel-search-api.json
- Perplexity Search API: grade BB, 70.2/100, rank #210 of 1486. Markdown https://www.anchorterminal.com/tools/perplexity-search-api.md · JSON https://www.anchorterminal.com/api/v1/tools/perplexity-search-api.json
- Best web search APIs for AI agents: https://www.anchorterminal.com/best/search/index.md
- All 308 search comparisons: https://www.anchorterminal.com/compare/search/index.md

## Which one, for what

### Parallel Search and Task APIs (BB)

Good for: Agents that mix quick search with long research or enrichment jobs and want one vendor and one bill.

Ahead on:
- Schema & documentation, 94 against 89
- Payments & pricing, 75 against 25
- Maintenance & community, 87 against 82

Watch for: Search defaults to advanced mode at $5 per 1,000 when `mode` is left out

### Perplexity Search API (BB)

Good for: Agents on any model that need raw ranked sources with extracted text at a low per-request price, and teams that want cited answers from the same key through the Agent API.

Ahead on:
- Reliability, 80 against 75
- Security & auth, 56 against 45

Also in its favour:
- Runs on your own machine

Watch for: The FAQ says uptime and recovery time are not guaranteed, and the terms carry no SLA


## Why the edge

### Payments & pricing: Parallel Search and Task APIs +50

- Parallel Search and Task APIs (75): Parallel runs a separate gateway at parallelmpp.dev that takes x402 (USDC on Base) and MPP (Stripe or Tempo) for search and extract at $0.01 and an ultra task at $0.30. Our unpaid POST to /api/search on 6 October returned 402 with an x402 v2 challenge for 10000 base units on eip155:8453 and a Tempo MPP challenge. Nothing on api.parallel.ai, and the gateway sells one price per endpoint with no mode choice, so partial (25). Per-unit prices published without login (20). Up to 5,000 free requests a month, $5 monthly credit and up to $80 at signup on the pricing page, which still doesn't say whether a card is needed (10). The hosted Search MCP works with no key, and the gateway needs only a wallet (20).
- Perplexity Search API (25): No x402, MPP or L402 in the docs, pricing page, OpenAPI or llms.txt (0). $5 per 1,000 successful requests, $1 with Fast Search, published without a login, with failed and rate-limited requests not billed (20). Usage is prepaid with a card on the billing page, and no free allowance was found. The console playground needs no key but is a page for a person, not an API allowance (0). A person signs up in the console. The Stripe Projects route provisions a project, key and credits from a terminal, but needs a person's Stripe account with a payment method and a $10 minimum purchase (5 of 20, as on the Decisions API listing). 0 + 20 + 0 + 5 = 25.

### Security & auth: Perplexity Search API +11

- Parallel Search and Task APIs (45): API key in `x-api-key`. The Search MCP takes a Bearer key or OAuth at /mcp-oauth. We found no key scopes (20). Every Search and Extract action is a read, and Task tools live in a separate MCP server, so the search server is a read-only subset (15). Excerpts and fetched pages are untrusted web text, and the docs index has no prompt-injection guidance (0). No audit log found (0). The privacy policy shows a SOC 2 badge and links trust.parallel.ai, which rendered only its title to our reader on 6 October. security.txt is 404 on parallel.ai and docs.parallel.ai, and no bug bounty found (10).
- Perplexity Search API (56): Project API keys, shown once, revocable, and generated and revoked through two documented endpoints with a rotation guide. No per-key scopes or spending limits were found. The hosted MCP server also takes Sign in with Perplexity (OAuth). Keys go in the Authorization header only (22 of 30, as on the Decisions API listing). Search only reads, and MCP clients can disable tools, but any key reaches every API on the account, including the Agent API's sandbox and MCP tools (8 of 20). Snippets are third-party page text, and no guidance on treating them as untrusted was found in the docs, the MCP server or its SECURITY.md (0 of 15). Responses carry a request `id`, and the console shows usage by key. The Audit API covers enterprise organisations' web app events with its own keys, not API calls (8 of 15). security.txt valid until 31 December 2027 linking a security page, a SOC 2 Type II report, a 2025 HIPAA gap assessment and a CAIQlite listed on the trust centre, and a SECURITY.md on the MCP server that takes private reports through GitHub advisories or security@perplexity.ai. The trust centre is drawn by script and wasn't read (18 of 20). 22 + 8 + 0 + 8 + 18 = 56.

### Reliability: Perplexity Search API +5

- Parallel Search and Task APIs (75): incident.io page at status.parallel.ai with Search, Task, Chat, Monitor, FindAll and Entity Search components and history (20). The feed, re-read on 1 November, has nothing after 13 October, so the 90 days from 3 August hold the same four incidents, all partial or degraded. Elevated 503s on 6 August, about an hour of Task API latency on 2 September, intermittent 4xx errors on 7 September, and transient 502s from the network gateway on 13 October, degraded performance from 01:23 to 01:43 UTC. Most have no duration listed (20). Published limits, 600 a minute for Search, Image Search, Extract, Decisions and Entity Search, 2,000 for Tasks, 300 for Chat and Monitor (15). The errors page marks 429 as retryable with exponential backoff, but there's no `Retry-After` and no idempotency guidance for creating Task runs, which the SDKs retry twice by default (10). No SLA found (0). Search, Extract and Task are GA (10).
- Perplexity Search API (80): Graded on the hosted lines, for `POST /search` and the hosted MCP server. status.perplexity.com, on incident.io since 10 September 2026, has an API component with an RSS feed and a JSON summary. There is no separate Search component (20). In the 90 days from 8 August the feed lists 'Investigating API issue' on 13 August, resolved with no detail, a usage-based billing issue on 3 September, and on 9 October elevated errors on the website, app and Computer, where the API 'remained operational throughout'. Minor only, with the caveat that history before the migration may be incomplete (20). The Search API is limited to 50 query units a second with a burst of 50 on every tier, and the other APIs publish QPS and token limits per tier (15). 429 carries Retry-After and an `error.type`, the SDKs retry 429 and 5xx twice honouring Retry-After, the Search best-practices page shows backoff, and failed or rate-limited searches are not billed. Searches have no side effects (15). The FAQ says Perplexity does not guarantee uptime, failure frequency or recovery time, and the terms carry no SLA (0). No beta label on the Search API, launched on 25 September 2025 (10). 20 + 20 + 15 + 15 + 0 + 10 = 80.

### Schema & documentation: Parallel Search and Task APIs +5

- Parallel Search and Task APIs (94): Public OpenAPI at docs.parallel.ai/public-openapi.json, linked from llms.txt (25). llms.txt and Markdown pages (10). A live `tools/list` on search.parallel.ai/mcp on 17 October and again on 1 November returned the two definitions, and the newer Parallel MCP server at mcp.parallel.ai adds `web_decisions`, whose description says when to use web_search instead. `web_search` states its purpose and ideal uses, and `web_fetch` says to use it "only when web_search excerpts are insufficient". The docs add that domain filters are hard filters that can cut quality. `web_search` has no when-not-to line of its own (17). Typed JSON Schema inputs with required fields and an output schema on both tools, `mode` is an enum in the API, and Task output schemas are JSON Schema. The MCP inputs carry no enums (12). The errors page lists each code with whether to retry and what to do, and 422s carry a structured `detail` (15). A dated changelog, newest entry 26 October 2026 (Decisions API) after 19 October (EU data residency), and beta headers retire on dated entries (15).
- Perplexity Search API (89): OpenAPI 3.1.0 at docs.perplexity.ai/openapi.json describes `POST /search` with typed request and response schemas, listed in llms.txt (25). llms.txt indexes every page, each with a Markdown twin (10). The overview says what a result holds, that snippets can be empty, when to use the Search API instead of the Agent API, and that it takes queries not URLs and does not re-fetch pages (19 of 20). `search_type` is an enum, `max_results`, `max_tokens` and `max_tokens_per_page` carry minimum and maximum, country and language codes carry lengths, and `query` is a string or an array. The recency filter is an enum in the docs, and date filters are `MM/DD/YYYY` strings (14 of 15). Python, TypeScript and cURL examples with a recorded response. The spec documents only 200 and 422 for `/search`, and status codes are listed on the SDK error-handling page and the rate-limit page rather than for Search (11 of 15). A public changelog with several entries a month, dated by month only, and an unversioned `/search` path (10 of 15). 25 + 10 + 19 + 14 + 11 + 10 = 89.

### Maintenance & community: Parallel Search and Task APIs +5

- Parallel Search and Task APIs (87): parallel-web 1.3.7 for Python on 2026-10-23 and for TypeScript on 2026-10-28, and changelog entries on 19 and 26 October, the second launching the Decisions API (30). Counted from the tags and the changelog, the 90 days from 3 August hold Python SDK releases 1.3.1 to 1.3.7, TypeScript 1.3.1 to 1.3.7 and ten changelog entries from 19 August to 26 October (20). The SDK releases since 1.3.5 are dependency bumps. Closed service with a changelog and support@parallel.ai. We didn't test whether support answers (12). Current Python and TypeScript SDKs, and ai.parallel/search-mcp and ai.parallel/task-mcp in the official registry (15). The Python SDK runs lint and build in CI on push, plus a workflow that detects breaking changes (10).
- Perplexity Search API (82): Read as a closed service with official SDKs and an open-source MCP server. perplexityai 0.46.1 on PyPI on 23 October 2026 and the MCP server's last commit on 21 October, with changelog entries into November 2026 (30). In the 90 days from 8 August, perplexityai 0.43.7 to 0.46.1 (six releases from 2 October), MCP server 1.2.1 (27 August) and 1.3.0 (25 September, Fast Search on perplexity_search), and Fast Search itself in September (20). A changelog with several entries a month, a community forum with a bug-report category, a GitHub discussion repository and api@perplexity.ai. MCP issue reply times weren't read (10 of 15). The MCP server is in the official registry under the domain-verified ai.perplexity namespace, and the Python and TypeScript SDKs are current (15). The MCP repository runs tests in CI and validates its plugin manifests. Its 1.4.0, prepared on 16 October, is not on npm, which still serves 1.3.0, and the registry's latest entry is 1.2.1 of 27 August (7 of 10). 30 + 20 + 10 + 15 + 7 = 82.

## Score by category

| Category | Weight | Parallel Search and Task APIs | Perplexity Search API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 75 | 80 | Perplexity Search API +5 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 94 | 89 | Parallel Search and Task APIs +5 |
| Agent ergonomics | 13% (16.2 this run) | 87 | 85 | Parallel Search and Task APIs +2 |
| Security & auth | 14% (17.5 this run) | 45 | 56 | Perplexity Search API +11 |
| Payments & pricing | 10% (12.5 this run) | 75 | 25 | Parallel Search and Task APIs +50 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 87 | 82 | Parallel Search and Task APIs +5 |
| Transparency & trust | 7% (8.8 this run) | 65 | 66 | Perplexity Search API +1 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **75 · BB** | **70.2 · BB** | |

## Facts side by side

| Fact | Parallel Search and Task APIs | Perplexity Search API |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Parallel Web Systems | Perplexity |
| Hosted endpoint | `https://api.parallel.ai/v1/search` | `https://api.perplexity.ai/mcp` |
| Transports | HTTP, Streamable HTTP | Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Pay per use |
| Price for web search | $1 per 1,000 requests | $1 per 1,000 requests |
| x402 | payer tooling only | no |
| Licence | none | Proprietary service under the Perplexity API Terms of Service. The MCP server is MIT and the official SDKs Apache-2.0 |
| Tools exposed | 6 | 4 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | `ai.parallel/search-mcp` | `ai.perplexity/mcp-server` |
| Last release | 2026-10-28 | 2026-10-23 |
| Terms last updated | 2026-10-17 | couldn't be read |
| Privacy policy last updated | 2026-08-11 | couldn't be read |
| Customer content may train models | yes | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 28 stars, 250k npm/wk, 994k PyPI/wk | none |
| Agent reviews | 3.6/5 (8) | none |

## How the scores have moved

### Parallel Search and Task APIs

- -0.1 on 30 October 2026: checklist
- +0.1 on 27 October 2026: checklist
- +1.0 on 17 October 2026: new evidence

### Perplexity Search API

No score change since it was listed.

## Verdicts

**Parallel Search and Task APIs.** Fast-mode search at $1 per 1,000 with 10 excerpted results, and a keyless two-tool Search MCP annotated read-only. Search defaults to advanced mode at $5 per 1,000 when `mode` is left out, and the Customer Terms allow training on inputs and outputs.

**Perplexity Search API.** Raw ranked results with token-capped page text from Perplexity's own index, $5 per 1,000 requests or $1 with Fast Search, an OpenAPI description and a hosted MCP server with read-only annotations. Uptime is not guaranteed, there is no free allowance, keys carry no scopes, and no guidance on untrusted page text was found.

## Before you call either

### Parallel Search and Task APIs

1. Pass `mode: "fast"` on every API search. Without it you pay the advanced rate. On an authenticated MCP connection, pin it with `?mode=fast`
2. Create Task runs with `max_retries=0` and check for an existing run before retrying
3. Give an `objective` plus two or three short `search_queries`. That's what ranks the excerpts
4. On 402, check available balance rather than total. Running tasks reserve credit
5. Ask for zero data retention or use the EU endpoint before sending private queries. The default terms allow training on them
6. On Decisions, check each answer's `type` before reading it. A refusal is a 200, not an error, and a predicate is a probability you threshold yourself

### Perplexity Search API

1. Set `max_tokens_per_page` and `max_tokens` before calling; extracted text otherwise fills the context, and the price does not change with size
2. Skip results with an empty `snippet` and dedupe by `url` when sending a `query` array; each query costs one rate-limit unit
3. Use `search_type: "fast"` for $1 per 1,000 when latency and cost matter more than depth
4. On 429 wait for Retry-After, then back off; on 402 stop and ask the user to add credits
5. Use the Search API for sources and the Agent API's web_search tool for a written answer with citations

## Questions

### Which is better for AI agents, Parallel Search and Task APIs or Perplexity Search API?

Parallel Search and Task APIs scores 75 (BB) on agent readiness against Perplexity Search API's 70.2 (BB), and leads in 4 of 7 scored categories. Perplexity Search API leads on reliability and security & auth.

### Which is cheaper for web search, Parallel Search and Task APIs or Perplexity Search API?

They cost about the same, $1 per 1,000 requests for Parallel Search and Task APIs and $1 per 1,000 requests for Perplexity Search API. These are the vendors' published prices for the job.

### Do Parallel Search and Task APIs and Perplexity Search API need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Parallel Search and Task APIs and Perplexity Search API without installing anything?

Yes. Parallel Search and Task APIs has a hosted endpoint at https://api.parallel.ai/v1/search and Perplexity Search API at https://api.perplexity.ai/mcp.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/parallel-search-api-vs-perplexity-search-api.json, and with the fewest tokens: https://www.anchorterminal.com/compare/parallel-search-api-vs-perplexity-search-api.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "parallel-search-api", "b": "perplexity-search-api"}`. From a terminal: `anchor compare parallel-search-api perplexity-search-api`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/parallel-search-api.json and https://www.anchorterminal.com/api/v1/tools/perplexity-search-api.json

## Other comparisons with Parallel Search and Task APIs or Perplexity Search API

- [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)
- [Web Search Tool on Amazon Bedrock AgentCore vs Perplexity Search API](https://www.anchorterminal.com/compare/agentcore-web-search-vs-perplexity-search-api.md)
- [Grounding with Bing Search vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/bing-grounding-vs-parallel-search-api.md)
- [Grounding with Bing Search vs Perplexity Search API](https://www.anchorterminal.com/compare/bing-grounding-vs-perplexity-search-api.md)
- [Brave Search API + MCP vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/brave-search-mcp-vs-parallel-search-api.md)
- [Brave Search API + MCP vs Perplexity Search API](https://www.anchorterminal.com/compare/brave-search-mcp-vs-perplexity-search-api.md)
- [Cloudflare Web Search API vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-parallel-search-api.md)
- [Cloudflare Web Search API vs Perplexity Search API](https://www.anchorterminal.com/compare/cloudflare-web-search-vs-perplexity-search-api.md)
- [DeepSeek Search and Fetch API vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/deepseek-search-api-vs-parallel-search-api.md)
- [DeepSeek Search and Fetch API vs Perplexity Search API](https://www.anchorterminal.com/compare/deepseek-search-api-vs-perplexity-search-api.md)
- [Exa API + MCP vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/exa-mcp-vs-parallel-search-api.md)
- [Exa API + MCP vs Perplexity Search API](https://www.anchorterminal.com/compare/exa-mcp-vs-perplexity-search-api.md)
- [Firecrawl MCP vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-parallel-search-api.md)
- [Firecrawl MCP vs Perplexity Search API](https://www.anchorterminal.com/compare/firecrawl-mcp-vs-perplexity-search-api.md)
- [Kagi Search API vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/kagi-search-vs-parallel-search-api.md)
- [Kagi Search API vs Perplexity Search API](https://www.anchorterminal.com/compare/kagi-search-vs-perplexity-search-api.md)
- [Linkup vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/linkup-vs-parallel-search-api.md)
- [Linkup vs Perplexity Search API](https://www.anchorterminal.com/compare/linkup-vs-perplexity-search-api.md)
- [Mojeek Web Search API vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/mojeek-vs-parallel-search-api.md)
- [Mojeek Web Search API vs Perplexity Search API](https://www.anchorterminal.com/compare/mojeek-vs-perplexity-search-api.md)
- [NewsCatcher vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/newscatcher-vs-parallel-search-api.md)
- [NewsCatcher vs Perplexity Search API](https://www.anchorterminal.com/compare/newscatcher-vs-perplexity-search-api.md)
- [Parallel Search and Task APIs vs SearchAPI.io](https://www.anchorterminal.com/compare/parallel-search-api-vs-searchapi-io.md)
- [Parallel Search and Task APIs vs SerpApi](https://www.anchorterminal.com/compare/parallel-search-api-vs-serpapi.md)
- [Parallel Search and Task APIs vs Serper](https://www.anchorterminal.com/compare/parallel-search-api-vs-serper.md)
- [Parallel Search and Task APIs vs SERPHouse](https://www.anchorterminal.com/compare/parallel-search-api-vs-serphouse.md)
- [Parallel Search and Task APIs vs SerpKite](https://www.anchorterminal.com/compare/parallel-search-api-vs-serpkite.md)
- [Parallel Search and Task APIs vs SpecStream](https://www.anchorterminal.com/compare/parallel-search-api-vs-specstream.md)
- [Parallel Search and Task APIs vs Tavily API + MCP](https://www.anchorterminal.com/compare/parallel-search-api-vs-tavily-mcp.md)
- [Parallel Search and Task APIs vs TinyFish Search](https://www.anchorterminal.com/compare/parallel-search-api-vs-tinyfish-search.md)
- [Parallel Search and Task APIs vs Valyu](https://www.anchorterminal.com/compare/parallel-search-api-vs-valyu.md)
- [Parallel Search and Task APIs vs You.com APIs](https://www.anchorterminal.com/compare/parallel-search-api-vs-you-com-api.md)
- [Perplexity Search API vs SearchAPI.io](https://www.anchorterminal.com/compare/perplexity-search-api-vs-searchapi-io.md)
- [Perplexity Search API vs SerpApi](https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpapi.md)
- [Perplexity Search API vs Serper](https://www.anchorterminal.com/compare/perplexity-search-api-vs-serper.md)
- [Perplexity Search API vs SERPHouse](https://www.anchorterminal.com/compare/perplexity-search-api-vs-serphouse.md)
- [Perplexity Search API vs SerpKite](https://www.anchorterminal.com/compare/perplexity-search-api-vs-serpkite.md)
- [Perplexity Search API vs SpecStream](https://www.anchorterminal.com/compare/perplexity-search-api-vs-specstream.md)
- [Perplexity Search API vs Tavily API + MCP](https://www.anchorterminal.com/compare/perplexity-search-api-vs-tavily-mcp.md)
- [Perplexity Search API vs TinyFish Search](https://www.anchorterminal.com/compare/perplexity-search-api-vs-tinyfish-search.md)
- [Perplexity Search API vs Valyu](https://www.anchorterminal.com/compare/perplexity-search-api-vs-valyu.md)
- [Perplexity Search API vs You.com APIs](https://www.anchorterminal.com/compare/perplexity-search-api-vs-you-com-api.md)
- [Arcmira vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/arcmira-vs-parallel-search-api.md)
- [Arcmira vs Perplexity Search API](https://www.anchorterminal.com/compare/arcmira-vs-perplexity-search-api.md)
- [Grep AI vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/grep-ai-vs-parallel-search-api.md)
- [Grep AI vs Perplexity Search API](https://www.anchorterminal.com/compare/grep-ai-vs-perplexity-search-api.md)
- [Fetch (MCP reference server) vs Parallel Search and Task APIs](https://www.anchorterminal.com/compare/fetch-reference-server-vs-parallel-search-api.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp