UUID API
The same UUID engine behind the public generator, exposed as a rate-limited HTTP API. Beta — we ship it when there's enough demand to support it.
Who would actually use this?
- Backends in languages that don't ship v7 yet — Python, Java pre-21, older Go. Save the trouble of pulling a 4th-party library.
- Audit-heavy systems — every UUID has a provenance record on your account.
- Bulk seeding — 10K UUIDs in one call for database migrations, fixture generation, anonymizing PII.
- Teams testing v7 adoption — same API, swap version field, compare results.
Sign up for early access
Related
FAQ
Why an API for UUID generation when libraries exist?
Most teams don't need an API for v4 — every language's stdlib has a UUID generator. The API is for: (1) v7 in languages whose stdlib hasn't caught up (Python's uuid module still doesn't ship v7 in 3.12 stdlib — you need an external package), (2) centralized auditing (every UUID issued goes through your account), and (3) bulk generation with metadata (10K UUIDs with prefixes, namespaces, or sortable variants in one call).
What's the actual feature set?
Estimated v1 surface: POST /v1/uuid with { version, count }; returns up to 1,000 UUIDs per call. v3/v5 with namespace + name. v7 with optional millisecond precision override (for backfill). Validate endpoint that decodes any UUID. Per-account rate limits.
Pricing range?
Estimated, subject to change once we have signups: Free tier — 1,000 UUIDs/month, no card. ~$10–25/month — 1M UUIDs, no rate-limit bursts. ~$50–150/month — bulk plus per-org auditing. Enterprise above. These are working numbers; the waitlist gets the real conversation.
Will it stay free if I just want a couple UUIDs?
The browser tool stays free forever. The API free tier is for code use; if you only need a UUID once in a while, just use the public generator — no account.