API marketplace

Score words by their letter tiles for Scrabble and Words With Friends. The score endpoint adds up the face value of each tile in a word — with the per-letter breakdown — and the values endpoint returns the point value of every letter for the chosen ruleset. Blank tiles (? _ *) count as zero. Both the standard English Scrabble distribution and the Words With Friends distribution are built in. Perfect for word-game apps and bots, puzzle and quiz tools, teaching and leaderboards. Note: this is the raw tile value — double/triple letter and word squares and the 50-point bingo bonus are not applied. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. Distinct from dictionary, spelling and text-statistics APIs.

Uptime

100.0%

Latency

83ms

Subs

4,320

Reflow plain text to a fixed column width on word boundaries — the classic word-wrap you need for terminal and CLI output, email and plain-text formatting, code comments, README and changelog blocks, and fixed-width reports. The wrap endpoint breaks text to a chosen width while preserving paragraphs (blank-line separated), with optional left indentation and the option to hard-break words longer than the line; the unwrap endpoint does the reverse, collapsing a wrapped block back into single-line paragraphs. Pure local computation — no key, no third-party service, instant; up to 200,000 characters via POST. Live, nothing stored. 3 endpoints. Distinct from case conversion, slugs and text statistics.

Uptime

100.0%

Latency

76ms

Subs

3,550

Everyday percentage maths as an API. Four clear operations: what is X% of a value (15% of 200 = 30); what percentage one number is of another (30 is 15% of 200); the percentage change between two numbers, with the direction and the raw difference (200 → 250 is a 25% increase); and applying a percentage increase or decrease to a value (200 + 15% = 230). Handy for discounts, tips and tax, growth and KPI deltas, progress bars, dashboards and quick spreadsheet-style sums — without writing a formula. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 5 endpoints. A focused calculator, distinct from a general math-expression engine.

Uptime

100.0%

Latency

89ms

Subs

3,723

Escape a string so it is safe to drop into a specific context. Pick a target — a regular expression (so the text matches literally), a shell command (POSIX single-quote wrapping), a JSON string, a CSV field (RFC 4180 quoting) or a SQL string literal — and get back the correctly escaped value, plus a short note on the rule applied. The contexts endpoint lists every target with a worked example. Perfect for code generation, building commands and queries, templating and data export, and safely interpolating user input. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. The SQL context is a quoted literal for convenience, not a replacement for parameterised queries. Distinct from base64/hex/URL/HTML-entity encoders.

Uptime

100.0%

Latency

75ms

Subs

4,600

Convert text to Unicode braille and back. Uses uncontracted (Grade 1) English braille: the 26 letters, digits with the number sign, capitals with the capital sign, and common punctuation, all output as Unicode Braille Patterns (U+2800–U+28FF) so they render anywhere. The to-braille endpoint turns ordinary text into braille; the from-braille endpoint decodes braille back to text. Unknown characters pass through unchanged. Perfect for accessibility tooling and education, labels and signage mockups, braille-display previews and learning resources. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. Grade 1 only (no contractions). Distinct from cipher/alphabet encoders and from general text transforms.

Uptime

100.0%

Latency

77ms

Subs

4,859

Add and verify check digits with the standard algorithms — Luhn (mod 10), Verhoeff, Damm and ISO 7064 mod 97-10 — on any number. The generate endpoint returns the check digit(s) and the complete number; the validate endpoint tells you whether a number's check digit is correct. Luhn is the familiar mod-10 scheme behind credit cards, IMEI and many ID numbers; Verhoeff and Damm are single-digit schemes that also catch all adjacent-transposition errors; mod 97-10 produces two check digits and is the scheme used by IBAN. Perfect for generating and validating reference, account, membership and order numbers, and for data-entry integrity. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. Distinct from credit-card and barcode validators, which apply a fixed algorithm to one specific number format.

Uptime

100.0%

Latency

76ms

Subs

3,905

Name any colour. The nearest endpoint takes a colour as a hex, an rgb() value, an r,g,b triple or another name and returns the closest of the 140+ CSS named colours — matched perceptually with CIE76 Lab distance, not naive RGB, so the name actually looks right — along with the distance and whether it is an exact match. The name endpoint resolves a CSS colour keyword (e.g. rebeccapurple, cornflowerblue) to its hex and RGB, and list returns the whole named-colour set. Perfect for design tools and pickers, accessibility and theming, turning brand hex codes into human labels, and naming colours in generated palettes. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. Distinct from colour conversion / palette / contrast tooling, which does not name colours.

Uptime

100.0%

Latency

78ms

Subs

3,457

Work with NDJSON / JSON Lines — the one-JSON-value-per-line format used by application and audit logs, streaming and LLM responses, jq, BigQuery, Elasticsearch bulk and many data pipelines. The to-array endpoint parses an NDJSON stream into a regular JSON array; to-ndjson does the reverse, turning a JSON array into NDJSON (one compact value per line); and validate checks every line independently, reporting which lines are valid and the exact parse error for any that are not. Blank lines are ignored. Perfect for log processing, ETL, data import/export and stream debugging. Pure local computation — no key, no third-party service, instant; up to 4 MB via POST. Live, nothing stored. 4 endpoints. Distinct from JSON validation/formatting and from CSV tooling.

Uptime

100.0%

Latency

76ms

Subs

4,737

Recipe and kitchen conversions as an API. Convert between volume units (teaspoon, tablespoon, cup, fl-oz, ml, litre, pint, quart, gallon) and between mass units (gram, kilogram, ounce, pound) — and, crucially, between volume and mass for a specific ingredient using its density, so 1 cup of all-purpose flour ≈ 125 g, 1 cup of granulated sugar ≈ 200 g and 1 cup of water ≈ 237 g. 30 common ingredients are built in (flours, sugars, butter, oils, honey, rice, oats, cocoa, cornstarch and more), each with its grams-per-cup. Perfect for recipe apps, scaling and "metric vs cups" conversion, shopping lists and meal-prep tools. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. Distinct from general physical unit conversion, which has no ingredient densities.

Uptime

100.0%

Latency

72ms

Subs

3,795

A running-pace calculator as an API. Work out pace and speed from a distance and a time (pace per kilometre and per mile, plus km/h, mph and m/s); compute the finish time from a distance and a target pace; predict your time at another distance using Peter Riegel's formula (T2 = T1 × (D2/D1)^1.06) — e.g. estimate a half-marathon from a 10K; and generate a split-time table for even pacing. Times accept seconds, M:SS or H:MM:SS. Perfect for running and fitness apps, race planning, training logs and pace bands. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 5 endpoints. Distinct from general unit conversion and from body-metric (BMI/BMR) health calculators.

Uptime

100.0%

Latency

74ms

Subs

3,157

Great-circle (as-the-crow-flies) navigation maths between latitude/longitude points. The distance endpoint returns the straight-line distance in metres, kilometres, miles and nautical miles, plus the initial and final compass bearing and the nearest 16-point compass direction. The destination endpoint computes where you end up from a start point, a bearing and a distance, and the midpoint endpoint finds the great-circle midpoint between two points. Perfect for proximity and radius search, geofencing, flight and shipping estimates, "distance from me" features and mapping. Pure local computation — no key, no third-party service, instant. These are straight-line distances on a spherical earth, not road routes. Live, nothing stored. 4 endpoints. Distinct from road routing, GeoJSON geometry measurement and coordinate-format conversion.

Uptime

100.0%

Latency

78ms

Subs

3,497

Convert and normalize plane angles. The convert endpoint moves a value between degrees, radians, gradians (gons), turns/revolutions, arcminutes, arcseconds, milliradians and DMS (degrees-minutes-seconds) — parse a DMS string like 12°34'56" or format a decimal angle as DMS. The normalize endpoint wraps any angle into the 0–360° or the −180–180° range. Perfect for graphics and game maths, CAD and surveying, robotics, astronomy and navigation headings. This covers plane angles specifically — a category general unit converters leave out. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. Distinct from general unit conversion and from geographic-coordinate conversion.

Uptime

100.0%

Latency

72ms

Subs

4,804

Address values inside a JSON document by JSON Pointer (RFC 6901) — the /a/b/0 path syntax used by JSON Patch (RFC 6902), JSON Schema and OpenAPI $ref. The get endpoint resolves the value at a pointer (and tells you whether it exists); set writes a value at a pointer and returns the modified document (use - as the final array token to append); and list enumerates every pointer in a document, optionally only the leaf values. Token escaping (~0 for ~, ~1 for /) is handled for you. Perfect for surgically reading and patching deep JSON, building config and form tooling, and walking API responses. Pure local computation — no key, no third-party service, instant; up to 2 MB via POST. Live, nothing stored. 4 endpoints. Distinct from JSONPath querying, JSON diff/patch and dot-notation flattening.

Uptime

100.0%

Latency

78ms

Subs

4,265

Produce a canonical hex dump of any input and parse a hex dump back into bytes. The dump endpoint formats data the way hexdump -C and xxd do — an offset column, the bytes in hex (grouped in eights), and a printable-ASCII gutter — with a configurable number of bytes per line and optional uppercase. Feed text as UTF-8, or binary as hex or base64. The parse endpoint reverses any hex dump — tolerating offset columns and ASCII gutters, or a plain run of hex — and returns the reconstructed bytes as hex, base64 and (when printable) text. Perfect for inspecting binary payloads, debugging protocols and file formats, diffing buffers and teaching. Pure local computation — no key, no third-party service, instant; up to 1 MB via POST. Live, nothing stored. 3 endpoints. Distinct from a plain base64/hex encoder.

Uptime

100.0%

Latency

75ms

Subs

4,522

Encode content into a data: URI and decode a data: URI back to its content (RFC 2397). data: URIs inline a file directly into HTML, CSS, JSON or email — perfect for small images, SVG, fonts and icons that you want to embed without a separate HTTP request. The encode endpoint wraps your content (given as UTF-8 text, base64 or hex for binary) with a chosen media type and charset, in either base64 or URL (percent) encoding; the decode endpoint parses any data: URI and returns its media type, charset, whether it was base64, the byte size, and the payload as text and/or base64. Pure local computation — no key, no third-party service, instant; up to 4 MB via POST. Live, nothing stored. 3 endpoints. Distinct from a plain base64/hex encoder and from SVG-specific tooling.

Uptime

100.0%

Latency

78ms

Subs

4,604

Match file paths against glob patterns — the same wildcard language used by .gitignore, CI/CD path filters, build tools and the shell. Test whether a single path matches a pattern, or filter a whole list of paths down to the ones that match. Full minimatch support: * (within a segment) and ** (across segments), ? for one character, [abc] character classes, {a,b,c} brace expansion and extended globs, with options for case-insensitivity, matching dotfiles and basename-only matching. Perfect for path-based rules, file selection, route guards, allow/deny lists and config validation. Pure local computation — no key, no third-party service, instant; send large lists via POST. Live, nothing stored. 3 endpoints. Distinct from regular-expression testing and from JSON path queries.

Uptime

100.0%

Latency

86ms

Subs

3,806

A Semantic Versioning (SemVer 2.0.0) toolkit as an API. Parse a version string into its major, minor, patch, prerelease and build parts; compare two versions; test whether a version satisfies an npm-style range (^1.2.3, ~1.4, >=2 <3, 1.x); increment a version to the next major, minor, patch or prerelease; and filter a list of versions by a range to find which match and the highest and lowest satisfying. Powered by the canonical node-semver. Perfect for dependency and release tooling, CI gates, update checkers, compatibility rules and package dashboards. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 6 endpoints. Distinct from package-registry lookups and vulnerability databases.

Uptime

100.0%

Latency

72ms

Subs

4,209

Generate and verify Apache/nginx htpasswd credentials. Hash a password with bcrypt (recommended), Apache's classic apr1 MD5, or sha1, and get back the ready-to-paste user:hash line for a .htpasswd file or an nginx auth_basic_user_file. The verify endpoint checks a password against any of those hash formats, auto-detecting the algorithm from the hash prefix ($2 for bcrypt, $apr1$ for apr1, {SHA} for sha1). Perfect for setting up HTTP Basic Auth, provisioning scripts, CI and container builds, and admin tooling. Pure local computation — credentials are hashed in memory and never stored; send them via POST. Live. 3 endpoints. Distinct from generic bcrypt password hashing — this targets the htpasswd file format and Apache-specific algorithms.

Uptime

100.0%

Latency

118ms

Subs

3,674

Normalize and fold Unicode text. Convert any string to one of the four Unicode normalization forms — NFC, NFD, NFKC, NFKD — so that visually identical text with different code-point compositions (é as one code point vs e + a combining accent) compares and stores consistently. Fold diacritics and special letters to plain ASCII (café → cafe, Straße → Strasse, Ångström → Angstrom, Łódź → Lodz) for slugs, search keys and filenames; the fi ligature and similar compatibility characters are expanded under NFKC/NFKD. And compare two strings for equality after normalization, optionally case-insensitively. Perfect for deduplication, search and indexing, username and identifier checks, and defending against look-alike (homoglyph) input. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. Distinct from Unicode character-database lookups and from text segmentation.

Uptime

100.0%

Latency

71ms

Subs

4,882

Every HTTP status code as an API. Look up any code (e.g. 404, 429, 503) and get its standard reason phrase, its class (1xx Informational, 2xx Success, 3xx Redirection, 4xx Client Error, 5xx Server Error), a plain-English description, the RFC that defines it, and handy flags for whether it is an error and whether it is commonly safe to retry (408, 425, 429, 500, 502, 503, 504). List every assigned code or filter by class, and enumerate the five status classes. Perfect for API clients and gateways, error pages, logging and monitoring dashboards, documentation and teaching. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. Distinct from host/uptime checkers that report a live status — this is the reference dictionary of the codes themselves.

Uptime

100.0%

Latency

78ms

Subs

4,187

Fast non-cryptographic checksums as an API. Compute CRC-32 — the integrity check used by ZIP, gzip, PNG and Ethernet — and Adler-32 — the checksum used by zlib — over UTF-8 text, hex or base64 input, returned in hex and as signed and unsigned 32-bit integers. Ideal for file- and message-integrity verification, cache keys and ETags, change detection and deduplication, where you want a quick fingerprint rather than a secure hash. Pure local computation — no key, no third-party service, instant; send binary via the hex or base64 encoding (up to 4 MB). Live, nothing stored. 4 endpoints. Explicitly NOT for security — for cryptographic digests (MD5, SHA-256, HMAC) use a hashing API instead.

Uptime

100.0%

Latency

76ms

Subs

3,343

A Unix file-permission calculator as an API. Convert a symbolic permission string (rwxr-xr-x) to its octal mode (755) and back, and explain any mode in plain English with a per-class breakdown (owner / group / others, each read / write / execute). Full support for the special bits — setuid (4), setgid (2) and the sticky bit (1) — so 4755 ↔ rwsr-xr-x and 1777 ↔ rwxrwxrwt are handled correctly, including the capital S/T forms. Perfect for Dockerfiles and CI scripts, deployment and provisioning tooling, teaching, and any time you need to double-check a chmod value. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. Distinct from anything that touches real files or networking.

Uptime

100.0%

Latency

70ms

Subs

3,654

Turn data into a ready-to-paste table. Give it JSON — either an array of objects (columns are taken from the keys) or an array of arrays (the first row is the header) — or raw CSV, and get back a clean GitHub-flavoured Markdown table or a monospace ASCII (box-drawn) table with auto-sized columns. Markdown output supports left/center/right column alignment and escapes pipes; the CSV parser is RFC-4180 aware (quoted fields, embedded commas and newlines). Perfect for README and documentation generation, CLI and log output, changelogs, chat bots and pull-request comments. Pure local computation — no key, no third-party service, instant; send large datasets via POST. Live, nothing stored. 3 endpoints. Distinct from CSV parsing/analysis and from Markdown rendering.

Uptime

100.0%

Latency

75ms

Subs

4,545

Render BBCode — the [b]…[/b] markup used by forums, bulletin boards, game communities and many comment systems — into clean HTML, or strip it down to plain text. Supports bold, italic, underline, strikethrough, lists, quotes, code blocks, links, images, colour and size. Dangerous URL schemes (javascript:, data:, vbscript:) in links and images are neutralised, so the HTML is safe to display. The to-text endpoint removes all markup for previews, search indexes, notifications and excerpts. Powered by the bbob parser. Pure local computation — no key, no third-party service, instant; send large posts via POST. Live, nothing stored. 3 endpoints. Distinct from Markdown rendering and HTML-to-Markdown conversion.

Uptime

100.0%

Latency

76ms

Subs

4,731