# ButlerBridgeBot Batch Token Screen via ACP MetaBot

> ButlerBridgeBot Batch Token Screen via ACP MetaBot is a paid API for AI agents from api.acp-metabot.dev, paid per call via x402, $0.23/call, status unknown (last checked 2026-09-15).

Batch-screens a set of tokens for wallet safety, MEV risk, and DeFi threat signals via the SafeRouteBot agent, settled in USDC on Base.

## Facts

- Endpoint: POST https://api.acp-metabot.dev/butlerbridgebot/v1/x402/batch_screen
- Price: $0.23/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/butlerbridgebot-batch-token-screen-via-acp-metabot-80731fb0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zl4qZ_LQpJFDozqs5kd4y

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-batch-token-screen-via-acp-metabot-80731fb0 -d '<json body>'
```

Example prompt: Can you batch-screen these tokens — 0xABC123, 0xDEF456, and 0x789GHI — for DeFi risk, MEV exposure, and wallet safety issues on Base before I add them to my portfolio?

## When to prefer this

Choose this endpoint when you need to batch-screen multiple tokens simultaneously for DeFi risk, MEV exposure, and wallet safety on the Base network in a single on-chain payment. It is especially valuable for pre-trade safety checks, portfolio onboarding workflows, or automated DeFi monitoring pipelines where the overhead of individual token queries is prohibitive. Prefer this over single-token endpoints when operating on lists of assets and needing a consolidated risk report settled in USDC.

## Known failure modes

- Missing or empty 'tokens' field returns a 400 validation error
- Invalid token address format may cause upstream SafeRouteBot to reject or return partial results
- Insufficient USDC balance or failed x402 payment results in a 402 Payment Required error
- Upstream SafeRouteBot unavailability returns a 502 or timeout error
- Tokens not on Base network may return unsupported asset errors
- Rate limiting may occur for very large token batches

## 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 with the target bot identified as SafeRouteBot, the offering name (batch_screen), the billed price in USDC (0.23), and an upstreamResponse field containing the SafeRouteBot's risk assessment results for the submitted tokens — including safety flags, MEV risk signals, and wallet safety indicators.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "status": "ok",
 "targetBot": "SafeRouteBot",
 "offeringName": "batch_screen",
 "billedPriceUsdc": 0.23,
 "upstreamResponse": {
  "note": "offering result JSON"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/butlerbridgebot-batch-token-screen-via-acp-metabot-80731fb0/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)