# Consumer Monetization
The complete guide to monetizing your AI agent with Stripe payments, per-tool pricing, and product catalogs.
---
The Monetize tab in the app builder (under **Launch**) gives you three ways to earn revenue from your AI agents: selling credit packages and subscriptions, setting per-tool pricing, and listing products for agentic commerce. This guide covers all three.
**Chipp takes no platform fee on consumer payments.** You keep 100% of the revenue minus Stripe's standard processing fee, paid straight into your connected Stripe account.
For the basics of connecting Stripe and creating your first package, see [Selling Access to Your AI](/docs/guides/selling-access). This guide covers the full Monetize tab in depth.
## The Monetize Tabs
| Tab | Purpose |
|-----|---------|
| **Sell** | Connect Stripe, enable monetization, and create credit packages or subscriptions |
| **Pricing** | Set what each message costs and add per-tool credit costs for valuable actions |
| **Catalog** | List products and manage API keys for agentic commerce (agent-to-agent transactions) |
| **Estimator** | Estimate your app's cost per session from real usage and get suggested package and subscription prices |
## Sell Tab
The Sell tab is where you connect payments and create packages. For full setup instructions, see [Selling Access to Your AI](/docs/guides/selling-access).
### Stripe Connect
Chipp uses Stripe Connect so payments go directly to your Stripe account. Click **Connect with Stripe**, complete the onboarding flow, and you'll see your account status with a link to your Stripe dashboard.
> **Note:** Stripe must be connected and charges must be enabled before you can create packages or list products. If charges are not yet enabled, complete the remaining verification steps in your Stripe dashboard.
### Monetization Toggle
Enable the **Monetization** toggle to require credits for using your agent. Configure free trial credits (given to new users automatically), currency, and tax behavior under **Checkout Settings**.
### Packages
| Package Type | How It Works |
|--------------|-------------|
| **One-time** | User buys a fixed number of credits. Each message costs your **Credits per message** price (1 by default). When credits run out, they buy more. |
| **Subscription** | User pays monthly or yearly. Configure whether subscriptions bypass credit checks or grant a recurring credit allotment. |
Each package has two separate inputs:
- **Customer pays**: the price, in your app's currency (for example `25.00` for $25.00).
- **Customer receives**: how many credits the customer gets (for example `1,000`).
The two are independent. Chipp never converts credits to money, so you can sell 1,000 credits for $25.00 or for $10.00. Credits are your own unit: you decide what a message or a tool costs in credits on the **Pricing** tab.
### Unit Name
Credits do not have to be called credits. Under **Unit name**, pick what your customers see: **Credits**, **Points** or **Tokens**. The word changes in the chat's balance meter, the **Buy** button, the package list, the Stripe Checkout line item and the tool approval card. Balances, prices, deductions and package quantities stay the same, and the API keeps its field names (`credits`, `creditCost`). Apps that never set a unit name keep showing **credits**.
### Usage Limits Are in Dollars
The **Per-user spending cap**, the **Recurring monthly allowance** and **Free Trial Usage** measure real AI usage cost, so you enter them in US dollars (for example `$25.00`). They are not credits, and they are not converted into credits.
### Unlimited for Subscribers
The **Unlimited for Subscribers** toggle controls whether active subscribers get unlimited access or still consume credits:
- **On**: Subscribers send unlimited messages. No credit deduction.
- **Off**: Subscribers still consume credits per message. Once a subscriber uses up their package's monthly credits, they are blocked until the next renewal.
### Revenue Stats
| Metric | Description |
|--------|-------------|
| **Total Revenue** | Lifetime earnings from this app |
| **Purchases** | Number of completed transactions |
| **Active Subs** | Currently active subscribers |
| **Customers** | Distinct paying users |
## Pricing Tab
The Pricing tab sets what your agent costs in credits: a price for each message, plus optional prices for individual tools.
### How It Works
While monetization is on, every message costs your **Credits per message** price. It is 1 credit by default, and you can set any whole number from 0 to 100. Per-tool pricing adds a charge on top of that when a specific tool runs (e.g., generating a report, querying a database), so high-value actions cost more than ordinary messages.
- A user needs at least the per-message price in credits to send a message. When their balance is lower, they are asked to buy more.
- Set **Credits per message** to **0** to make conversation free. Priced tools still charge, so users pay only when your agent performs a valuable action.
- Active subscribers are not charged per message while **Unlimited for Subscribers** is on.
- Per-message credits are not charged while the free trial type is **Time** or **Usage**.
Changes save automatically and apply to the next message, no republish needed.
Credit pricing applies only while the **Monetization** toggle is on. If you turn monetization off, messages and priced tools run free and users are not asked to approve a charge.
### Setting the Price per Message
Open the Pricing tab. The **Messages** section at the top has a **Credits per message** field. Enter a whole number from 0 to 100. Clear the field to go back to the default of 1.
### Setting Up Tool Pricing
**1.**
Open the Pricing tab
All tools configured on your app appear, grouped by source: Custom Actions, Hosted Integrations, MCP Integrations, and Components.
**2.**
Set the pricing mode
Each tool is **Free** by default. Turn on the tool's switch to charge credits per execution. Active subscribers are never charged for priced tools (the row shows **Free for subscribers**).
**3.**
Set the credit cost
For priced tools, enter the cost per execution. Consumers approve each charge before the tool runs. Changes save automatically.
A consumer has 60 seconds to approve. After that the tool does not run and nothing is charged. If they click **Approve** later, the card says the approval timed out, and they can ask again.
### Example Pricing Strategy
| Tool | Mode | Cost | Rationale |
|------|------|------|-----------|
| `search_knowledge` | Free | 0 | Low-cost operation, encourages usage |
| `generate_report` | Credits | 5 | High-value output |
| `send_email` | Credits | 2 | External side effect |
| `query_database` | Credits | 3 | Direct data access |
> **Tip:** Keep everyday tools free and price only the high-value actions. Set the per-message price to match your model costs (or 0 for free conversation), so costs line up with the value your agent delivers.
## Catalog Tab
The Catalog tab powers **agentic commerce** -- the ability for external AI agents to discover, purchase, and use your agent's capabilities programmatically through the Agent Commerce Protocol (ACP).
### What Is Agentic Commerce?
Agentic commerce lets other AI agents (not just human users) buy and use your agent's services. For example, a customer support agent could purchase access to your specialized analysis tool, or a research agent could buy your data enrichment service on a per-use basis.
Unlike consumer payments, Agent Catalog orders carry a 5% Chipp platform fee. The rest goes to your connected Stripe account.
### Products
List items for sale through the agent catalog:
| Field | Description |
|-------|-------------|
| **Name** | Product name shown in the catalog |
| **Description** | What the product does |
| **SKU** | Unique identifier |
| **Price** | Cost in cents (e.g., 999 = $9.99) |
| **Currency** | Payment currency: USD (default), EUR, or GBP. Checkout charges in this currency |
| **Fulfillment** | **Automatic** (your agent runs the bound tool right after payment) or **Manual** (you fulfill the order yourself) |
| **Bound tool** | Automatic only. The tool your agent runs to fulfill the order, chosen from the tools connected to your app, with optional JSON parameters. Without one, orders wait as `confirmed` |
### API Keys
API keys let external agents authenticate when purchasing. Create keys in the Catalog tab with a label so you can tell them apart -- each key is shown only once at creation.
Click **Webhook** on a key to set the HTTPS URL that receives signed order notifications and to generate a signing secret. Private and internal addresses are refused. See [ACP Webhooks](/docs/acp/webhooks).
### Orders
The Catalog tab shows recent orders from external agents with status, amount, currency, and timestamp.
> **Note:** You need at least one passing evaluation (a score of 70% or higher) before you can list products in the Catalog. Evals help ensure consistent quality for paying customers. See [Understanding Evals](/docs/guides/understanding-evals).
## Putting It All Together
A common monetization strategy combines all three tabs:
1. **Sell**: Create a free trial (10 credits) and a subscription ($29/month with unlimited access)
2. **Pricing**: Make conversation free (set **Credits per message** to 0), charge 3-5 credits for high-value tool executions
3. **Catalog**: List your agent's unique capabilities as products for other AI agents to purchase
This gives you three revenue streams: direct consumer subscriptions, per-action credit revenue, and programmatic agent-to-agent commerce.
> **Note:** Monetization works best with sign-up. Free trial credits go only to signed-up users, and anonymous visitors cannot buy packages. In the **Access** tab, choose **Required Sign-up** or **Encouraged Sign-up** (not **Open Access**) before enabling credits.
## Reading the Consumers Tab
If your agent sets a **monthly allowance**, the Consumers tab shows three columns instead of one **Credits** column:
- **Monthly allowance**: the dollars remaining this cycle, with how much was used out of the total. A top-up purchase never hides it.
- **Top-up balance**: the credits a consumer bought or was granted, with how many are used and how many remain.
- **Billing cycle**: when the current cycle started and when the allowance resets next.
Usage draws down the monthly allowance first. Top-up credits are spent only after the allowance runs out. When the allowance resets, only the allowance refills. Unused top-up credits carry forward unchanged.
For example, a consumer has a $40 monthly allowance and uses all of it. They buy a top-up and use 20 of its 40 credits. After the reset, the row shows **$40.00 remaining** for the monthly allowance and **20 remaining** for the top-up.
The cycle dates are the schedule the allowance reset runs on, which counts monthly from the day the consumer joined your agent. They are not a Stripe renewal date. A consumer whose spending is pooled across a workspace, an anonymous visitor, or any consumer of an agent with no monthly allowance shows a short note such as **Workspace pool** or **No recurring cycle** instead of dates.
## Checking One Person's Balance and Spend
Open your app, go to **Insights > Consumers**, and click a person's name. Their record opens with a **Billing and usage** section that shows only that person's money in this app:
- **Monthly balance available**: what is left of the app's monthly allowance this month, with how much they used and when it last reset. A person in a workspace's shared pool shows **Shared pool** instead.
- **Top-up balance**: the credits they bought or were granted. This is a separate balance from the monthly allowance, and the two are never added together.
- **Total usage**: what their conversations cost in total.
- **Usage by month**: their spend grouped by the month each conversation started. The figures are the same costs you see on each conversation in **Insights > Conversations**, so the two views always agree.
- **Transaction history**: top-ups, grants, credit adjustments and credits spent on messages or priced tools.
A person who has not chatted yet, or has never bought credits, sees a short "nothing yet" note in that section.
> **Note:** Your organization's own Chipp credit balance (the wallet that pays for every app) is not shown here. Find it in **Settings > Billing**.
## Troubleshooting
### Stripe Not Connecting
1. Make sure you complete all Stripe onboarding steps
2. Check that your Stripe account has charges enabled
3. If stuck, disconnect and reconnect Stripe
### Users Not Being Charged
1. Verify the **Monetization** toggle is enabled in the Sell tab
2. Check that at least one package exists
3. Confirm the user's credits are exhausted (free trial credits may still be active)
4. Check **Credits per message** in the Pricing tab. At 0, messages are free and only priced tools charge
### Tool Pricing Not Taking Effect
1. Per-tool pricing only applies when monetization is enabled
2. Verify the tool's switch is on (the row shows a credit cost, not **Free**)
3. Active subscribers are never charged for priced tools
4. Changes save automatically -- refresh the page if the UI seems stuck