# Prooftask

> Result agreements and delivery acceptance. Agree what counts as complete, submit an exact version, and retain a verifiable delivery record.

Canonical product: https://prooftask.com/.
Agent API: https://prooftask.com/api/agents/v1
Participation assistants: https://prooftask.com/developers/participation-agents.md (item-scoped credentials, no project access).
Agent API automates the agreement workflow; API integration acceptance is a separate delivery use case described at /materials#api.
HTTP/OpenAPI integration is available. Read /api/agents/v1/capabilities first. An agent can start a connection at POST /api/agents/v1/connections; the user signs in or registers and approves its code and exact scope in Prooftask. Poll the private device code at the returned interval. The human chooses a collaboration role, tasks and exact projects/proposals, then reviews the actual permissions and expiry. Read-only access requires no task selection. Acceptance and record issuance are separate approvals, never task defaults. Never use a browser session as an agent token.

## Result specifications
- [Public discovery OpenAPI](https://prooftask.com/api/public/openapi.json): Search, pinned version reads and preparation; creates no agreement.
- [Public specifications](https://prooftask.com/specifications): Versioned editable examples with completion criteria and required evidence.
- [Specification discovery](https://prooftask.com/api/public/specifications): Read-only catalog; q and industry filters.
- [Machine discovery](https://prooftask.com/api/discover): Returns matching public specifications only.

## Public results and providers
- [Published result summaries](https://prooftask.com/showcase): Only currently available, jointly approved summaries; no private originals.
- [Provider starting guide](https://prooftask.com/for-providers): Prepare a delivery and share a specification with a customer.

## Practical delivery guides
- [Automation acceptance](https://prooftask.com/guides/automation-acceptance): Scope, test cases, evidence and a pinned specification to prepare a draft.
- [Review and reuse](https://prooftask.com/guides/delivery-review): Invitations, submitted versions, signed packages and the next project.

## Start here
- [Developer quick start](https://prooftask.com/developers): Authorization, commands and verification.
- [Complete public workflow guide](https://prooftask.com/developers/agent-workflows.md): Prepare full drafts, create buyer agreements, manage supplier proposals, submit materials and export issued records. Authorization, retries and human handoff are covered.
- [OpenAPI contract](https://prooftask.com/api/agents/v1/openapi.json): Agent operations and public creation prerequisites.
- [Example client](https://prooftask.com/developers/agent-client.mjs): Node 24+, no dependencies. Run discover "automation", then specification business-automation 2 (pinned example) without credentials. For new drafts, use the exact version and digest returned by discovery; these commands are read-only.
- [Creation input example](https://prooftask.com/developers/agent-project.json): Edit real terms, prepare locally, review, then explicitly create.
- [Manage agent access](https://prooftask.com/agents): Human sign-in is required to issue credentials.

## Delivery services and prices
Record Delivery retains the exact agreement, delivered version, materials and buyer decision. A Result Credit is consumed only on successful Result issuance after explicit acceptance. The published record-credit catalog and organization lifetime allowance remain separate from signing services.
Signed Delivery is a visible service with ordinary agreement signatures, a final buyer decision signature, required verification within the quoted scope and original/process evidence. US$29 is a reference pending commercial review, not an automatically purchasable offer. Read /api/delivery-services/support and /pricing for current availability. A human reviews a fixed service quote and pays before sending. Agents cannot purchase or sign.
The current final-only signing policy is explicitly versioned; older all-review signing obligations keep their semantics. Routine corrections are native project events under the new policy. Supplementary signing of an issued Result does not retrospectively sign a pre-work agreement. Extra proof is quoted only beyond the package scope.

## Creation and recovery
To prepare without committing, POST /api/agents/v1/drafts with CREATE_DRAFT and a stable requestId. It accepts complete BUYER or SUPPLIER draft fields and returns a private link to the shared human editor. Nothing is sent or agreed; the human reviews, edits and explicitly confirms using separate agreement authority. Draft preparation never grants access to the eventual project. Read /developers/agent-workflows.md for the input contract.

Supplier proposals use /api/agents/v1/proposals with separate CREATE_PROPOSAL, UPDATE_PROPOSAL, PUBLISH_PROPOSAL, RESPOND_PROPOSAL and WITHDRAW_PROPOSAL grants. Read the exact proposal head and automation revision before writing. Publication is not buyer acceptance. Buyer acceptance creates the final agreement, which the supplier must separately confirm. Only explicitly scoped proposals and their resulting project are included. Fixed signing, human-required decisions and financial authority remain separate.
Read /api/acceptance/legal-config for current documents. Supply an explicitly chosen purpose, contract basis and sharing policy. POST /api/acceptance/confirmation-preview with legalContext and operation AGREEMENT to read the exact confirmation. A preview does not establish consent or create an agreement. POST /api/agents/v1/projects only after reviewing the terms and confirmation.
Inspect availableActions and blockedActions. WAIT_FOR_HUMAN includes requiredHumanAction and a humanUrl. Open required signing in the human workspace; agents cannot sign or resume themselves. Reread after human action. Retry uncertain writes with the exact saved request and requestId.

## Verification and limits
- [Trust center](https://prooftask.com/trust): Trust boundaries and independently verifiable exports.
- [Public issuer key bundle](https://prooftask.com/.well-known/prooftask-trust-bundle.json): Confirm keys independently before reliance.
Use ISSUE_RESULT_RECORD with POST /projects/{id}/issue-record to request issuance of the exact accepted version using at most one authorized result credit. Missing coverage returns a payer handoff and a durable continuation; changed state, pause or revoked authority stops it. No automatic purchase is authorized. Renewing the same grant keeps its saved jobs. Node and Python examples are available.

Export /projects/{id}/exports/result-package for portable verification. Cryptographic integrity is not work-quality verification, organization authority or payment. Original materials remain in agreed storage. The API supports project polling and authorized event webhooks; see /developers/project-events.md. It does not provide an MCP endpoint or a workflow scheduler. Use /me to confirm tenantId and organizationId. After credential replacement, reconcile the original project/request before creating another submission.