Track 01Agent
AI-agent outcome receipt
Capture measurable completion, latency, freshness and output-integrity evidence for an autonomous workflow.
16 / Builder challenge
Build one integration another developer can verify.
The PactVerity Integration Challenge is accepting proposals for three independent reference integrations. Selection, implementation and acceptance are separate evidence gates.
ApplicationsOpenReference awards3 × 1,000 USDCPool statusCommitted, not escrowed
01 / Challenge
Three useful integration tracks.
Each entry must use a real public or test service, call the operational Receipt API beta and disclose where its evidence originates.
Track 02API
API or SLA verification
Convert service observations into a deterministic receipt with thresholds another developer can reproduce.
Track 03Tooling
Evidence adapter
Build a small open-source adapter, SDK example or test harness that improves receipt reproducibility.
Public questions and independent review
Use the GitHub work items for scope questions that benefit every applicant. Qualified security reviewers can also respond to the separate independent review request . Do not post secrets, private customer data or vulnerability details in a public issue.
02 / Required deliverables
Acceptance requires working public evidence.
- A public source repository with an open-source licence and setup instructions.
- A working integration that calls the PactVerity Receipt API beta; a mock-up alone does not qualify.
- A recorded demonstration and a machine-readable sample assurance receipt.
- A reproducibility guide with test inputs, expected outputs and known limitations.
- No secrets, customer data, misleading adoption claims or token-price promotion.
- Disclosure of employment, investment, sponsorship or other material connection to PactVerity.
03 / Public judging
A 100-point evidence rubric.
Submissions must score at least 70 overall and cannot pass with a zero in technical correctness, reproducibility or security.
| Criterion | Points | What is evaluated |
|---|---|---|
| Technical correctness | 30 | Real API use, valid receipt construction and accurate status boundaries. |
| Reproducibility | 25 | A second developer can run the project and obtain the documented result. |
| Evidence quality | 20 | Measurements are relevant, traceable and not presented as independently true when caller-supplied. |
| Security and privacy | 15 | No exposed secrets, unsafe wallet requests or unnecessary personal data. |
| Clarity | 10 | Concise documentation, useful demo and explicit limitations. |
Reward terms
Three accepted reference integrations may each earn 1,000 USDC. Payment becomes due only after the public repository, working demo, sample receipt and limitations pass the rubric and are accepted in writing. Payment is targeted within seven days of acceptance, subject to lawful eligibility and receipt details. No PVTY purchase, holding or promotion is required.
04 / Apply
Propose a reference integration.
Applications are reviewed for fit before implementation. An application is not acceptance, endorsement, employment or a promise of payment.