MochaviPayloads View on GitHub

Any payload. One dependable URL.

Fixture data without the fixture server.

Small sample files with fictional users, projects and tasks in JSON, XML, CSV, YAML, NDJSON, plain text, HTML, MessagePack, CBOR and PDF. Fetch them from tests, demos and prototypes or download them. There is no account or API key, a published v1 URL always returns the same bytes, and the data is CC0.

Open JSONOpen XMLOpen CSVBrowse every payload
Formats
11
Payload assets
101
Runtime backend
None

Formats

Pick the bytes you need

Read the full manifest
11 files

JSON

application/json; charset=utf-8View endpoints 11 files

XML

application/xml; charset=utf-8View endpoints 11 files

CSV

text/csv; charset=utf-8View endpoints 11 files

YAML

application/yaml; charset=utf-8View endpoints 11 files

NDJSON

application/x-ndjson; charset=utf-8View endpoints 11 files

Plain text

text/plain; charset=utf-8View endpoints 11 files

HTML

text/html; charset=utf-8View endpoints 11 files

MessagePack

application/msgpackView endpoints 11 files

CBOR

application/cborView endpoints 1 file

PDF

application/pdfView endpoints 1 file

JSON Schema

application/schema+json; charset=utf-8View endpoints

Quick start

Use one stable URL

curl

curl -fsS https://payloads.mochavi.com/v1/users.json
Browser example
const response = await fetch("/v1/users.json");
const payload = await response.json();
Python example
from urllib.request import urlopen

with urlopen("https://payloads.mochavi.com/v1/users.json") as response:
    payload = response.read()

Collections and files

Common endpoints

View every endpoint
PathMedia typeSize
/v1/users.jsonapplication/json; charset=utf-81.6 KB
/v1/users.xmlapplication/xml; charset=utf-82.9 KB
/v1/users.csvtext/csv; charset=utf-8741 B
/v1/projects.yamlapplication/yaml; charset=utf-8529 B
/v1/tasks.ndjsonapplication/x-ndjson; charset=utf-8485 B
/v1/files/pdf/dataset-summary.pdfapplication/pdf680 B
/v1/schemas/dataset.schema.jsonapplication/schema+json; charset=utf-86.0 KB

Practical guides

Use fixtures with intent

View all guides
Guide

For coding agents

Give your coding agent fixed sample data URLs instead of letting it write fixtures from memory. A v1 Payloads file never changes and has a published SHA-256, so the tests it writes stay reproducible.

Read guide Guide

Deterministic API fixtures

A practical pattern for using stable public fixture URLs in repeatable client and parser tests.

Read guide Guide

Cross-format test data

Use one canonical users, projects and tasks dataset across formats to test conversions and parser consistency.

Read guide

Common questions

What Payloads is and is not

Is Payloads a fake REST API?

No. It serves versioned static files over GET. There are no simulated writes, authentication flows or request-dependent responses.

Can I use the endpoints from a browser?

Yes. Published v1 assets allow cross-origin requests and require no account or API key.

Will a v1 payload change?

No published v1 asset is changed in place. A future incompatible dataset belongs under a new version.

Can I verify the exact bytes?

Yes. The public manifest records the media type, byte size and SHA-256 checksum of every asset.

Can a coding agent use Payloads for test fixtures?

Yes. The guide for coding agents has curl, fetch, pytest and Vitest snippets and a short block to paste into AGENTS.md or CLAUDE.md.

License

Use it freely

Project-owned fixture data and generated payloads are available under CC0 1.0 Universal. Source code and documentation use the MIT License. Mochavi names and logos are not included in either grant.

Read the licensing boundaries