Core concepts

Bundles

Which models a key may reach, and at what markup.

Every key is minted under a bundle. The bundle decides which aliases that key can reach and what margin sits on top of provider cost.

Create a tier

seams bundles add pro --name Pro --price 29/month

# slug          pro
# price         $29.00/month

Allow models and set a spend limit

seams bundles allow pro app/fast app/smart
seams bundles edit pro --spend-limit 50/month
seams bundles show pro

Deny a model or remove the bundle

seams bundles deny pro app/vision
seams bundles rm pro --yes

Alias matching

Three pattern forms, and never a regex: an exact alias, a prefix with a trailing wildcard, or a bare wildcard for everything the customer owns.

text
app/smart      exact
app/*          every alias in this namespace
*               everything

Write-time validation, so a request only does a plain lookup. A bundle that names a model that does not exist is refused when it is saved, not when a request arrives.

Routers ride along

Allow aliases on the bundle, not router names. After those aliases are allowed, creating a router whose targets are all on this bundle attaches the router here automatically. Callers then use the router slug or any allowed alias. See Routers for the create step.

Pricing lives here too

Markup and sell prices on the bundle are how usage-based margin is set. Subscription price and includes are how plans mint allotments. For the full map of strategies, usage, prepaid, plans, outcomes, resell, see Pricing strategies.