API archive entry · source-reported
UI Names
Generate random fake names
From the publisher
README & documentation
Source previewRead the project’s overview, installation instructions and usage examples. The original README is the source of truth.
This is the repo for uinames.com. Feel free to contribute to the project by adding names. Keep in mind that more isn't better. Quality over quantity. Quality being the most common/popular names in a region. When the option to pick a region at random is selected, a region will be picked based on the amount of possible name-combinations for that region. A region with more names is more likely to be picked, and regions with less names are less likely to be picked. I propose having a maximum of 100 male names, 100 female names and 300 last names per region. That's 60.000 possible combinations per region. All responses are returned as JSON(P) over HTTP(S). There is currently no request limit. However, please keep the amount of requests to a minimum, and cache responses whenever possible. Number of names to return, between 1 and 500: https://uinames.com/api/?amount=25 Limit results to the…
Read the full README ↗ · Preview checked 2026-09-20T19:24:13.783Z
Inside the original README — Document outline
- uinames.com
- The Algorithm
- The Layout (JSON)
- The API
- Basic usage
- Optional Parameters
- Extra Data
- https://uinames.com/api/?ext
- Exception handling
- Author
- Credit
- License
Headings are captured from the source. Links open the publisher’s document, not a locally hosted copy.
Links from the README
References supplied by the publisher, not independently verified endorsements. Check the destination before downloading files or entering credentials.
Documentation belongs to its respective authors. A listing is not a grant of reuse or training rights. Confirm the document’s own terms at the source.
Where these facts came from
AltAPIs imported it from Public API Lists. The source link and dates remain visible for independent inspection.
What is reported
- Name, category, and short description
- Authentication label
- HTTPS and CORS labels
- Provider/source URL
What is not established
- Current uptime or availability
- Pricing, quotas, and rate limits
- Security, compliance, or licensing posture
- SDK quality or endpoint completeness
Record checkpoints
- First observed: Sep 20, 2026
- Last directory-field change: Sep 20, 2026
- Current source observation: Sep 20, 2026
Source reference
This page separates source-reported facts from questions that need live provider verification.