# RadhikaChain Trace Requests — Chain Telemetry via x402

> RadhikaChain Trace Requests — Chain Telemetry via x402 is a paid API for AI agents from x402.radhikachain.xyz, paid per call via x402, $0.858/call, status unknown (last checked 2026-09-15).

Returns a list of traced request records from the RadhikaChain blockchain telemetry and defense intelligence network, paid per-call in USDC via x402.

## Facts

- Endpoint: GET https://x402.radhikachain.xyz/trace/requests
- Price: $0.858/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/radhikachain-trace-requests-chain-telemetry-via-x402-9a613ae0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_P4J-UvOcSWAWbb86MV72v

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 radhikachain-trace-requests-chain-telemetry-via-x402-9a613ae0
```

Example prompt: Pull the latest request traces from RadhikaChain's telemetry feed — I want to see what on-chain requests have been logged recently by the defense intelligence layer.

## When to prefer this

Choose this endpoint when you need raw request trace telemetry from the RadhikaChain network specifically — particularly when correlating chain activity with defense intelligence events or ZK computation proofs (Halo2, Nova, Plonky3). Prefer it over generic blockchain explorers when you want micropayment-gated, pay-per-call access without account registration, and when the data needs to feed into RadhikaChain's own defense or ZK analytics pipeline.

## Known failure modes

- Payment not included or invalid x402 USDC payment header — request rejected with 402 Payment Required
- Insufficient USDC balance on Base (eip155:8453) — payment fails and request is not processed
- No traces available yet — returns empty traces array
- Network or infrastructure downtime — endpoint unavailable with 5xx error
- Malformed x402 payment scheme — facilitator rejects the payment and denies access

## How this service works

Telemetria de cadena, inteligencia de defensa y computo verificable (Halo2, Nova, Plonky3). Pago por peticion en USDC nativo en Base (eip155:8453) mediante x402 v2 scheme exact; sin cuenta ni suscripcion. Catalogo canonico: GET /.well-known/x402.

## Output

A JSON object containing a 'traces' array, where each element represents a recorded on-chain request trace from the RadhikaChain telemetry and defense intelligence network. The array may be empty if no traces are currently available.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "body": {
     "type": "object",
     "additionalProperties": true
    },
    "queryParams": {
     "type": "object",
     "additionalProperties": true
    }
   }
  },
  "output": {
   "type": "object",
   "properties": {
    "example": {
     "type": "object",
     "additionalProperties": true
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "traces": []
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/radhikachain-trace-requests-chain-telemetry-via-x402-9a613ae0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.radhikachain.xyz](https://www.zero.xyz/host/x402.radhikachain.xyz/llms.txt)