Maybe you have a thousand product descriptions to rewrite, a backlog of support emails to summarize, or a team that keeps pasting the same instructions into a chat window every morning. Doing that one conversation at a time does not scale, and handing everyone their own login quickly turns into a mess of who can see what. Anthropic makes its Claude models available through an API, a way for software to talk directly to other software, so your own applications, or an AI assistant acting for you, can send that work to Claude, organize who on your team has access, and run agents on a schedule.
What Anthropic does
Anthropic describes itself as an AI safety company, and it builds the Claude family of large language models. A large language model is software trained on a great deal of text that can read, write, summarize and reason in plain language. Anthropic offers those models through a single API, alongside tools for processing work in batches, uploading files, managing agents and administering an organization’s workspaces and members. Anthropic also authors the Model Context Protocol, a standard way of connecting AI agents to other services. More on the Anthropic website.
What you can get done
The capabilities below are the ones our catalog maps for Anthropic, chosen for the jobs a business is most likely to hand off.
Get answers and drafts from Claude
This is the heart of it. You send Claude a prompt, and it sends back a reply. The bigger win for a business is the batch: instead of sending a thousand requests one at a time and waiting on each, you submit them together, let them process in the background, and collect the results when they are done.
POST /v1/messagessends a prompt to Claude and gets its next message back.POST /v1/messages/batchessubmits a batch of message requests to run asynchronously.GET /v1/messages/batches/{message_batch_id}checks whether a batch has finished processing.POST /v1/messages/batches/{message_batch_id}/cancelstops a batch before it finishes.GET /v1/messages/batcheslists the batches submitted in a workspace.
Choose the right model and the right prompt
Claude comes in several models, from faster and lighter to larger and more capable. Your software can ask which ones your account can use, rather than someone keeping a list by hand. There is also an experimental tool that writes a starting prompt for you when you describe the task.
GET /v1/modelslists the Claude models available to your API key.GET /v1/models/{model_id}looks up a model, or resolves a short alias to the exact model it points to.POST /v1/experimental/generate_promptgenerates a prompt from a description of the task.
Set up and run agents
An agent is an AI setup that can take steps on its own, using tools you give it. These operations let you define an agent once, keep track of its versions as you change it, and deploy it to run on a schedule, pausing or retiring it when you no longer need it. They are currently marked beta.
POST /v1/agents?beta=truecreates an agent.POST /v1/agents/{agent_id}?beta=trueupdates an agent’s configuration.GET /v1/agents/{agent_id}/versions?beta=truepages through an agent’s earlier versions.POST /v1/deployments/{deployment_id}/pause?beta=truepauses a scheduled deployment.POST /v1/deployments/{deployment_id}/archive?beta=truearchives a deployment you no longer need.
Organize your team into workspaces
A workspace is a separate area inside your organization’s account, useful for keeping one department’s or one client’s work apart from another’s. Creating and tidying them from software means a new project can get its own space the moment it starts.
GET /organizations/workspaceslists the workspaces in your organization.POST /organizations/workspacescreates a workspace.POST /organizations/workspaces/{workspace_id}renames a workspace.POST /organizations/workspaces/{workspace_id}/archivearchives a workspace and makes it read-only.
Control who has access to each workspace
People join, change roles and leave. Managing workspace membership through the API means your existing onboarding and offboarding steps can include Claude access, instead of someone remembering to do it later.
GET /organizations/workspaces/{workspace_id}/memberslists who has access to a workspace.POST /organizations/workspaces/{workspace_id}/membersadds a teammate to a workspace.POST /organizations/workspaces/{workspace_id}/members/{user_id}changes a member’s role.DELETE /organizations/workspaces/{workspace_id}/members/{user_id}removes someone’s access to a workspace.
Workflows that put it together
A workflow is a recipe of several calls made in order to finish a real job. APIs.io catalogs 11 for Anthropic, including these:
- Create Batch, Poll, and Retrieve Results submits a batch, waits until processing ends, then fetches the results.
- Count Tokens Then Create Message estimates how large a prompt is, and only sends it when it fits a budget.
- Discover a Model and Send a Message lists the available models, confirms the one you chose exists, then sends a message with it.
- Create Workspace and Add a Member creates a workspace, adds a user, and confirms they appear on the roster.
- Onboard an Org Member into a Workspace finds a member by email, creates a workspace, and adds them to it.
- Cancel a Message Batch and Confirm requests cancellation of a batch and checks until it has stopped.
Ask for it in plain language
Our conversational overlays for Anthropic map everyday questions to the operation that answers them, so an AI assistant knows which call answers which question. These are the kinds of things you can ask:
- “How do I run many Claude prompts at once asynchronously?”
- “Is my message batch done processing yet?”
- “Which Claude models can I use with my API key right now?”
- “How do I give a teammate access to a workspace?”
- “How do I temporarily stop a deployment from running on its schedule?”
- “Can Claude write a good prompt for me if I just describe the task?”
You can browse one in the Anthropic Agents API phrasing overlay.
Getting started
Anthropic’s API is paid, and it is a hosted service, so you call their endpoint rather than running anything yourself. Your developer will want the documentation for sending messages, streaming replies and listing models. On APIs.io, see the Anthropic profile, the Messages API, the Models API and the Files API. Pick the one repetitive writing or reading task your team does most often, because that is your first batch.
