# Machine to machine token pricing (follow-up)

**URL:** <https://community.auth0.com/t/machine-to-machine-token-pricing-follow-up/38353>\
**Category:** Get Help\
**Tags:** pricing\
**Created:** [February 24, 2020, 3:04am UTC](https://community.auth0.com/t/machine-to-machine-token-pricing-follow-up/38353 "2020-02-24T03:04:14Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jmangelo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jmangelo/32/7923_2.png) [@jmangelo](https://community.auth0.com/u/jmangelo)\
**Post date:** [February 24, 2020, 3:11pm UTC](https://community.auth0.com/t/machine-to-machine-token-pricing-follow-up/38353/2 "2020-02-24T15:11:56Z")

</div>

There may have been some confusion in the previous reply as one of the screenshots referred to user quota, but for client credentials (which is the flow where machine to machine quota would apply) **there’s no refresh token currently issued** so the second question does not apply.

In relation to your first question, the shorter the lifetime, technically the more frequently you would have to obtain a new machine to machine token (so costs would indeed be higher) because it would be expected that more tokens would need to be issued.

Also have in mind that although machine to machine is strictly related to client credentials (not all client credentials flows count for that quota as mentioned at this other [reply](http://community.auth0.com/t/does-oauth-token-api-calls-count-toward-machine-to-machien-tokens/36642/2). Spoiler: an access token issued with client credentials for the Auth0 Management API won’t count for example.

---

_[View the full topic](https://community.auth0.com/t/machine-to-machine-token-pricing-follow-up/38353)._
