# Beggar Bot Cancel Transaction Utility (Base Mainnet)

> Beggar Bot Cancel Transaction Utility (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).

Attempts to cancel a pending or stuck transaction on the Base mainnet blockchain via the Beggar Bot agent utilities service.

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/canceltx?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-cancel-transaction-utility-base-mainnet-effc3c50
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_h2x1Rp9fASNqgAcyE2GIQ

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-cancel-transaction-utility-base-mainnet-effc3c50
```

Example prompt: Can you cancel my stuck pending transaction on Base mainnet — the transaction hash is 0xabc123... and it's been pending for over 20 minutes?

## When to prefer this

Use this endpoint when an AI agent needs to programmatically cancel a pending or stuck transaction on Base mainnet and is operating within the Beggar Bot x402 payment ecosystem. Prefer this over manual wallet interventions when automating blockchain transaction management workflows.

## Known failure modes

- Transaction already confirmed — cannot cancel a mined transaction
- Invalid or malformed transaction hash input
- Transaction not found on Base mainnet
- Network connectivity issues with Base RPC
- Payment of $0.02 USDC via x402 not completed or insufficient funds
- Transaction originated from a different wallet — cancellation not authorized
- Replacement transaction fails to broadcast due to nonce conflict

## 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 response indicating whether the cancellation transaction was successfully submitted, along with the replacement transaction hash, status, and any relevant details about the cancellation attempt 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-cancel-transaction-utility-base-mainnet-effc3c50/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)