Agify.io logo

Agify.io

Agify.io

Estimates the age from a first name.

Visit site ↗Health checked 1d ago
Use it when

No authentication required

Watch for

Only estimates age from first names

First check

Start by making REST API calls without authentication. Use the provided website for documentation and testing.

Auth
none
CORS
Yes
HTTPS
Yes
Signup
None
Latency
700 ms
Protocol
REST
Pricing
free

Uptime · 30-day window

Probes: 30Uptime: 100%Avg latency: 639ms
01

About this API

Agify.io is a simple API that estimates a person's age based solely on their first name. It is useful for developers who want to infer demographic information without requiring explicit age input from users.

This API is relevant for applications that need quick age approximations for personalization, analytics, or validation purposes. Since it does not require authentication, it is easy to integrate and test.

While it provides a straightforward service, the accuracy depends on the underlying data and may vary based on name popularity and regional differences. It is best used as a supplementary tool rather than a definitive source of age data.

02

What you can build

  • 1Display estimated age from user first name
  • 2Generate demographic insights based on names
  • 3Validate age assumptions in user profiles
03

Strengths & limitations

Strengths

  • No authentication required
  • Simple and focused functionality
  • Quick age estimation from names

Limitations

  • Only estimates age from first names
  • Accuracy depends on name data coverage
04

Getting started

Start by making REST API calls without authentication. Use the provided website for documentation and testing.

05

FAQ

Do I need an API key to use Agify.io?+

No, Agify.io does not require any authentication or API key.

What kind of data does Agify.io return?+

It returns an estimated age based on the provided first name.

Can I use Agify.io from a browser?+

Yes, since it uses REST and requires no authentication, it can be called from browsers.

Is HTTPS required to use the API?+

While not explicitly stated, using HTTPS is recommended for security.

06

Technical details

CORS: YesHTTPS: YesSignup: NoOpen source: No
Auth type
none
Pricing
free
Protocols
REST
Response time
700 ms
Last health check
8/13/2026, 5:30:27 AM
07

Tags