Generate a UUID v7

Input JSON

{
  "operation": "uuid",
  "version": 7,
  "count": 2
}

Captured output JSON

{
  "operation": "uuid",
  "version": 7,
  "count": 2,
  "uuids": [
    "01a15b11-fb85-73ba-a9b7-0ac84110cb96",
    "01a15b11-fb85-73bb-97a5-d6106b00ddc7"
  ],
  "time_ordered": true,
  "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 7 puts a 48-bit Unix millisecond timestamp in the leading bits, so these sort in the order they were made — useful as a database primary key where version 4 would scatter writes across an index.",
    "Ids minted inside the same millisecond carry the RFC 9562 §6.2 counter in rand_a, so the ids in this response are strictly increasing even when the clock does not move.",
    "The timestamp is this server's clock, and it is readable by anyone holding the id. Do not use version 7 where the creation time is a secret."
  ],
  "notice": "General information only, computed from the caller's own input. Nothing sent here is stored.",
  "checked_at": "2026-10-20T20:47:47.588Z"
}

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":7,"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

Tool reference and limits · API key guide