Live data from Hacker News

Anthropic officially bans using subscription auth for third party use

code.claude.com

21–30 of 827 posts

Re: Anthropic officially bans using subscription auth for third party use

#21
post #6

And I just bought my mac mini this morning... Sorry everyone

You know that if you are just using a cloud service and not running local models, you could have just bought a raspberry pi.

Harder to get at the Apple ecosystem. I have an old Macbook that just serves my reminders over the internet.

Re: Anthropic officially bans using subscription auth for third party use

#22
post #3

Is this a direct shot at things like OpenClaw, or am I reading it wrong?

Opencode as well. Folks have been getting banned for abusing the OAuth login method to get around paying for API tokens or whatever. Anthropic seems to prefer people pay them.

its not that innocent.

a 200 dollar a month customer isn't trying to get around paying for tokens, theyre trying to use the tooling they prefer. opencode is better in a lot of ways.

tokens get counted and put against usage limits anyway, unless theyre trying to eat analytics that are CC exclusive they should allow paying customers to consume to the usage limits in however way they want to use the models.

Re: Anthropic officially bans using subscription auth for third party use

#23

I really hope someone from any of those companies (if possible all of them) would publish a very clear statement regarding the following question: If I build a commercial app that allows my users to connect using their OAuth token coming from their ChatGPT/Claude etc. account, do they allow me (and their users) to do this or not? I totally understand that I should not reuse my own account to provide services to other…

I don't see how they can get more clear about this, considering they have repeatedly answered it the exact same way.

Subscriptions are for first-party products (claude.com, mobile and desktop apps, Claude Code, editor extensions, Cowork).

Everything else must use API billing.

Re: Anthropic officially bans using subscription auth for third party use

#26

In enterprise software, this is an embedded/OEM use case. And historically, embedded/OEM use cases always have different pricing models for a variety of reasons why. How is this any different than this long established practice?

It's not, but do you really think the people having Claude build wrappers around Claude were ever aware of how services like this are typically offered.

Re: Anthropic officially bans using subscription auth for third party use

#27
post #2

From the legal docs: > Authentication and credential use > Claude Code authenticates with Anthropic’s servers using OAuth tokens or API keys. These authentication methods serve different purposes: > OAuth authentication (used with Free, Pro, and Max plans) is intended exclusively for Claude Code and Claude.ai. Using OAuth tokens obtained through Claude Free, Pro, or Max accounts in any other product, tool, or service…

why wouldn't they just make it so the SDK can't use claude subs? like what are they doing here?

Re: Anthropic officially bans using subscription auth for third party use

#28
post #23

I really hope someone from any of those companies (if possible all of them) would publish a very clear statement regarding the following question: If I build a commercial app that allows my users to connect using their OAuth token coming from their ChatGPT/Claude etc. account, do they allow me (and their users) to do this or not? I totally understand that I should not reuse my own account to provide services to other…

I don't see how they can get more clear about this, considering they have repeatedly answered it the exact same way. Subscriptions are for first-party products (claude.com, mobile and desktop apps, Claude Code, editor extensions, Cowork). Everything else must use API billing.

The biggest reason why this is confusing is the Claude Agent SDK[0] will use subscription/oauth credentials if present. The terms update implies that there's some use cases where that's ok and other use cases (commercial?) where using their SDK on a user's device violates terms.

[0] https://platform.claude.com/docs/en/agent-sdk/overview

Re: Anthropic officially bans using subscription auth for third party use

#29
post #23

I really hope someone from any of those companies (if possible all of them) would publish a very clear statement regarding the following question: If I build a commercial app that allows my users to connect using their OAuth token coming from their ChatGPT/Claude etc. account, do they allow me (and their users) to do this or not? I totally understand that I should not reuse my own account to provide services to other…

I don't see how they can get more clear about this, considering they have repeatedly answered it the exact same way. Subscriptions are for first-party products (claude.com, mobile and desktop apps, Claude Code, editor extensions, Cowork). Everything else must use API billing.

What if you wrap the service using their Agent SDK?

Re: Anthropic officially bans using subscription auth for third party use

#30

I really hope someone from any of those companies (if possible all of them) would publish a very clear statement regarding the following question: If I build a commercial app that allows my users to connect using their OAuth token coming from their ChatGPT/Claude etc. account, do they allow me (and their users) to do this or not? I totally understand that I should not reuse my own account to provide services to other…

It is pretty obviously no. API keys billed by the token, yes, Oauth to the flat rate plans no. > OAuth authentication (used with Free, Pro, and Max plans) is intended exclusively for Claude Code and Claude.ai. Using OAuth tokens obtained through Claude Free, Pro, or Max accounts in any other product, tool, or service — including the Agent SDK — is not permitted and constitutes a violation of the Consumer Terms of Ser…

If you look at this tweet [1] and in particular responses under it, it still seems to me like some parts of it need additional clarification. For instance, I have seen some people interpret the tweet as meaning using the OAuth token is actually ok for personal experimentation with the Agent SDK, which can be seen as a slight contradiction with what you quoted. A parent tweet also mentioned the docs clean up causing some confusion.

None of this is legal advice, I'm just trying to understand what exactly is allowed or not.

[1] https://x.com/trq212/status/2024212380142752025?s=10

Post reply on HN