# LimitGuard Blockchain Wallet Verification

> LimitGuard Blockchain Wallet Verification is a paid API for AI agents from api.limitguard.ai, paid per call via x402, $0.1/call, status unknown (last checked 2026-10-10).

Verifies a blockchain wallet address by checking on-chain activity and returning risk flags and an activity score

## Facts

- Endpoint: POST https://api.limitguard.ai/v1/mcp/verify-wallet?utm_source=zero.xyz
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/limitguard-blockchain-wallet-verification-6641c162
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5_bRkHgqx4bcj7bRG5PEf

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 limitguard-blockchain-wallet-verification-6641c162 -d '<json body>'
```

Example prompt: Before I send payment, can you verify that the wallet address 0x742d35Cc6634C0532925a3b844Bc454e4438f44e on Base (eip155:8453) is safe — check its on-chain activity and flag any risk issues?

## When to prefer this

Use this endpoint when you need a fast, lightweight on-chain risk check for a specific wallet address before executing a transaction, onboarding a counterparty, or screening an agent wallet. Prefer this over full entity compliance checks when you have a wallet address (not a name/company) and need a binary validity signal plus risk flags without a full KYB/KYC report.

## Known failure modes

- Invalid wallet address format returns validation error
- Unsupported chain_id returns error or defaults to eip155:8453
- Wallet with no on-chain history may return low activity_score with empty risk_flags
- Payment failure (insufficient USDC balance) blocks the request
- Newly deployed wallet may have limited data, reducing confidence in results

## How this service works

MCP tool: Screen a wallet: OFAC SDN address match, on-chain signals (contract check, native and USDC balance, transaction count, first seen on Base) and named risk rules with up to 3 advice items. On Base, also reports any ERC-8004 agent the wallet owns and its open on-chain reputation as descriptive signals, never scored. $0.11. Accepts EVM (0x...) and Solana (base58) addresses.

## Output

Returns a JSON object with: wallet_valid (boolean indicating if the address is a valid, active wallet), activity_score (0-100 integer reflecting on-chain engagement), and risk_flags (array of risk indicators such as sanctions hits, mixer usage, or suspicious patterns)

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain_id": {
   "type": "string",
   "description": "CAIP-2 chain ID (default: eip155:8453); base, eth, solana, btc also accepted"
  },
  "wallet_address": {
   "type": "string",
   "description": "Blockchain wallet address"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "advice": [
   {
    "why": "no OFAC SDN match as of 2026-09-23; no rule fired",
    "action": "proceed with standard monitoring",
    "expected_result": "re-screen on material change"
   }
  ],
  "sanctions": {
   "hit": false,
   "as_of": "2026-09-23",
   "lists": [],
   "source": "ofac_sdn",
   "status": "ok",
   "programs": []
  },
  "risk_level": "low",
  "risk_score": 0,
  "rules_fired": [],
  "unavailable": []
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/limitguard-blockchain-wallet-verification-6641c162/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.limitguard.ai](https://www.zero.xyz/host/api.limitguard.ai/llms.txt)