---
title: "Estimate the credit cost of a planned call (or batch of calls)"
method: POST
path: "/v1/estimate"
tags: ["events"]
---

# Estimate the credit cost of a planned call (or batch of calls)

`POST /v1/estimate`

## Request

- Base URL: `https://lumify.ai`
- URL: `https://lumify.ai/v1/estimate`
- Auth: HTTP bearer

## Request body

- EstimateRequest
  - `calls` EstimateCall[], required: One or more planned calls to estimate in a single round-trip.
    - `tool` string, required: The MCP tool / SDK call to estimate, e.g. 'get_event', 'batch_get_events', 'get_odds'. See GET /v1/estimate/tools for the full supported list.
    - `arguments` object: Same arguments you'd pass to that tool/endpoint, e.g. {"event_id": 123, "include_odds": true}.

## Response `200`

Min/max credit range per requested call, plus totals. Costs are data-dependent (e.g. odds/intelligence/splits not yet ingested are free), so this is a range, not an exact number — the real call's X-Credits-Used response header reports what it actually billed. Estimating is always free (X-Credits-Used: 0).

- EstimateResponse
  - `estimates` EstimateResult[], required
    - `tool` string, required
    - `min_credits` integer, required: Cheapest realistic outcome (e.g. requested data not yet available).
    - `max_credits` integer, required: Priciest realistic outcome (e.g. all requested data is available).
    - `note` string, nullable: Why the cost varies, when it does.
  - `total_min_credits` integer, required
  - `total_max_credits` integer, required

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/lumify/apis/lumify-sports-intelligence-api.md) · [All operations](https://skmtc.dev/lumify/apis/lumify-sports-intelligence-api/llms.txt) · [OpenAPI document](https://skmtc.dev/lumify/apis/lumify-sports-intelligence-api/revisions/f91ea41a2606?raw)