Agent-ready OpenAPI document · curated by JenticData EnrichmentContact EnrichmentapiKey1 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Predict the likely age associated with a first name in a given country to enrich CRM, marketing, or analytics records that lack age data.
Use for: Predict the likely age for the name 'Jane', Get age predictions for a batch of 10 first names in one call, Find the age distribution for a name biased toward Brazil, Check whether the name 'Aoife' has a prediction with a high sample count
Not supported: Does not validate identity, perform KYC, infer gender, or look up exact birth dates - use for statistical age estimation from first names only.
Jentic publishes the only available OpenAPI specification for Agify API, keeping it validated and agent-ready. Agify predicts the most likely age of a person based on their first name, optionally biased by a country code for localised distributions. The API exposes a single GET endpoint that accepts one or more name parameters and returns the predicted age along with the sample count behind the prediction. Free tier requests are unauthenticated; higher tiers attach an apikey query parameter.
Install Jentic One Beta
Connect the Agify API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Agify 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.
1
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%2Fagify.io%2Fagify" | sh2
Step 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%2Fagify.io%2Fagify" | 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.
Capabilities
What an agent can do with Agify API.
Predict the most likely age for a single first name via GET /?name=jane
Batch up to 10 names per request by repeating the name query parameter
Bias predictions by country with the country_id parameter (ISO-3166 alpha-2)
Inspect the sample count behind each prediction to gauge confidence
Use Cases
Patterns agents use Agify API for, with concrete tasks.
★ CRM Age Enrichment
Add a likely-age field to contact records that only contain a first name and country, so segmentation and personalisation can proceed without explicit age input. The agent batches first names against GET / with the country_id parameter and writes the predicted age back to the CRM. Suitable for marketing teams running broad demographic segmentation.
GET /?name=Maria&name=Joao&country_id=BR and write the predicted age for each contact back to the CRM record
Survey and Analytics Demographics
Fill in approximate age groups for survey responses or product analytics events when only the respondent's first name is captured. Combine Agify with Genderize and Nationalize to triangulate a demographic profile without asking direct PII questions. Suited for early-stage research where directly asking for age would reduce response rate.
For each survey respondent, GET /?name={first_name} and bucket the predicted age into 18-24, 25-34, 35-44, 45+
Localised Personalisation
Bias the age prediction by country code so that the same first name ('Olga' in Russia vs Spain) returns the correct local distribution. The agent passes country_id alongside name to GET /. Useful for international email campaigns where age skews vary by market.
For each contact in DE, FR, and IT segments, GET / with the local country_id and choose the email variant matched to the predicted age band
Agent-Driven Identity Triangulation
Let a Jentic-connected agent pair Agify with Genderize and Nationalize calls to enrich a sparse identity record from a first name alone. The agent searches Jentic for each prediction operation, loads schemas, and combines results into a single enriched profile. This is the standard demographic triangulation pattern packaged as an agent recipe.
Given the name 'Camille', call Agify, Genderize, and Nationalize and return a combined profile with age, gender, and probable country
Key Endpoints
1 endpoints — jentic publishes the only available openapi specification for agify api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/
Predict the age for one or more first names, optionally biased by country
GET
/
Predict the age for one or more first names, optionally biased by country
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
Agify API
- Foundational (D+)49/100
94
Foundational Compliance63
Developer Experience & Jentic Compatibility52
AI-Readiness & Agent Experience94
Agent Usability15
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
94
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
52
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
59%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
15
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
15%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Agify API by hand means appending its apikey as a query parameter for paid tiers and coding a call against its single estimation endpoint. Through Jentic you install once, import the Agify API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Agify exposes one read operation that takes the name and country as query parameters, so the agent is limited to that single age-estimation lookup. You choose whether that operation is in the allowed set, so nothing else is reachable.
Credential isolation
Your Agify apikey is stored once, encrypted, by your own Jentic One instance and appended as a 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 'predict age from a first name', and Jentic returns the estimation operation with its query parameter schema for name and country_id so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Agify API through Jentic.
Why is there no official OpenAPI spec for Agify API?
Agify does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Agify 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 Agify API use?
Free tier requests are unauthenticated. Paid tiers add an apikey query parameter (name 'apikey') to lift daily limits. Through Jentic the apikey is stored in the credential vault and appended at call time.
Can I batch multiple names in one Agify request?
Yes. Repeat the name query parameter up to ten times in a single GET / call (for example /?name=Alice&name=Bob). The response is an array of objects, one per name, with the predicted age and sample count.
What are the rate limits for the Agify API?
The free tier allows 100 requests per day per IP. Paid tiers raise this and are gated by apikey. The API returns 429 with X-Rate-Limit headers when the daily quota is exhausted; agents should retry on the next day or upgrade the key.
How do I predict ages for a list of contacts through Jentic?
Use the Jentic search 'predict age from a name'. Jentic returns the GET / operation; load its schema, supply the name parameters (and optional country_id), and execute. The response gives age and count for each name in the same order.
Can Agify return predictions biased by country?
Yes. Pass country_id as an ISO-3166 alpha-2 code (e.g. BR, DE, JP) alongside name. The prediction uses that country's name-age distribution rather than the global average, which materially changes results for names that skew older or younger by country.
Can I limit what my agent is allowed to do with the Agify API?
Yes. Agify exposes a single read operation that predicts a likely age from a first name, taking the name and an optional country code as query parameters, so the agent is confined to that one age-estimation lookup and nothing else. Because Jentic One runs self-hosted on your own infrastructure, you decide whether that operation is in the allowed set for a given agent, and your own rules govern which operations and credentials it may use. If you leave it out, the agent cannot reach Agify at all, and the stored apikey is appended at call time rather than handed to the agent.
GET STARTED