Pricing
Your infrastructure. Your business.
There are two sides to an agent product: what it costs you to run, and what you charge your users. Keep them separate. Inlay's launch rates are still being defined; your product's pricing stays yours.
Pricing status
Launch rates pending
Public prices, included allowances, usage rates, and any billing fees have not been set. This is not a free-access offer or a promise that every feature is included.
Access is request-only. During manual onboarding, discuss your workload, required features, limits, and commercial terms before deciding whether to proceed.
Builder to Inlay
What you pay
The platform and usage behind your product. Model tokens and server-tool usage are metered, but metering is not an approved public price. Rates, packaging, allowances, and limits remain pending.
Your users to your business
What you charge
Your own plans, allowances, and credit top-ups. Inlay provides billing data and hosted payment flows for your app to use, subject to setup. These are your customer offers, not Inlay subscription tiers.
What you're evaluating
A map of the platform, not a bundle of promised inclusions. Use the guides to check the fit; confirm availability and commercial scope during onboarding.
| Capability | What it supports | Read the guide |
|---|---|---|
| Agent design and execution | Build graphs, publish agent versions, and connect your own interface through the SDK. | Versions |
| Models and server tools | Configured OpenAI-compatible models and server-side tools, with usage recorded by model or tool. Availability varies by deployment. | Server tools |
| Knowledge and state | Document retrieval, citations, and run-, user-, or agent-scoped state, with explicit public field visibility. | RetrievalState and memory |
| Product integration | Streaming conversation rows, structured outputs, progress, and optional generated TypeScript clients. | Typed clients |
| Customer billing | Plans, credit balances, usage, invoice information, and hosted subscription and top-up flows for your users. | Billing |
Billing your users
Your pricing page. Your paywall.
Define and publish plans, set allowances, and display a user's balance and usage in your interface. A quota denial is a billing state for your app to handle with an upgrade or top-up flow, not something to retry in a loop.
Hosted subscriptions and top-ups require a connected Stripe account with charges enabled. Subscription checkout requires a published plan and is for new subscriptions; existing plan changes are operator-side today. Top-up credits depend on payment confirmation through the webhook flow.
Invoice operations and payment setup still need an operator. Do not treat the billing API as a promise of fully automatic invoices, payouts, or tax handling. Review the billing guide and confirm the operating requirements during onboarding.
Before you start
Bring the shape of your workload.
Tell us what the agent does, who will use it, which models and tools it needs, and whether you plan to charge your users. Include retrieval, memory, or scheduled work if they are part of the product.
The open pricing decisions are platform charges, usage rates, included allowances, overage rules, and any fees for customer billing. No numeric rate or fee is being quoted on this page.
Build the product only you can build.
Tell us who it's for and what the agent needs to do. Inlay is in private beta, with access reviewed and onboarding handled manually.