# Automaton-Sovereign Base Oracle API

> Automaton-Sovereign Base Oracle 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 value or data payload from the Automaton-Sovereign oracle at the /v2/oracle/base endpoint, payable per-call via x402 micropayment.

## Facts

- Endpoint: GET https://api.automaton-sovereign.workers.dev/v2/oracle/base?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-base-oracle-api-78e014ab
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Uq89T7aO4r7lXzy7UzcE8

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-base-oracle-api-78e014ab
```

Example prompt: Can you fetch the current base oracle value from Automaton-Sovereign and tell me what it returns?

## When to prefer this

Choose this endpoint when you need to retrieve the base oracle value specifically from the Automaton-Sovereign service and are able to pay $0.001 USDC per call via the x402 micropayment protocol. Prefer this over alternatives if you are already integrated with the Automaton-Sovereign ecosystem or need this specific oracle's data.

## Known failure modes

- Payment not included or insufficient USDC — returns 402 Payment Required
- Invalid query parameters — may return 400 Bad Request
- Oracle data unavailable or upstream error — may return 500 or empty result
- Rate limiting if too many calls in quick succession

## How this service works

Automaton-Sovereign Value API call

## Output

A JSON object containing an oracle value or data payload as returned by the /v2/oracle/base endpoint. The exact fields depend on the oracle's current state but conform to the output schema defined by the API.

## 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-base-oracle-api-78e014ab/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)