# Pressfox > Pressfox turns JSON into branded reports. A team designs a report template in the browser and publishes it; their system (or an AI agent) sends data to one REST endpoint, `POST https://api.pressfox.io/api/v1/reports`, with a template key and a payload; Pressfox checks the payload against the template's contract (refusing with a 422 that names the field), renders it, and returns a hosted link and a PDF. Images travel as https URLs inside the payload. Authentication is a workspace API key (`pf_test_…` for watermarked, unmetered tests; `pf_live_…` for real documents). Rendering and hosting run in the EU. Templates are made in the dashboard: from a pack, a blank page, or a PDF of a report the team already produces ("Start from your report"; a dashboard feature, there is no API for it). Integrate in three calls: `GET /api/v1/templates` to find the template key, `GET /api/v1/templates/{key}/contract` for the JSON Schema of its payload, `POST /api/v1/reports` to create the report. Templates are versioned: send `"template": "key@N"` to pin version N (recommended in production; without it the current version is used), and read that version's contract at `GET /api/v1/templates/key@N/contract`. A retired version answers `410 version_retired`. AI assistants can do the same through the Pressfox MCP server: by URL (`https://mcp.pressfox.io/mcp`, the user signs in with OAuth and approves the app; preview) or locally over stdio with an API key. ## Docs - [API reference (Markdown)](https://pressfox.io/docs/api.md): reports, templates and contracts, versions and pinning, images by URL, assets, access policies, shares, Markdown output, webhooks, errors, test and live mode, MCP - [API guide (HTML, canonical)](https://pressfox.io/docs): the same content, written by hand and kept in step with the server - [Every route and schema](https://pressfox.io/docs/api): generated from the server's OpenAPI document - [Markdown output](https://pressfox.io/docs#markdown): every report can also be read as Markdown (`"formats": ["markdown"]`, then `markdown_url` or `GET /api/v1/reports/{id}/markdown`), built by code with tables and labels intact - [Verify a document](https://pressfox.io/docs#verification): anyone checks a PDF at `/verify` (Standard and above); the public `GET /api/verification/check/{sha256}` answers genuine, replaced, revoked or not found - [A password on the PDF itself](https://pressfox.io/docs#pdf-password): `pdf_password` per report, or a field of the data named in the template; the file opens only with it (Standard and above) - [Labels and corrections](https://pressfox.io/docs#labels): find reports by `label.=`, replace an issued report with `corrects` - [Sign a document in your provider](https://pressfox.io/docs/signing): Pressfox collects no signatures; send the PDF with DocuSign, Yousign or any provider - [Error catalogue](https://pressfox.io/docs/errors): every error `code`, what it means and the fix, and why an accepted report failed - [Use Pressfox from AI agents (MCP)](https://pressfox.io/docs#mcp): connect by URL with OAuth (Claude custom connector) or locally with a key; the tools ## Optional - [Everything in one file](https://pressfox.io/llms-full.txt): the Markdown API reference and the MCP setup, for loading into a context window - [Security](https://pressfox.io/security): hosting, encryption, access policies, retention - [Pricing](https://pressfox.io/pricing): plans and limits - [Product tour](https://pressfox.io/product): designer, Playground, the request and its answers, sharing, brands, versions, quality guarantees, limits - [Use cases](https://pressfox.io/use-cases): inspections, invoices and statements, visit summaries, field reports, client reports, agreements; what each template holds, what it costs, what it does not do - [Integrations](https://pressfox.io/integrations): recipes by system, webhooks, email shares, custom domains, AI agents, rate limits, what is available and what is coming - [Languages and AI](https://pressfox.io/ai): five report languages, reviewed translations, what each AI feature sends and to whom - [Questions](https://pressfox.io/faq): answers for every team - [Contact](https://pressfox.io/contact): one address, a subject line per purpose