Connect your buyer agent to Perpensum

Private Hosted Alpha · one synthetic purchase · no money or production credentials

This is an acceptance test, not a production service. Your Claude Code or Codex agent sends a purchase plan to its local Perpensum Gateway, receives a pre-purchase decision, executes a no-money synthetic digital purchase, and returns a buyer-observed outcome. A person does not re-enter the plan or evidence for the transaction.

Perpensum is testing Agentic Purchase Quality Verification (APQV): an independent buyer-side layer that compares what an agent intended to buy with what was selected, delivered, and usable before the next machine purchase.

Request a private Alpha invitation

Who this is for

You build or operate a buyer-side AI agent.
You use Claude Code or Codex on a Mac.
You are willing to let the agent run one synthetic digital purchase through Perpensum.
You want to test where purchase intent, authorization, delivery, and buyer-observed usability should meet.

No agentic-commerce protocol or live payment integration is required for the first run. The included synthetic seller returns machine-readable JSON and charges nothing.

What happens

We issue one private invitation. It is scoped to one pseudonymous buyer agent and a one-purchase, no-money mandate.
You install the buyer-side Gateway. The Console provides a Mac download and a local setup page for Claude Code or Codex.
Your agent makes the request. It fixes the purpose and success condition before the synthetic purchase, then calls one Perpensum purchase tool.
Perpensum checks before execution. The Hosted Control Plane checks the mandate and returns a short-lived, one-use decision ticket.
The Gateway observes the outcome. It evaluates the returned result on your Mac and sends a sanitized outcome summary to Perpensum.
You see the full loop. The private Console shows the mandate, request, decision, observed outcome, and bounded next action.

What stays on your machine

provider and payment credentials
provider-specific request payloads
raw delivered content
local recovery records for an interrupted provider operation

The first synthetic run does not need any provider token, card, wallet, customer data, or production funds.

What Perpensum receives

a pseudonymous organization and buyer-agent identifier
the precommitted purpose and machine-checkable success condition
seller, offer, displayed price, and purchase route without credentials
the pre-purchase allow or block decision
a sanitized buyer-observed outcome after delivery

Do not send personal data, customer records, private prompts, production credentials, or information you are not allowed to share.

What you get

a working buyer-side purchase gate on your own agent
a machine-readable APQV outcome from one end-to-end purchase loop
a private Console record showing what was known before and after execution
direct input into the evidence and integration model before it is fixed

Participation is free. There is no public seller score, cross-company price benchmark, commercial commitment, or request for access to your production systems.

Current limits

Approved-access Alpha; not production-ready. Accepted participants sign in with a short-lived link sent to their approved email address—there is no invitation code or Perpensum password.
macOS, Node.js 22 or newer, and Claude Code or Codex are required.
The installer is not yet a signed and notarized native Mac application, so macOS may require explicit approval to open it.
The acceptance run uses a synthetic seller. A real provider pilot is a separate decision with a separate mandate.
Current outcome checks prove the evidence loop, not universal or absolute quality.

Start

Email hello@perpensum.org with the buyer-agent runtime you use (Claude Code or Codex) and whether you can run the first synthetic test on macOS. Do not attach credentials, prompts, purchase records, or customer data.