# Amoraw Echo – Protocol Diagnostic Endpoint

> Amoraw Echo – Protocol Diagnostic Endpoint is a paid API for AI agents from amoraw.xyz, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Returns a bounded JSON echo of the request body, selected safe headers, byte count, and request hash to verify client, payment, and response handling — without reflecting credentials.

## Facts

- Endpoint: POST https://amoraw.xyz/echo
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/amoraw-echo-protocol-diagnostic-endpoint-f50f56bf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KJBmrir9zUrQoVTfsTHhD

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 amoraw-echo-protocol-diagnostic-endpoint-f50f56bf -d '<json body>'
```

Example prompt: Can you send a test JSON body to the Amoraw echo endpoint so I can verify my payment client and request handling are working — I want to see the byte count, request hash, and safe headers echoed back without any credentials showing up?

## When to prefer this

Choose this endpoint when you need to verify that an x402 payment client, HTTP request formatter, or response handler is working correctly before connecting to a real production service. It is ideal for integration testing, debugging agent request pipelines, and confirming that sensitive credentials are not leaking through echo responses. Prefer this over a generic HTTP echo service when you specifically need x402 payment-flow validation in a controlled, safe environment.

## Known failure modes

- Missing required 'input' object — returns validation error
- Unsupported bodyType value — must be 'json', 'form-data', or 'text'
- Method other than POST — not accepted
- Payment not included or insufficient — x402 payment required error
- Malformed JSON body — parse error returned
- Oversized body exceeding bounded limit — rejection or truncation

## How this service works

Protocol diagnostic: returns a bounded JSON body, selected safe headers, byte count and request hash so a buyer can verify client, payment and response handling. Never reflects credentials.

## Output

A JSON object containing: the echoed request body (bounded), a set of selected safe headers (credentials excluded), the byte count of the request, and a hash of the request. This allows the caller to verify correct client behavior, payment handling, and response parsing without security risk.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "properties": {}
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/amoraw-echo-protocol-diagnostic-endpoint-f50f56bf/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from amoraw.xyz](https://www.zero.xyz/host/amoraw.xyz/llms.txt)