Entropy Token Generator

platform.entropy_token

ProductionBounded custom (Class B)best-effortinstantv1.0.0

No network

Overview

We generate a cryptographically secure random token using SecureRandom and return it base64url-encoded. Each call produces a unique, unpredictable value — useful as nonces, session identifiers, or proof-of-freshness tokens. Omit bytes to get 32 random bytes (range 16..64). Do not use this for structured UUIDs, human-readable passwords, or alphabet/prefix control — use the dedicated security.generate_secure_token skill instead.

LLMs cannot generate cryptographic randomness. Any token an LLM produces is pattern-derived and predictable. We guarantee each token comes from a cryptographically secure random source.

Reliability

Non-deterministic by design — each call produces a new, independent token. The bytes come from the JVM's SecureRandom, a cryptographic random source; nothing is derived from your label, your tenant, or the clock. Retry-safe: calling again simply produces another token, and the previous one is gone. No side effects, no storage, no network dependency. Input validation (not retryable): bytes outside 16..64; label longer than 64 chars; batch array longer than 50.

Context footprint

Replaces a fundamentally impossible LLM task (true randomness) with a single tool call. Zero ambiguity about entropy quality. A single token costs 1 execution credit; a batch costs 1 credit per item.

When to use it

Whenever you need an unpredictable, unique token for security or freshness purposes.

When you need a random integer (use math.random_number), a deterministic identifier derived from input, or a token with a specific alphabet or prefix (use security.generate_secure_token).

Scope

Note

Generates cryptographically secure random tokens using SecureRandom, encoded as base64url strings. Each token is unique and unpredictable.

Non-goals

Does not generate structured UUIDs (v4 or v7)
Does not store or manage tokens — output is ephemeral
Does not generate human-memorable passwords
Does not offer an alphabet choice or a token prefix — this is the raw base64url primitive; use security.generate_secure_token for hex, base32, or alphanumeric output, a 'sk_live'-style prefix, or a reported entropy width

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 output possible

What this means

This skill may receive sensitive content and may return submitted, transformed, extracted, or reformatted content.

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 may contain submitted or transformed 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
bytes	integer	No	Random-byte count; omit it for 32.
label	string	No	Bookkeeping label; omit it for empty.
batch	array	No	From 1 through 50 closed token requests with optional bytes and label; omit it for one token.

Output schema

Field	Type	Required	Description
tool	string	Yes	Producing skill key.
version	string	Yes	Producing semantic version.
tenant_id	string	Yes	Bounded platform correlation identifier.
request_id	string	Yes	Bounded platform correlation identifier.
server_time	string	Yes	UTC generation instant.
label	string	Yes	Resolved bookkeeping label.
bytes	integer	Yes	Random-byte count actually generated for this token.
token	string	Yes	Unpadded Base64url random token.

API contract

POST /v1/execute

curl

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"platform.entropy_token","input":{"bytes":32}}'

Integrations

TypeScript SDK

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

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

const { output } = await sq.execute("platform.entropy_token", {"bytes":32});

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 structured UUIDs (v4 or v7)
Does not store or manage tokens — output is ephemeral
Does not generate human-memorable passwords
Does not offer an alphabet choice or a token prefix — this is the raw base64url primitive; use security.generate_secure_token for hex, base32, or alphanumeric output, a 'sk_live'-style prefix, or a reported entropy width
Generating human-readable passwords
Creating random numbers within a range (use math.random_number)
Producing deterministic identifiers
A token that must fit a specific alphabet or carry an environment marker (use security.generate_secure_token)

How to call

POST /v1/execute (requires authentication)

Request bodyjson

{
  "skillKey": "platform.entropy_token",
  "input": {
    "bytes": 32
  }
}

Examples

Default 32-byte token for a one-time nonce

Inputjson

{
  "bytes": 32
}

Expected outputjson

{
  "tool": "platform.entropy_token",
  "token": "Xq7mB2vTdKp9LrN4sYhC1jZ8wEfG5aUoQ3iM6bVxRtA",
  "version": "1.0.0",
  "bytes": 32,
  "request_id": "req-9f3c21a7",
  "server_time": "2026-05-23T10:00:00Z",
  "tenant_id": "tenant-4821",
  "label": ""
}

Tip

32 bytes is the default and gives you a 43-character token; yours will of course be a different value

Shorter labelled token for a CSRF cookie