Random User Generator
Free random user data API for generating realistic fake user profiles with names, addresses, photos, and contact data for UI mockups and testing. Open-source REST API with no authentication required, seedable for reproducibility, and multi-format output (JSON, CSV, YAML, XML).
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Random User Generator the way a machine reads it — 38 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Random User Generator scores 48.4/100 (developing), with a separate agent-readiness read of 39/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Random User Generator
Each block below is one kind of artifact we hold for Random User Generator. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Random User Generator Users API
Generate one or more synthetic user records.
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Random User Generator API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Randomuser Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Randomuser Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Free and unauthenticated
No API key, no signup, no per-key quotas; just hit the endpoint.
Seedable reproducibility
The same (seed, page, results, version) tuple always returns the same users.
Multi-nationality cohort
Mix 21 nationalities (v1.4) so addresses, IDs, and phone formats stay locale-appropriate.
Field projection
Use `inc` / `exc` to keep payloads small and skip CPU-heavy fields like `login`.
Multi-format output
JSON, PrettyJSON, CSV, YAML, XML; plus JSONP via `callback`.
Path-pinned versioning
Lock requests to /1.0/ through /1.4/ so upstream releases never break your fixtures.
Pre-generated portrait images
Three resolutions (large, medium, thumbnail) hosted on randomuser.me.
Open source
MIT-licensed Node.js codebase; self-hostable if you need air-gapped operation.
Scroll within the panel for all 8 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Randomuser Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Random User Generator API Rules
SPECTRALRandom User Generator API Rules
SPECTRALJSON Schema 2
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
UserResponse
JSON SCHEMAUser
JSON SCHEMAJSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Randomuser User Structure
JSON STRUCTUREExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Frontend prototyping
Populate UI mockups, design comps, and Storybook fixtures with realistic users.
Test data for QA / CI
Generate seeded fixtures for unit, integration, and snapshot tests.
Load testing
Bulk-generate up to 5000 users per request to seed performance test runs.
i18n / localization
Request specific nationalities to validate address parsing, phone formats, and Unicode rendering.
Demo content
Populate sales demos, sandbox environments, and tutorials with realistic-looking accounts.
Avatar placeholders
Use the picture URLs as throwaway avatars for prototyping.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
jQuery / AJAX
Documented usage with $.ajax for browser-side fetches.
Node.js
Use directly from server-side JavaScript; offline module available.
Photoshop Extension
Pull synthetic users straight into design comps (legacy extension).
Sketch Extension
Sketch plugin for filling layers with random users (legacy).
Model Context Protocol
Multiple community MCP servers expose the API to LLM agents (pipeworx-io, hugo-85, rycid).
Solutions 3
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Hosted API
Free, public, donation-funded endpoint at randomuser.me/api.
Offline npm module
Generate the same shape of users without network calls using the offline RandomAPI module.
Self-hosted
Clone Randomuser.me-Node and run the generator inside your own infrastructure.
Resources
Every other property we hold for Random User Generator — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/randomuser · machine-readable index on apis.io