The gateway market has a trust problem before it has a pricing problem. Developers already know that low price can hide model substitution, pooled credentials, data ambiguity, or unstable supply. So the first question is not ‘how cheap is it?’ It is ‘what exactly happens to my request?’
What transfers trust
A trustworthy gateway pins the requested model, returns an error when identity is unclear, records request-level Activity, and explains the data path. Those are checks a builder can verify.
- Requested model equals served model, or the call fails.
- Activity shows the charge, model, and usage.
- Operator identity and retention policy are visible.
A practical standard for any gateway
Exact model handling and visible accounting let you treat a gateway as infrastructure rather than a gamble. Verify the model, inspect Activity, then decide whether the next request belongs there.
Why it matters
If you are comparing gateways, use these checks to turn a model logo into evidence you can actually inspect.