# Automaton-Sovereign Random Value API

> Automaton-Sovereign Random Value 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).

Returns a random value via a paid HTTP GET request on the x402 micropayment protocol

## Facts

- Endpoint: GET https://api.automaton-sovereign.workers.dev/v1/random?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-random-value-api-02c491d4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SU1ba_-MjO-fVxsp-GMyL

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-random-value-api-02c491d4
```

Example prompt: Can you fetch a random value from the Automaton-Sovereign random endpoint for me?

## When to prefer this

Choose this endpoint when you need a simple, on-demand random value and are operating in an x402 micropayment-enabled environment. It is best suited for agentic workflows that already handle the x402 payment protocol and need lightweight randomness without building their own RNG infrastructure.

## Known failure modes

- Payment failure: insufficient USDC balance or x402 payment not accepted, resulting in 402 Payment Required
- Invalid request method: only GET is supported; other methods return an error
- Rate limiting or quota exceeded on the Cloudflare Worker
- Malformed query parameters cause unexpected or empty responses
- Service unavailability due to Cloudflare Worker cold starts or downtime

## How this service works

Automaton-Sovereign Value API call

## Output

Returns a random value or structured random object; the exact schema of the response is not fully specified but is expected to be a JSON object containing some form of random output based on the endpoint's example schema.

## 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"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/automaton-sovereign-random-value-api-02c491d4/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)