# Agent Bounty Radar – Base Wallet Preflight

> Agent Bounty Radar – Base Wallet Preflight is a paid API for AI agents from agent-bounty-radar-29837.alissonayres-trb.chatgpt.site, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Checks a Base/EVM wallet address for ETH and USDC balances and determines whether it is ready to make x402 micropayments on Base.

## Facts

- Endpoint: POST https://agent-bounty-radar-29837.alissonayres-trb.chatgpt.site/x402/base-wallet-preflight
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-bounty-radar-base-wallet-preflight-aad6e45b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ex9wS5SFqqxyyShaZqatA

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 agent-bounty-radar-base-wallet-preflight-aad6e45b -d '<json body>'
```

Example prompt: Before I start making x402 API calls, can you preflight check my Base wallet 0xAbC1234567890abcdef1234567890AbCdEf12345 to see if it has enough USDC and ETH to actually pay for requests?

## When to prefer this

Use this endpoint when you need to pre-validate whether a specific Base/EVM wallet address is funded and capable of executing x402 micropayments before attempting paid API calls — especially to avoid wasted payment attempts or to diagnose why an agent wallet is failing to pay. Prefer this over on-chain RPC calls when you want a structured, opinionated readiness report rather than raw balance data, and when you are operating in the x402/Base ecosystem specifically.

## Known failure modes

- Invalid wallet address format (not a valid 0x 42-char hex) — API likely returns a 4xx validation error
- Unpaid request returns HTTP 402 with PAYMENT-REQUIRED header; the agent must retry with a valid x402 payment
- Wallet address is valid but has never been used — balances return as 0 and all readiness flags are false
- Base network RPC timeout or unavailability may cause delayed or failed responses
- Address is a contract rather than an EOA, which may limit payment-readiness interpretation

## How this service works

Two fixed-price x402 v2 APIs on Base. Unpaid requests return HTTP 402 with PAYMENT-REQUIRED; paid retries return JSON and PAYMENT-RESPONSE.

## Output

Returns a JSON object with the Base network name and chain ID (8453), the wallet's current ETH and USDC balances as strings, the address type (e.g. externally_owned_account or contract), and a payment_readiness object indicating whether the wallet has outgoing transaction history, sufficient USDC to cover a payment, and enough ETH for direct gas coverage.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "address": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{40}$",
   "description": "Public 42-character Base/EVM wallet address."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "network": {
   "name": "Base",
   "chain_id": 8453
  },
  "balances": {
   "eth": "0",
   "usdc": "0"
  },
  "address_type": "externally_owned_account",
  "payment_readiness": {
   "has_outgoing_history": false,
   "can_cover_usdc_payment": false,
   "has_eth_for_direct_gas": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-bounty-radar-base-wallet-preflight-aad6e45b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-bounty-radar-29837.alissonayres-trb.chatgpt.site](https://www.zero.xyz/host/agent-bounty-radar-29837.alissonayres-trb.chatgpt.site/llms.txt)