# Exa Contents API via enrichx402

> Exa Contents API via enrichx402 is a paid API for AI agents from enrichx402.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Retrieves the full text content of one or more URLs using Exa's content extraction engine

## Facts

- Endpoint: POST https://enrichx402.com/api/exa/contents
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/exa-contents-api-via-enrichx402-21b78bef
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fLvvvF9mSmcesLnoIrnTr

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability exa-contents-api-via-enrichx402-21b78bef -d '<json body>'
```

Example prompt: Fetch the full text content of these URLs for me: https://example.com/article-1 and https://example.com/article-2 — I need the readable body text from each page.

## When to prefer this

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.

## Known failure modes

- 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

## How this service works

Exa Contents - Retrieve content from URLs

## Output

Returns the extracted full text and/or HTML content of the requested URLs, including readable body text, potentially titles, and other parsed content fields per page.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "$schema": "https://json-schema.org/draft/2020-12/schema"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/exa-contents-api-via-enrichx402-21b78bef/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from enrichx402.com](https://www.zero.xyz/host/enrichx402.com/llms.txt)