Show HN: Seams handles access, spend caps, and metering on one request path

Seams, a new startup, launched a gateway that combines access control, spend caps, and metering on a single request path for AI products, allowing customers to call models under their own names while tracking costs and revenue. The service, hosted at <app>.portal.ourseams.com, provides a branded portal, key management, and real-time spend controls, with no storage of message content.

Build the portal to launch your AI product. A gateway your customers call, model names you own, routing you control, metered and capped while the response is still streaming. Monetization Plans, balances, and your markup. See provider cost and revenue on the same ledger. Access Choose which models each customer can call, under your own names. Repoint without redeploying. Control Know who is calling and what they can spend. Caps are checked while the stream is open. What we offer Access, control, and monetization in one place Model access, spend control, and billing that match: one portal for your customers, one gateway for you. - Your portal - We host it at <app .portal.ourseams.com: your product name on our subdomain. Wire our components into your app or send customers straight to the hosted surface. - Your model names - Customers call <app /smart, not the provider's SKU. Name models the way your product delivers value; swap the provider or route behind the scenes as your product grows. - Controls - Bundles decide which models a caller can reach. Routers decide how those names resolve. Caps decide when a call stops, including mid-stream. Build with seams Everything between the model and the invoice From the first call to your thousandth customer: who may reach which model, how that name resolves, and how spend is metered and capped. Access under names you own Bundles decide which models each customer can reach. Aliases and routers decide how those names resolve. Change them without redeploying a client. Keys your team mints and revokes One key per end user on a shared balance. Mint and rotate credentials without splitting spend. Revoked keys stay listed for audit. A portal with your name on it Hosted at <app .portal.ourseams.com, in your brand. Usage, spending, and keys. Your customers never see a vendor name. Margin you can see before the invoice See which models drive cost and margin so you know what to price and what to keep. Frequently asked questions Common questions No. We meter the call and pass the stream through. There is no place in our usage records to store message content. All the portal infrastructure your product needs Gateway, aliases, and routing behind names your product owns. Metering, holds, and spend caps that hold for the life of the stream. A portal on <app .portal.ourseams.com, keys, usage, and limits under your name. Point your clients at Seams sign in, connect a provider, ship Sign in, point your base URL at your application gateway, and mint a key for your first customer. Metering and caps start on the first call. Bring your own provider key to start.