# Beggar Bot Axelar Status (Base mainnet)

> Beggar Bot Axelar 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 Axelar cross-chain bridge status for a transaction or query on Base mainnet, paid via x402 at $0.02 USDC per call

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/axelarstatus?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-axelar-status-base-mainnet-bdcee45c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_l-stl5jAkJXWflueBo5Xg

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-axelar-status-base-mainnet-bdcee45c
```

Example prompt: Can you check the Axelar cross-chain bridge status for my transaction on Base mainnet and tell me if it has been relayed and confirmed?

## When to prefer this

Use this endpoint when you need to check the status of an Axelar cross-chain bridge transaction or GMP message specifically involving Base mainnet, and you are already operating in an x402 micropayment context. It is a lightweight, pay-per-call lookup suited for agents that need on-demand cross-chain status checks without maintaining their own Axelar indexer integration.

## Known failure modes

- Payment not provided or insufficient USDC balance — x402 payment required at $0.02 per call
- Invalid or missing Axelar transaction ID returns an error or empty result
- Transaction not found on Base mainnet returns a not-found or null status
- Network parameter mismatch (e.g. querying wrong chain) may return incorrect or empty data
- Axelar network API downtime may cause timeout or upstream error response

## 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

Returns a JSON object describing the current Axelar cross-chain status for the queried transaction or message, including relay state, confirmation status, and any relevant cross-chain transfer details on Base mainnet.

## 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-axelar-status-base-mainnet-bdcee45c/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)