> ## Documentation Index > Fetch the complete documentation index at: https://docs.zelto.ai/llms.txt > Use this file to discover all available pages before exploring further. # Get benchmark spend > Month-to-date benchmark spend for the organization (what Zelto bills: platform cost plus margin and BYOK fees), the monthly cap and per-run approval threshold, the included credit left and the runs waiting for an owner's approval. ## OpenAPI ````yaml /docs-openapi.json get /v1/benchmarks/spend openapi: 3.1.0 info: title: Zelto REST API version: v1 description: >- Programmatic access to your Zelto organization. Every endpoint is scoped to the organization the API key belongs to. Mint a key at Settings → Integrations → API integration. servers: - url: https://api.zelto.ai description: Production security: - bearerAuth: [] tags: - name: Monitors description: Filtered, asynchronous exports of stored monitor results. - name: Agents description: Voice and text agents normalised through Zelto's ingestion pipeline. - name: Conversations description: >- Phone calls, chats, and voicemails — plus their transcripts and recordings. - name: Customer Metrics description: >- Customer-provided evaluations attached to a conversation (requires metrics enabled). - name: Reviews description: Human review state for conversations. - name: Buckets description: Reviewer routing — group conversations for batched review. - name: Companies description: Clients or brands your agents work for, and their logos. - name: Findings description: >- Structured issues discovered during analysis, with optional conversation attachments and comments. - name: Experiments description: >- Prospective measurement of two externally routed prompt versions across independent monitor outcomes. - name: Organizations description: >- Headless org provisioning. Requires an admin/service API key (not a read-only org-scoped customer key). - name: AI providers description: >- Your organization's own (bring-your-own) AI provider keys. Monitors can run on them instead of Zelto's built-in models. Owner or admin keys only; the secret is write-only. - name: Benchmarks description: >- Repeatable evaluations of agent prompts, models and speech-to-text engines over a fixed set of cases, scored by Judges. paths: /v1/benchmarks/spend: get: tags: - Benchmarks summary: Get benchmark spend description: >- Month-to-date benchmark spend for the organization (what Zelto bills: platform cost plus margin and BYOK fees), the monthly cap and per-run approval threshold, the included credit left and the runs waiting for an owner's approval. operationId: getBenchmarkSpend responses: '200': description: Successful response. content: application/json: schema: $ref: '#/components/schemas/BenchmarkSpendStatus' '400': $ref: '#/components/responses/ValidationFailed' '401': $ref: '#/components/responses/Unauthorized' components: schemas: BenchmarkSpendStatus: type: object properties: month: type: string description: The UTC calendar month, `YYYY-MM`. plan: type: string paid: type: boolean description: Whether the plan can be billed past the included credit. monthToDateUsd: type: number description: >- Billed this month by benchmark runs, plus what queued and running runs have reserved. settledUsd: type: number description: Billed so far this month. reservedUsd: type: number description: Estimated cost still reserved by queued and running runs. monthlyCapUsd: anyOf: - type: number description: >- USD, to micro-dollar precision (up to 6 decimals), so sub-cent spend such as a Judge try is visible. - type: 'null' description: The cap in effect, or null for no cap. monthlyCapSource: type: string enum: - owner - plan description: Whether an owner set the cap or it is the plan default. planDefaultMonthlyCapUsd: anyOf: - type: number description: >- USD, to micro-dollar precision (up to 6 decimals), so sub-cent spend such as a Judge try is visible. - type: 'null' capRemainingUsd: anyOf: - type: number description: >- USD, to micro-dollar precision (up to 6 decimals), so sub-cent spend such as a Judge try is visible. - type: 'null' description: Cap minus month to date (never below 0), or null for no cap. approvalThresholdUsd: anyOf: - type: number description: >- USD, to micro-dollar precision (up to 6 decimals), so sub-cent spend such as a Judge try is visible. - type: 'null' description: 'Runs estimated above this need an owner''s approval. Null: off.' freeCreditUsd: type: number description: Platform credit included each month (Free plan). creditRemainingUsd: type: number description: >- USD, to micro-dollar precision (up to 6 decimals), so sub-cent spend such as a Judge try is visible. pendingApprovals: type: array items: type: object properties: id: type: string runId: type: string reason: type: string enum: - monthly_cap - threshold status: type: string enum: - pending - approved - rejected - expired estimatedCostUsd: type: number description: USD. monthToDateUsd: anyOf: - type: number description: USD. - type: 'null' capUsd: anyOf: - type: number description: USD. - type: 'null' requestedBy: type: - string - 'null' decidedBy: type: - string - 'null' decisionNote: type: - string - 'null' decidedAt: type: - string - 'null' expiresAt: type: string createdAt: type: string benchmarkId: type: string benchmarkName: type: string required: - id - runId - reason - status - estimatedCostUsd - monthToDateUsd - capUsd - requestedBy - decidedBy - decisionNote - decidedAt - expiresAt - createdAt - benchmarkId - benchmarkName additionalProperties: {} description: Open approval requests across the organization, oldest first. canEditSettings: type: boolean description: Whether the caller is an owner and may change the cap and threshold. required: - month - plan - paid - monthToDateUsd - settledUsd - reservedUsd - monthlyCapUsd - monthlyCapSource - planDefaultMonthlyCapUsd - capRemainingUsd - approvalThresholdUsd - freeCreditUsd - creditRemainingUsd - pendingApprovals - canEditSettings additionalProperties: {} description: >- Month-to-date benchmark spend against the cap and the included credit, with open approval requests. Error: type: object required: - error properties: error: type: string description: >- Short error name: `Unauthorized`, `Validation failed`, `Not found`, or a stable snake_case code you can match on, such as `unknown_query_parameter`, `invalid_parameter`, `payload_too_large` or `not_found`. message: type: string description: A plain-English sentence saying what is wrong and how to fix it. code: type: string description: >- Stable, machine-readable cause; match on this rather than on `error` or `message`. On a 401: `missing_credentials`, `malformed_credentials`, `ingest_key_not_allowed` (a write-only observability ingest key was used on an endpoint that needs an API key), `key_expired` or `invalid_credentials`. Elsewhere, for example: `not_found`, `invalid_parameter`, `unknown_query_parameter`, `missing_parameter`, `validation_failed`, `invalid_json`, `payload_too_large`, `conversation_not_found`, `plan_required`. hint: type: string description: >- The next step to try: where to find the right id, which parameters the endpoint takes, how to upgrade the plan, how to authenticate. parameter: type: string description: 'With `invalid_parameter`: the query parameter that was rejected.' unknown: type: array items: type: string description: >- With `unknown_query_parameter`: the parameters that were sent but are not accepted here. valid: type: array items: type: string description: >- With `unknown_query_parameter`: the parameters this endpoint accepts. details: type: object additionalProperties: true responses: ValidationFailed: description: >- The request body or query string failed validation. `code` says which kind (`validation_failed`, `invalid_json`, `invalid_parameter`, `unknown_query_parameter`, `missing_parameter`), and an enum filter names the allowed values in `valid` (every repeated value is checked, e.g. `?status=open&status=zz` is a 400). A `validation_failed` body also carries `message` (the first failing fields), `hint` (how to fix it, for example that a finding `description` is a TipTap JSON document and not a string) and `details` (field name to messages). content: application/json: schema: $ref: '#/components/schemas/Error' Unauthorized: description: >- Missing or invalid API key. The body names the cause in `code` (for example `ingest_key_not_allowed` when a write-only ingest key is used here) with a `message` and `hint`. content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: bearerAuth: type: http scheme: bearer description: >- Send `Authorization: Bearer YOUR_API_KEY`. The key resolves to a single organization. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.