# Exa Contents Fetcher (Synapse x402)

> Exa Contents Fetcher (Synapse x402) is a paid API for AI agents from anibalb.duckdns.org, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-31).

Fetches the full text content and metadata of one or more web pages by URL using the Exa content API, paid per call in USDC via x402.

## Facts

- Endpoint: GET https://anibalb.duckdns.org/x402/exa-contents?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/exa-contents-fetcher-synapse-x402-f361020e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GFnFJP37eCCYPiWn3dXLS

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-fetcher-synapse-x402-f361020e
```

Example prompt: Can you fetch the full text content of these URLs for me: https://example.com and https://openai.com/blog — I need the title, body text, and any links on each page.

## When to prefer this

Choose this endpoint when you need clean, readable text extracted from one or more specific URLs without setting up accounts or API keys — especially useful in agentic pipelines that need to read web content on-demand and pay micropayments per call. It is backed by Exa's content API which is tuned for clean text extraction suitable for LLM consumption, making it preferable to raw HTML scrapers when you need structured, readable output.

## Known failure modes

- Invalid or unreachable URL returns empty results or error for that entry
- Paywalled or bot-protected pages may return partial or empty text
- Payment failure via x402 returns 402 status before content is delivered
- Malformed 'urls' query parameter returns a 400 or empty response
- Rate limiting or upstream Exa API outage causes 5xx errors

## How this service works

Public data and utility APIs paid per call in USDC on Base (x402). No accounts, no API keys. 174 routes: crypto/equity data, onchain reads, DNS/email/security intel, geo/weather, x402 payment diagnostics, dev utilities and more.

## Output

Returns a JSON object with a count of results and an array of result objects, each containing the URL, extracted plain text body, page title, and a list of links found on that page.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "urls": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "count": 2,
  "results": [
   {
    "url": "https://example.com",
    "text": "...",
    "links": [],
    "title": "Example Domain"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/exa-contents-fetcher-synapse-x402-f361020e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from anibalb.duckdns.org](https://www.zero.xyz/host/anibalb.duckdns.org/llms.txt)