# Sapien Proof of Quality Docs Sapien Proof of Quality (PoQ) is a consensus and attestation system for subjective expert outputs. These docs explain how to define PoQ projects, validate outputs, interpret reports, and integrate with the API. ## Primary Entry Points - [Docs Home](https://sapien-ai-docs-production.up.railway.app/) - [Full Agent Context](https://sapien-ai-docs-production.up.railway.app/llms-full.txt) ## Docs ### Get started - [What is PoQ](https://sapien-ai-docs-production.up.railway.app/start/introduction): Proof of Quality (PoQ) is a verification layer for AI work. You define quality as a rubric, a panel of independent validators scores each item against it, consensus resolves one verdict per item, and PoQ seals the rubric, outcome, and level of agreement as a permanent onchain attestation. Instead of asking anyone to trust an internal review process, PoQ records how the decision was reached — and anyone can verify that record. - [Quickstart](https://sapien-ai-docs-production.up.railway.app/start/quickstart): Create your first PoQ project: bring your data, describe the validations you want, and get your datapoints ready for review. Two paths get you there: ### Build your project - [The PoQ workflow](https://sapien-ai-docs-production.up.railway.app/build/poq-workflow): Every PoQ project moves through the same three phases: you Define the work, validators Validate it, and the engine Attests to the outcome in a durable report that can be verified. - [Define your spec](https://sapien-ai-docs-production.up.railway.app/build/defining-your-spec): PoQ projects start as intent and become configuration. Every project runs on one artifact: poq.toml, the executable, deterministic spec the engine reads. Everything else on this page is a way of arriving at it. - [Supported data types](https://sapien-ai-docs-production.up.railway.app/build/supported-data-types): Ingestion is the single pipeline that turns your uploaded files into datapoints. Whatever you bring (a CSV of labels, a folder of JSON, a bundle of PDFs, or a long Markdown report), ingestion reads it, normalizes it into one canonical format , and produces datapoints from that canonical form. Every supported file type is just a different on-ramp to the same pipeline, not a separate, one-off behavior. ### Get it validated - [How consensus works](https://sapien-ai-docs-production.up.railway.app/validate/consensus-explained): Imagine a cooking contest. One dish comes out of the kitchen, and a panel of judges tastes it. Each judge fills out the same scorecard, and somehow all those opinions have to become one verdict : does this dish move on, or not? - [How quality is measured](https://sapien-ai-docs-production.up.railway.app/validate/quality-rating): Validation returns two independent numbers for every datapoint, both 0-100: - [Validation interface](https://sapien-ai-docs-production.up.railway.app/validate/validation-ui): The interface shown to a validator renders data from the ingestion phase according to transformations in the project's specification (poq.toml). This page describes the evidence and evaluation elements that can be defined via the project's specification. - [PoQ Report](https://sapien-ai-docs-production.up.railway.app/validate/poq-report): A PoQ Report is the durable artifact a PoQ project produces once all required validator inputs are in. It answers: what was reviewed, by whom, against what criteria, and with what level of agreement. ### Integrate with your pipeline - [API keys](https://sapien-ai-docs-production.up.railway.app/integrate/api-keys): Developer API keys enable programmatic access to PoQ by both developers and agents. Use them to access the PoQ Developer API (/developer/v1) and the PoQ MCP server (/mcp). - [Developer API](https://sapien-ai-docs-production.up.railway.app/integrate/developer-api): The Developer API is the HTTP integration surface for managing PoQ projects and data. - [MCP server](https://sapien-ai-docs-production.up.railway.app/integrate/mcp): The MCP server exposes the Developer API as Model Context Protocol tools over streamable HTTP. Use the same API keys as the REST surface. ### Examples - [poq.md examples](https://sapien-ai-docs-production.up.railway.app/examples/poq-md): Plain-language prompts in poq.md draft into poq.toml. Examples use a Beatles catalog review theme. - [poq.toml examples](https://sapien-ai-docs-production.up.railway.app/examples/poq-toml): A poq.toml file turns uploaded data into review items: what to ingest, what evidence validators see, what questions they answer, and how review slots are assigned. These examples use the current namespaced layout from the poq.toml reference. ### Reference - [poq.toml spec](https://sapien-ai-docs-production.up.railway.app/reference/poq-toml): The poq.toml file for each Sapien project is its system spec . It turns the data you upload into a working project: the fields on each review item, what validators see, the questions they answer, and how they are scored. - [poq.toml — project](https://sapien-ai-docs-production.up.railway.app/reference/poq-toml/project): The [project] section of the poq.toml spec — declares the spec format version (spec_version) and an optional tag. - [poq.toml — ingestion](https://sapien-ai-docs-production.up.railway.app/reference/poq-toml/ingestion): The ingestion.* sections of the poq.toml spec — declare sources, optional joins, and the field projection that becomes each datapoint row. - [poq.toml — validation](https://sapien-ai-docs-production.up.railway.app/reference/poq-toml/validation): The validation.* sections of the poq.toml spec — task UI, evidence, rubric, dimension-level consensus outcomes, ground truth, and onboarding. - [poq.toml — validators](https://sapien-ai-docs-production.up.railway.app/reference/poq-toml/validators): The validators.* sections of the poq.toml spec — who reviews each item, how many, pay, routing by field values, and gates before claim. - [poq.toml — attestation](https://sapien-ai-docs-production.up.railway.app/reference/poq-toml/attestation): The attestation.* section of the poq.toml spec — signed PoQ Report export: schema, signing key, payload fields, and output format. - [PoQ Report spec](https://sapien-ai-docs-production.up.railway.app/reference/poq-report): This is the field-by-field reference for the PoQ Report payload — the canonical JSON that every PoQ Report is a render of. For the conceptual overview (what a report is, how to read it, and how to verify one), see the PoQ Report guide. - [Sapien Tokenomics](https://sapien-ai-docs-production.up.railway.app/reference/tokenomics): How the $SAPIEN token enforces data quality through staking, peer validation, reputation, and slashing — plus token distribution, emissions, and governance.