# 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) turns expert judgment into a score you can prove. A panel of independent, collateral-backed validators reviews each item against your rubric, consensus collapses their scores into one rating per item, and the result is sealed as a permanent onchain attestation. - [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 where input files become datapoints. When a project is defined, its data folder is read according to the spec (poq.toml), and every validator sees only what ingestion produces. This page describes the file types the ingestion process accepts and what each one turns into. ### 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? - [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/proof-report): A PoQ Report is the durable artifact a PoQ project produces once its datapoints have received all required validator inputs. It is the thing a customer, auditor, or downstream system inspects later to answer: 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. - [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. - [Stake & collateral](https://sapien-ai-docs-production.up.railway.app/validate/sapien-vault): The Sapien Vault is the onchain economic-security layer for Proof of Quality (PoQ). You can deposit SAPIEN and receive vault shares ( vSAPIEN ). Locking stake as collateral for validation work is optional and at your sole discretion if you choose to participate as a validator. When you do lock, the vault escrows that collateral and applies unlock or slash outcomes decided by the offchain PoQ engine.