Cache Responses to Cut Costs
Every request costs tokens, and tokens add up faster than most people expect. This post shows exactly where your credits go.
How to save 🛠️
The tactics below are easy to implement today and typically cut API spending by a meaningful margin.
Quick reference
| Item | Details | Tip |
|---|---|---|
| Setup | Two-minute setup from the panel | Do this first |
| Usage | Token-based billing | Watch the logs |
| Support | Email + forum | We reply fast |
Common questions
Here are the questions people ask most often about this topic.
Frequently asked questions ❓
How long does cache to save take?
It depends on your setup, but most people finish in well under ten minutes with the steps above.
Do I need any special tools?
No. Anything that can make an HTTPS call works: curl, Python, Node.js or your favorite HTTP client.
Does this cost extra credits?
No more than a normal request. The techniques here are designed to keep your spend predictable.
Where can I get more help?
Check the forum or email support and we will point you in the right direction.
Works well with the Python SDK too.
Worked perfectly on my first try.
Thanks for the kind words!
Good overview for beginners.
Just what I was looking for.