RSA key generate

POST /api/rsa-keygen3 quota units per call · cache hits free

Generate an RSA keypair in your browser. Configurable key size (2048/3072/4096), hash, and intended usage (sign+verify or encrypt+decrypt). Returns PKCS#8 PEM private key + SPKI PEM public key.

Generates an RSA keypair using the browser/Workers Web Crypto API. Returns the **private key** as PKCS#8 PEM and the **public key** as SubjectPublicKeyInfo (SPKI) PEM — the standard wire formats accepted by `openssl`, `ssh-keygen -m PEM`, jose / JWT libraries, AWS KMS imports, etc. Inputs: - `bits`: 2048, 3072, or 4096. - `hash`: SHA-256/384/512 — embedded in the algorithm parameters for sign/verify variants. - `usage`: `signing` (PSS/PKCS1) or `encryption` (OAEP). **Security note:** the private key is returned in the API response. Don't send it anywhere unencrypted, don't log it, and clear it from clipboard/scrollback after use.

Inputs

Name	Type	Default	Description
bits	number (2048…4096)	2048	Modulus length (2048, 3072, or 4096).
hash	enum (SHA-256 \| SHA-384 \| SHA-512)	"SHA-256"	Hash algorithm baked into the key parameters.
usage	enum (signing \| encryption)	"signing"	Intended use. 'signing' → RSA-PSS; 'encryption' → RSA-OAEP.

Response

Modes: json. Cache: not cacheable.

Every response carries x-cache (HIT / MISS / BYPASS), x-cache-signature (stable across identical inputs), and the rate-limit headers listed below.

Quota & limits

Cost per call	3 units against the 10,000-unit monthly quota. Cache hits are free — only cache misses decrement.
Burst limit	200 requests per rolling minute, shared across all tools.
Max request size	`4 KiB` (base64 inflates file payloads ~33% — the limit applies to the decoded bytes).
Max response size	`16 KiB`
Timeout	30s wall clock.
Rate-limit headers	`X-RateLimit-Limit`, `X-RateLimit-Remaining`, `X-RateLimit-Burst-Limit` on every response; `X-Quota-Warning` once 80% of the monthly quota is spent; `Retry-After` on 429s.

Errors

Errors are JSON with an error string; schema failures add a details object (Zod's flattened field errors).

Status	When	Body
400	Input fails the tool's schema (wrong type, missing required field, malformed base64) or the file bytes can't be parsed as the expected format.	{ "error": "invalid inputs", "details": { "fieldErrors": { … } } }
401	Missing or invalid X-Api-Key / X-Account-Id headers (or no session when called from the browser).	{ "error": "unauthorized" }
404	Unknown tool id, or calling /api/* on the website hostname instead of api.xtract.bot.	{ "error": "not found" }
413	Request body over the tool's max request size, or an image header declaring more megapixels than the tool's pixel budget.	{ "error": "…exceeds maxRequestBytes…" }
415	Content-Type isn't application/json on the json-body transport.	{ "error": "unsupported content-type; expected application/json" }
429	Monthly quota or the 200/min burst limit exhausted. Check Retry-After and the X-RateLimit-* headers.	{ "error": "monthly quota exceeded", "monthRemaining": 0, … }
5xx	Conversion engine failure. Safe to retry; if it persists, the input is hitting a bug — please report it.	{ "error": "…" }

Code samples

Built from the default example.


curl -X POST https://api.xtract.bot/api/rsa-keygen \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -H "X-Account-Id: $XTRACT_ACCOUNT_ID" \
  -H "X-Api-Key: $XTRACT_API_KEY" \
  -d '{
  "bits": 2048,
  "hash": "SHA-256",
  "usage": "signing"
}'