> ## Documentation Index > Fetch the complete documentation index at: https://docs.iotools.cloud/llms.txt > Use this file to discover all available pages before exploring further. # LLM API Cost Calculator > Estimate the USD cost of an LLM API workload from input/output token counts and daily call volume, using published per-model list prices — with per-call, per-day, per-month and per-year projections and a side-by-side model comparison. [Try LLM API Cost Calculator in your browser →](https://iotools.cloud/tool/llm-api-cost-calculator/) ## OpenAPI ````yaml https://api.iotools.cloud/v1/openapi post /v1/tool/llm-api-cost-calculator openapi: 3.1.0 info: title: iotools.cloud API version: 1.0.0 description: >- Run any iotools.cloud tool over HTTP. Authenticate with `Authorization: Bearer iot_live_…`. **Only `POST /v1/tool/{slug}` costs credits.** Every GET here — the catalog, a tool's schema, your balance — is free. A tool call is charged its own weight or your plan's per-call minimum, whichever is larger; `x-iotools-credit-cost` on each operation is quoted at the free-tier minimum, and `GET /v1/tools/list` returns the exact figure for your key. `GET /v1/me/credits` reports what you have left, and `GET /v1/me/usage` reports what it went on. Failures are RFC 9457 problem documents — branch on `code`. servers: - url: https://api.iotools.cloud description: Production security: - bearerAuth: [] tags: - name: Catalog description: Find a tool and read its contract. Free. - name: Converters description: >- Convert between formats, encodings, and units — Base64, CSV and JSON, timestamps, and more. Fast, free, and processed right in your browser. - name: Formatters description: >- Format, beautify, minify, and validate code and data — JSON, HTML, CSS, SQL, and regex. Clean up messy input in one click, with nothing to upload. - name: Generators description: >- Generate exactly what you need and on demand — passwords, UUIDs, QR codes, hashes, random numbers, and more. Secure, instant, and free. - name: Calculators description: >- Crunch the numbers fast — from everyday math to specialized conversions and unit work. Free online calculators that run entirely in your browser. - name: Editors description: >- Edit and transform text, code, and images with quick, focused editors that run entirely in your browser — nothing to install, and no sign-up needed. - name: Utilities description: >- Everyday developer and web utilities — DNS and IP lookups, redirect and certificate checkers, and other quick diagnostics. Free and privacy-friendly. - name: Account description: Your key's allowance, limits and usage history. paths: /v1/tool/llm-api-cost-calculator: post: tags: - Calculators summary: LLM API Cost Calculator description: >- Estimate the USD cost of an LLM API workload from input/output token counts and daily call volume, using published per-model list prices — with per-call, per-day, per-month and per-year projections and a side-by-side model comparison. [Try LLM API Cost Calculator in your browser →](https://iotools.cloud/tool/llm-api-cost-calculator/) operationId: run_llm_api_cost_calculator requestBody: required: false content: application/json: schema: type: object properties: inputTokens: type: number description: Input Tokens minimum: 0 maximum: 10000000 outputTokens: type: number description: Output Tokens minimum: 0 maximum: 10000000 callsPerDay: type: number description: Calls / Day minimum: 0 maximum: 10000000 model: enum: - gpt-4o - gpt-4o-mini - gpt-4-turbo - gpt-4 - gpt-3.5-turbo - o1 - o1-mini - claude-3-5-sonnet - claude-3-opus - claude-3-haiku - gemini-1-5-pro - gemini-1-5-flash - llama-3-1-405b - llama-3-1-70b - llama-3-1-8b description: Model pricingMode: enum: - realtime - batch description: Pricing Mode required: [] examples: gpt_4o_1000_in_500_out_1000_calls_day_real_time: summary: GPT-4o · 1000 in / 500 out · 1000 calls/day (real-time) value: inputTokens: '1000' outputTokens: '500' callsPerDay: '1000' model: gpt-4o pricingMode: realtime gpt_4o_batch_pricing_50_off: summary: GPT-4o · batch pricing (50% off) value: inputTokens: '1000' outputTokens: '500' callsPerDay: '1000' model: gpt-4o pricingMode: batch responses: '200': description: Tool output content: application/json: examples: gpt_4o_1000_in_500_out_1000_calls_day_real_time: summary: GPT-4o · 1000 in / 500 out · 1000 calls/day (real-time) value: tool: llm-api-cost-calculator tool_version: 1.0.1 outputs: breakdown: - metric: Input cost / call value: $0.002500 - metric: Output cost / call value: $0.005000 - metric: Cost / call value: $0.007500 - metric: Cost / day value: $7.50 - metric: Cost / month value: $228.28 - metric: Cost / year value: $2,739 comparison: - model: GPT-4o provider: OpenAI in-out-1m: $2.50 / $10.00 per-call: $0.007500 per-day: $7.50 per-month: $228.28 - model: GPT-4o mini provider: OpenAI in-out-1m: $0.1500 / $0.6000 per-call: $0.000450 per-day: $0.4500 per-month: $13.70 - model: GPT-4 Turbo provider: OpenAI in-out-1m: $10.00 / $30.00 per-call: $0.0250 per-day: $25.00 per-month: $760.94 - model: GPT-4 provider: OpenAI in-out-1m: $30.00 / $60.00 per-call: $0.0600 per-day: $60.00 per-month: $1,826 - model: GPT-3.5 Turbo provider: OpenAI in-out-1m: $0.5000 / $1.50 per-call: $0.001250 per-day: $1.25 per-month: $38.05 - model: o1 provider: OpenAI in-out-1m: $15.00 / $60.00 per-call: $0.0450 per-day: $45.00 per-month: $1,370 - model: o1-mini provider: OpenAI in-out-1m: $3.00 / $12.00 per-call: $0.009000 per-day: $9.00 per-month: $273.94 - model: Claude 3.5 Sonnet provider: Anthropic in-out-1m: $3.00 / $15.00 per-call: $0.0105 per-day: $10.50 per-month: $319.59 - model: Claude 3 Opus provider: Anthropic in-out-1m: $15.00 / $75.00 per-call: $0.0525 per-day: $52.50 per-month: $1,598 - model: Claude 3 Haiku provider: Anthropic in-out-1m: $0.2500 / $1.25 per-call: $0.000875 per-day: $0.8750 per-month: $26.63 - model: Gemini 1.5 Pro provider: Google in-out-1m: $1.25 / $5.00 per-call: $0.003750 per-day: $3.75 per-month: $114.14 - model: Gemini 1.5 Flash provider: Google in-out-1m: $0.0750 / $0.3000 per-call: $0.000225 per-day: $0.2250 per-month: $6.85 - model: Llama 3.1 405B provider: Meta in-out-1m: $3.00 / $3.00 per-call: $0.004500 per-day: $4.50 per-month: $136.97 - model: Llama 3.1 70B provider: Meta in-out-1m: $0.8800 / $0.8800 per-call: $0.001320 per-day: $1.32 per-month: $40.18 - model: Llama 3.1 8B provider: Meta in-out-1m: $0.1800 / $0.1800 per-call: $0.000270 per-day: $0.2700 per-month: $8.22 credits_used: 3 credits_remaining: null gpt_4o_batch_pricing_50_off: summary: GPT-4o · batch pricing (50% off) value: tool: llm-api-cost-calculator tool_version: 1.0.1 outputs: breakdown: - metric: Input cost / call value: $0.001250 - metric: Output cost / call value: $0.002500 - metric: Cost / call value: $0.003750 - metric: Cost / day value: $3.75 - metric: Cost / month value: $114.14 - metric: Cost / year value: $1,370 comparison: - model: GPT-4o provider: OpenAI in-out-1m: $1.25 / $5.00 per-call: $0.003750 per-day: $3.75 per-month: $114.14 - model: GPT-4o mini provider: OpenAI in-out-1m: $0.0750 / $0.3000 per-call: $0.000225 per-day: $0.2250 per-month: $6.85 - model: GPT-4 Turbo provider: OpenAI in-out-1m: $5.00 / $15.00 per-call: $0.0125 per-day: $12.50 per-month: $380.47 - model: GPT-4 provider: OpenAI in-out-1m: $15.00 / $30.00 per-call: $0.0300 per-day: $30.00 per-month: $913.13 - model: GPT-3.5 Turbo provider: OpenAI in-out-1m: $0.2500 / $0.7500 per-call: $0.000625 per-day: $0.6250 per-month: $19.02 - model: o1 provider: OpenAI in-out-1m: $7.50 / $30.00 per-call: $0.0225 per-day: $22.50 per-month: $684.84 - model: o1-mini provider: OpenAI in-out-1m: $1.50 / $6.00 per-call: $0.004500 per-day: $4.50 per-month: $136.97 - model: Claude 3.5 Sonnet provider: Anthropic in-out-1m: $1.50 / $7.50 per-call: $0.005250 per-day: $5.25 per-month: $159.80 - model: Claude 3 Opus provider: Anthropic in-out-1m: $7.50 / $37.50 per-call: $0.0262 per-day: $26.25 per-month: $798.98 - model: Claude 3 Haiku provider: Anthropic in-out-1m: $0.1250 / $0.6250 per-call: $0.000438 per-day: $0.4375 per-month: $13.32 - model: Gemini 1.5 Pro provider: Google in-out-1m: $0.6250 / $2.50 per-call: $0.001875 per-day: $1.88 per-month: $57.07 - model: Gemini 1.5 Flash provider: Google in-out-1m: $0.0375 / $0.1500 per-call: $0.000112 per-day: $0.1125 per-month: $3.42 - model: Llama 3.1 405B provider: Meta in-out-1m: $3.00 / $3.00 per-call: $0.004500 per-day: $4.50 per-month: $136.97 - model: Llama 3.1 70B provider: Meta in-out-1m: $0.8800 / $0.8800 per-call: $0.001320 per-day: $1.32 per-month: $40.18 - model: Llama 3.1 8B provider: Meta in-out-1m: $0.1800 / $0.1800 per-call: $0.000270 per-day: $0.2700 per-month: $8.22 credits_used: 3 credits_remaining: null schema: type: object required: - tool - tool_version - outputs - credits_used - credits_remaining properties: outputs: type: object properties: breakdown: type: array description: Cost breakdown items: type: object properties: metric: type: string description: Metric value: type: string description: Value x-iotools-columns: - metric - value comparison: type: array description: Model comparison items: type: object properties: model: type: string description: Model provider: type: string description: Provider in-out-1m: type: string description: In / Out ($/1M) per-call: type: string description: Per Call per-day: type: string description: Per Day per-month: type: string description: Per Month x-iotools-columns: - model - provider - in-out-1m - per-call - per-day - per-month tool: type: string description: The tool's slug, echoing the {slug} in the request path. tool_version: type: string description: Output-contract version for this tool. credits_used: type: integer description: >- Credits this call consumed, after any settlement refund. 0 when metering is disabled. credits_remaining: type: - integer - 'null' description: >- Credits left in the current monthly allowance, or null when metering is disabled. request_id: type: string description: Correlation id, also sent as x-request-id. '400': $ref: '#/components/responses/ValidationError' '401': $ref: '#/components/responses/Unauthorized' '402': $ref: '#/components/responses/InsufficientCredits' '403': $ref: '#/components/responses/ToolNotAllowed' '404': $ref: '#/components/responses/ToolNotFound' '413': $ref: '#/components/responses/PayloadTooLarge' '429': $ref: '#/components/responses/RateLimited' '500': $ref: '#/components/responses/ToolFailed' '503': $ref: '#/components/responses/ToolDisabled' security: - bearerAuth: [] components: responses: ValidationError: description: Invalid request. content: application/problem+json: schema: type: object description: >- RFC 9457 problem document, served as application/problem+json. Branch on `code`; `title` is human prose and may be reworded without notice. Some failures add extension members — `fields` on validation errors, `retry_after` on 429s, `credits_used`/`credits_remaining` on billing-adjacent failures — documented on the responses that carry them. required: - type - title - status - code properties: type: type: string format: uri description: Stable documentation URI for this failure. examples: - https://iotools.cloud/docs/errors/validation_error title: type: string description: Short human-readable summary of the failure. examples: - Invalid request status: type: integer description: HTTP status code, matching the response's own status. code: type: string description: >- Stable machine-readable error code — branch on this, not `title`. enum: - validation_error detail: type: string description: Human explanation of this occurrence. request_id: type: string description: Correlation id, also sent as x-request-id. fields: type: - object - string additionalProperties: type: string description: >- What failed: a map of field name → message. Absent when the body itself is malformed; a single string when the failure isn't tied to one field. example: type: https://iotools.cloud/docs/errors/validation_error title: Invalid request status: 400 code: validation_error detail: One or more inputs are invalid — see `fields`. request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11 fields: inputString: Required Unauthorized: description: Missing or invalid API key. content: application/problem+json: schema: type: object description: >- RFC 9457 problem document, served as application/problem+json. Branch on `code`; `title` is human prose and may be reworded without notice. Some failures add extension members — `fields` on validation errors, `retry_after` on 429s, `credits_used`/`credits_remaining` on billing-adjacent failures — documented on the responses that carry them. required: - type - title - status - code properties: type: type: string format: uri description: Stable documentation URI for this failure. examples: - https://iotools.cloud/docs/errors/invalid_api_key title: type: string description: Short human-readable summary of the failure. examples: - Invalid API key status: type: integer description: HTTP status code, matching the response's own status. code: type: string description: >- Stable machine-readable error code — branch on this, not `title`. enum: - invalid_api_key detail: type: string description: Human explanation of this occurrence. request_id: type: string description: Correlation id, also sent as x-request-id. example: type: https://iotools.cloud/docs/errors/invalid_api_key title: Invalid API key status: 401 code: invalid_api_key detail: 'Provide ''Authorization: Bearer ''.' request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11 InsufficientCredits: description: Monthly credit allowance exhausted. content: application/problem+json: schema: type: object description: >- RFC 9457 problem document, served as application/problem+json. Branch on `code`; `title` is human prose and may be reworded without notice. Some failures add extension members — `fields` on validation errors, `retry_after` on 429s, `credits_used`/`credits_remaining` on billing-adjacent failures — documented on the responses that carry them. required: - type - title - status - code properties: type: type: string format: uri description: Stable documentation URI for this failure. examples: - https://iotools.cloud/docs/errors/insufficient_credits title: type: string description: Short human-readable summary of the failure. examples: - Insufficient credits status: type: integer description: HTTP status code, matching the response's own status. code: type: string description: >- Stable machine-readable error code — branch on this, not `title`. enum: - insufficient_credits detail: type: string description: Human explanation of this occurrence. request_id: type: string description: Correlation id, also sent as x-request-id. credits_used: type: integer description: Always 0 — a refused call charges nothing. credits_remaining: type: integer description: Credits left in the allowance — fewer than this call costs. example: type: https://iotools.cloud/docs/errors/insufficient_credits title: Insufficient credits status: 402 code: insufficient_credits detail: This call costs 1 credit and 0 remain in this month's allowance. request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11 credits_used: 0 credits_remaining: 0 ToolNotAllowed: description: Tool exists but has no API surface. content: application/problem+json: schema: type: object description: >- RFC 9457 problem document, served as application/problem+json. Branch on `code`; `title` is human prose and may be reworded without notice. Some failures add extension members — `fields` on validation errors, `retry_after` on 429s, `credits_used`/`credits_remaining` on billing-adjacent failures — documented on the responses that carry them. required: - type - title - status - code properties: type: type: string format: uri description: Stable documentation URI for this failure. examples: - https://iotools.cloud/docs/errors/tool_not_allowed title: type: string description: Short human-readable summary of the failure. examples: - Tool not available over the API status: type: integer description: HTTP status code, matching the response's own status. code: type: string description: >- Stable machine-readable error code — branch on this, not `title`. enum: - tool_not_allowed detail: type: string description: Human explanation of this occurrence. request_id: type: string description: Correlation id, also sent as x-request-id. example: type: https://iotools.cloud/docs/errors/tool_not_allowed title: Tool not available over the API status: 403 code: tool_not_allowed detail: >- "Background Remover" is available on iotools.cloud but has no API endpoint. request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11 ToolNotFound: description: No such tool. content: application/problem+json: schema: type: object description: >- RFC 9457 problem document, served as application/problem+json. Branch on `code`; `title` is human prose and may be reworded without notice. Some failures add extension members — `fields` on validation errors, `retry_after` on 429s, `credits_used`/`credits_remaining` on billing-adjacent failures — documented on the responses that carry them. required: - type - title - status - code properties: type: type: string format: uri description: Stable documentation URI for this failure. examples: - https://iotools.cloud/docs/errors/tool_not_found title: type: string description: Short human-readable summary of the failure. examples: - Tool not found status: type: integer description: HTTP status code, matching the response's own status. code: type: string description: >- Stable machine-readable error code — branch on this, not `title`. enum: - tool_not_found detail: type: string description: Human explanation of this occurrence. request_id: type: string description: Correlation id, also sent as x-request-id. example: type: https://iotools.cloud/docs/errors/tool_not_found title: Tool not found status: 404 code: tool_not_found detail: No tool with that slug. See GET /v1/tools/list. request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11 PayloadTooLarge: description: Body too large. content: application/problem+json: schema: type: object description: >- RFC 9457 problem document, served as application/problem+json. Branch on `code`; `title` is human prose and may be reworded without notice. Some failures add extension members — `fields` on validation errors, `retry_after` on 429s, `credits_used`/`credits_remaining` on billing-adjacent failures — documented on the responses that carry them. required: - type - title - status - code properties: type: type: string format: uri description: Stable documentation URI for this failure. examples: - https://iotools.cloud/docs/errors/payload_too_large title: type: string description: Short human-readable summary of the failure. examples: - Payload too large status: type: integer description: HTTP status code, matching the response's own status. code: type: string description: >- Stable machine-readable error code — branch on this, not `title`. enum: - payload_too_large detail: type: string description: Human explanation of this occurrence. request_id: type: string description: Correlation id, also sent as x-request-id. example: type: https://iotools.cloud/docs/errors/payload_too_large title: Payload too large status: 413 code: payload_too_large detail: Request body exceeds this tool's size limit. request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11 RateLimited: description: Per-minute rate limit exceeded. headers: Retry-After: description: Seconds to wait before retrying (RFC 9110 delta-seconds). schema: type: integer content: application/problem+json: schema: type: object description: >- RFC 9457 problem document, served as application/problem+json. Branch on `code`; `title` is human prose and may be reworded without notice. Some failures add extension members — `fields` on validation errors, `retry_after` on 429s, `credits_used`/`credits_remaining` on billing-adjacent failures — documented on the responses that carry them. required: - type - title - status - code properties: type: type: string format: uri description: Stable documentation URI for this failure. examples: - https://iotools.cloud/docs/errors/rate_limited title: type: string description: Short human-readable summary of the failure. examples: - Rate limit exceeded status: type: integer description: HTTP status code, matching the response's own status. code: type: string description: >- Stable machine-readable error code — branch on this, not `title`. enum: - rate_limited detail: type: string description: Human explanation of this occurrence. request_id: type: string description: Correlation id, also sent as x-request-id. retry_after: type: integer description: >- Seconds until the window resets — the same value as the `Retry-After` header. example: type: https://iotools.cloud/docs/errors/rate_limited title: Rate limit exceeded status: 429 code: rate_limited detail: Too many requests. Retry in 30s. request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11 retry_after: 30 ToolFailed: description: Tool failed to run. content: application/problem+json: schema: type: object description: >- RFC 9457 problem document, served as application/problem+json. Branch on `code`; `title` is human prose and may be reworded without notice. Some failures add extension members — `fields` on validation errors, `retry_after` on 429s, `credits_used`/`credits_remaining` on billing-adjacent failures — documented on the responses that carry them. required: - type - title - status - code properties: type: type: string format: uri description: Stable documentation URI for this failure. examples: - https://iotools.cloud/docs/errors/processing_error - https://iotools.cloud/docs/errors/internal_error title: type: string description: Short human-readable summary of the failure. examples: - Tool failed to run - Internal error status: type: integer description: HTTP status code, matching the response's own status. code: type: string description: >- Stable machine-readable error code — branch on this, not `title`. enum: - processing_error - internal_error detail: type: string description: Human explanation of this occurrence. request_id: type: string description: Correlation id, also sent as x-request-id. credits_used: type: integer description: >- Always 0 on `processing_error` — a failed run is refunded, floor included. credits_remaining: type: integer description: >- Credits left after the refund. Absent when metering is disabled. example: type: https://iotools.cloud/docs/errors/processing_error title: Tool failed to run status: 500 code: processing_error detail: The tool failed to run. Please try again. request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11 credits_used: 0 ToolDisabled: description: Tool temporarily disabled. content: application/problem+json: schema: type: object description: >- RFC 9457 problem document, served as application/problem+json. Branch on `code`; `title` is human prose and may be reworded without notice. Some failures add extension members — `fields` on validation errors, `retry_after` on 429s, `credits_used`/`credits_remaining` on billing-adjacent failures — documented on the responses that carry them. required: - type - title - status - code properties: type: type: string format: uri description: Stable documentation URI for this failure. examples: - https://iotools.cloud/docs/errors/tool_disabled - https://iotools.cloud/docs/errors/api_unconfigured title: type: string description: Short human-readable summary of the failure. examples: - Tool temporarily disabled - API not configured status: type: integer description: HTTP status code, matching the response's own status. code: type: string description: >- Stable machine-readable error code — branch on this, not `title`. enum: - tool_disabled - api_unconfigured detail: type: string description: Human explanation of this occurrence. request_id: type: string description: Correlation id, also sent as x-request-id. example: type: https://iotools.cloud/docs/errors/tool_disabled title: Tool temporarily disabled status: 503 code: tool_disabled detail: This tool is temporarily unavailable. Try again shortly. request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11 securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: iot_live_… ````