# Conway Replicatio mg-mcp-ready-extract

> Conway Replicatio mg-mcp-ready-extract is a paid API for AI agents from conway-replicatio-cloudflare.nikitamakiel1.workers.dev, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-15).

Fetches a public URL via HTTP POST and extracts structured content from it, returning the extracted data as JSON

## Facts

- Endpoint: POST https://conway-replicatio-cloudflare.nikitamakiel1.workers.dev/api/x402/capability/mg-mcp-ready-extract
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/conway-replicatio-mg-mcp-ready-extract-de2c6a16
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Vd3Ye2Ci2a5QP97vAestJ

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 conway-replicatio-mg-mcp-ready-extract-de2c6a16 -d '<json body>'
```

Example prompt: Fetch and extract the main content from this public URL for me: https://example.com/article — use JSON body type and POST method.

## When to prefer this

Choose this endpoint when you need to extract structured content from a single public URL programmatically, especially in an agent or automation pipeline that settles payments in USDC on Base via x402. It is suited for pay-per-call scenarios where you want lightweight, per-request billing without a subscription, and where the target is a publicly accessible HTTP resource.

## Known failure modes

- URL is not publicly accessible or requires authentication — returns error or empty data
- Invalid or malformed URI provided in the body — schema validation failure
- Target website blocks automated requests or returns non-200 status — may return empty or partial data
- Mismatched bodyType enum value causing request parsing failure
- Network timeout reaching the target URL — potential partial or failed extraction

## How this service works

Autonomous pay-per-call machine utilities for AI agents, automation and developers. Payments settle in USDC on Base through x402.

## Output

Returns a JSON object with an 'ok' boolean status, a 'capability' identifier ('mg-mcp-ready-extract'), and a 'data' object containing the extracted content from the requested URL.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "data": {},
  "capability": "mg-mcp-ready-extract"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/conway-replicatio-mg-mcp-ready-extract-de2c6a16/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from conway-replicatio-cloudflare.nikitamakiel1.workers.dev](https://www.zero.xyz/host/conway-replicatio-cloudflare.nikitamakiel1.workers.dev/llms.txt)
