Video / Evidence / PactVerity technical series

PactVerity Receipt API Beta: Developer Walkthrough

A developer-oriented tour of the public API, receipt creation, verification and known-answer health testing.

Project statusLive public MVPPVTY tokenLive on Solana
Recorded 16 August 2026:This is a historical educational recording, not a live status report. Use the current evidence links below for product, supply and market status. Future utility described in the recording is not a deployed benefit.

Five-minute narrated explainer · original publication: 16 August 2026. Page and evidence links reviewed 27 September 2026.

Watch on the official YouTube channel ↗

Recheck the current evidence

Original narration transcript

The transcript preserves the historical recording. It is not rewritten to imply that later developments were already live when the video was recorded.

PactVerity exposes a Receipt API beta, verification endpoint, public receipt activity surface, OpenAPI document and known-answer health check. The goal is to let developers inspect the current deployment directly. This walkthrough stays conceptual so it remains useful as the beta evolves. Always review the live specification at pactverity dot com before integrating.

The API index identifies the service and links the public endpoints. A developer should confirm the schema version, engine version and current deployment notes before sending production-like data. Because the service is a beta, compatibility and availability may change. Use synthetic or non-sensitive test inputs first, and never submit credentials, private keys or confidential customer information.

A receipt request describes the service terms, provider reference, supplied evidence and checks to run. The exact schema is defined in the OpenAPI document. The response records the evaluation outcome, individual check results, timing, engine information and a digest. A successful response means the beta processed that request; it is not a guarantee that the external evidence source was truthful.

The verification endpoint accepts a compatible receipt and evaluates whether its structure and digest are internally consistent. This supports portability: a stored receipt can be checked later without depending on the page where it was first created. Integrators should preserve the complete artifact and avoid transforming fields in ways that break canonicalisation or digest verification.

The public health endpoint runs a known-answer execution and reports service versions, receipt verification and simulation reproducibility. It also states important boundaries, including whether the deployment moves funds or performs on-chain settlement. A passing health check is useful operational evidence, but it is not an independent audit, uptime guarantee, load test or customer adoption metric.

Integrations should distinguish transport errors, schema errors, failed service conditions and failed receipt verification. Do not collapse every outcome into a green or red badge. Store the error context needed for review while minimising sensitive information. Timeouts and retries should also be bounded so an agent cannot create ambiguous duplicate actions or hide an earlier failure.

Use explicit schema versions, test fixtures and a controlled adapter around the API. Monitor changes in the public specification and keep your own copy of test receipts. Avoid connecting a beta verification result directly to irreversible financial action. Any future settlement use should wait for appropriate security review, legal design, testing and independent validation.

The best pilot begins with one API or agent service and one precise condition. Review the OpenAPI specification, run the known-answer health check and create a synthetic receipt. Then document the evidence source and threat model. PactVerity invites developers and security reviewers to share reproducible feedback through the public project contact.

Continue the series