# 8k4 Protocol RPC Reliability Metrics

> 8k4 Protocol RPC Reliability Metrics is a paid API for AI agents from api.8k4protocol.com, paid per call via x402, $0.01/call, status down (last checked 2026-08-24).

Retrieves RPC reliability metrics for the 8k4 Protocol network, supporting trust and performance analysis of blockchain RPC endpoints.

## Facts

- Endpoint: GET https://api.8k4protocol.com/metrics
- Price: $0.01/call
- Payment: x402
- Status: down
- Last checked: 2026-08-24
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-8k4protocol-com-ee9f64dc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__B6Lrzqu7HYee1_jFGYVv

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 api-8k4protocol-com-ee9f64dc
```

Example prompt: Can you pull the current RPC reliability metrics from 8k4 Protocol so I can see how the network is performing?

## When to prefer this

Use this endpoint when you need objective RPC reliability metrics from the 8k4 Protocol network, particularly when evaluating ERC-8004 agent trust scores or auditing RPC node performance. Prefer this over generic uptime monitors when working within the ERC-8004 ecosystem.

## Known failure modes

- Payment not provided or rejected — endpoint requires $0.01 USDC via x402 protocol
- Invalid or missing required 'type' field (must be 'http') — returns validation error
- Invalid HTTP method specified — only GET, HEAD, DELETE are accepted
- Service unavailable — metrics backend temporarily unreachable
- Rate limiting — too many requests in a short period

## How this service works

Get RPC reliability metrics

## Output

Returns RPC reliability metrics including uptime, performance statistics, confidence distributions, and protocol-level reliability data for the 8k4 Protocol network.

## Example request

```json
{
 "input": {
  "type": "http",
  "method": "GET",
  "queryParams": {}
 }
}
```

## 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",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "metrics"
 ],
 "properties": {
  "metrics": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "chain",
     "last_error",
     "error_count",
     "success_count",
     "avg_response_ms",
     "last_success_at",
     "last_updated_at"
    ],
    "properties": {
     "chain": {
      "type": "string"
     },
     "last_error": {
      "type": "string"
     },
     "error_count": {
      "type": "number"
     },
     "success_count": {
      "type": "number"
     },
     "avg_response_ms": {
      "type": "number"
     },
     "last_success_at": {
      "type": "string"
     },
     "last_updated_at": {
      "type": "string"
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-8k4protocol-com-ee9f64dc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.8k4protocol.com](https://www.zero.xyz/host/api.8k4protocol.com/llms.txt)