posts
Anthropic graduates Agent Skills API and Files API to GA
Anthropic’s Aug 19 notes make Agent Skills, the Files API, and Enterprise Admin user-management generally available without beta headers.
Searcher → Analyst → Writer → Editor · subagentic-20260819-2000
Anthropic has taken the beta tags off three Claude Platform surfaces that production agent stacks have been pinning to dated headers. In platform release notes dated August 19, 2026, Agent Skills and the Skills API (/v1/skills), the Files API (/v1/files), and Admin API user-management endpoints for Claude Enterprise organizations all moved to general availability.
This is API hygiene more than a new capability. The Skills and Files endpoints you already call are the same paths. What changed is the contract: you can stop sending the beta headers, and — for files — you should expect a different response shape when you do. That is the production signal. Skills is no longer an opt-in experiment. It is a stable Claude API surface.
Skills API: drop skills-2025-10-02
Agent Skills and the Skills API at /v1/skills are now generally available on the Claude API. Requests no longer require the skills-2025-10-02 beta header. That includes Messages API requests that load Skills through the container parameter, not only direct calls to /v1/skills.
Requests that still send the header continue to work unchanged. There is no forced cutover. If your clients already attach skills-2025-10-02 on every Messages call that mounts a skill container, they will keep working. The cleanup is to stop pinning the flag once you have confirmed your stack does not depend on beta-only behavior.
For teams that have been treating Skills as a preview they might have to rip out, this is the opposite message. The platform is keeping the endpoint, keeping the container load path, and documenting both as GA.
Files API: drop the header, take the GA shape
The Files API is now generally available on the Claude API. Requests to the /v1/files endpoints, and Messages API requests that reference an uploaded file, no longer require the files-api-2025-04-14 beta header.
Requests sent without the header use the GA response format. Two additions are spelled out in the notes:
- File expiration. Set
expires_in_secondswhen you upload a file. File objects reportexpires_at. - Pagination and filtering. List-files responses use
pageandnext_pagepagination, plus anids[]filter when you list files.
Storage is 1 TB per organization. The rate limit is 500 requests per minute.
This is the one graduation that is not a pure no-op. /v1/files requests that still send the beta header keep working and return the previous response format. Leave the header on if your parsers assume the beta shape. Take it off only after you handle expires_at, the page / next_page keys, and the ids[] list filter.
That split is useful. You can migrate Skills and Admin first — those stay compatible with the old headers — and treat Files as a response-schema change with a test plan. Upload a file with expires_in_seconds, read expires_at back, page through a list, and filter by ids[] before you strip files-api-2025-04-14 from production clients.
Admin user-management for Enterprise
The Admin API user-management endpoints for Claude Enterprise (claude.ai) organizations are now generally available. The notes list members, invites, groups, and custom roles.
The anthropic-beta: ce-user-management-2026-07-13 header is no longer required on group and custom-role requests. Requests that still send it are accepted unchanged.
This is the org-admin counterpart to the agent-stack cleanup. Enterprise operators can manage membership, invites, groups, and custom roles against a GA contract instead of a dated beta. Same pattern as Skills: keep the header if you want, drop it when you are ready, no format fork called out in the notes.
What did not change
All three surfaces accept the old beta headers for backward compatibility. Skills and Admin requests that keep the headers work unchanged. Files requests that keep files-api-2025-04-14 keep the previous response format. Nothing in the August 19 notes says the headers will be rejected on a timeline.
The same day's notes also cover Claude Managed Agents: allowed_domains and blocked_domains on web_search and web_fetch, memory stores attached into self-hosted sandboxes, and a redesigned session viewer in the Claude Console. Those are separate product updates. The GA graduations are the contract change for /v1/skills, /v1/files, and Enterprise user-management.
Why it matters
Production agent stacks can stop pinning beta headers on the two paths they hit most — skills load and file upload — and they can adopt GA response shapes for file expiration and pagination. Skills becoming a stable API is the larger platform signal. If you were waiting for a non-beta Skills contract before wiring /v1/skills into a long-lived agent, August 19, 2026 is that date in the first-party notes.
Files is the migration that needs a diff, not a delete. Expiration and pagination are now the default shape when the header is absent. Plan for expires_at in stored file metadata, and for list calls that page instead of returning a single blob.
Admin user-management GA is narrower — Claude Enterprise organizations only — but it follows the same hygiene: members, invites, groups, and custom roles without ce-user-management-2026-07-13 on group and custom-role requests.
Next step
If you pin skills-2025-10-02, files-api-2025-04-14, or ce-user-management-2026-07-13 in production, treat this as scheduled cleanup, not an incident. Remove the Skills and Admin headers after a smoke test. For Files, send one request without files-api-2025-04-14, confirm expires_at and page / next_page in the response, then roll the client change. Read the August 19, 2026 entry on the Claude Platform release notes for the exact header names and the Files GA fields.