ProductLive
Proof Engine v1
Public browser verification, receipt export and deterministic rechecking are operational.
12 / Media kit
Official assets and evidence-bounded facts.
Use these materials when covering PactVerity. Product, token, market and adoption claims should remain separate so readers can distinguish working software from future plans.
Project statusLive public MVPPVTY tokenLive on Solana
01 / Boilerplate
Approved project description.
This paragraph may be reused in articles, directories and partner materials.
About PactVerity
PactVerity is a public AI-service evidence-verification project for APIs, software agents and measurable digital services. Its operational Proof Engine v1 and Receipt API beta turn caller-supplied service evidence into deterministic, portable assurance receipts. Planned custody, settlement and dispute layers are not yet deployed.
02 / Fast facts
Facts that can be independently checked.
APIBeta
Receipt API
Bounded receipt creation, verification, health and OpenAPI endpoints are publicly inspectable.
PVTYSolana
Fixed token
Originally 50,000,000 PVTY were issued; current supply can decrease through burns; mint and freeze authorities are removed. Market access depends on independently available liquidity.
Canonical mint
8a9P2My6dUhKYJacztYv6bSjKJ1XZwTYY3qz5VwgcGML
03 / Downloads
Brand and technical assets.
Use the full project name PactVerity and token symbol PVTY. Do not imply endorsements, guaranteed availability or financial returns.
- Download the Proof Engine demonstration video
- Download square PVTY token artwork
- Download PactVerity vector mark
- Open the API specification
- Open technical press notes
- Open the reviewer and media evidence brief
- Download the complete developer kit
- Open the current PVTY platform-correction packet
- Open the current weekly Phantom-readiness report
- Open the 30-day evidence-led growth operator plan
- Open the seven-day evidence campaign
- Open the public benchmark
- Read the current whitepaper
04 / Official channels
Confirm announcements at the source.
01 / Audience map
Four technical audiences, four relevant entry points.
Audience 01Evidence first
AI-agent publications
Pitch the gap between narrative agent claims and deterministic evidence. Offer the failure-case dataset and reproducible demo, not a token-price story.
Audience 02Evidence first
Solana builders
Pitch portable verification receipts, optional wallet signatures and the open reference adapters. State that planned settlement utility is not deployed.
Audience 03Evidence first
Security researchers
Pitch the threat model, tamper tests and claim-boundary review. Invite critical findings and responsible disclosure.
Audience 04Evidence first
API communities
Pitch latency, uptime, freshness and output-integrity checks that can be reproduced from explicit inputs.
02 / Demonstration asset
Upload the video natively; link to the reproducible case.
The MP4 is prepared for native X and YouTube uploads. Use separate campaign links so attention can be connected to product actions without treating views as adoption.
03 / Download packs
Give editors and reviewers the complete boundary.
04 / Publication test
A pitch is ready only when every sentence has a source.
- Use the live health, programme and market endpoints for current numbers.
- Label first-party demonstrations and known-answer tests.
- Publish zero verified integrations or reviews until independent evidence changes the register.
- When PVTY is mentioned, include shallow liquidity, volatility, independent DEX operation and total-loss risk.