# Automaton-Sovereign Merkle Proof API

> Automaton-Sovereign Merkle Proof API is a paid API for AI agents from api.automaton-sovereign.workers.dev, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-02).

Generates or retrieves a Merkle proof for a given input via the Automaton-Sovereign value API

## Facts

- Endpoint: GET https://api.automaton-sovereign.workers.dev/v2/merkle/prove?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/automaton-sovereign-merkle-proof-api-0ee8810d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yMvFzniLoNmSpbRsG83YQ

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 automaton-sovereign-merkle-proof-api-0ee8810d
```

Example prompt: Can you get a Merkle proof for my data element from the Automaton-Sovereign Merkle prove endpoint so I can cryptographically verify its inclusion in the tree?

## When to prefer this

Choose this endpoint when you need a cryptographic Merkle inclusion proof from the Automaton-Sovereign service specifically — particularly in agentic or blockchain contexts where micro-payment (x402) flows are expected and you need tamper-evident proof of data membership without full dataset disclosure.

## Known failure modes

- Element not found in the tree — returns 404 or empty proof
- Invalid or missing query parameters — returns 400 bad request
- Payment not provided or insufficient — returns 402 Payment Required
- Service unavailable on Cloudflare Workers — returns 503
- Malformed proof output if tree is in an inconsistent state

## How this service works

Automaton-Sovereign Value API call

## Output

Returns a Merkle proof object containing the proof path (sibling hashes), the root hash, and any relevant metadata needed to independently verify that a given element is a member of the Merkle tree.

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object"
    }
   }
  },
  "output": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/automaton-sovereign-merkle-proof-api-0ee8810d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.automaton-sovereign.workers.dev](https://www.zero.xyz/host/api.automaton-sovereign.workers.dev/llms.txt)