# Uuid parse strict

`uuid-parse-strict` · version 1.0.0 · Identifiers & check digits · free, no key needed

Strictly parse one canonical lowercase RFC 9562 UUID.

**Use when you need to: strictly parse uuid · inspect uuid version and variant · validate canonical uuid syntax.**

## Decide before calling

Read the [versioned contract](/v1/tools/uuid-parse-strict/versions/1.0.0) and the supported scope below. Reuse `uuid-parse-strict@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-parse-strict@1.0.0` for strictly parse uuid. 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

- strictly parse uuid
- inspect uuid version and variant
- validate canonical uuid syntax
- uuid text to 16 bytes
- network order octets of a uuid
- reject noncanonical uuid spelling

## Not supported

- lenient UUID parsing
- UUID generation

## Behavior

- Only the 8-4-4-4-12 lowercase hexadecimal form is accepted; braces and uppercase are rejected.
- Nil and max UUID values are valid and version is the high nibble of octet 6.
- Disclaimer: format transform only; provides no confidentiality, integrity, or authenticity.

## Input

- `uuid` (string, required): max length 36; pattern `^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$`

## Output

- `uuid` (string, required): pattern `^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$`
- `bytes` (array of integer, required): min items 16; max items 16; each min 0; each max 255
- `version` (integer, required): min 0; max 15
- `variant` (one of "ncs", "rfc9562", "microsoft", "future", required)

## Limits

- max uuid chars: 36

## Example

Request input:

```json
{
  "uuid": "00000000-0000-0000-0000-000000000000"
}
```

Response:

```json
{
  "result": {
    "uuid": "00000000-0000-0000-0000-000000000000",
    "bytes": [
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0
    ],
    "version": 0,
    "variant": "ncs"
  }
}
```

## How to call it

### MCP

Connect `https://computefirst.net/mcp` ([setup](/docs#connect)), then call `execute` with:

```json
{
  "id": "uuid-parse-strict",
  "version": "1.0.0",
  "input": {
    "uuid": "00000000-0000-0000-0000-000000000000"
  }
}
```

### HTTP (no key)

```sh
curl -X POST https://computefirst.net/v1/tools/uuid-parse-strict/versions/1.0.0/execute \
  -H "Content-Type: application/json" \
  -d '{"uuid":"00000000-0000-0000-0000-000000000000"}'
```

The machine-readable contract is at [/v1/tools/uuid-parse-strict/versions/1.0.0](/v1/tools/uuid-parse-strict/versions/1.0.0).

### CLI

```sh
node cli.mjs run uuid-parse-strict 1.0.0 --input input.json --base-url https://computefirst.net
```

Get the client at [/clients/cli/](/clients/cli/).

## Related tools

- [Uuid inspect](/tools/uuid-inspect): Validate a canonical UUID and report its lowercase value, variant, version, and nil status.
- [Uuid format](/tools/uuid-format): Format exactly 16 octets as an RFC 9562 UUID string.
- [Ulid parse canonical](/tools/ulid-parse-canonical): Parse a canonical uppercase ULID into its exact timestamp, randomness, and 16 bytes.
- [Isin validate](/tools/isin-validate): Validate a 12-character ISIN's ISO 6166 Luhn check digit and parse its country prefix, NSIN and NSIN scheme.
- [Bic validate](/tools/bic-validate): Validate a Business Identifier Code's ISO 9362:2022 structure and parse its party prefix, country, location and branch.
- [Cn resident id parse](/tools/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.