Fake Data Generator
Generate up to 1,000 realistic fake records for a schema, in the right locale, such as Swedish or Japanese names.
fake-data-generate Example
{
"fields": [
{
"name": "name",
"type": "string"
},
{
"name": "email",
"type": "email"
}
],
"locale": "en-US",
"schema": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"email": {
"type": "string"
}
}
}
} {
"data": [
{
"name": "Sarah Mitchell",
"email": "sarah.mitchell@gmail.com"
},
{
"name": "James Rodriguez",
"email": "jrodriguez1987@yahoo.com"
},
{
"name": "Emily Chen",
"email": "emily.chen@outlook.com"
},
{
"name": "Michael Thompson",
"email": "mthompson@protonmail.com"
},
{
"name": "Jessica Patel",
"email": "j.patel92@gmail.com"
},
{
"name": "David Kowalski",
"email": "dkowalski@icloud.com"
},
{
"name": "Amanda Garcia",
"email": "agarcia.writer@yahoo.com"
},
{
"name": "Christopher Lee",
"email": "c.lee2024@gmail.com"
},
{
"name": "Nicole Washington",
"email": "nicole.w@outlook.com"
},
{
"name": "Brandon Murphy",
"email": "bmurphy85@protonmail.com"
}
],
"locale": "en-US",
"schema_used": "json_schema",
"record_count": 10
} Inputs
| Field | Type | Required | What it is |
|---|---|---|---|
count | integer | No | — |
fields | array | No | Array of {name, type} |
locale | string | No | — |
schema | object | No | JSON Schema |
Output fields
How reliably each field appears in a successful answer.
| Field | Type | Appears |
|---|---|---|
data | array | Always (present in every successful answer) |
locale | string | Always (present in every successful answer) |
record_count | integer | Always (present in every successful answer) |
How to call it
The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.
# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
-H "Authorization: Bearer $STRALE_API_KEY" \
-H 'Content-Type: application/json' \
-d '{
"capability_slug": "fake-data-generate",
"inputs": {
"fields": [
{
"name": "name",
"type": "string"
},
{
"name": "email",
"type": "email"
}
],
"locale": "en-US",
"schema": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"email": {
"type": "string"
}
}
}
},
"max_price_cents": 5
}' {
"tool": "strale_execute",
"arguments": {
"slug": "fake-data-generate",
"inputs": {
"fields": [
{
"name": "name",
"type": "string"
},
{
"name": "email",
"type": "email"
}
],
"locale": "en-US",
"schema": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"email": {
"type": "string"
}
}
}
},
"max_price_cents": 5
}
} import { Strale } from "straleio";
const strale = new Strale({ apiKey: process.env.STRALE_API_KEY! });
const result = await strale.do({
capability_slug: "fake-data-generate",
inputs: {
"fields": [
{
"name": "name",
"type": "string"
},
{
"name": "email",
"type": "email"
}
],
"locale": "en-US",
"schema": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"email": {
"type": "string"
}
}
}
},
max_price_cents: 5,
}); import os
from straleio import Strale, DoRequest
strale = Strale(api_key=os.environ["STRALE_API_KEY"])
result = strale.do(DoRequest(
capability_slug="fake-data-generate",
inputs={
"fields": [
{
"name": "name",
"type": "string",
},
{
"name": "email",
"type": "email",
},
],
"locale": "en-US",
"schema": {
"type": "object",
"properties": {
"name": {
"type": "string",
},
"email": {
"type": "string",
},
},
},
},
max_price_cents=5,
)) # No account. The first request answers 402 with the price in USDC;
# an x402 client pays it from your wallet and repeats the request.
curl -i -X POST https://api.strale.io/x402/v2/fake-data-generate \
-H 'Content-Type: application/json' \
-d '{
"fields": [
{
"name": "name",
"type": "string"
},
{
"name": "email",
"type": "email"
}
],
"locale": "en-US",
"schema": {
"type": "object",
"properties": {
"name": {
"type": "string"
},
"email": {
"type": "string"
}
}
}
}' Limitations
Generated values can fail strict format or checksum checks
Generated fake data follows realistic patterns but may not pass strict validation (e.g., valid-checksum IBANs, real postal codes)
What to do instead: For fields requiring valid checksums or format validation, use dedicated validators on the generated data
Output size cap per call
Structured output is limited to about 4000 output tokens per call; requests exceeding this limit are refused rather than returned truncated. Although `count` accepts up to 1000, wide records can exceed the output limit with fewer results; an identical retry does not help.
What to do instead: Request a smaller 'count' — fewer records per call
Related tools
- Agent Trace Analysis €0.20
- API Docs Generator €0.20
- API Mock Responses €0.05
- Changelog Generator €0.03
- Code Converter €0.05
- Commit Message Generator €0.05