# Soren EIP-3009 Authorization Echo

> Soren EIP-3009 Authorization Echo is a paid API for AI agents from soren.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).

Decodes and echoes back a signed EIP-3009 payment authorization field-by-field so developers can inspect and debug what the server actually received

## Facts

- Endpoint: GET https://soren.com/v1/echo-payment
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/soren-eip-3009-authorization-echo-ff305db6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_waRgfuf6UTd12fsX-pHTm

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 soren-eip-3009-authorization-echo-ff305db6
```

Example prompt: Can you decode and echo back my signed EIP-3009 authorization so I can see exactly what fields the server received — payer, recipient, value, nonce, and validity window — to figure out where my signature is going wrong?

## When to prefer this

Use this endpoint when debugging EIP-3009 or x402 payment authorization signing issues, especially when the only feedback from a live endpoint is a generic 'invalid' error. It is ideal for development and testing workflows where you need to confirm what the server actually receives from your signed payload. Prefer this over attempting to decode the signature client-side since it shows server-side parsing results directly.

## Known failure modes

- Missing or malformed Authorization header — returns error indicating no valid EIP-3009 payload was found
- Invalid signature encoding — returns error indicating the signature could not be parsed
- Expired validity window — may be echoed back with a flag indicating the authorization is already expired
- Network or server error — standard HTTP 5xx response

## How this service works

Decodes YOUR signed EIP-3009 authorization and hands it back field by field — payer, value, recipient, validity window, nonce — so you can see exactly what the server received. Signing bugs are miserable to debug because the only feedback is usually "invalid"; this shows you which field is wrong. Free simulated failure cases live at https://soren.com/v1/conformance

## Output

A structured breakdown of the decoded EIP-3009 authorization fields as received by the server, including: payer address, recipient address, value, validity window (valid-after and valid-before timestamps), and nonce. Enables developers to identify exactly which field is malformed or missing when debugging signing failures.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/soren-eip-3009-authorization-echo-ff305db6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from soren.com](https://www.zero.xyz/host/soren.com/llms.txt)