Inside Piskes's Metered AI Gateway for External Developers
Piskes now issues API keys to external developers for an OpenAI-compatible AI gateway, available on credits or bring-your-own-key.
Until now, the AI gateway that powers every model call across Piskes's 17 apps was internal infrastructure — the thing your workspace used, not something you could point your own code at. That's changed. External developers can now get their own API key and call the same OpenAI-compatible gateway directly, the same shape of product as OpenRouter, Portkey, or Helicone: one endpoint, many providers behind it.
What you actually get
A signup issues a real API key scoped to your account, usable against standard OpenAI-compatible endpoints — chat completions, embeddings, and a models listing — with the specific provider inferred from the model name you call. You don't need a separate account or key for each underlying provider; the gateway handles routing to whichever one a given model belongs to.
There are two ways to pay for usage: metered credits, drawn down as you make calls, or bring-your-own-key (BYOK), where you supply your own provider credentials and the gateway charges a smaller fee on top rather than marking up the full cost of each call. Both paths were built, deployed, and verified end to end against production — a real signup, issuing a real key, with usage and balance endpoints correctly resolving that key's activity.
One thing to know before you reach for a card
Stripe payment is not live yet. The keys required to process a card payment aren't set, so the billing routes that would normally handle a purchase currently return a safe, controlled unavailable response rather than attempting — and failing — a charge. In practice, that means the way to get started today is through credits or BYOK access rather than expecting to pay by card on day one. We'll announce separately when card payment is live; until then, don't expect a checkout flow to work.
Why this matters
This is a genuinely new surface, not a repackaging of something that already existed for internal use — external developers now have a real, working, production-verified way to call a multi-provider AI gateway under their own key, without ever holding a provider credential of their own unless they choose BYOK specifically for that reason. If you've been paying for a separate AI gateway product, or hand-rolling multi-provider routing yourself, this is worth a look.