# Bot Bazaar MCP Tool Token Budget Estimator

> Bot Bazaar MCP Tool Token Budget Estimator is a paid API for AI agents from bot-bazaar.fly.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-11-20).

Estimates the LLM prompt token footprint consumed by an MCP server's tools/list schemas given a tool count.

## Facts

- Endpoint: GET https://bot-bazaar.fly.dev/v1/x402/mcp-tool-token-budget?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bot-bazaar-mcp-tool-token-budget-estimator-772fd83a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_H6euis2K2m982ES7bNx0d

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 bot-bazaar-mcp-tool-token-budget-estimator-772fd83a
```

Example prompt: How many prompt tokens will my MCP server's tool schemas consume if it exposes 12 tools?

## When to prefer this

Use this endpoint when you need a quick, inexpensive estimate of how many LLM prompt tokens an MCP server's tool schema list will occupy, especially when planning context window budgets, comparing MCP server sizes, or deciding whether to lazy-load tools. Prefer this over manual token counting or full LLM inference when you only need a rough budget figure based on tool count.

## Known failure modes

- Missing required tool_count query parameter returns an error
- Invalid or non-numeric tool_count value causes a validation error
- Network or server-side errors on the fly.dev host return 5xx responses
- x402 payment not fulfilled results in 402 Payment Required response blocking the call

## How this service works

Estimate the LLM prompt token footprint consumed by an MCP server's tools/list schemas.

## Output

Returns an estimated token count representing the LLM prompt token footprint that an MCP server's tools/list schema payload would consume, given the number of tools exposed by the server.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "tool_count": {
       "type": "string",
       "description": "Number of tools exposed by MCP server"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bot-bazaar-mcp-tool-token-budget-estimator-772fd83a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bot-bazaar.fly.dev](https://www.zero.xyz/host/bot-bazaar.fly.dev/llms.txt)
