apidx UUID Generator
Random UUID v4 (RFC 9562) as an HTTP API. Version and variant bits are set exactly as the RFC's Appendix A.3 "Ver and Var Overwrite"; randomness comes from the platform CSPRNG.
An alternative to the X Pay UUID listing on x402 Bazaar — same per-call shape, sold there and on RapidAPI Hub.
API
GET /v1/uuid?count=1&format=uuid — the RapidAPI listing proxies this endpoint.
GET /x402/uuid — the direct x402 face: an unpaid call returns 402 with the payment metadata; a paid call returns the UUIDs.
count— 1 to 100 (default 1)format—uuid(default) |urn|hex|int(RFC 9562 §4 presentation forms)- Response:
{"success":true,"uuids":[…],"count":N,"format":"…","uuid":"…"}—uuidappears exactly when one UUID in uuid form is requested. - Rate limit: 30 requests / 10 s per client IP.
Pricing
Pay per call in USDC with x402, or buy prepaid credits by card. The same price holds on RapidAPI, which bills its subscribers and pays us out.
| Endpoint | What it does | Price | Free |
|---|
Try it
curl "$ORIGIN/v1/uuid?count=5"
Spec
UUIDs follow RFC 9562 (§4 string format, §4.1 variant, §4.2 version, §5.4 UUIDv4 layout). The test suite checks the RFC's own Appendix A.3 vector verbatim. Service descriptor: /v1/status.
Buy credits
Your API key (shown once; keep it):
Send it as Authorization: Bearer <key>. Credits appear after payment.