Understand APQV without installing anything or exposing a real purchase.
Run it now →Zero setup · zero dollars · synthetic evidence
Run one machine purchase through Perpensum.
See the actual buyer-side sequence: freeze the mandate, authorize one execution, observe delivery, verify usability, and return evidence to the next purchase decision.
APQV lifecycle
- Purchase mandateWaiting to run
- Pre-purchase decisionWaiting to run
- Synthetic provider executionWaiting to run
- Buyer-observed verificationWaiting to run
- APQV evidence recordWaiting to run
Public sandbox boundary. This demonstration makes no real purchase, evaluates no real seller, moves no money, uses no credentials, and retains no record. It does not determine fraud or absolute quality.
How to run this
The same flow in four commands
Node.js 18 or later is enough. The downloaded file calls the public synthetic endpoint and prints only the bounded outcome.
mkdir perpensum-quickstartcd perpensum-quickstartcurl -O https://perpensum.org/quickstart/quickstart.mjsnode quickstart.mjs
Choose an integration path
Try first. Connect when the boundary is clear.
One narrow tool for an AI agent. The package is built and tested privately, but is not on npm yet.
Read the proposed connection →A small JavaScript client for embedding Perpensum. The release candidate is private until licensing and naming are approved.
Read the SDK preview →