# BotPay Network Payment API

> BotPay Network Payment API is a paid API for AI agents from api.botpay.network, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-22).

Processes a micropayment of $0.01 USDC on Base network via HTTP GET, enabling pay-per-call API access through the x402 payment protocol

## Facts

- Endpoint: GET https://api.botpay.network/pay?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/botpay-network-payment-api-799b83b6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_z1-J68PCl9nv1FNBlgAJW

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 botpay-network-payment-api-799b83b6
```

Example prompt: Pay $0.01 USDC on the Base network to access the BotPay API using the x402 protocol and return whatever the endpoint sends back.

## When to prefer this

Choose this endpoint when you need to make a single pay-per-call request to the BotPay network and your agent wallet holds USDC on Base. It is specifically suited for x402-protocol-enabled agents that can attach payment headers to HTTP requests. Prefer this over free-tier alternatives when BotPay data or bot-network access is explicitly required.

## Known failure modes

- Insufficient USDC balance on Base wallet returns 402 Payment Required
- Invalid or missing x402 payment header causes authentication rejection
- Network congestion on Base L2 causes transaction timeout
- Malformed GET request with unexpected query parameters returns 400 Bad Request
- Payment confirmed but API service unavailable returns 503

## How this service works

BotPay provides payment access, API discovery, automated service delivery, and settlement infrastructure for AI agents, applications, robots, and connected machines.

## Output

The endpoint returns a response body (structure varies) after the $0.01 USDC micropayment on Base is confirmed via x402 protocol. On success, the agent receives the API payload plus a payment receipt. On failure, a 402 Payment Required or error status is returned.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "testRunId": {
   "type": "string",
   "maxLength": 100,
   "description": "Optional caller-supplied correlation ID."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "message": "Receipt ID: pi_38ep4k",
  "protocol": "x402",
  "resource": "/pay",
  "receiptId": "pi_38ep4k"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/botpay-network-payment-api-799b83b6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.botpay.network](https://www.zero.xyz/host/api.botpay.network/llms.txt)