Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GeneradorDNI 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%2Fgeneradordni.es%2Fgeneradordni" | 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%2Fgeneradordni.es%2Fgeneradordni" | 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 GeneradorDNI API.
Generate valid Spanish NIF, NIE, and CIF identifiers for tax-form test fixtures
Produce synthetic IBAN account numbers and credit card details that pass Luhn checks
Mint full person profiles including passport and social security numbers for staging databases
Create Spanish-format vehicle plate numbers and 17-character VINs for fleet management tests
GET STARTED
Return company profiles with CIF, address, and trade name for B2B onboarding flows
Output randomised Lorem-style characters, words, and paragraphs for UI placeholder content
Patterns agents use GeneradorDNI API for, with concrete tasks.
★ QA Fixture Seeding
QA teams building test suites for Spanish-market applications need locale-correct identifiers that pass downstream validation. GeneradorDNI returns NIFs, NIEs, CIFs, and IBANs that conform to the official check-digit algorithms, so test cases exercise real validation paths instead of skipping them. A typical staging seed run takes minutes via /doi/nif and /bank/account and replaces hand-curated fixture files.
Call /doi/nif and /bank/account to produce 50 valid NIF and IBAN pairs and write them to a staging fixture file
Demo Environment Population
Sales demos and product onboarding need realistic-looking customer profiles without leaking real PII. GeneradorDNI builds full person and company profiles - name, identifier, address, banking, vehicle - that look authentic to a Spanish reviewer but contain no real identities. The /profiles/person and /profiles/company endpoints return ready-to-insert JSON.
Generate 25 person profiles via /profiles/person and load them into the demo CRM as new contacts
Payment Flow Testing
Engineers testing checkout and recurring-billing flows need card numbers and bank accounts that satisfy validators without triggering live transactions. GeneradorDNI emits Luhn-valid card numbers and structurally-correct IBANs through /bank/card and /bank/account so unit tests cover form validation and tokenisation paths end-to-end.
Generate 10 Luhn-valid Visa card numbers via /bank/card and feed them into the checkout integration test
AI Agent Synthetic Data Pipeline
AI agents building or tearing down test environments need a deterministic data source. Through Jentic, an agent searches for Spanish synthetic data, loads the GeneradorDNI schema, and calls the relevant generator endpoint. Credentials stay in your Jentic One instance and the agent never handles the raw query-string api_key.
Search Jentic for 'generate Spanish test profile', load the /profiles/person schema, execute the call, and return 5 profiles to the calling workflow
31 endpoints — jentic publishes the only available openapi specification for generadordni api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/doi/nif
Generate a Spanish NIF identifier
/doi/nie
Generate a Spanish NIE identifier for foreign residents
/doi/cif
Generate a Spanish company CIF
/bank/account
Generate a synthetic IBAN account number
/bank/card
Generate a Luhn-valid credit card number
/profiles/person
Generate a complete synthetic person profile
/profiles/company
Generate a complete synthetic company profile
/vehicle/vin
Generate a 17-character vehicle identification number
/doi/nif
Generate a Spanish NIF identifier
/doi/nie
Generate a Spanish NIE identifier for foreign residents
/doi/cif
Generate a Spanish company CIF
/bank/account
Generate a synthetic IBAN account number
/bank/card
Generate a Luhn-valid credit card number
/profiles/person
Generate a complete synthetic person profile
/profiles/company
Generate a complete synthetic company profile
/vehicle/vin
Generate a 17-character vehicle identification number
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the GeneradorDNI API by hand means registering your api_key, appending it as a query parameter on every request, and mapping each generator path yourself. Through Jentic you install once, import GeneradorDNI from the API Directory, store the key once, and your agent calls it.
Permission scoping
GeneradorDNI's generators like /doi/nif and /profiles/person take their options in the query string rather than the URL path, so scope the agent to the operations it needs, such as generating synthetic person profiles. You choose the operations it may call, so generators like bank card or vehicle VIN data are not included unless you add them.
Credential isolation
Your GeneradorDNI api_key is stored once, encrypted, by your own Jentic One instance and attached as the api_key query parameter at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'generate a synthetic Spanish NIF' or 'create test company data', and Jentic returns the matching GeneradorDNI operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using GeneradorDNI API through Jentic.
Why is there no official OpenAPI spec for GeneradorDNI API?
GeneradorDNI does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call GeneradorDNI API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the GeneradorDNI API use?
GeneradorDNI uses an API key passed as the api_key query parameter on every request. Through Jentic the key is stored encrypted in the vault and injected at execution time, so the raw key never appears in agent context or logs.
Can I generate valid Spanish NIF and CIF identifiers with this API?
Yes. Call GET /doi/nif for personal NIFs, GET /doi/nie for foreign-resident identifiers, and GET /doi/cif for company tax IDs. All values follow the official Spanish check-digit algorithm so they pass downstream validators.
What are the rate limits for the GeneradorDNI API?
The OpenAPI spec does not declare formal rate limits. The service is intended for fixture and demo seeding rather than runtime traffic, so batch your requests and cache results in your test environment instead of calling per-test.
How do I generate a batch of test profiles with GeneradorDNI through Jentic?
Run pip install jentic, search Jentic for 'generate Spanish test profile', then call /profiles/person via the load and execute flow. The agent receives a structured profile object with name, NIF, address, and banking fields ready to insert into your sandbox database.
Is the GeneradorDNI API free?
GeneradorDNI is a free public service for synthetic data generation. There is no paid tier exposed in the spec; usage etiquette is to keep volume reasonable and not use it as a runtime dependency.
Can I limit what my agent is allowed to do with the GeneradorDNI API?
Yes. Because you run Jentic One yourself, your own rules decide which GeneradorDNI operations and credentials the agent can use, so you can allow only the generators it needs, such as GET /profiles/person or GET /doi/nif for synthetic person and NIF data. Since these generators pass their options in the query string rather than the URL path, you scope access at the operation level. Operations you do not add, like bank card generation via GET /bank/card or vehicle VIN generation via GET /vehicle/vin, stay off limits to the agent.
Know of an official OpenAPI document? Contribute it →
For Agents
Generate Spanish-format synthetic test data - NIF, NIE, CIF, IBAN, credit cards, vehicle plates, person and company profiles - for seeding QA and demo environments.
Use for: I need to generate a valid Spanish NIF for a test user, Get a synthetic IBAN that will pass bank-validation logic, Create a fake CIF and company profile for an onboarding demo, Produce a Spanish vehicle plate and VIN pair for fleet test data
Not supported: Does not handle real PII, identity verification, or KYC checks - use for synthetic Spanish-locale test data generation only.
Jentic publishes the only available OpenAPI specification for GeneradorDNI API, keeping it validated and agent-ready. GeneradorDNI is a Spanish-context fake data generator that returns synthetic NIF, NIE, CIF, IBAN, credit card, vehicle plate, VIN, person profile, company profile, passport, and social security identifiers. It is designed for QA suites, demo environments, and seeding development databases without exposing real personal data. Output is returned in JSON and is locale-correct for Spain so test fixtures pass downstream validation rules.