01
Working product
Proof Engine v1 creates deterministic assurance receipts from supplied API and AI-service evidence, then independently rechecks their structure and digest.
14 / Project brief
Evaluate the working evidence—not a promise.
PactVerity is building verification infrastructure for APIs, AI agents and measurable digital services. This brief separates the operational product, independently checkable token facts and future protocol work so technical evaluators can examine the project without promotional ambiguity.
Proof EngineOperationalReceipt APIPublic betaIndependent auditPending
01 / Thesis
Autonomous services need portable evidence.
An agent can call an API, buy data or complete a digital workflow without a person inspecting every step. The missing layer is a compact record of what was promised, which evidence was supplied, which checks ran and whether another system can reproduce the result.
02
Developer surface
The public Receipt API beta, health endpoint, OpenAPI specification and GitHub resources provide a reproducible technical evaluation path.
03
Finalized token
Exactly 50,000,000 PVTY exist on Solana. The canonical mint is published and its mint and freeze authorities are removed.
02 / Verify
Follow the public evidence trail.
Each link below leads to a working product surface, source record or explicit risk boundary.
ProductLive
Create a receipt
Run explicit latency, uptime, freshness and output-commitment checks in the public browser engine.
APIBeta
Inspect the interface
Review the health response, OpenAPI document, receipt schema and developer examples.
PVTYSolana
Verify token facts
Check the complete canonical mint, fixed supply, treasury account and removed authorities.
Source
Review the repository
Inspect the official public code, specifications and quick-start material.
Design
Read the protocol model
Separate the operational evidence layer from proposed custody, settlement and challenge components.
Risk
Review the limitations
Understand evidence quality, software, token, liquidity, regulatory and delivery risks.
03 / Open gates
What is not yet complete.
Credible evaluation includes unresolved work. These items are not described as delivered, adopted or independently assured.
- Independent security assurance is pending; published internal testing is not an external audit.
- Automated service custody and settlement are not deployed to Solana devnet or mainnet.
- No customer, revenue, adoption or transaction-volume claim is made from the deterministic simulator.
- An executable public DEX route must be verified live; liquidity, price, resale access and future value are never guaranteed.
- A formal protocol-operating entity and complete allocation and vesting implementation remain to be published.
04 / Engage
Evaluate, integrate or challenge the model.
Technical reviewers, potential integration partners, researchers and responsible security specialists can request a focused discussion using the public project contact.
Start with a specific diligence question.
Describe the API, AI-agent workflow or project claim you want to evaluate and link to any public technical context. Do not send confidential customer data, credentials, private keys or wallet recovery phrases.
Working product