Input JSON
{
"operation": "uuid",
"version": 4,
"count": 2
}Attest tools · Developer utilities: cron, regex, UUID, slug and JSON
Generate a random UUID
Generate two version 4 UUIDs for sample record identifiers.
Captured output JSON
{
"operation": "uuid",
"version": 4,
"count": 2,
"uuids": [
"a9e7cea8-2805-43c7-b3a9-fdba976fc7d1",
"50c19c54-91c5-4321-ba17-2b8e28376b20"
],
"time_ordered": false,
"variant": "RFC 9562 (obsoletes RFC 4122)",
"limits": {
"max_count": 100
},
"source": "Generated locally. Version 4 from node:crypto randomUUID; version 7 built to RFC 9562 §5.7 with the §6.2 monotonic counter.",
"notes": [
"Version 4 is 122 random bits from the operating system CSPRNG (node:crypto randomUUID). Unguessable, but unordered: as a database key it scatters inserts across the index."
],
"notice": "General information only, computed from the caller's own input. Nothing sent here is stored.",
"checked_at": "2026-10-20T20:47:47.583Z"
}API call
curl -s -X POST https://getattest.com.au/api/v1/dev \
-H "authorization: Bearer $ATTEST_API_KEY" \
-H "content-type: application/json" \
--data-raw '{"operation":"uuid","version":4,"count":2}'Run this call with your own bearer key. Issue an API key.
About this example
The input was validated and run locally through the registered service. The output above is a display preview of the captured service result. File bytes are described instead of printed, and strings longer than 400 characters are truncated; the HTTP API also adds call_id, credits_charged and credits_remaining. Timestamps and generated identifiers will vary.
Source: apps/api/svc/dev_utils.mjs