> ## 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. # Keyboard Mileage Calculator > Estimate how far your fingers travel while typing — daily, weekly, yearly and over any number of years — from your typing speed, hours per day and keyboard type. Includes keystroke, word and typing-time totals, plus fun distance comparisons (marathons, 5Ks, times around the equator). Runs entirely in your browser. [Try Keyboard Mileage Calculator in your browser →](https://iotools.cloud/tool/keyboard-mileage-calculator/) ## OpenAPI ````yaml https://api.iotools.cloud/v1/openapi post /v1/tool/keyboard-mileage-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/keyboard-mileage-calculator: post: tags: - Calculators summary: Keyboard Mileage Calculator description: >- Estimate how far your fingers travel while typing — daily, weekly, yearly and over any number of years — from your typing speed, hours per day and keyboard type. Includes keystroke, word and typing-time totals, plus fun distance comparisons (marathons, 5Ks, times around the equator). Runs entirely in your browser. [Try Keyboard Mileage Calculator in your browser →](https://iotools.cloud/tool/keyboard-mileage-calculator/) operationId: run_keyboard_mileage_calculator requestBody: required: false content: application/json: schema: type: object properties: keyboardType: enum: - compact - laptop - standard - mechanical - custom description: Keyboard type customTravel: type: number description: Distance per keystroke (cm) minimum: 0.1 maximum: 20 typingSpeed: type: number description: Typing speed (WPM) minimum: 1 maximum: 300 hoursPerDay: type: number description: Hours spent typing per day minimum: 0.1 maximum: 24 daysPerWeek: type: number description: Days typing per week minimum: 1 maximum: 7 years: type: number description: Time span (years) minimum: 0.1 maximum: 100 required: [] examples: standard_keyboard_50_wpm_4h_day_5_days_week_10_years: summary: Standard keyboard, 50 WPM, 4h/day, 5 days/week, 10 years value: keyboardType: standard typingSpeed: '50' hoursPerDay: '4' daysPerWeek: '5' years: '10' mechanical_keyboard_fast_typist_one_year: summary: Mechanical keyboard, fast typist, one year value: keyboardType: mechanical typingSpeed: '80' hoursPerDay: '6' daysPerWeek: '5' years: '1' custom_compact_keyboard_light_typing_5_years: summary: Custom compact keyboard, light typing, 5 years value: keyboardType: custom customTravel: '1.2' typingSpeed: '40' hoursPerDay: '2' daysPerWeek: '3' years: '5' responses: '200': description: Tool output content: application/json: examples: standard_keyboard_50_wpm_4h_day_5_days_week_10_years: summary: Standard keyboard, 50 WPM, 4h/day, 5 days/week, 10 years value: tool: keyboard-mileage-calculator tool_version: 1.0.2 outputs: summary: >- Over 10 years, your fingers travel an estimated 2,964 km (1,842 mi) while typing. distanceTable: - period: Daily distance: 1.140 km (0.708 mi) - period: Weekly distance: 5.700 km (3.542 mi) - period: Yearly distance: 296.4 km (184.2 mi) - period: Total (10 years) distance: 2,964 km (1,842 mi) statsTable: - metric: Total keystrokes value: 156,000,000 - metric: Keystrokes per day value: 60,000 - metric: Total words typed value: 31,200,000 - metric: ≈ novels (80,000 words each) value: '390.0' - metric: Total hours spent typing value: 10,400 - metric: Finger speed while typing value: 7.92 cm/s (0.285 km/h) comparisonsTable: - equivalent-to: Marathons (42.195 km) count: '70.25' - equivalent-to: 5K races count: '592.8' - equivalent-to: Trips around Earth's equator count: '0.0740' notes: >- Assumes 1.9 cm of finger travel per keystroke and the standard "1 word = 5 characters" convention, so 50 WPM = 250 keystrokes/min. This is a fun order-of-magnitude estimate, not measured biomechanics — actual finger travel varies with typing technique, keyboard layout and how close your fingers stay to the home row. 52 weeks/year and even key distribution are assumed; leap years and typing-free vacations aren't modeled. credits_used: 5 credits_remaining: null mechanical_keyboard_fast_typist_one_year: summary: Mechanical keyboard, fast typist, one year value: tool: keyboard-mileage-calculator tool_version: 1.0.2 outputs: summary: >- Over 1 year, your fingers travel an estimated 823.7 km (511.8 mi) while typing. distanceTable: - period: Daily distance: 3.168 km (1.969 mi) - period: Weekly distance: 15.8 km (9.8 mi) - period: Yearly distance: 823.7 km (511.8 mi) - period: Total (1 year) distance: 823.7 km (511.8 mi) statsTable: - metric: Total keystrokes value: 37,440,000 - metric: Keystrokes per day value: 144,000 - metric: Total words typed value: 7,488,000 - metric: ≈ novels (80,000 words each) value: '93.6' - metric: Total hours spent typing value: 1,560 - metric: Finger speed while typing value: 14.67 cm/s (0.528 km/h) comparisonsTable: - equivalent-to: Marathons (42.195 km) count: '19.52' - equivalent-to: 5K races count: '164.7' - equivalent-to: Trips around Earth's equator count: '0.0206' notes: >- Assumes 2.2 cm of finger travel per keystroke and the standard "1 word = 5 characters" convention, so 80 WPM = 400 keystrokes/min. This is a fun order-of-magnitude estimate, not measured biomechanics — actual finger travel varies with typing technique, keyboard layout and how close your fingers stay to the home row. 52 weeks/year and even key distribution are assumed; leap years and typing-free vacations aren't modeled. credits_used: 5 credits_remaining: null custom_compact_keyboard_light_typing_5_years: summary: Custom compact keyboard, light typing, 5 years value: tool: keyboard-mileage-calculator tool_version: 1.0.2 outputs: summary: >- Over 5 years, your fingers travel an estimated 224.6 km (139.6 mi) while typing. distanceTable: - period: Daily distance: 0.288 km (0.179 mi) - period: Weekly distance: 0.864 km (0.537 mi) - period: Yearly distance: 44.9 km (27.9 mi) - period: Total (5 years) distance: 224.6 km (139.6 mi) statsTable: - metric: Total keystrokes value: 18,720,000 - metric: Keystrokes per day value: 24,000 - metric: Total words typed value: 3,744,000 - metric: ≈ novels (80,000 words each) value: '46.8' - metric: Total hours spent typing value: 1,560 - metric: Finger speed while typing value: 4.00 cm/s (0.144 km/h) comparisonsTable: - equivalent-to: Marathons (42.195 km) count: '5.32' - equivalent-to: 5K races count: '44.9' - equivalent-to: Trips around Earth's equator count: '0.0056' notes: >- Assumes 1.2 cm of finger travel per keystroke and the standard "1 word = 5 characters" convention, so 40 WPM = 200 keystrokes/min. This is a fun order-of-magnitude estimate, not measured biomechanics — actual finger travel varies with typing technique, keyboard layout and how close your fingers stay to the home row. 52 weeks/year and even key distribution are assumed; leap years and typing-free vacations aren't modeled. 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: Result distanceTable: type: array description: Estimated finger-travel distance items: type: object properties: period: type: string description: Period distance: type: string description: Distance x-iotools-columns: - period - distance statsTable: type: array description: Keystrokes, words & time items: type: object properties: metric: type: string description: Metric value: type: string description: Value x-iotools-columns: - metric - value comparisonsTable: type: array description: Distance comparisons items: type: object properties: equivalent-to: type: string description: Equivalent to count: type: string description: Count x-iotools-columns: - equivalent-to - count notes: type: string description: Notes 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_… ````