# Conway Replicatio MG Catalog Evidence

> Conway Replicatio MG Catalog Evidence is a paid API for AI agents from conway-replicatio-cloudflare.nikitamakiel1.workers.dev, paid per call via x402, $0.06/call, status unknown (last checked 2026-09-20).

Fetches and returns catalog evidence data from a given public URL, settling payment in USDC on Base via x402

## Facts

- Endpoint: POST https://conway-replicatio-cloudflare.nikitamakiel1.workers.dev/api/x402/capability/mg-catalog-evidence
- Price: $0.06/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/conway-replicatio-mg-catalog-evidence-2c22ab06
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iGm30ZtTtNC7Oyij7hWOr

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-catalog-evidence-2c22ab06 -d '<json body>'
```

Example prompt: Can you fetch the catalog evidence from this public URL — https://example.com/my-catalog-item — and return whatever evidence data it has?

## When to prefer this

Use this endpoint when you need to programmatically fetch and extract catalog evidence from a known public URL within an AI agent or automation pipeline, especially when USDC micropayment settlement via x402 on Base is already part of your infrastructure. Prefer this over generic HTTP fetch utilities when you specifically want structured catalog evidence output with a normalized response format.

## Known failure modes

- Invalid or non-public URL returns an error response with ok: false
- URL is unreachable or times out, causing a fetch failure
- Malformed request body (missing required fields) returns a validation error
- Payment settlement failure on Base/USDC may cause the call to be rejected before processing
- URL returns non-JSON or unexpected content that cannot be parsed as catalog evidence

## 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 indicating success, a 'data' object containing the catalog evidence extracted from the provided URL, and a 'capability' field confirming the endpoint used ('mg-catalog-evidence').

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "data": {},
  "capability": "mg-catalog-evidence"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/conway-replicatio-mg-catalog-evidence-2c22ab06/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)