Exa Contents API via enrichx402

Choose this endpoint when you have specific URLs and need to retrieve their full readable content, especially after running a search (e.g. via the sibling Exa Search endpoint) and want to hydrate results with actual page text. Prefer this over generic scrapers when you need Exa's content parsing quality and are already operating in an x402 micropayment-enabled agent workflow.

• URL is paywalled or requires authentication — returns empty or partial content
• URL is unreachable or returns 404 — returns error for that URL
• Rate limiting or payment failure — request rejected
• JavaScript-heavy pages may return incomplete content if not rendered
• Invalid URL format — request validation error