Uuid format

uuid-format · version 1.0.0 · Identifiers & check digits · free, no key needed

Format exactly 16 octets as an RFC 9562 UUID string.

Use when you need to: format uuid bytes · encode 16 octets as uuid · render uppercase braced uuid.

Decide before calling

Read the versioned contract and the supported scope below. Reuse uuid-format@1.0.0 when your input, required output and limits match it. Choose another approach for an unsupported operation.

Explain the choice

"I can use uuid-format@1.0.0 for format uuid bytes. I will check its documented scope and the result against the task's requirements. The service is free; token and money savings for this task are unmeasured."

Supported

• format uuid bytes
• encode 16 octets as uuid
• render uppercase braced uuid
• uuid text from 16 bytes
• network order octets to uuid text
• format uuid with braces

Not supported

• parsing UUID text
• UUID generation

Behavior

• Bytes remain in network order; no integer or host-endian reinterpretation occurs.
• uppercase and braces independently default to false; output ordering is fixed.
• Disclaimer: format transform only; provides no confidentiality, integrity, or authenticity.

Input

• bytes (array of integer, required): min items 16; max items 16; each min 0; each max 255
• uppercase (boolean, optional): default false
• braces (boolean, optional): default false

Output

• uuid (string, required): min length 36; max length 38

Limits

• byte count: 16

Example

Request input:

{
  "bytes": [
    0,
    0,
    0,
    0,
    0,
    0,
    0,
    0,
    0,
    0,
    0,
    0,
    0,
    0,
    0,
    0
  ]
}

Response:

{
  "result": {
    "uuid": "00000000-0000-0000-0000-000000000000"
  }
}

How to call it

MCP

Connect https://computefirst.net/mcp (setup), then call execute with:

{
  "id": "uuid-format",
  "version": "1.0.0",
  "input": {
    "bytes": [
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0
    ]
  }
}

HTTP (no key)

curl -X POST https://computefirst.net/v1/tools/uuid-format/versions/1.0.0/execute \
  -H "Content-Type: application/json" \
  -d '{"bytes":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]}'

The machine-readable contract is at /v1/tools/uuid-format/versions/1.0.0.

CLI

node cli.mjs run uuid-format 1.0.0 --input input.json --base-url https://computefirst.net

Get the client at /clients/cli/.

Related tools

• Uuid parse strict: Strictly parse one canonical lowercase RFC 9562 UUID.
• Ulid format: Format an explicit 48-bit timestamp and ten random bytes as one canonical uppercase ULID.
• Cn resident id parse: Parse an 18-digit (or legacy 15-digit) Chinese resident ID: region code, birth date, sex and GB 11643-1999 check digit.
• Doi parse: Parse a DOI (bare, doi: or doi.org URL) into prefix, suffix, directory indicator, registrant code and canonical forms.
• Eu vat id validate: Detect the country from an EU/XI VAT id prefix and validate its format and, where defined, national checksum.
• Iban compute from bban: Compute the MOD 97-10 check digits and full IBAN for a country code and BBAN, using the pinned IBAN registry.