# Need to update Claude API Key

**URL:** <https://community.pickaxe.co/t/need-to-update-claude-api-key/7847>\
**Category:** General\
**Created:** [December 28, 2025, 6:51am UTC](https://community.pickaxe.co/t/need-to-update-claude-api-key/7847 "2025-12-28T06:51:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![uapllc](https://avatars.discourse-cdn.com/v4/letter/u/59ef9b/32.png) [@uapllc](https://community.pickaxe.co/u/uapllc)\
**Post date:** [December 28, 2025, 6:51am UTC](https://community.pickaxe.co/t/need-to-update-claude-api-key/7847/1 "2025-12-28T06:51:34Z")

</div>

I have a client that wants to keep using their api key, will this still be an option with the new pricing plan?

---

<div class="post-metadata">

**Author:** ![abhi](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/abhi/32/5009_2.png) [@abhi](https://community.pickaxe.co/u/abhi)\
**Post date:** [December 28, 2025, 2:55pm UTC](https://community.pickaxe.co/t/need-to-update-claude-api-key/7847/2 "2025-12-28T14:55:07Z")

</div>

BYOK won’t be supported with the new pricing.

All tools will use Pickaxe’s in-house API keys, including the managed Claude API, so clients won’t need to bring or manage their own keys.

---

<div class="post-metadata">

**Author:** ![uapllc](https://avatars.discourse-cdn.com/v4/letter/u/59ef9b/32.png) [@uapllc](https://community.pickaxe.co/u/uapllc)\
**Post date:** [December 28, 2025, 3:31pm UTC](https://community.pickaxe.co/t/need-to-update-claude-api-key/7847/3 "2025-12-28T15:31:31Z")

</div>

Im aware of this but, I have specific a contractual agreement with a client to use their api keys. Is there anything that can be done?

---

<div class="post-metadata">

**Author:** ![abhi](https://yyz2.discourse-cdn.com/flex004/user_avatar/community.pickaxe.co/abhi/32/5009_2.png) [@abhi](https://community.pickaxe.co/u/abhi)\
**Post date:** [December 29, 2025, 5:36am UTC](https://community.pickaxe.co/t/need-to-update-claude-api-key/7847/4 "2025-12-29T05:36:11Z")

</div>

Oh! Got it, thanks for sharing the additional context…  
our first priority is to make sure your client is comfortable, even though we can’t support using their API key directly.

If you can share what’s driving the requirement (privacy, transparency, compliance, etc.), that helps a lot. In many cases, we can provide additional documentation or client-addressed details around how we handle models, usage, and data to meet those needs. Feel free to email us at [info@pickaxe.co](mailto:info@pickaxe.co) and we can review any custom requirements together.