UUID Generation API

Name: UUID Generation API API
Brand: UUID Generation API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsPackage RegistryapiKey3 EndpointsREST

For Agents

Generate UUIDs (default and version-specific) via a small REST API for prototypes, scripts, and agent workflows that need hosted unique identifiers.

Connect the UUID Generation API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the UUID Generation API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with UUID Generation API API.

Generate a default UUID via a single GET request

Generate a version-specific UUID by passing the version path parameter

Batch UUIDs via POST when shaping a multi-id request

Seed test fixtures with deterministic UUID-shaped identifiers

GET STARTED

Start building with UUID Generation API API

Explore with Jentic

View OpenAPI Document

The UUID Generation API produces RFC-style universally unique identifiers via a small REST surface. Three endpoints cover a default UUID generation, a versioned UUID generation by version number, and a POST variant for batch or shaped requests. The API is suitable for prototypes, lightweight microservices, scripted data pipelines, and agent workflows that prefer a hosted UUID source over an in-process library. Responses are short JSON objects containing the generated identifier and version metadata.

Use Cases

Patterns agents use UUID Generation API API for, with concrete tasks.

★ Hosted UUID Source for Lightweight Scripts

Scripts that run in environments without a UUID library can call the UUID Generation API to mint identifiers on demand. The default endpoint returns a UUID per call and the version-specific endpoint lets the caller choose a UUID version by path parameter. This is faster than installing a library when the script is short-lived or runs in a constrained sandbox.

Call GET /uuid once per inbound record and store the returned identifier as the primary key.

Test Data and Fixtures

Engineers seed test data with UUIDs from the API instead of generating them locally. Calling the POST variant or looping the GET endpoint produces a fixtures file of ready-shaped identifiers, which the test suite then reads in. This approach can keep test environments deterministic across machines when paired with a shared seed file.

Loop GET /uuid 1000 times and write each identifier to a fixtures CSV used by the integration tests.

Tracked Links and Tickets

When generating short tracked links or support tickets, calling the UUID API supplies a unique identifier that can be encoded into the link or ticket reference. Pairing the UUID with another tool (such as a QR Code generator) produces a fully scannable, traceable artefact in two API calls.

Call GET /uuid for each support ticket and attach the returned identifier as the ticket reference.

AI Agent Identifier Tool

Wire the UUID Generation API into Jentic so any agent can mint a unique identifier when one is needed mid-workflow. Through Jentic the agent searches by intent, the API key remains vaulted, and the agent receives the UUID JSON to pass into a downstream tool such as a database write or a tracked link.

Use Jentic to search 'generate a uuid', load GET /uuid, and execute it to obtain an identifier for the next step in the workflow.

Key Endpoints

3 endpoints — the uuid generation api produces rfc-style universally unique identifiers via a small rest surface.

METHOD

PATH

DESCRIPTION

GET

/uuid

Generate a default UUID

POST

/uuid

Generate a UUID via a POST request for shaped or batch use

GET

/uuid/version/{version}

Generate a UUID of a specific version

GET

/uuid

Generate a default UUID

POST

/uuid

Generate a UUID via a POST request for shaped or batch use

GET

/uuid/version/{version}

Generate a UUID of a specific version

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The X-Fungenerators-Api-Secret API key is stored encrypted in the Jentic vault. Agents call the UUID operation through Jentic and the key is added to the request server-side, never in the agent's prompt or logs.

Intent-based discovery

Agents search Jentic for intents like 'generate a uuid' and receive the GET /uuid operation along with its parameter schema, ready to execute.

Time to first call

Direct Fungenerators integration: about an hour for header auth and request handling. Through Jentic: under 10 minutes to first successful call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Fun Generators API

Same vendor; pairs UUIDs with QR Codes for tracked links and tickets

Use QR Code alongside UUID when each generated identifier needs a scannable artefact.

Complementary

Name Generation API

Same vendor; pairs unique identifiers with themed names for labelled assets

Add Namegen alongside UUID when assets need both a unique identifier and a human-readable name.

Alternative

Random Lottery Number generator API

Same vendor; produces bounded random number sets instead of UUIDs

Choose Lottery when the use case needs lottery-shaped numeric draws rather than universal identifiers.

FAQs

Specific to using UUID Generation API API through Jentic.

What authentication does the UUID Generation API use?

It uses an API key supplied in the X-Fungenerators-Api-Secret request header. Through Jentic the key is held encrypted in the vault and attached at execution time, so agents never see the raw secret.

Can I generate a version 4 UUID with this API?

Yes. Call GET /uuid/version/{version} with the version number you want (for example 4). The response is a JSON object containing the generated UUID.

What are the rate limits for the UUID Generation API?

The OpenAPI spec does not declare explicit rate limits. Fungenerators applies plan-based quotas listed on its subscription page at fungenerators.com, so consult the plan you signed up for.

How do I generate a UUID through Jentic?

Search 'generate a uuid' via the Jentic SDK or MCP server, load GET /uuid, and execute it. Install with pip install jentic and authenticate using your ak_* key.

Why use a hosted UUID API instead of a local library?

Most production code should generate UUIDs locally. The API is useful when the runtime cannot install dependencies, when scripts need a shared external source for auditability, or when an agent workflow needs a UUID inside a tool call rather than a code execution step.

What is the difference between the GET and POST variants on /uuid?

GET /uuid returns a default UUID with no body. POST /uuid accepts a request body, which the live API uses to shape batch or version-specific generation. Use the GET variant for the simplest one-off call.