# ScrapFly Content Pulse API

> ScrapFly Content Pulse API is a paid API for AI agents from scravfly.vercel.app, paid per call via x402, $0.15/call, status unknown (last checked 2026-09-15).

Analyzes a text input and returns a structured content pulse or sentiment/engagement signal for the given text.

## Facts

- Endpoint: POST https://scravfly.vercel.app/api/content/pulse
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/scrapfly-content-pulse-api-9ecf1d05
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qrrkePvRvomf3zeV3fXGi

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-pulse-api-9ecf1d05 -d '<json body>'
```

Example prompt: Can you run a content pulse analysis on this paragraph: 'Our new product launch exceeded all expectations, driving record sales and rave reviews from customers across all demographics'?

## When to prefer this

Use this endpoint when you need a fast, pay-per-use content pulse or engagement signal on a specific text passage, particularly within an agentic workflow that already uses x402 micropayments on Base chain. Prefer this over general-purpose LLM sentiment calls when you want a structured, consistent API response for content analysis at scale.

## Known failure modes

- Missing required `text` field returns validation error
- Empty string input may return null or error data
- Very long text inputs may time out or be truncated
- Invalid JSON body returns HTTP 400
- Payment failure on x402 Base chain returns 402 Payment Required

## 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 content pulse analysis results for the submitted text — likely including engagement, tone, or quality signals.

## Request schema (JSON Schema)

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

## 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-pulse-api-9ecf1d05/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from scravfly.vercel.app](https://www.zero.xyz/host/scravfly.vercel.app/llms.txt)
