For teams
One account for the whole team
Invite your colleagues, give each the role they need, run the team on its own budget of tokens, and keep the lists your test data is drawn from in one shared place.
Private or Team
Every account starts with a private organization. Add a team organization next to it whenever people join — you switch between them in the dashboard header.
Private
- Only you
- Uses your tokens, including the free 2,000 a month
- Great for personal projects
Team
- Invite your team
- Has its own budget of tokens — no personal free tier
- Shared dictionaries for everyone in it
Owner, admin, member
Three roles, so the people who run the integration and the people who use it each get exactly what they need.
| Role | Can |
|---|---|
| Owner | Everything an admin can, and manage admins too — promote, demote, suspend or remove them. |
| Admin | Invite people, create and revoke the team’s API keys, and promote, suspend or remove members. |
| Member | Use the team’s API keys an admin hands them, see the team’s usage, and edit its dictionaries. |
Invite, suspend, remove
Invite people by email: they get a single-use link, valid for seven days, which you can cancel until it is used. Someone stepping away for a while can be suspended — they keep their seat but lose all access until you reactivate them. Removing someone takes them out of the team for good. API keys belong to the team, not to the person who created them, so none of this breaks an integration; each key still shows who created it and how many tokens it has spent.
Its own budget
A team spends from its own wallet: the tokens bought for it, billed separately from anyone’s personal account. Every API key of the team draws on that one balance, and the API keys page shows how many tokens each key has spent. The personal free tier stays personal — a team has none, so inviting people never multiplies free tokens. Calls cost exactly what they cost anywhere else: one token plus a tenth per record.
Shared dictionaries
Keep the team’s own lists — product tiers, client segments, plan names — in the dashboard, one entry per row, weights optional. Every member can edit them, and the enum generator draws from one by name: no JSON to build into the URL, and one place to change it for everyone. A saved change is live on the next call.
# The list "client-products", saved in the dashboard:
# basic weight 1
# premium weight 3
curl -H "Authorization: Bearer $TEAM_API_KEY" \
"https://api.real-fake-data.com/v1/enum?dictionary=client-products&count=3"
{
"data": [
{ "value": "premium", "probability": 0.75 },
{ "value": "basic", "probability": 0.25 },
{ "value": "premium", "probability": 0.75 }
]
}Getting started
- Sign in to the dashboard and open the organization menu in the header.
- Choose “Add new organization” and pick Team — or turn a private organization into a team under Settings.
- Buy tokens for the team, then invite people from the Members tab.
- Create the team’s API keys and hand them to whoever runs the integration.
Bring your team in
Creating a team costs nothing. It runs on the tokens you buy for it — the same prepaid credits, with no subscription and no expiry.