canonical: https://jentic.com/apis/fungenerators.com/fungenerators-uuid

# Fungenerators UUID Generation API

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.

## For AI agents

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

## Scope

Does not provide cryptographic key generation, hashing, or persistent identifier registries - use for hosted UUID generation only.

## Capabilities

- 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
- Supply identifiers to lightweight scripts that prefer a hosted source over a local library

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| 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 |

## Key resources

- **UUID** — Generate a UUID via a default or version-specific endpoint

## Why Jentic

- **Setup:** Wiring the UUID Generation API by hand means configuring its secret-key request header auth against api.fungenerators.com and handling the generate and version calls yourself. Through Jentic you install once, import the UUID Generation API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** This API exposes generation operations rather than per-resource paths, so scope it by operation: limit the agent to the operations it needs, such as generating a UUID or requesting a specific UUID version, and leave anything you do not want it running out of the allowed set. Every operation the agent can run is one you chose to include.
- **Credential handling:** Your Fungenerators API secret is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'generate a UUID' or 'create a version 4 identifier', and Jentic returns the matching UUID Generation API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Fun Generators API** — Same vendor; pairs UUIDs with QR Codes for tracked links and tickets
- **Name Generation API** — Same vendor; pairs unique identifiers with themed names for labelled assets
- **Random Lottery Number generator API** — Same vendor; produces bounded random number sets instead of UUIDs

## FAQ

### 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.

### Can I limit what my agent is allowed to do with the UUID Generation API?

Yes. Because you run Jentic One yourself, your own rules decide which operations the agent may call, and this API is scoped by operation rather than by resource path. You can allow only the operations the agent needs, such as generating a default UUID or requesting a specific UUID version, and leave every other operation out of the allowed set. Only the operations you explicitly include are ones the agent can run, and your Fungenerators API secret stays with your instance and is attached at execution time.