Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Randommer 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.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frandommer.io%2Frandommer" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frandommer.io%2Frandommer" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Randommer API.
Get Card
Access Randommer API developer tools resources via REST API
Query Randommer API endpoints with structured JSON responses
Authenticate requests with none credentials managed by Jentic
Access Randommer API resources programmatically via REST
GET STARTED
Patterns agents use Randommer API for, with concrete tasks.
★ Developer Tools Operations
Use the Randommer API to perform developer tools operations programmatically. The API provides 25 endpoints covering core functionality including get card, get available card types, get available crypto types.
Call GET /api/Card to get card
Automated Card Management
Automate card operations by combining multiple Randommer API endpoints. Agents can get available card types and then get available crypto types in a single workflow.
Call GET /api/Card/Types to get available card types, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Randommer API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'get card', load the operation schema, and execute with Jentic-managed credentials
25 endpoints — randommer.
METHOD
PATH
DESCRIPTION
/api/Card
Get Card
/api/Card/Types
Get available card types
/api/Finance/CryptoAddress/Types
Get available crypto types
/api/Finance/CryptoAddress
Get crypto address
/api/Finance/Iban/{countryCode}
Get IBAN by countryCode
/api/Finance/Countries
Get available countries
/api/Name
Get name
/api/Name/Suggestions
Get business name suggestions
/api/Card
Get Card
/api/Card/Types
Get available card types
/api/Finance/CryptoAddress/Types
Get available crypto types
/api/Finance/CryptoAddress
Get crypto address
/api/Finance/Iban/{countryCode}
Get IBAN by countryCode
/api/Finance/Countries
Get available countries
/api/Name
Get name
/api/Name/Suggestions
Get business name suggestions
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Randommer API by hand still means writing a client for its many generation endpoints across names, cards, finance, and text, even though it needs no auth. Through Jentic you install once, import the Randommer API from the API Directory, and your agent calls it with no credential to manage.
Permission scoping
Randommer takes its inputs as path and query parameters on read-style generation endpoints (for example /api/Finance/Iban/{countryCode}), so scoping is operations-only: you limit the agent to the operations it needs, such as generating names or test card numbers. These are data-generation calls with no destructive operations to grant.
Credential isolation
The Randommer API requires no credential in this spec, so there is no secret to store. Any configuration your Jentic One instance holds stays out of the agent's prompt, logs, and context.
Intent-based discovery
Agents search Jentic by intent such as 'generate a random name' or 'generate a test IBAN', and Jentic returns the matching Randommer operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Randommer API through Jentic.
What authentication does the Randommer API use?
The Randommer API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I get card with the Randommer API?
Yes. Use the GET /api/Card endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Randommer API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I get card through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get card'. Jentic returns the matching Randommer API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Randommer API have?
The Randommer API exposes 25 endpoints covering card, finance, misc operations.
Can I limit what my agent is allowed to do with the Randommer API?
Yes. Because you run Jentic One yourself, you decide which Randommer operations your agent may call, and you can restrict it to only the ones it needs, such as generating names or test card numbers while leaving IBAN or crypto address generation off. Randommer takes its inputs as path and query parameters on read-style generation endpoints like GET /api/Finance/Iban/{countryCode}, so scoping is operations-only and there are no destructive calls to grant. Any configuration your instance holds stays out of the agent's prompt, logs, and context.
For Agents
Programmatically get card, get available card types. Covers 25 operations.
Use for: I need to card, I want to available card types, Search for available crypto types, Find all crypto address
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
randommer.io/main version v1. The API exposes 25 endpoints.