# Beggar Bot Across Bridge Status (Base Mainnet)

> Beggar Bot Across Bridge Status (Base Mainnet) is a paid API for AI agents from beggar-bot-demand.beggarbot.workers.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-11-04).

Returns the status of an Across Protocol cross-chain bridge transaction on Base mainnet

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/acrossstatus?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/beggar-bot-across-bridge-status-base-mainnet-ba69fc50
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xBgrqrQocqRPpVvFZF_jq

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 beggar-bot-across-bridge-status-base-mainnet-ba69fc50
```

Example prompt: Can you check the Across Protocol bridge status for my Base mainnet deposit — I sent USDC across chains and want to know if the transfer has been filled yet?

## When to prefer this

Use this endpoint when you need to check the real-time status of an Across Protocol cross-chain bridge transaction specifically on Base mainnet. Prefer this over generic blockchain explorers when you need structured, agent-readable bridge-specific status (filled, pending, failed) rather than raw on-chain data. It is paid ($0.02 USDC via x402) so use it when a definitive bridge status lookup is required rather than for speculative polling.

## Known failure modes

- Invalid or missing deposit/transaction identifier returns an error
- Deposit ID not found on Base mainnet returns a not-found or empty response
- Network connectivity issues to Across Protocol indexer may cause timeouts
- x402 payment failure (insufficient USDC balance) prevents the call from completing
- Specifying an unsupported network value may return an error or unexpected results

## How this service works

Paid: /v1/verify, /v1/risk, /v1/receipt cost $0.01 USDC per call on Base mainnet via x402 (payTo 0x719227f384b66BFEF00093D6d8d32fA9dC2B40e7); utilities analyze Base mainnet (USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) by default, network=base-sepolia optional; /v1/receipt/verify and discovery files are free. Operator: Beggar Bot.

## Output

A JSON object describing the current status of an Across Protocol bridge deposit on Base mainnet, including whether the deposit has been filled, is pending, or has failed, along with relevant deposit metadata and cross-chain transfer details.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/beggar-bot-across-bridge-status-base-mainnet-ba69fc50/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from beggar-bot-demand.beggarbot.workers.dev](https://www.zero.xyz/host/beggar-bot-demand.beggarbot.workers.dev/llms.txt)