Your product moved into agents. Your revenue didn’t.
The point of sale follows the point of use. Your customers now use your product inside agents — Inception lets them buy and expand there.
Your best sales engineer, answering the buyer's agent.
The first evaluation of your product now happens in an agent, before anyone asks for a demo. Your Agent Concierge is there for it, on your own marketing site.
Your plans, limits and integrations, with proof
Plan limits, what each tier includes, the integrations you support and where your security documentation lives — every answer read from your plan data, with a link to its source where one is published, never quoted from memory.
The comparison worth making
Every answer ends with the next useful question, and the questions shift as the agent moves from exploring to comparing to deciding.
Answer pricing, take the demo request
Get pricing from your published plan data, or request a demo with your team. The buyer confirms on your page, or their own agent completes the request with their go-ahead.
Guided evaluation, for the buyer's agent.
The buyer's agent evaluates your product the way a good sales engineer would want it to — with real answers, the honest limits, and a clear next step.
-
We are a six-person team shipping about forty thousand API calls a day. What would we pay, and is the free tier worth starting on?
called
get_pricing -
At that volume you would outgrow the free tier inside the first week, so the team plan is where you would settle. Both figures come from the published plan page.
- Plan limits · published
- Team plan inclusions
Worth asking next
- Compare the team plan with the one above it
- Request a demo with a solutions engineer
-
How does the team plan compare with the one above it? And is the platform SOC 2 Type II?
called
get_pricing -
The plan above raises the limits and adds priority support; at forty thousand calls a day, the team plan covers you. SOC 2 is not something I will answer yes to from a spec sheet — the trust page and the sales team confirm it, so it can go on a demo request as a question for them.
- Plan comparison · published
Worth asking next
- Request a demo with a solutions engineer
- Read the trust page
-
Please request a demo for them, and note the SOC 2 question. Tuesday afternoon works.
called
book_demo -
Their agent, with their go-ahead
Here are their name and email. They agreed to be contacted about the demo.
called
confirm_requestor
The person, on your page
Request a demo
Share a time that suits you. Nothing is sent until you confirm.
- Team size
- 2 to 10
- Stack
- Next.js on Vercel, Stripe
- Security
- SOC 2 report
- Preferred time
- Tuesday afternoon
Requesting a demo is not a purchase; published pricing and the vendor's terms of service govern.
Nothing reaches you without their go-ahead, and every lead says how it was given. The demo time is agreed as a second step.
-
What you receive
The demo request reaches your team with the buyer's words, their team size and stack, the SOC 2 question, how they said yes and what their agent asked first.
Demo requests that arrive briefed.
When a buyer's agent asks your site about pricing and plans, each question lands in your workspace with the answer it got. A demo request arrives with what their agent asked first.
- get_pricing answers from your published plans, never from memory
- The demo request carries the buyer's words, their team size and stack, and how they said yes
- Nothing reaches you without their go-ahead, and every lead says how it was given
- It arrives by email and in your Leads inbox, with a link to replay the conversation
1. Stated facts
- team size band
- 2_10
- stack
- Next.js on Vercel, Stripe
- compliance needs
- soc2
- preferred window
- Tuesday afternoon
2. Verbatim ask
“Six of us, about forty thousand API calls a day. We want to see how the team plan handles that volume, and we need the SOC 2 report before we can sign anything.”
7. Provenance
- surface
- MCP
- approval method
- agent_authorized
10. Contact
- name
- Priya Natarajan
- priya@northwind.example
What their agent asked first
- answered “What would a six-person team pay at forty thousand API calls a day?”
- answered “How does the team plan compare with the one above it?”
- partly answered “Is the platform SOC 2 Type II?”
Replay the conversation
The point of sale follows the point of use.
On your site, their agent completes the request. In your product, the upgrade moment reaches them as a card in your brand, or as facts their agent can act on.
The pricing page is disappearing into the tool call.
Reaching for a capability they don't have yet is the strongest buying signal a user can send — and they send it mid-task, at the moment they need it most. Here is what your product does with that moment today.
This is your highest-intent user at their most urgent — and today, your product abandons them.
And inside the product, the moment converts where it happens.
A user hits a paid limit inside an agent. Instead of a dead error, they get the right upgrade in the thread, pay on your Stripe, and the task resumes.
Your customer opens an agent, not your dashboard.
They came to get something done — not to read your pricing page. The agent is the surface now.
Your product, mid-task, inside an agent.
Inception Agents watches the workflow through your MCP tools, so revenue moments are read from real usage, not guessed.
The user pushes further — typed, sent, blocked.
One more request tips them past a plan limit — and the tool call comes back blocked.
A usage limit. Yesterday, this was a dead error.
No pricing page, no billing portal, no context switch. Left alone, the task just dies here.
The right upgrade, framed by what they're doing.
Inception Agents picks the plan that clears this exact block and shows it in-thread, with the reason attached.
Checkout in the thread. Your Stripe, your prices.
Checkout renders inside the conversation on your own Stripe account — your prices, your margins, your customer.
The task picks up exactly where it stopped.
Entitlements update, and the task resumes where it stopped.
Your revenue card, dealt into the thread.
Your upgrade moment, as a card in your brand inside Claude and ChatGPT, on your own Stripe. Proven end to end in Stripe test mode.
See every revenue moment you're missing.
Every wall your users hit inside an agent, split into new customers and expansion, whether or not it converted yet.
- Unrealized revenue from free and trial users, and from paying ones
- Every question agents ask your site about pricing and plans, and whether it got a real answer
- Conversion from the moment to paid, measured in the thread
- Signed events your own marketing tools can act on
From the first evaluation to the upgrade that follows it.
One measure for when an agent moves a buyer forward, whether on your site or in your product.
-
It reads before it asks
The buyer's agent pulls a short briefing of your plans, limits and integrations first, each fact carrying the link that proves it.
Brief -
Answers from your published plans
get_pricing answers from your published plan data, never from memory. A compliance question goes to a person, because a schema should never be the thing that says yes.
Evaluate -
The demo request, briefed
The buyer confirms on your page, or their own agent completes the request with their go-ahead. It arrives with what their agent asked first, and the time is agreed as a second step.
Request -
The wall becomes the offer
Later, inside the product, a limit the user actually hits becomes an upgrade card in your brand, on your Stripe, and the task they were doing resumes.
Convert -
One price per demo request
A demo request is billed once, when it reaches you, and an upgrade step inside your product is one Revenue Moment. Test requests are never billed.
Count
We make your Stripe checkout agent-aware.
One import into the MCP server you already run. Your entitlement logic stays yours, and Stripe keeps the money.
- Your existing Stripe catalog, prices and customers — nothing re-created
- Your entitlement logic decides; we route the moment it produces
- Our outage cannot break your tools
- Admin approval and sales routing when the user cannot buy
// one import; your entitlement logic stays yours
import { registerExpansionPack } from '@inception-agents/expansion-pack';
registerExpansionPack(server, {
apiKey: process.env.INCEPTION_API_KEY,
resolveEntitlement, // yours
// or entitlementSource: 'stripe' — your Stripe decides
});AI agents are your newest revenue channel. Make them your best.
51%
-
Demos that arrive briefed.
The buyer’s agent can read your published pricing before anyone asks for a demo, and the request arrives with their team size, stack and what their agent asked first.
-
Upgrades where the work happens.
When a user hits a paid limit inside an agent, the right upgrade reaches them in the thread, they pay on your Stripe, and the task resumes.
-
Revenue you can see.
Every wall your users hit inside an agent, split into new customers and expansion, whether or not it converted yet, plus every question buyers’ agents ask your site.
Pay per demo request.
$70 per demo request that reaches you. No monthly fee.
+ Revenue Orchestration Pack: $0.50 per Revenue Moment
Demo and trial requests from a buyer's agent on your marketing site are priced per request. Inside your product, the Revenue Orchestration Pack is priced per Revenue Moment, and your buyers pay on your own Stripe.
Founding customers start with a free pilot.
How pricing works →Asked and answered.
Do we need an MCP server?
For the revenue moments inside your product, yes — one import into the MCP server you already run. For the Agent Concierge on your marketing site, no. Its tools are served on your own domain, through our WordPress plugin or a small Cloudflare Worker.
What reaches our team when a buyer's agent requests a demo?
The request, with the buyer's words, their team size and stack, how they said yes, and what their agent asked first, by email and in your Leads inbox, with a link to replay the conversation in your dashboard.
Does Stripe still hold the money?
Yes. Checkout runs on your own Stripe account, against your existing catalog and customers. We route the moment and attribute the revenue; we never hold funds.
Can your outage break our tools?
No. Every call the expansion pack makes to us has a five-second timeout, and on failure it fails open to your own answer — your users are never blocked by our outage.
How is a compliance question handled?
It goes to a person. When a buyer's agent asks about SOC 2, HIPAA, GDPR or FedRAMP, your Agent Concierge flags it for review and says so, rather than answering yes from a schema.
Where do the existing use cases fit?
They are the moments this converts inside the product — free-tier limits, trial gates, usage walls, feature gates and admin approval. Each has its own page, linked above.
Can you get our product recommended by AI?
No one can promise which vendor an agent picks, and nothing here buys placement. When an agent uses your site’s tools, your Agent Concierge answers from your published plans, and takes the demo request.
The pricing page is disappearing into the tool call.
Convert free-tier, trial, and usage-wall moments inside MCP workflows into paid revenue.