# Vextorium EVM Signature Verify

> Vextorium EVM Signature Verify is a paid API for AI agents from api.vextorium.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-19).

Verifies an EVM wallet signature (EIP-191 personal_sign or EIP-712 typed data) and recovers the signer address

## Facts

- Endpoint: POST https://api.vextorium.com/v1/evm-signature-verify?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vextorium-evm-signature-verify-7cf3c321
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FVHb92y1e5FgsBPPRh0Ty

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 vextorium-evm-signature-verify-7cf3c321 -d '<json body>'
```

Example prompt: Can you verify this Ethereum signature for me — the message was 'Hello World', the signature is 0xabc123..., and the wallet address I expect to have signed it is 0x7E5F4552091A69125d5DfCb7b8C2659029395Bdf?

## When to prefer this

Use this endpoint when you need to cryptographically verify that a specific Ethereum wallet signed a given message or typed data payload — especially for Web3 authentication flows, on-chain agreement verification, or any scenario where you must recover the signer address from an EVM-compatible signature. Prefer this over manual cryptographic libraries when operating as an AI agent that needs a simple pay-per-call HTTP API without managing local crypto dependencies.

## Known failure modes

- Invalid or malformed signature hex returns invalid result or error
- Missing required signature field causes request rejection
- Address mismatch between signer and expected_address returns valid=false
- Malformed EIP-712 data object causes parsing error
- Unsupported signature type may return null or error response

## How this service works

Verify an Ethereum signature: a personal_sign (EIP-191) message or EIP-712 typed data. Recovers the signer address and, if you pass one, confirms it matches. Local computation; EIP-1271 contract wallets are not covered.

## Output

Returns whether the signature is valid (boolean), the recovered signer address, the signed hash, the detected signature type (e.g. 'EIP-191 personal_sign'), and the expected address for comparison.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "address": {
   "type": "string"
  },
  "message": {
   "type": "string"
  },
  "signature": {
   "type": "string"
  },
  "eip712_data": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "type": "EIP-191 personal_sign",
  "valid": true,
  "signer": "0x7E5F4552091A69125d5DfCb7b8C2659029395Bdf",
  "signed_hash": "0x517cc9957090f83459004d4980c16e723e44524c30d84175324025d957b0451a",
  "expected_address": "0x7E5F4552091A69125d5DfCb7b8C2659029395Bdf"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vextorium-evm-signature-verify-7cf3c321/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.vextorium.com](https://www.zero.xyz/host/api.vextorium.com/llms.txt)