/docs/getting-started
Getting started
forecraft is a form platform whose first user is an agent. An agent creates a form, previews it, publishes it and reads the answers through a REST API or an MCP server; a…
Read once, build forever.
How forecraft works, written short enough for a context window. Start with getting started; agents can skip to the curl sequence.
Every page
/docs/for-agents
The curl sequence
Everything an agent with only an API key needs, in order: create a form, preview it, publish it, open it, submit to it as a person would, then list and export the answers. Each…
/docs/definitions
Form definitions
A form is one JSON document with four keys. The API accepts and returns it, the designer edits it, and the public page renders it. There is no second representation.
/docs/rules
Rules
Rules say what a schema cannot: which fields are on screen, which are required today, what must agree with what, which values are derived, and which wizard step comes next.…
/docs/api
API reference
The REST API is the product: the dashboard, the designer and the MCP server are clients of these same routes. Everything is JSON under /api/v1. The machine-readable version is…
/docs/mcp
forecraft MCP server
packages/mcp/index.mjs is a Model Context Protocol server that lets an agent build and run forms, and design and issue PDF reports and documents (invoices, letters,…
/docs/reports
Reports and documents
A report is one JSON definition — the data's schema, a sample, a layout of blocks and a few curated appearance choices — that prints as an A4 or US Letter PDF. A document is…
/docs/report-style
Report house style
forecraft's documents should read like paper from a good law firm or accountant: calm, exact, legible and expensive-looking. The renderer already does most of this for you —…
Reading for a machine?
The same contract, in the formats agents parse best.