fittings-crypto-random-bytes

Original：🇺🇸 English

Translated

1 scripts

Generate CSPRNG bytes from the Web Crypto API, returned as hex, base64 or a UUID. Never Math.random. Called as GET /v1/crypto/random-bytes, it takes bytes, encoding and returns value, encoding. Observed on-chain demand: agents need unguessable nonces, tokens and idempotency keys, and a language runtime without a CSPRNG or a model asked to "pick a random number" both produce predictable output. Reading this schema and dry-running the call are free and need no wallet; a real call costs $0.003, paid in USDC on Base over x402.

1installs

Sourcefittings-sh/fittings

Added on2026-08-17

NPX Install

npx skill4agent add fittings-sh/fittings fittings-crypto-random-bytes

SKILL.md Content

View Translation Comparison →

Cryptographically secure random bytes

crypto.random-bytes

on

https://fittings.sh

. One endpoint, deterministic compute.

Generate CSPRNG bytes from the Web Crypto API, returned as hex, base64 or a UUID. Never Math.random.

The call

GET https://fittings.sh/v1/crypto/random-bytes

Field	Type	Required	Notes
`bytes`	number	no	1-1024
`encoding`	string	no	hex \| base64 \| uuid

Example input:

json

{
  "bytes": 32,
  "encoding": "hex"
}

Metered

The 402 quotes a ceiling — the price of the declared cap, 1024 bytes — and settlement is for what the call actually used. A small request settles for less than it was quoted, so read the quote as an upper bound rather than a price.

Cost and provenance


Price	$0.003 per call, metered per bytes
Source	none (pure compute)
Licence	none-needed

Why call it rather than answer from memory

Observed on-chain demand: agents need unguessable nonces, tokens and idempotency keys, and a language runtime without a CSPRNG or a model asked to "pick a random number" both produce predictable output.

Calling it

A skill is loaded on its own, so this document has to be enough by itself. It does not assume the general

fittings

skill is also loaded.

call.mjs

ships alongside this file; if it is missing (this document reached you without the rest of the skill), fetch it once with

curl -sO https://fittings.sh/skill/call.mjs

.

Free, and needs no wallet. Read the schema and see what a call would cost:

bash

curl -s https://fittings.sh/catalog/crypto.random-bytes | jq

Paying. The endpoint answers

402 Payment Required

with a signed quote, you sign an authorization, and a facilitator settles it — you never send a transaction and never pay gas. Before it spends anything, the client checks its own hash against the gateway and refuses rather than sign with logic the gateway has moved past:

bash

# Dry run. Prints the quote and pays nothing, because no key is set.
node call.mjs crypto.random-bytes bytes=32 encoding=hex

# For real: a wallet holding USDC on Base, and nothing else.
export FITTINGS_PRIVATE_KEY=0x...
node call.mjs crypto.random-bytes bytes=32 encoding=hex

Spending is never a side effect of curiosity: with no

FITTINGS_PRIVATE_KEY

the client fetches the quote and stops.

FITTINGS_MAX_PRICE

caps what it will pay without asking, and defaults to $0.05.

Use a throwaway wallet holding a few dollars, not a main one. The key sits in plaintext wherever the agent runs, and the whole cost of entry is USDC on Base — no account, no API key, and no ETH, because the payer signs off-chain and the facilitator broadcasts and pays the gas.

Writing your own client instead of using this one?

@x402/core

and

@x402/evm

on npm, and the

fittings

skill records the two things that cost real debugging time: the challenge is in a response header rather than the body, and it must be re-signed from the exact request being retried.

If this is not the right service,

https://fittings.sh/catalog/search?q=...

searches all of them for free.