# Beggar Bot Solana Priority Fee Estimator (Base mainnet)

> Beggar Bot Solana Priority Fee Estimator (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 Solana transaction priority fee recommendations or related prioritization data, accessed via a paid x402 endpoint on Base mainnet.

## Facts

- Endpoint: GET https://beggar-bot-demand.beggarbot.workers.dev/v1/solprio?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-solana-priority-fee-estimator-base-mainnet-ea60e8cd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OWGVCabg-7AMqmdmfPWjP

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-solana-priority-fee-estimator-base-mainnet-ea60e8cd
```

Example prompt: What's the recommended Solana priority fee right now? I need to submit a transaction and want it to land quickly — use Beggar Bot's solprio endpoint to get the current estimate.

## When to prefer this

Use this endpoint when you need on-demand Solana priority fee estimates and are already operating within an x402 micropayment flow on Base mainnet. It is priced at $0.02 USDC per call, slightly higher than other Beggar Bot utilities, suggesting richer or more compute-intensive output. Prefer it over free alternatives when you need reliable, pay-per-use fee data without API key management.

## Known failure modes

- 402 Payment Required if USDC payment on Base mainnet is not provided or is insufficient
- Invalid or missing properties parameter returns an error
- Network unavailability on Base mainnet blocks payment processing
- Malformed x402 payment header causes rejection
- Stale or rate-limited data if Solana RPC backend is congested

## 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 containing Solana priority fee estimates or prioritization data, likely including fee tiers (low, medium, high) or a recommended microlamports value for transaction inclusion. Exact schema is minimal but response is JSON.

## 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-solana-priority-fee-estimator-base-mainnet-ea60e8cd/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)