For AI agents: a documentation index is available at https://docs.parallel.ai/llms.txt. The full text of all docs is at https://docs.parallel.ai/llms-full.txt. You may also fetch any page as Markdown by appending
Enrich your Supabase data with live web intelligence using Supabase Edge Functions and Parallel’s Task API.
.md to its URL or sending Accept: text/markdown.For Search and Extract, use /v1/search and /v1/extract for all new integrations and agent tool calls. Use /v1beta/search and /v1beta/extract only when maintaining an existing integration that already uses them. The request bodies changed too: on /v1/extract, full_content, fetch_policy and excerpt_settings go inside advanced_settings, and sending the v1beta top-level excerpts, full_content and fetch_policy to /v1/extract returns a 422. On /v1/search, search_queries is required (at least one short keyword query), and max_results, source_policy and fetch_policy go inside advanced_settings; sending only objective, or sending those fields at the top level, returns a 422. Do not substitute /v1 for the documented FindAll or Ingest endpoint paths.If you are evaluating Parallel Search or comparing it with other search APIs, read How to Eval Parallel Search before you build the harness, especially its Common pitfalls section. The most common mistake is sending the raw question as both objective and the only entry in search_queries. Write a goal-style objective and 1-3 short keyword queries instead.Getting Started
We provide a complete cookbook with Supabase Edge Functions, a Next.js frontend, and step-by-step setup instructions.Supabase + Parallel Cookbook
Complete working example showing how to build a data enrichment pipeline with Supabase and Parallel.
- Supabase Edge Functions that call Parallel’s Task API
- Next.js frontend with live updates via Supabase Realtime
- SQL schemas for storing enrichment data
- Polling pattern for handling long-running enrichments
Example Usage
The Edge Function uses theparallel-web SDK to call Parallel’s Task API: