Set up with the assistant

The setup assistant turns a description of your product and pricing into Base316's model. Open a project, pick the environment (usually Sandbox), and choose Product → Setup assistant.

We sell an API. Free gets 1,000 calls a month, Pro is $49/month with 100,000
calls and $0.002 per extra call.

The assistant reads what the environment already has, then proposes what is missing: here a meter that counts api.call events, a metered api_calls feature, and the two plans. Its reply tells you what your application has to do for the model to work: the event name and payload property to send for each meter, and the feature key to check.

Nothing changes until you apply

The assistant can read the environment but cannot write to it. Everything it wants to create appears under Proposed changes. Untick anything you do not want and press Apply. Proposals run in order, so a plan can use a feature proposed above it in the same list. If one fails, for example because its key is already taken, it is marked with the reason and the rest still apply.

Proposals from several messages accumulate, so you can keep refining: "add an annual version of Pro at $490", "add a seats feature with 5 included". If a pricing decision is genuinely open, such as a limit or a price you did not mention, the assistant asks rather than inventing a number.

What it can propose

• meters, with their event name, aggregation and payload property
• features: boolean, metered or quantity
• plans with a recurring price, a trial, entitlements and per-unit overage prices — or a per-model (MATRIX) price, one unit price per value of a meter's groupBy property such as the AI model
• roles and their permissions
• add-ons, including one that bills a firm per client tenant
• tenants, client tenants of a firm, inherited roles and tenant branding

It cannot edit or delete existing things. For that, use the matching screen in the dashboard.

Overage and check()

An overage price makes a limit soft. check() keeps allowing usage past the plan's limit plus any credits, reports usage.overage: true, and that usage is billed at the overage price. Without an overage price the limit is hard and check() refuses at it with USAGE_LIMIT_EXCEEDED.

To put a ceiling on what a customer can be charged, give the entitlement a hard cap: check() refuses past it with HARD_CAP_REACHED, and credits do not raise it. The assistant says this whenever it proposes an overage price, and can propose a cap with it. See Gate a feature.

Who can use it

Members who can manage the organization. Every message is a call to a model, and applying creates catalog entries, so view-only members see the page but cannot send messages.

Your messages, and a summary of the environment's catalog (meters, features, plans, roles, add-ons and the first 50 tenants), are sent to Anthropic to generate replies. See the privacy policy.