# Conway Replicatio MG Procure Decision

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

Sends an HTTP POST request to a specified public URL and returns a procurement decision result via a pay-per-call machine utility

## Facts

- Endpoint: POST https://conway-replicatio-cloudflare.nikitamakiel1.workers.dev/api/x402/capability/mg-procure-decision?utm_source=zero.xyz
- Price: $0.09/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/conway-replicatio-mg-procure-decision-1d599383
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UI8APugK6OWqK-DpZ-v6g

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-decision-1d599383 -d '<json body>'
```

Example prompt: Send a JSON POST request to https://my-procurement-service.example.com/decide on my behalf and bring back the procurement decision result — this is a pay-per-call call that settles in USDC.

## When to prefer this

Choose this endpoint when you need to autonomously dispatch a POST request to a public URL as part of a procurement or decision-making workflow, especially in agent pipelines where pay-per-call micro-payment settlement via USDC on Base is acceptable. Prefer this over general HTTP relay tools when the use case involves procurement decision logic and you want a structured, machine-utility-oriented wrapper.

## Known failure modes

- Invalid or unreachable target URL returns an error response
- Non-public or firewalled URLs may time out or be rejected
- Incorrect bodyType enum value causes a validation error
- Missing required 'url' field in body results in schema rejection
- Payment failure (insufficient USDC) prevents the call from executing
- Target URL returns non-200 status which may propagate as an error

## 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 decision payload from the target URL, and a 'capability' field confirming 'mg-procure-decision'. The agent receives the raw decision result from the proxied endpoint.

## Response schema (JSON Schema)

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

## More

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