Back to Browse
Identity Mint — Server-Side UUIDv4/v5 + Handle Generation
x402
Identity Mint — Server-Side UUIDv4/v5 + Handle Generation is a paid API for AI agents from agent402.tools, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-14).
Mints a random UUIDv4 user-id, derives a deterministic UUIDv5 correlation-id from an email, and slugifies a display name into a URL-safe handle in one round-trip
Price / call$0.05
Success—
StatusUnknown
How this service works
Bundled execution of the Server-side identity mint workflow - The server-side identity-issuance round-trip: mint a random user-id (UUIDv4), derive a deterministic cross-system correlation-id (UUIDv5), turn the display name into a URL-safe handle, ...
Output
Returns a bundled identity object containing: a random UUIDv4 as the user-id, a deterministic UUIDv5 correlation-id derived from the email, a URL-safe slugified handle derived from the display name, and a signed JWT using the provided HMAC secret.
Example use cases
Example prompt
“Mint a new server-side identity for user 'Jane Doe' with email jane.doe@example.com — generate a random UUID for them, derive a deterministic correlation ID from their email, and produce a URL-safe handle, signing with my secret 'supersecrethmac42'.”
Technical details
Endpoint
POSThttps://agent402.tools/api/skill/identity-mintWhen to prefer
Use this endpoint when you need to atomically provision a new user identity in a single server-side call — specifically when you need all three artifacts (random UUID, deterministic correlation UUID from email, URL-safe handle) plus a signed JWT in one round-trip, rather than calling separate UUID, slug, and JWT libraries or endpoints individually.
Side effects
- Missing required fields (email, displayName, signingSecret) returns a 4xx validation error
- Invalid or malformed email may result in a non-deterministic or error UUIDv5
- Insufficient payment (x402 protocol) results in a 402 Payment Required response
- Malformed signingSecret may produce an invalid JWT or error response
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| string | the user's email (used to derive the deterministic UUIDv5 correlation ID) | |
| displayName | string | the user's display name (will be slugified for the URL handle) |
| signingSecret | string | the server's JWT HMAC signing secret |
Output
Schema · Response
{
"type": "json",
"example": {
"args": {
"email": "alice.oconnor@example.com",
"displayName": "Alice O'Connor",
"signingSecret": "server_demo_jwt_secret_do_not_use_in_prod"
},
"pack": "identity-mint",
"steps": [
{
"ok": true,
"slug": "uuid",
"result": {}
},
{
"ok": true,
"slug": "uuid-v5",
"result": {}
},
{
"ok": true,
"slug": "slugify",
"result": {}
},
{
"ok": true,
"slug": "password",
"result": {}
},
{
"ok": true,
"slug": "hash",
"result": {}
},
{
"ok": true,
"slug": "jwt-sign",
"result": {}
},
{
"ok": true,
"slug": "base64",
"result": {}
}
],
"summary": "7/7 steps succeeded"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"