# Conway Replicatio mg-procure-evidence

> Conway Replicatio mg-procure-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-15).

Fetches and retrieves content or evidence from a given public URL via a paid HTTP POST relay, returning structured proof of the response.

## Facts

- Endpoint: POST https://conway-replicatio-cloudflare.nikitamakiel1.workers.dev/api/x402/capability/mg-procure-evidence
- Price: $0.06/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-procure-evidence-be93a584
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9QILdYB-ES6aF4Wd1Psya

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-procure-evidence-be93a584 -d '<json body>'
```

Example prompt: Fetch the content from https://api.example.com/public-data as evidence — use a JSON body type with a POST method and include the URL as the primary source.

## When to prefer this

Choose this endpoint when you need a paid, auditable HTTP fetch of a public URL with structured evidence output, especially in agent workflows requiring proof-of-retrieval or compliance documentation. Prefer it over generic HTTP fetch tools when you need x402 USDC micropayment settlement and a canonical evidence record returned in a consistent JSON envelope.

## Known failure modes

- Invalid or inaccessible URL returns an error or empty data object
- Non-public or restricted URLs may result in access denial
- Malformed input schema (missing required fields: url, type, method, bodyType) causes validation failure
- Payment failure via x402/USDC results in request rejection before processing
- Downstream URL timeout may cause delayed or empty response

## 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, a 'data' object containing the fetched evidence payload from the target URL, and a 'capability' field confirming 'mg-procure-evidence'. The data field holds the structured response retrieved from the provided URL.

## Response schema (JSON Schema)

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

## More

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