UUID Generator (v4 / v7)

security.generate_uuid

ProductionBounded custom (Class B)best-effortinstantv1.0.0

No network

Overview

You choose the UUID version, count, and output format; we generate RFC 9562 UUID v4 or v7 values using SecureRandom. v7 supports an explicit timestampMs for controlled testing and optional monotonic ordering within the same millisecond. Do not use this for deterministic content-derived IDs (use platform.uuid_namespace_id) or secret tokens (use platform.entropy_token or security.generate_secure_token).

An agent cannot produce real randomness, and hand-written identifiers rarely get the RFC 9562 version and variant bits right. You get standards-compliant values from a cryptographic random source instead.

Reliability

BEST_EFFORT and non-deterministic: the random bits of both v4 and v7 come from the JVM's SecureRandom, so no two calls agree. Pin timestampMs and the v7 timestamp prefix becomes reproducible, but the trailing random bits still change. Treat a v7 value as an identifier, never as a secret — the leading 48 bits are simply the clock. Input validation (not retryable): a version other than v4 or v7; a format other than canonical, urn or no_hyphen; count outside 1 to 10000; a negative timestampMs.

Context footprint

Replaces an impossible LLM task (true randomness + exact bit layout) with one call. A successful call costs 1 execution credit.

When to use it

Whenever you need standard unique identifiers, especially v7 when you want keys that sort by creation time.

When the identifier has to be derived from your data, or when you need a secret rather than an identifier.

Scope

Note

Generates RFC 9562 UUID v4 (fully random) or UUID v7 (48-bit time-ordered prefix + CSPRNG) using java.security.SecureRandom.

Non-goals

Does not generate deterministic UUID v5 (use platform.uuid_namespace_id)
Does not guarantee global uniqueness by tracking issued values
Does not produce non-standard or vanity IDs

Properties

IdempotentRetry safeStreaming supportedFile input supportedRequires external service

Capabilities

generationrandomness

Cost & billing

Flat rate per invocation

MetercallsBillable onsuccessCost per call1 credit

File handling

Accepts file_refProduces file_refMax input64 B

How we handle your data

Sensitive input, safe output

What this means

This skill may receive sensitive content, but it does not target sensitive data and returns only a structured non-sensitive result.

Squillify guarantees

Runs inside Squillify
This skill runs inside Squillify.
Payloads are not sent to an external service by this skill.
Squillify does not permanently store submitted payloads.
Telemetry records metadata only, not submitted content.
Submitted payloads are not used for training.
Submitted payloads are not reviewed by humans.
This skill does not target sensitive data.
The response does not contain submitted content.

Your responsibility

Squillify does not determine whether submitted content is sensitive. Your application is responsible for deciding what data it is allowed to submit. Your application is responsible for securing the response.

Read the Microskill Data Handling Policy

Input schema

Field	Type	Required	Description
version	string	No	UUID version; omit it for v4.
count	integer	No	UUID count; omit it for one.
format	string	No	Text format; omit it for canonical.
timestampMs	integer	No	v7 Unix millisecond clock; omit it to sample the wall clock for v7, unused for v4.
monotonic	boolean	No	Whether same-ms v7 values increase; omit it for true.

Output schema

Field	Type	Required	Description
version	string	Yes	Generated UUID version.
uuids	array	Yes	From 1 through 10,000 generated UUID strings in the requested text format, preserving request order.
timestampMs	integer	No	Caller-supplied v7 Unix millisecond.

API contract

POST /v1/execute

curl

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"security.generate_uuid","input":{"version":"v7","count":3}}'

Integrations

TypeScript SDK

import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("security.generate_uuid", {"version":"v4"});

Errors

Code	HTTP	Retryable	Description
VALIDATION_ERROR	400	No	The request payload failed schema validation.
UNAUTHORIZED	401	No	Missing or invalid API key.
SKILL_NOT_ACCESSIBLE	403	No	The API key is not granted access to this skill.
SKILL_NOT_AVAILABLE_FOR_PLAN	403	No	This skill is not included in your current plan.
PLAN_ELIGIBILITY_UNAVAILABLE	503	Yes	Plan eligibility could not be decided. Retry after backoff.
SKILL_NOT_FOUND	404	No	The requested skill or version does not exist.
TENANT_RATE_LIMITED	429	Yes	Request rate limit exceeded. Retry after backoff.
QUOTA_EXCEEDED	429	Yes	Plan quota exhausted. Retryable once the quota period resets.
EXECUTION_TIMEOUT	504	Yes	Execution exceeded the allowed time budget.

Other limits

Limit	Value
Recommended inline bytes	32 KiB

Limitations

Does not generate deterministic UUID v5 (use platform.uuid_namespace_id)
Does not guarantee global uniqueness by tracking issued values
Does not produce non-standard or vanity IDs
Deterministic content-derived IDs (use platform.uuid_namespace_id)
Cryptographic secrets or tokens (use platform.entropy_token)
Treating v7 as unguessable — it is partially time-derived

How to call

POST /v1/execute (requires authentication)

Request bodyjson

{
  "skillKey": "security.generate_uuid",
  "input": {
    "version": "v4"
  }
}

Examples

One random v4 identifier

Inputjson

{
  "version": "v4"
}

Expected outputjson

{
  "version": "v4",
  "uuids": [
    "f47ac10b-58cc-4372-a567-0e02b2c3d479"
  ]
}

Tip

Every bit but the version and variant markers is random, so your value will differ

Three time-ordered v7 keys from a fixed clock