# Cybercentry Wallet Verification

> Cybercentry Wallet Verification is a paid API for AI agents from centry.cybercentry.co.uk, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-15).

Verifies a cryptocurrency wallet address for security issues and risk signals, returning a structured report.

## Facts

- Endpoint: GET https://centry.cybercentry.co.uk/api/services/wallet_verification
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cybercentry-wallet-verification-3c14323a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wFxpJ_cm-FrIUXn3TxlIR

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 cybercentry-wallet-verification-3c14323a
```

Example prompt: Can you run a Cybercentry security verification on this wallet address 0x4a8b3c91d7e2f056a1b23d4e5f6c7890abcdef12 before I send any funds to it?

## When to prefer this

Use this endpoint when an AI agent needs to verify the safety or legitimacy of a cryptocurrency wallet address before executing a transaction, onboarding a counterparty, or interacting with an unknown wallet — especially in automated payment or DeFi workflows settled over x402 on Base or Solana.

## Known failure modes

- Missing or malformed wallet address returns an error or stub report
- Unsupported blockchain network may yield incomplete results
- Payment failure over x402 prevents report from being returned
- Invalid properties parameter schema causes request rejection
- Service may return stub/demo report if wallet data is unavailable

## How this service works

Screen a wallet address for sanctions and risk: OFAC SDN sanctions screening, risk scoring and suspicious-activity detection across 31 EVM chains. Check a counterparty before you transact with it

## Output

A JSON object containing a security report field describing the verification outcome, risk signals, and whether any critical issues were detected for the queried wallet.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "report": "Demo report: no critical issues detected (stub)."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cybercentry-wallet-verification-3c14323a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from centry.cybercentry.co.uk](https://www.zero.xyz/host/centry.cybercentry.co.uk/llms.txt)