Tools

Parallel

The Parallel Search API
View as Markdown

Proxies Parallel’s Search API, with Parallel’s /v1 base folded into the route:

POST /parallel/search   → https://api.parallel.ai/v1/search

POST only. Every control (objective, search_queries, processor, …) travels in the JSON body and is forwarded unchanged.

Parallel’s broader surface (Task, Extract, Chat, Monitor, Find All) is deliberately not exposed — only the synchronous Search API is proxied.

What the gateway injects and strips

  • The x-api-key header is injected, overwriting any client-supplied one.
  • The Authorization header is stripped before forwarding — Parallel has no use for your gateway token.

Example

$curl -X POST "$GATEWAY/parallel/search" \
>  -H "Authorization: Bearer $TOKEN" \
>  -H "Content-Type: application/json" \
>  -d '{"objective": "Find recent news about Cloudflare Workers", "search_queries": ["cloudflare workers news"]}'

The response is Parallel’s JSON, returned unchanged. For request and response fields, follow Parallel’s documentation — the gateway does not alter them.