# Axiom Cortex commerce and checkout

> The catalog is ready for SaaS commerce. Hosted checkout is not live until the payment account, legal terms, and fulfillment controls are verified.

## What buyers can purchase

Axiom Cortex uses a usage-first model. The billable unit is one complete interview evaluation for one candidate and one role or blueprint version. It includes the question-level evidence review and whole-interview synthesis. It is not a charge per question, token, method, reviewer seat, or pass/fail recommendation.

| Offer | Reference price | Purchase shape |
| --- | --- | --- |
| Single evaluation | $29 one time | One defined role and one recorded interview |
| Campaign pack | $1,499 one time for 125 evaluations | A hiring campaign with a defined usage period |
| Scale commitment | 1,000+ evaluations | Negotiated quantity and usage period |
| Enterprise proof of value | $2,500 one time for 100 evaluations over 45 days | Bounded two-role rollout before a larger commitment |

These are proposed commercial tests. A price becomes a live checkout offer only after the product identifier, payment terms, taxes, refund handling, validity period, and fulfillment path are verified.

## Recommended checkout path

The static site should stay a fast public catalog. A hosted payment page should collect payment details, while a server-side checkout route creates the session and a signed webhook records the paid evaluation credits. The recommended implementation is Stripe-hosted Checkout Sessions, with Billing added only when a buyer chooses optional recurring replenishment.

The site must never place a secret key, webhook secret, card field, or fake payment link in static HTML. Pricing buttons currently open the beta conversation because checkout is not configured. That state is deliberate, so a buyer cannot pay for an offer that has no verified fulfillment owner.

## What must be ready before launch

1. Create and verify the catalog products and price identifiers in the payment account.
2. Publish the current Terms, Privacy Notice, refund policy, tax treatment, validity period, and production data-processing terms.
3. Add a server-side checkout session route and a signed webhook endpoint.
4. Make fulfillment idempotent, issue credits once, reconcile refunds, and keep a support audit trail.
5. Connect paid credits to an authorized product workspace without sending candidate data through the public site.

The payment events that need an explicit handler include `checkout.session.completed`, `payment_intent.succeeded`, and `charge.refunded`. A successful payment does not make an employment decision. The product still requires a qualified human reviewer to inspect evidence, gaps, and limits.

## Buyer and data boundary

Buyers bring an authorized interview recording or transcript, role criteria, questions, ideal-answer criteria, and candidate metadata through the production application. The public site and read-only demonstration do not collect candidate media or payment details. Do not process candidate data until the production terms, access controls, retention, deletion, and support ownership are confirmed.

See the [public pricing page](https://axiomcx.dev/pricing/), the [pricing and packaging reference](https://axiomcx.dev/knowledge/pricing-and-packaging.md), the [application disclaimer](https://axiomcx.dev/knowledge/application-disclaimer.md), and the [machine-readable commerce catalog](https://axiomcx.dev/data/commerce.json).