# README to ICP Extractor

> README to ICP Extractor is a paid API for AI agents from api.the402.ai, paid per call via x402, $0.053/call, status unknown (last checked 2026-09-15).

Extracts Ideal Customer Profile (ICP) information from a README file, returning a structured job for async processing

## Facts

- Endpoint: POST https://api.the402.ai/v1/services/svc_83f457536df543d5/purchase
- Price: $0.053/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/readme-to-icp-extractor-fc34e2c2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2SYniC_a_aBTySWUWyjDn

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 readme-to-icp-extractor-fc34e2c2 -d '<json body>'
```

Example prompt: Can you extract the Ideal Customer Profile from this README? Here's the content: 'We built DataPipe for data engineers at mid-size SaaS companies who need to sync Postgres to Snowflake without writing custom ETL pipelines...'

## When to prefer this

Use this endpoint when you need to automatically determine the Ideal Customer Profile from a product's README or documentation, especially when analyzing open-source repositories or SaaS product docs at scale. Prefer this over manual analysis when processing multiple READMEs or when you need structured ICP data for downstream enrichment pipelines.

## Known failure modes

- Missing or empty README content causes job creation to fail
- Malformed or non-markdown input may produce incomplete ICP extraction
- Payment of $0.053 USDC not completed results in 402 Payment Required error
- Service timeout if README is excessively large
- Job status may remain pending if upstream processing queue is busy

## How this service works

Purchase: README to ICP Extractor

## Output

Returns a job_id, status string, and thread_id representing the asynchronous extraction job. The agent can poll or reference the thread_id to retrieve the extracted ICP once processing completes.

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "job_id": {
   "type": "string"
  },
  "status": {
   "type": "string"
  },
  "thread_id": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/readme-to-icp-extractor-fc34e2c2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.the402.ai](https://www.zero.xyz/host/api.the402.ai/llms.txt)