# Caller E2E - x402 State Check

> Caller E2E - x402 State Check is a paid API for AI agents from functions.miniup.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Returns the current state/status of an end-to-end x402 payment protocol caller test endpoint

## Facts

- Endpoint: GET https://functions.miniup.app/caller-e2e-x402/state
- 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/caller-e2e-x402-state-check-532ab8c1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_z_5bO2IzLrJuEHObV8l08

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 caller-e2e-x402-state-check-532ab8c1
```

Example prompt: Check the current state of the x402 Caller E2E endpoint and tell me if it returns ok.

## When to prefer this

Use this endpoint when you need to verify that an x402 micropayment-gated API call works correctly end-to-end, especially when testing or debugging x402 protocol integrations. Prefer this over generic health checks when specifically validating paid API access patterns with the x402 standard.

## Known failure modes

- Payment not sent or rejected — 402 Payment Required returned if x402 payment header is missing or invalid
- Endpoint unavailable — 5xx error if miniup.app infrastructure is down
- Malformed request — 400 if request structure doesn't match required schema
- Network timeout — endpoint may be unresponsive under load

## How this service works

Caller E2E - x402: 

## Output

Returns a JSON object containing an 'ok' boolean field indicating whether the x402 caller end-to-end flow is operational. A successful response with ok: true confirms the paid endpoint is reachable and functioning correctly.

## 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"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "ok": {
       "type": "boolean"
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/caller-e2e-x402-state-check-532ab8c1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from functions.miniup.app](https://www.zero.xyz/host/functions.miniup.app/llms.txt)
