Gandr for agencies and integrators.
1 unit
a stream, the voice cost you can quote without a forecast
Every client fleet gets its own key, its own cloned voices and its own usage read at GET /v1/usage, on one integration you write once. Then a cost you can put in a proposal and still honour in month nine.
Why agencies quote streams
- Fixed cost per client stream, margin is arithmetic, not hope.
- Per-key usage via GET /v1/usage keeps every client fleet separately auditable.
- A client’s campaign spike is served by their stream count, not billed as an overage you have to explain.
A client book, priced
Meter cells are minutes × 1,000 characters × the published $30, $100 range; the Gandr column is streams × $150. Put either column in the client proposal, only one of them survives contact with a good campaign.
table 01
Three client engagements, one month
| Engagement | Minutes / mo | On a $30, $100 meter | On Gandr streams |
|---|---|---|---|
| Reception desk, 1 stream | 4,000 | $120, $400 | $150 |
| Support desk, 2 streams | 8,000 | $240, $800 | $300 |
| Localisation catalogue, 5 streams | 20,000 | $600, $2,000 | $750 |
Operational posture
Redundant serving behind one endpoint, and a committed stream that doubles as the second vendor clients want on the org chart. Every claim links to a published sheet you can hand to a client’s procurement.
A key and one stream to size it on, before anyone talks about a fleet.
Get a key for your stack