Explanation of the cache control function price of the anthropic api

What are you trying to achieve?

Hello team,
Sorry for the inconvenience, I’m a new player in the make court.

There is a point that I don’t really understand regarding the cache control of anthropic.

This cache control is made to store certain imposing contents.
This functionality costs a lot more tokens, because we are supposed to gain from the exchange with the other api calls requesting access to the cache, ok.
On the other hand, during the following api calls, if we have to mention the cache to use it, we have to put back all the content that we have already cached?
And in this case, given the many api calls to access the cache and the imposing content of the latter, it costs us a lot more, right?

example:
api call to cache, and then 15 api calls to access this cache and generate a response

Thanks for your feedback

Hello @Charl75,
welcome to the Make community!

Could you please give more details about the issue you get? It seems to be related to the way their API works. Do you want to understand how Anthropic handles its cache, or do you want to understand how we could leverage it in Make?

Kind regards,

Benjamin