# Beggar Bot NFT Send Build Utility (Base Mainnet)

> Beggar Bot NFT Send Build 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-10).

Builds an NFT send transaction payload on Base mainnet for use by AI agents, paid via x402 micropayment.

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/nftsendbuild?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/beggar-bot-nft-send-build-utility-base-mainnet-b437b186
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_u1fVPDqdoLMY7c2hc0yra

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-nft-send-build-utility-base-mainnet-b437b186
```

Example prompt: Build me an NFT send transaction on Base mainnet for token ID 42 from my wallet to 0xAbCd1234... using the NFT contract at 0x1234abcd... so I can sign and broadcast it.

## When to prefer this

Use this endpoint when an AI agent needs to programmatically build an NFT send/transfer transaction on Base mainnet without manually encoding calldata. Prefer this over generic transaction builders when you need a purpose-built, micropayment-gated utility specifically designed for Base mainnet NFT operations within an agentic workflow.

## Known failure modes

- Invalid or missing NFT contract address returns error
- Invalid token ID or non-existent token returns error
- Malformed recipient or sender address causes failure
- Payment of $0.02 USDC via x402 not provided results in 402 Payment Required
- Network unavailable or Base mainnet RPC errors cause timeout
- Unsupported NFT standard or contract type may return unrecognized 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

A JSON object containing the constructed NFT send transaction payload for Base mainnet, including calldata, to/from addresses, and other fields needed to sign and broadcast the transaction.

## 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-nft-send-build-utility-base-mainnet-b437b186/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)