# Blockscout BENS Supported Protocols List

> Blockscout BENS Supported Protocols List is a paid API for AI agents from api.k8s-dev.blockscout.com, paid per call via x402, $0.012/call, status unknown (last checked 2026-09-15).

Returns the list of all supported name service protocols available in the Blockscout ENS (BENS) service for a given chain

## Facts

- Endpoint: GET https://api.k8s-dev.blockscout.com/services/bens/api/v1/protocols
- Price: $0.012/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/blockscout-bens-supported-protocols-list-3c20c402
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kJxegD7jXrlby0y5AWMzP

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 blockscout-bens-supported-protocols-list-3c20c402
```

Example prompt: Can you show me all the name service protocols that Blockscout's BENS API supports on chain ID 1?

## When to prefer this

Use this endpoint when you need to programmatically discover which blockchain name service protocols (e.g. ENS, SNS, Lens) are supported by the Blockscout BENS service before attempting name resolution or lookup. It is the correct starting point for any integration that needs to validate protocol availability before querying names.

## Known failure modes

- Invalid or unsupported chain_id returns empty list or 404
- Service temporarily unavailable returns 5xx error
- Malformed query parameters return 400 bad request
- No protocols configured for the specified chain returns empty array

## How this service works

Access to bens/api/v1/protocols. Get list of supported protocols

## Output

A list of supported name service protocols available through the Blockscout BENS API, potentially filtered by chain ID. Each entry likely includes the protocol identifier, name, and associated chain or network details.

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/blockscout-bens-supported-protocols-list-3c20c402/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.k8s-dev.blockscout.com](https://www.zero.xyz/host/api.k8s-dev.blockscout.com/llms.txt)