Keep your OpenAI API key. Portkey replaces it with a virtual one.
If the buying rule is “we will not hand the OpenAI API key to a middle box that replaces it,” CostSlice matches that rule.
Portkey issues virtual keys through a Model Catalog. The app holds Portkey’s key. The provider key lives behind their catalog.
CostSlice does not replace your OpenAI API key. Authorization is forwarded. We never store it. There is no virtual key. Point base_url at https://api.costslice.com/v1 and send x-cs-key.
If you need a catalog of models and virtual keys, Portkey is that job. If you need OpenAI cost per customer and you will keep the OpenAI API key, CostSlice is that job.
Not an AI gateway. vs LiteLLM. Demo: sample P&L.
Worked example: the sample workspace still uses your OpenAI API key. acme-health shows $4,812 against a $2,400 plan. No virtual key was issued to get that row.
Starter is free. No credit card. Operator: Media Yard LLC, PO Box 73, Pennsauken, NJ 08110. hello@costslice.com
Questions
- Does Portkey use virtual keys?
- Yes. Portkey’s Model Catalog and virtual keys sit in front of providers. CostSlice does not issue a virtual key.
- Where does the OpenAI API key live with CostSlice?
- In your product’s environment variables. We forward Authorization. We never store the OpenAI API key.
- Is CostSlice a gateway?
- No. OpenAI only. No routing, cache, or other providers.