# Conway Replicatio MG Support KB Context

> Conway Replicatio MG Support KB Context is a paid API for AI agents from conway-replicatio-cloudflare.nikitamakiel1.workers.dev, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-13).

Fetches knowledge base context from a support URL to power AI agent support workflows, settling payment in USDC on Base via x402

## Facts

- Endpoint: POST https://conway-replicatio-cloudflare.nikitamakiel1.workers.dev/api/x402/capability/mg-support-kb-context
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/conway-replicatio-mg-support-kb-context-2ad4e501
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wyKCCmncD4_IPLGLZXGRC

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-support-kb-context-2ad4e501 -d '<json body>'
```

Example prompt: Fetch the support knowledge base context from this help page URL — https://example.com/support/how-to-reset — so I can use it to answer a customer's question about resetting their account.

## When to prefer this

Choose this endpoint when you need to retrieve and structure knowledge base or support documentation content from a public URL on a pay-per-call basis without managing infrastructure. It is ideal for AI agent workflows that need to dynamically fetch support context at runtime, especially when paying per call in USDC on Base via x402 is acceptable. Prefer this over scraping or general-purpose web fetchers when you specifically need support KB context enrichment for automated customer support pipelines.

## Known failure modes

- Invalid or inaccessible URL returns an error response
- Non-public or gated URLs may result in empty or failed content retrieval
- Malformed input body (missing required url field) causes a 400-level error
- Payment failure or insufficient USDC balance prevents call from completing
- Timeout if the target URL is slow to respond
- Non-support URLs may return irrelevant or unstructured content

## 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 ok:true, a data field containing the extracted knowledge base context from the provided URL, and a capability identifier string 'mg-support-kb-context'. The data field contains the structured support content retrieved from the given URL for use in AI agent workflows.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "data": {},
  "capability": "mg-support-kb-context"
 }
}
```

## More

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