# EVM RPC Client Software Identifier

> EVM RPC Client Software Identifier is a paid API for AI agents from twin.unykorn.org, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-01).

Identifies which client software (e.g. Geth, Nethermind, Erigon) is running behind an EVM-compatible RPC endpoint for a given blockchain network

## Facts

- Endpoint: POST https://twin.unykorn.org/evm-node-info?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-rpc-client-software-identifier-37c84aee
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8m2BJ0JSzVrp_z0gMZ0qq

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 evm-rpc-client-software-identifier-37c84aee -d '<json body>'
```

Example prompt: Can you tell me which client software is running behind the Ethereum RPC node — like whether it's Geth, Erigon, or Nethermind?

## When to prefer this

Choose this endpoint when you need to programmatically identify or audit the specific EVM client software (Geth, Nethermind, Erigon, Besu, etc.) behind an RPC node for one of the 10 supported chains. Ideal for infrastructure audits, debugging RPC anomalies, or researching client diversity across networks. Prefer this over manual RPC introspection when you need a structured, paid API response with a receipt for compliance or logging.

## Known failure modes

- Unsupported chain enum value returns validation error
- Node unreachable or timeout results in error response
- RPC endpoint does not expose client version info (some nodes hide it), leading to null or unknown client result
- Payment failure via x402 protocol prevents request from completing

## How this service works

Which client software is behind an RPC endpoint — Genesis402 / UnyKorn Operator Network

## Output

Returns a JSON object indicating whether the request succeeded, the type of result ('evm-node-info'), details about the detected client software running behind the specified EVM chain's RPC endpoint, a generation timestamp, and a payment receipt including transaction hash, USD amount, and a receipt ID.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "params": {
   "type": "object",
   "properties": {
    "chain": {
     "enum": [
      "ethereum",
      "base",
      "polygon",
      "arbitrum",
      "optimism",
      "bsc",
      "avalanche",
      "gnosis",
      "linea",
      "scroll"
     ],
     "type": "string"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "type": "evm-node-info",
  "receipt": {
   "tx_hash": "0x<64hex>",
   "amount_usd": 0.001,
   "receipt_id": "g402-<16hex>"
  },
  "generated_at": "<iso8601>"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-rpc-client-software-identifier-37c84aee/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from twin.unykorn.org](https://www.zero.xyz/host/twin.unykorn.org/llms.txt)