Payment readiness without payment false positives

Verify separates commerce-adjacent signals from observed payment execution. Single words like meter, card, wallet, balance, buy, amount, price, rate, interest, limit, usage, or pricing are treated as weak context unless paired with commercial nouns or payment-action evidence such as checkout session creation, payment intent capture, charge, refund, subscription mutation, or order purchase.

Weak context

Not payment capable

Terms like card, meter, amount, price, rate, interest, balance, or limit alone do not make a server payment-capable.

Moderate context

Inferred

Usage metering, billing, receipts, invoices, fares, or commercial quote fields are commerce-adjacent until execution is observed.

Strong evidence

Observed execution

Requires paired action/object evidence for checkout, payment, charge, refund, subscription, settlement, or purchase flows.

Filter the public inventory

PAYMENT CAPABILITY

Observed payment execution

Servers where Verify sees paired payment-action evidence such as checkout session creation, payment intent capture, charge, refund, or subscription mutation.

Open filter

COMMERCE CONTEXT

Billing, usage, or commercial quote context

Servers with usage metering, billing, invoice, receipt, quote, fare, or commercially contextual price/amount fields but no observed payment execution.

Open filter

AUTH FOR PAYMENT

Payment-like tools without auth

Use this to investigate servers with payment execution signals where auth evidence is missing or partial.

Open filter

CONFIRMATION

No observed human confirmation

Payment-execution candidates where Verify has not seen an explicit confirm, approve, or human-in-the-loop step.

Open filter

DELEGATION

Autonomous purchase risk

Servers classified as high-risk or policy-limited autonomous purchase candidates.

Open filter

Classifier Rules

Numeric price context does not mean commercial quote context. Amount, price, rate, interest, balance, or limit can appear in math, statistics, charting, and calculator tools without commerce intent.
Commercial quote context does not mean payment execution. Quotes, fares, invoices, receipts, and pricing fields stay commerce-adjacent until Verify observes an executable payment, checkout, charge, refund, subscription, settlement, or purchase action.
Payment execution is required before autonomous-purchase delegation can be considered. Without observed execution, delegation stays quote-only, usage-metering, research-only, cart-building, or none.

Fields exposed in reports

Field	Values	Meaning
commerce_signal	none, weak, moderate, strong	Strength of commerce evidence. Weak terms alone do not imply payment capability.
payment_execution_detected	yes, no, unknown	Whether paired payment-action evidence was observed.
billing_or_usage_detected	yes, no	Usage, quota, credits, billing, invoice, receipt, or clearly metered-plan context.
numeric_price_context	yes, no	Ambiguous numeric/finance words such as amount, price, rate, interest, balance, or limit.
commercial_quote_context	yes, no	Quote/pricing context only when paired with travel, retail, product, billing, payment, or other commercial nouns.
quote_or_pricing_detected	yes, no	Alias for commercial_quote_context; numeric price words alone do not set this field.
checkout_or_charge_detected	yes, no	Observed checkout, payment initiation, charge, capture, or settlement signal.
checkout_term_observed	yes, no	A checkout word was present. This can be yes while checkout_or_charge_detected is no if no executable checkout action was observed.
payment_capable	none, inferred, observed, verified	Observed is reserved for stronger payment-execution combinations; inferred means commerce context only.
delegation_level	quote_only, usage_metering_context, human_confirmed_purchase, policy_limited_autonomous_purchase, unknown_high_risk	How risky delegated agent action appears from available evidence.