> ## 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. # Coffee Brew Ratio Calculator > Calculate how much coffee and water to use for pour-over, French press, AeroPress, Chemex, drip, moka pot, cold brew or espresso — from the water you have, the coffee you have, or the cups you want — with grams, ounces, tablespoons and a grind/temperature/time brew guide. [Try Coffee Brew Ratio Calculator in your browser →](https://iotools.cloud/tool/coffee-brew-ratio-calculator/) ## OpenAPI ````yaml https://api.iotools.cloud/v1/openapi post /v1/tool/coffee-brew-ratio-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/coffee-brew-ratio-calculator: post: tags: - Calculators summary: Coffee Brew Ratio Calculator description: >- Calculate how much coffee and water to use for pour-over, French press, AeroPress, Chemex, drip, moka pot, cold brew or espresso — from the water you have, the coffee you have, or the cups you want — with grams, ounces, tablespoons and a grind/temperature/time brew guide. [Try Coffee Brew Ratio Calculator in your browser →](https://iotools.cloud/tool/coffee-brew-ratio-calculator/) operationId: run_coffee_brew_ratio_calculator requestBody: required: true content: application/json: schema: type: object properties: method: enum: - pour-over - chemex - french-press - aeropress - drip - moka-pot - turkish - cold-brew-concentrate - cold-brew - espresso - custom description: Brew method customRatio: type: number description: Custom ratio (1:x) minimum: 3 maximum: 30 strength: enum: - mild - standard - strong description: Strength solveFrom: enum: - water - coffee - cups description: I know… amount: type: number description: Amount minimum: 0 waterUnit: enum: - ml - floz description: Water unit coffeeUnit: enum: - g - oz - tbsp description: Coffee unit cupSize: enum: - '6' - '8' - '12' description: Cup size required: - amount examples: pour_over_from_350_ml_of_water: summary: Pour-over from 350 mL of water value: method: pour-over strength: standard solveFrom: water amount: '350' waterUnit: ml strong_french_press_for_four_8_oz_mugs: summary: Strong French press for four 8 oz mugs value: method: french-press strength: strong solveFrom: cups amount: '4' cupSize: '8' espresso_from_an_18_g_dose: summary: Espresso from an 18 g dose value: method: espresso strength: standard solveFrom: coffee amount: '18' coffeeUnit: g custom_1_15_from_4_tablespoons_of_coffee: summary: Custom 1:15 from 4 tablespoons of coffee value: method: custom customRatio: '15' strength: standard solveFrom: coffee amount: '4' coffeeUnit: tbsp responses: '200': description: Tool output content: application/json: examples: pour_over_from_350_ml_of_water: summary: Pour-over from 350 mL of water value: tool: coffee-brew-ratio-calculator tool_version: 1.0.2 outputs: summary: >- Use 21.9 g coffee with 350 mL water (1:16) for about 306 mL brewed. breakdown: - item: Brew method value: Pour-over (V60, Kalita) - item: 'Ratio (coffee : water)' value: '1:16' - item: Coffee value: 21.9 g · 0.77 oz · 4.4 tbsp - item: Water value: 350 mL · 11.8 fl oz - item: Estimated brewed coffee value: 306 mL · 10.4 fl oz - item: Grind size value: Medium-fine - item: Water temperature value: 92–96 °C (198–205 °F) - item: Brew time value: 2:30–3:30 min credits_used: 5 credits_remaining: null strong_french_press_for_four_8_oz_mugs: summary: Strong French press for four 8 oz mugs value: tool: coffee-brew-ratio-calculator tool_version: 1.0.2 outputs: summary: >- Use 84.5 g coffee with 1115 mL water (1:13.2) for about 946 mL brewed. breakdown: - item: Brew method value: French press - item: 'Ratio (coffee : water)' value: 1:13.2 (strong, from 1:15) - item: Coffee value: 84.5 g · 2.98 oz · 16.9 tbsp - item: Water value: 1115 mL · 37.7 fl oz - item: Estimated brewed coffee value: 946 mL · 32 fl oz - item: Grind size value: Coarse - item: Water temperature value: 93–96 °C (200–205 °F) - item: Brew time value: 4 min steep credits_used: 5 credits_remaining: null espresso_from_an_18_g_dose: summary: Espresso from an 18 g dose value: tool: coffee-brew-ratio-calculator tool_version: 1.0.2 outputs: summary: Use 18 g coffee for 36 g of espresso out (1:2). breakdown: - item: Brew method value: Espresso - item: 'Ratio (coffee : water)' value: '1:2' - item: Coffee value: 18 g · 0.63 oz · 3.6 tbsp - item: Beverage yield (in the cup) value: 36 g - item: Grind size value: Fine - item: Water temperature value: 90–94 °C (194–201 °F) - item: Brew time value: 25–30 s credits_used: 5 credits_remaining: null custom_1_15_from_4_tablespoons_of_coffee: summary: Custom 1:15 from 4 tablespoons of coffee value: tool: coffee-brew-ratio-calculator tool_version: 1.0.2 outputs: summary: >- Use 20 g coffee with 300 mL water (1:15) for about 260 mL brewed. breakdown: - item: Brew method value: Custom ratio - item: 'Ratio (coffee : water)' value: '1:15' - item: Coffee value: 20 g · 0.71 oz · 4 tbsp - item: Water value: 300 mL · 10.1 fl oz - item: Estimated brewed coffee value: 260 mL · 8.8 fl oz credits_used: 5 credits_remaining: null schema: type: object required: - tool - tool_version - outputs - credits_used - credits_remaining properties: outputs: type: object properties: summary: type: string description: Recipe breakdown: type: array description: Brew breakdown items: type: object properties: item: type: string description: Item value: type: string description: Value x-iotools-columns: - item - value 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' '422': $ref: '#/components/responses/UnprocessableInput' '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://docs.iotools.cloud/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://docs.iotools.cloud/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://docs.iotools.cloud/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://docs.iotools.cloud/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://docs.iotools.cloud/errors/insufficient_credits - >- https://docs.iotools.cloud/errors/vendor_api_tier_limit_exceeded title: type: string description: Short human-readable summary of the failure. examples: - Insufficient credits - Free-tier API limit reached for this tool 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 - vendor_api_tier_limit_exceeded 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://docs.iotools.cloud/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://docs.iotools.cloud/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://docs.iotools.cloud/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://docs.iotools.cloud/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://docs.iotools.cloud/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://docs.iotools.cloud/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://docs.iotools.cloud/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 UnprocessableInput: description: Well-formed request, but there is no result to return. 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://docs.iotools.cloud/errors/unprocessable_input title: type: string description: Short human-readable summary of the failure. examples: - Input cannot be processed 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: - unprocessable_input 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 `unprocessable_input` — 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://docs.iotools.cloud/errors/unprocessable_input title: Input cannot be processed status: 422 code: unprocessable_input detail: >- This video has no captions or subtitles, so there is no transcript to extract. request_id: e4042b29-8f1e-4c7a-9b52-6f0d1a3c7e11 credits_used: 0 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://docs.iotools.cloud/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://docs.iotools.cloud/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://docs.iotools.cloud/errors/processing_error - https://docs.iotools.cloud/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://docs.iotools.cloud/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://docs.iotools.cloud/errors/tool_disabled - https://docs.iotools.cloud/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://docs.iotools.cloud/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_… ````