Anthropic revoked OpenAI\u2019s API access to its models on Tuesday, multiple sources familiar with the matter tell WIRED. OpenAI was informed that its access was cut off due to violating the terms of service.<\/p>\n
\u201cClaude Code has become the go-to choice for coders everywhere, and so it was no surprise to learn OpenAI’s own technical staff were also using our coding tools ahead of the launch of GPT-5,\u201d Anthropic spokesperson Christopher Nulty said in a statement to WIRED. \u201cUnfortunately, this is a direct violation of our terms of service.\u201d<\/p>\n
According to Anthropic\u2019s commercial terms of service<\/a>, customers are barred from using the service to \u201cbuild a competing product or service, including to train competing AI models\u201d or \u201creverse engineer or duplicate\u201d the services. This change in OpenAI\u2019s access to Claude comes as the ChatGPT-maker is reportedly<\/a> preparing to release a new AI model, GPT-5, which is rumored<\/a> to be better at coding.<\/p>\n OpenAI was plugging Claude into its own internal tools using special developer access (APIs), instead of using the regular chat interface, according to sources. This allowed the company to run tests to evaluate Claude\u2019s capabilities in things like coding and creative writing against its own AI models, and check how Claude responded to safety-related prompts involving categories like CSAM, self-harm, and defamation, the sources say. The results help OpenAI compare its own models\u2019 behavior under similar conditions and make adjustments as needed.<\/p>\n \u201cIt\u2019s industry standard to evaluate other AI systems to benchmark progress and improve safety. While we respect Anthropic\u2019s decision to cut off our API access, it\u2019s disappointing considering our API remains available to them,\u201d OpenAI\u2019s chief communications officer Hannah Wong said in a statement to WIRED.<\/p>\n Nulty says that Anthropic will \u201ccontinue to ensure OpenAI has API access for the purposes of benchmarking and safety evaluations as is standard practice across the industry.\u201d The company did not respond to WIRED\u2019s request for clarification on if and how OpenAI’s current Claude API restriction would impact this work.<\/p>\n Top tech companies yanking API access from competitors has been a tactic in the tech industry for years. Facebook did the same to Twitter-owned Vine<\/a> (which led to allegations of anticompetitive behavior) and last month Salesforce restricted competitors<\/a> from accessing certain data through the Slack API. This isn\u2019t even a first for Anthropic. Last month, the company restricted the AI coding startup Windsurf\u2019s direct access to its models after it was rumored OpenAI was set to acquire it. (That deal fell through<\/a>).<\/p>\n Anthropic\u2019s chief science officer Jared Kaplan spoke to TechCrunch<\/a> at the time about revoking Windsurf\u2019s access to Claude, saying, \u201cI think it would be odd for us to be selling Claude to OpenAI.\u201d<\/p>\n A day before cutting off OpenAI\u2019s access to the Claude API, Anthropic announced<\/a> new rate limits on Claude Code, its AI-powered coding tool, citing explosive usage<\/a> and, in some cases, violations of its terms of service<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"Anthropic revoked OpenAI\u2019s API access to its models on Tuesday, multiple sources familiar with the matter tell WIRED.…\n","protected":false},"author":3,"featured_media":111983,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[21234,24142,70885,738,31067,305,158,67,132,68],"class_list":{"0":"post-111982","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-technology","8":"tag-algorithms","9":"tag-anthropic","10":"tag-api","11":"tag-artificial-intelligence","12":"tag-coding","13":"tag-openai","14":"tag-technology","15":"tag-united-states","16":"tag-unitedstates","17":"tag-us"},"share_on_mastodon":{"url":"","error":""},"_links":{"self":[{"href":"https:\/\/www.europesays.com\/us\/wp-json\/wp\/v2\/posts\/111982","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/us\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/us\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/us\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/us\/wp-json\/wp\/v2\/comments?post=111982"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/us\/wp-json\/wp\/v2\/posts\/111982\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/us\/wp-json\/wp\/v2\/media\/111983"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/us\/wp-json\/wp\/v2\/media?parent=111982"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/us\/wp-json\/wp\/v2\/categories?post=111982"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/us\/wp-json\/wp\/v2\/tags?post=111982"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}