Prototypes and mockups

A user list with real names, real titles and real faces reads completely differently from six rows of John Doe. Point your prototype at /api/people and the screen looks finished before the backend exists.

Seed data for development databases

Pull the roster once, map it onto your users table, and every developer on the team gets the same believable data set. Ids and slugs are stable, so fixtures written today still work next year.

Design systems and component libraries

Avatar groups, people pickers, org charts, comment threads: every component that needs a person now has a consistent set of them. Headshots are square and uniform, and the placeholder fallback keeps the same dimensions, so nothing jumps.

Demos and screenshots

Marketing screenshots and conference demos need a team that looks like a team. Use /api/departments/sales and everyone in the frame belongs there.

Teaching and student projects

A first fetch() is more fun when the response has personality. No API key means no sign-up flow standing between a student and their first working request, and open CORS means it works from a plain HTML file.

Internal tools

Building a directory, an on-call rotation or an approvals screen? Develop against a fake company with departments, branches and managers already in place, then swap the base URL for the real one.

Ready when you are: get started or copy an example.