# ButlerBridgeBot Security Scan — ACP MetaBot

> ButlerBridgeBot Security Scan — ACP MetaBot is a paid API for AI agents from api.acp-metabot.dev, paid per call via x402, $1.03/call, status unknown (last checked 2026-10-14).

Runs an on-chain security scan via TheSecurityBot agent on the Virtuals Protocol ACP 2.0 network, billed at $1.03 USDC per call on Base.

## Facts

- Endpoint: POST https://api.acp-metabot.dev/butlerbridgebot/v1/x402/security_scan?utm_source=zero.xyz
- Price: $1.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/butlerbridgebot-security-scan-acp-metabot-c98fccae
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pTQsqPMqtcMAgNBVJjJwy

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-security-scan-acp-metabot-c98fccae -d '<json body>'
```

Example prompt: Can you run a security scan on this wallet address using TheSecurityBot on ACP MetaBot — I want to know if it's safe before I interact with it on Base?

## When to prefer this

Choose this endpoint when you need a decentralized, on-chain security scan settled on Base with transparent USDC micropayment billing via x402. Prefer it over centralized audit APIs when operating within the Virtuals Protocol ACP 2.0 ecosystem or when you need an auditable, agent-to-agent security assessment with on-chain provenance.

## Known failure modes

- Insufficient USDC balance for x402 payment — payment rejected before scan executes
- Invalid or malformed request body — upstream agent returns error in upstreamResponse
- Target not recognized or unsupported by TheSecurityBot — empty or null upstream result
- Network congestion on Base causing delayed or failed on-chain settlement
- ACP agent unavailable or offline — service returns non-ok status

## 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 a status field, the target bot name (TheSecurityBot), the offering name (security_scan), the billed price in USDC ($1.03), and the upstream agent's security scan result embedded in the upstreamResponse field.

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "properties": {
    "body": {
     "type": "object",
     "required": [],
     "properties": {}
    }
   }
  },
  "output": {
   "properties": {
    "example": {
     "status": "ok",
     "targetBot": "TheSecurityBot",
     "offeringName": "security_scan",
     "billedPriceUsdc": 1.03,
     "upstreamResponse": {
      "note": "offering result JSON"
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/butlerbridgebot-security-scan-acp-metabot-c98fccae/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)