Agify API

Name: Agify API
Brand: Agify API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentContact EnrichmentapiKey1 EndpointsREST

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.

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.

Step 1: 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

Step 2: 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 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)

GET STARTED

Start building with Agify API

Explore with Jentic

View OpenAPI Document

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

Why Jentic?

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

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.

Time to first call

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.