Seams

A gateway your customers call, model names you own, routing you control, metered and capped while the response is still streaming.

Plans, balances, and your markup. See provider cost and revenue on the same ledger.

Choose which models each customer can call, under your own names. Repoint without redeploying.

Know who is calling and what they can spend. Caps are checked while the stream is open.

Your customers get one page that answers what did I spend and how much is left, under your name, on your subdomain. Every answer it gives is a support ticket nobody has to read.

Four pages your customers read, not four you build Usage, spending, keys and activity, hosted at <app>.portal.ourseams.com with your product name, your colour and your logo. Your customers never see ours.

The gateway underneath is what makes the page true Every number on it was written on the request path: metered as the response streamed, held against a balance, settled to the cent. Nothing is reconciled overnight.

The names and the limits are yours to set Bundles decide which models a caller can reach. Routers decide how those names resolve. Caps decide when a call stops, including mid-stream.

A proxy and a meter is a weekend. Money that is right mid-sentence is not.