# ScrapFly Content Clarify API

> ScrapFly Content Clarify API is a paid API for AI agents from scrapfly.vercel.app, paid per call via x402, $0.1/call, status unknown (last checked 2026-10-24).

Simplifies and clarifies text content to a specified reading level using AI-powered rewriting

## Facts

- Endpoint: POST https://scrapfly.vercel.app/api/content/clarify?utm_source=zero.xyz
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-24
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/scrapfly-content-clarify-api-07639978
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-FB94m3on-Sa7j5M9-Xpv

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 scrapfly-content-clarify-api-07639978 -d '<json body>'
```

Example prompt: Can you clarify this insurance policy paragraph and rewrite it at a 6th grade reading level so our customers can actually understand what they're signing? Here's the text: 'The indemnification clause herein stipulates that the policyholder shall bear no liability for consequential damages arising from third-party negligence...'

## When to prefer this

Choose this endpoint when you need to automatically rewrite text content to be more accessible or match a specific reading level — especially useful in educational, healthcare, legal, or consumer-facing content pipelines where readability is critical. It is better suited than general LLM prompts when you want a pay-per-use, API-first approach with consistent formatting and no need to manage your own model infrastructure.

## Known failure modes

- Empty or missing text field returns a validation error
- Unsupported or unrecognized reading_level value may default or return an error
- Very long text inputs may be truncated or exceed processing limits
- Payment failure via x402 results in 402 response before processing begins
- Ambiguous or multilingual text may produce lower-quality simplification

## How this service works

69 endpoints for data, content generation, and web scraping. Pay per request via x402 on Base chain.

## Output

Returns a JSON object with a success boolean and a data object containing the clarified and simplified version of the input text, rewritten to match the specified reading level.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "text"
 ],
 "properties": {
  "text": {
   "type": "string",
   "description": "text"
  },
  "reading_level": {
   "type": "string",
   "description": "reading_level"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "success"
 ],
 "properties": {
  "data": {
   "type": "object"
  },
  "success": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/scrapfly-content-clarify-api-07639978/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from scrapfly.vercel.app](https://www.zero.xyz/host/scrapfly.vercel.app/llms.txt)