← Blog

What Is Claude Bot Called Now? Naming Explained

2026-09-11 · 5 min read · SubToAPI Team

If you're searching "what is Claude bot called now," you probably used or heard about an AI assistant called "Claude bot" at some point and want to know its current name. The short answer: there has never been an official Anthropic product called "Claude Bot." The assistant is, and has always been, called Claude. What's changed is the model naming underneath it, the products it ships in, and — separately — a web crawler that shares a similar name but does something completely different.

This confusion is understandable because "Claude bot," "Claude AI," "Claude chatbot," and "ClaudeBot" get used interchangeably in casual conversation even though they refer to different things. This article sorts out exactly what's what as of today.

The assistant is called Claude

Anthropic's AI assistant is officially named Claude, not "Claude Bot" or "ClaudeGPT" or anything similar. It ships across several surfaces:

None of these are called "bot" anywhere in Anthropic's naming. If you saw "Claude bot" somewhere, it was almost certainly a nickname someone used informally, a third-party integration (a Discord bot, Slack bot, or browser extension built on top of the Claude API), or a mix-up with the crawler below.

Claude the model vs. Claude the crawler

There's a genuinely separate thing that does carry the word "bot" in its name: ClaudeBot, Anthropic's web crawler that indexes public content to help train models. It identifies itself in server logs via its user-agent string and is unrelated to the chat assistant you talk to. If your search intent is actually about the crawler that's showing up in your site's access logs, that's a different topic — the assistant Claude and the crawler ClaudeBot are two distinct systems built by the same company.

For the rest of this article, we're focused on the assistant — the thing people mean when they say "I use Claude bot to write emails" or "is Claude bot down."

Claude's current model names

What actually changes over time, and causes most of the naming confusion, is the underlying model lineup. Anthropic ships versioned model families rather than renaming the product itself:

Each family gets numbered generations (e.g., a "4" series), and models are referenced by API identifiers like claude-opus-4 or claude-sonnet-4 style strings, which change as new versions ship. So when people ask "what's Claude called now," they're often really asking "which model version am I on," not asking about a rebrand of the product itself. The assistant's name — Claude — hasn't changed since launch.

If you actually want to build with Claude

If your real goal isn't naming trivia but access — you want to call Claude from your own app, script, or internal tool — there are two common paths:

Direct API access. Sign up for an Anthropic API account, generate a key, and pay per token based on usage. This is the standard route if you're comfortable managing billing separately from any Claude subscription you already pay for personally or as a team.

Turning an existing subscription into an API. If you or your team already pay for Claude access and don't want a second, usage-metered bill, SubToAPI wraps that access behind a standard HTTPS API. You get an application key (sub_live_...), a dashboard, and the same request shapes developers expect:

curl https://api.subtoapi.app/v1/messages \
  -H "Authorization: Bearer $SUBTOAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "claude-sonnet-4",
    "max_tokens": 512,
    "messages": [
      {"role": "user", "content": "Summarize this changelog in 3 bullets."}
    ]
  }'

It supports streaming responses, tool use, and usage metadata per key, with plans starting at €9/month for solo developers and per-seat pricing for teams (€19) and larger orgs (€49). There's a free trial at signup if you want to test it against your own use case first. See the pricing page or jump straight to the quickstart for a full walkthrough.

Streaming example

const res = await fetch("https://api.subtoapi.app/v1/messages", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.SUBTOAPI_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    model: "claude-sonnet-4",
    max_tokens: 1024,
    stream: true,
    messages: [{ role: "user", content: "Draft a release note for v2.3." }]
  })
});

More detail on streaming behavior and event formats is in the streaming docs, and if you need function calling or structured tool outputs, check the tools docs. General request/response shapes are covered in the messages docs.

The bottom line

"Claude bot" was never an official name — the product is Claude, the crawler is ClaudeBot, and the models underneath both get versioned separately (Opus, Sonnet, Haiku). If you landed here trying to figure out what to actually call it in documentation, code comments, or a support ticket, "Claude" is correct. If you landed here trying to access Claude programmatically, start with the quickstart or sign up to get a key.

Questions

Is "Claude bot" the same as ChatGPT's bot naming convention? No. OpenAI's assistant is called ChatGPT and its API models are named GPT-4, GPT-4o, etc. Anthropic's assistant is Claude, with model families named Opus, Sonnet, and Haiku. Neither company uses "bot" as part of the official product name.

Why do people call it "Claude bot" if that's not the real name? It's a natural naming pattern — people say "ChatGPT bot," "Claude bot," or "Gemini bot" the same way they'd say "the Slack bot," using "bot" generically for any conversational AI, even when the product's real name doesn't include it.

Does ClaudeBot the web crawler affect my website? It can add to your server load and appears in access logs by its user-agent. Site owners who want to block or allow it typically manage that through robots.txt, separate from any decision about using the Claude assistant or API.

Turn your Claude access into an HTTPS API

SubToAPI gives you application API keys, streaming, tool use and usage insights on top of your existing Claude access — set up in minutes.

Start free  Read the quickstart →