Perpensum / Proposed category / Version 0.1

Agentic Purchase Quality Verification

APQV: a proposed buyer-side quality layer for agentic commerce

Agentic Purchase Quality Verification (APQV) is the continuous, evidence-based process of independently comparing an AI agent's purchase mandate and constraints with the selected source, seller representations, price, transaction, delivery, and buyer-observed outcome, then using observed matches, mismatches, risk signals, and evidence gaps to inform the next purchase decision.

Quality here means the quality of the purchase as a whole, not the absolute quality of the product or service. APQV does not answer whether a purchase was universally good. It asks how the executed purchase and observed outcome aligned with the buyer's conditions, and what the evidence justifies doing next.

Try the synthetic Playground Read the machine-readable definition

The missing question

Existing evidenceQuestion it can answerQuestion that remains
Mandate and authorizationWas the agent allowed to buy?Did the authorized purchase satisfy the purpose?
Checkout and paymentWas an order placed and value transferred?Was the result usable by the buyer?
Provider status and delivery receiptDid the provider report success or issue a response?Did the response meet the pre-purchase criteria?
Order and fulfillment recordWhat did the seller record as fulfilled?What did the buyer independently observe?

These layers are complementary. MCP and A2A connect tools and agents. UCP and ACP represent commerce flows. AP2 supplies mandate and authorization evidence. Payment and receipt systems record settlement and response events. APQV would consume that evidence without treating any one of those events as proof that the buyer's purpose was met.

Why this becomes necessary

Companies are beginning to give AI agents mandates and budgets. If agents buy data, inference, research, software actions, and work from other agents or APIs, transaction volume can grow beyond what people can inspect one purchase at a time.

A buyer agent can learn from its own history, but its view begins cold and remains narrow. The APQV hypothesis is that machine purchasing needs an independent quality layer that observes the same bounded evidence across purchases, detects repeatable mismatches, and returns that evidence to the point where the next purchase is selected.

This is structurally similar to media quality verification in digital advertising: once machines execute purchases at high volume, the buyer needs an independent measurement and control layer. The object being measured is different. APQV measures an agentic purchase against the buyer's mandate and observed outcome.

The APQV loop

  1. Commit the buyer's purpose.Record constraints and acceptance criteria before the result is known.
  2. Snapshot the offer.Preserve the selected source, seller representations, price, and terms.
  3. Observe the transaction.Keep authorization, order, payment, delivery, retry, and refund evidence separate by provenance.
  4. Observe the buyer-side outcome.Test whether the delivered result can actually be used for the committed purpose.
  5. Compare and return.Report matches, mismatches, risk signals, evidence gaps, and the bounded action justified before the next purchase.

A minimal outcome vocabulary

The current experiment uses five states. They are deliberately operational rather than universal seller scores.

StateObserved meaningTypical next action
usableDelivery met the frozen criteria for this purpose.Keep eligible
delivered_unusableA delivery arrived but did not meet the frozen criteria.Hold for the same purpose
paid_without_deliveryPayment was observed without delivery or a durable recovery path.Hold and investigate
delivery_pending_recoverableDelivery is missing, but retry remains available without repurchasing.Retry the entitlement
insufficient_evidenceThe record cannot support a bounded conclusion.Collect evidence

The APQV Playground lets you change synthetic evidence and see these states update. Its default case is a provider that reports succeeded while the buyer's required fields are missing.

What APQV does not claim

Initial scope

The first practical scope is machine-verifiable digital outcomes and services: API results, extraction, transcription, translation, generation, analysis, datasets, and paid agent work. These can be observed by the buying system without requiring a person, sensor, or logistics partner to inspect a physical item.

Physical goods remain within the long-term idea, but they add evidence problems—condition, authenticity, durability, returns—that should not be hidden behind a premature claim of coverage.

Open questions

  1. Which buyer-side observations can be collected without exposing sensitive business data?
  2. Where should an independent quality check sit so it can affect the next purchase?
  3. Which outcome states remain comparable across different digital purchase purposes?
  4. How should cross-buyer evidence be aggregated without exposing participants or coordinating prices?
  5. When is a mismatch evidence of poor fulfillment, and when is there enough evidence to investigate fraud?

Status and authorship

APQV is a proposed category, not an adopted standard. Version 0.1 is published to make the boundary testable and to invite disagreement. The five outcome states are a minimal working vocabulary, not a claim that every future purchase fits them.

Perpensum proposes the term and is building an independent APQV evaluation layer, so it has a commercial interest in the category. That interest is stated rather than hidden. Perpensum does not accept payment, partnership, or preferential terms from an evaluated party in exchange for how that party is evaluated.

The definition and this document are licensed under CC BY 4.0. Quote, critique, implement, and derive from them with attribution. The structured definition is published alongside the prose.