Monetization

Know the two billing relationships#

Monetization lets a site owner sell an offer to a visitor. This is separate from the owner's Make Agent Fast plan, credit packs, and custom-domain add-on. Creator revenue/order records and owner platform usage must be reconciled separately.

The page displays its current checkout mode. Polar (live payments) can accept configured real purchases. Local/dev (test mode) is for development behavior and must never be represented as settled production payment.

Create an offering#

Choose one of the supported kinds:

Enter a specific title, description, price in cents, currency, and optional Polar product key. The key maps the offering to a configured provider product. An active offering can be shown or recommended in the agent conversation; an inactive one remains owner-visible but should not be sold.

Use one canonical source for price, fulfillment, availability, refund terms, tax treatment, and support. Add those approved facts to knowledge; the agent must not invent a discount, guarantee, delivery time, or scarcity claim.

Gate the agent behind paid access#

Create and activate a Paid access offering first, then select it under Members-only agent. Visitors who have not unlocked it receive a purchase/unlock path instead of normal chat access. Only active access products can be selected; the runtime also fails open rather than permanently bricking chat if a selected offer disappears.

Test logged-out/new-visitor, successful checkout, return access, canceled checkout, duplicate provider event, inactive offer, and refund/revocation behavior before launch.

Configure checkout rails#

For live Polar checkout, the platform deployment and product mapping must be configured. An optional Korean-payment control can offer KakaoPay/Naver Pay/Toss for KRW offers only when the platform reports that rail as available; turning on an unavailable toggle does not create a provider integration.

Use provider test mode where supported, then verify a small real purchase according to your operational policy. Confirm currency minor units: for USD, 2500 means $25.00. Do not guess cent behavior for a currency with different minor-unit conventions.

Review orders and revenue#

The page reports paid-order count, revenue rollup, and recent purchases. “Paid” reflects the recorded checkout/provider state; reconcile provider fees, taxes, refunds, chargebacks, payouts, and fulfillment in the appropriate financial system.

Deleting an offering does not erase historical order or billing records. Deactivating is safer than deleting when an operator needs the existing configuration for investigation.

Optional outcome pricing#

Pay per outcome can deduct a fixed owner-wallet credit amount for a qualified lead or booked call in addition to normal usage. It is not visitor checkout and does not become creator revenue. Leave it off unless the owner understands the extra credit charge and the exact event definitions.

Launch checklist#

• Live/test checkout mode is unmistakable.
• Offer title, description, currency, price, and provider product match.
• Fulfillment, access duration, refunds, tax, support, and privacy are documented.
• Agent knowledge contains only approved commercial claims.
• Success, cancel, duplicate, refund, and inactive-offer paths are tested.
• Purchase alerts, fulfillment owner, accounting reconciliation, and incident process are assigned.

Troubleshooting#