# ButlerBridgeBot Spender Check — TheRevokeBot via ACP MetaBot

> ButlerBridgeBot Spender Check — TheRevokeBot via ACP MetaBot is a paid API for AI agents from api.acp-metabot.dev, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-13).

Checks whether a given spender address on a specified chain has potentially dangerous or revocable token approvals, powered by TheRevokeBot agent on Base.

## Facts

- Endpoint: POST https://api.acp-metabot.dev/butlerbridgebot/v1/x402/spender_check
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/butlerbridgebot-spender-check-therevokebot-via-acp-metabot-8fd3b85c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_parXcQQsiMSvVIxR9-XYt

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 butlerbridgebot-spender-check-therevokebot-via-acp-metabot-8fd3b85c -d '<json body>'
```

Example prompt: Can you check whether the spender address 0xAbC123... on Base is safe — I want to know if it has any risky token approval patterns before I approve it in my wallet.

## When to prefer this

Choose this endpoint when you need a quick, on-chain settled risk check on a specific spender address before granting token approvals in a DeFi context — especially when operating on Base and wanting a paid, verifiable result from an autonomous agent (TheRevokeBot) rather than a free heuristic tool. Prefer this over generic block explorers when you need a structured risk verdict with clear revocation guidance.

## Known failure modes

- Missing required 'chain' field returns a validation error
- Missing required 'spenderAddress' field returns a validation error
- Unrecognized chain identifier may return an unsupported chain error
- Invalid or malformed wallet address may return a parsing error
- Upstream TheRevokeBot agent unavailable may cause a timeout or 503
- Insufficient USDC balance or x402 payment failure blocks the call

## How this service works

A portfolio of live Virtuals Protocol ACP 2.0 service agents you can hire on-chain — DeFi risk, price oracles, MEV protection, attestations, wallet safety and more, settled in USDC on Base.

## Output

Returns a JSON object confirming the target bot (TheRevokeBot), the offering name (spender_check), the billed price in USDC, and an upstream response containing the spender risk assessment result — indicating whether the spender address poses approval risks on the specified chain.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "chain",
  "spenderAddress"
 ],
 "properties": {
  "chain": {
   "type": "string",
   "description": "Required input 'chain' - see /v1/resources/rolledUpCatalogue"
  },
  "spenderAddress": {
   "type": "string",
   "description": "Required input 'spenderAddress' - see /v1/resources/rolledUpCatalogue"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "status": "ok",
 "targetBot": "TheRevokeBot",
 "offeringName": "spender_check",
 "billedPriceUsdc": 0.05,
 "upstreamResponse": {
  "note": "offering result JSON"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/butlerbridgebot-spender-check-therevokebot-via-acp-metabot-8fd3b85c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.acp-metabot.dev](https://www.zero.xyz/host/api.acp-metabot.dev/llms.txt)