api-20260820T170710Z / page 10 of 10 / documentation capture

cli-sdks-libraries/cli/using Changed · +2 / -2 lines

from line 16

1616

1717Run `ant --help` for the full resource list, or append `--help` to any subcommand for its flags.

1818

19Resources in beta (including agents, sessions, deployments, environments, and skills) live under the `beta:` prefix. Commands in this namespace automatically send the appropriate `anthropic-beta` header for that resource, so you don't need to pass it yourself. Use `--beta <header>` only to override the default (for example, to opt into a different schema version).

19Resources in beta (including agents, sessions, deployments, and environments) live under the `beta:` prefix. Commands in this namespace automatically send the appropriate `anthropic-beta` header for that resource, so you don't need to pass it yourself. Use `--beta <header>` only to override the default (for example, to opt into a different schema version).

2020

2121```bash

2222ant models list

from line 152

152152Flags that take a file path, such as `--file` on the upload command, accept a bare path:

153153

154154```bash

155ant beta:files upload --file ./report.pdf

155ant files upload --file ./report.pdf

156156```

157157

158158To inline a file's contents into a string-valued field, prefix the path with `@`:

get-started Changed · +2 / -2 lines

from line 436

436436 }

437437

438438 dependencies {

439 implementation("com.anthropic:anthropic-java:2.53.0")

439 implementation("com.anthropic:anthropic-java:2.57.0")

440440 }

441441

442442 application {

from line 462

462462 <dependency>

463463 <groupId>com.anthropic</groupId>

464464 <artifactId>anthropic-java</artifactId>

465 <version>2.53.0</version>

465 <version>2.57.0</version>

466466 </dependency>

467467 </dependencies>

468468 </project>

manage-claude/api-and-data-retention Changed · +2 / -2 lines

from line 199

201201| [Tool search](https://platform.claude.com/docs/en/agents-and-tools/tool-use/tool-search-tool) | `/v1/messages` (with `tool_search` tool) | <Eligible>Yes</Eligible> | <Eligible status="no">No</Eligible> | Server-side tool executed by Anthropic; the tool definitions in the request are searched in memory per call and nothing is stored after the response. |

202| [Web fetch](https://platform.claude.com/docs/en/agents-and-tools/tool-use/web-fetch-tool) | `/v1/messages` (with `web_fetch` tool) | <Eligible>Yes</Eligible> | <Eligible status="no">No</Eligible> | Fetched web content returned in the API response. [Dynamic filtering](https://platform.claude.com/docs/en/agents-and-tools/tool-use/web-search-tool#dynamic-filtering) is not eligible for ZDR or HIPAA. Website publishers may retain request data (such as fetched URLs and request metadata) according to their own policies. |

202| [Web fetch](https://platform.claude.com/docs/en/agents-and-tools/tool-use/web-fetch-tool) | `/v1/messages` (with `web_fetch` tool) | <Eligible>Yes</Eligible> | <Eligible status="no">No</Eligible> | Fetched web content returned in the API response. [Dynamic filtering](https://platform.claude.com/docs/en/agents-and-tools/tool-use/web-fetch-tool#dynamic-filtering) is not eligible for ZDR or HIPAA. Website publishers may retain request data (such as fetched URLs and request metadata) according to their own policies. |

203203| [Web search](https://platform.claude.com/docs/en/agents-and-tools/tool-use/web-search-tool) | `/v1/messages` (with `web_search` tool) | <Eligible>Yes</Eligible> | <Eligible>Yes</Eligible> | Real-time web search results returned in the API response. [Dynamic filtering](https://platform.claude.com/docs/en/agents-and-tools/tool-use/web-search-tool#dynamic-filtering) is not eligible for ZDR or HIPAA. |

204204

205205## Retention regardless of arrangement

from line 281

281281* [Structured outputs](https://platform.claude.com/docs/en/build-with-claude/structured-outputs)

282282* [Prompt caching](https://platform.claude.com/docs/en/build-with-claude/prompt-caching)

283283* [Batch processing](https://platform.claude.com/docs/en/build-with-claude/batch-processing)

284* [Files API reference](https://platform.claude.com/docs/en/api/beta/files/upload)

284* [Files API reference](https://platform.claude.com/docs/en/api/files/upload)

285285* [Trust Center](https://trust.anthropic.com/resources)

286286

managed-agents/memory Changed · +2 / -2 lines

from line 13

1313<Note>

1414 Don't combine `agent-memory-2026-07-22` with `managed-agents-2026-04-01` on a memory store request: sending both returns a `400` error. If your code sets beta headers explicitly, replace `managed-agents-2026-04-01` with `agent-memory-2026-07-22` on memory store calls rather than adding a second value. Session endpoints, including attaching a memory store to a session, still use `managed-agents-2026-04-01`.

1515

16 On July 22, 2026, the `managed-agents-2026-04-01` header adopts the same list behavior on `GET /v1/memory_stores/{memory_store_id}/memories`; sending `agent-memory-2026-07-22` opts you into that behavior now. Page cursors from requests made without the header aren't valid with it, so restart from the first page.

16 `GET /v1/memory_stores/{memory_store_id}/memories` behaves the same under either header: results come back in a stable, server-defined order, and `path_prefix` and `depth` apply the same way.

1717</Note>

1818

1919## Overview

from line 377

377377

378378### How the agent accesses memory

379379

380Each attached store is mounted inside the session's sandbox as a directory under `/mnt/memory/`. The directory name is the store's display name sanitized to a filesystem-safe slug (lowercased; non-alphanumeric runs become a single hyphen), so a store named "Demo Memory" mounts at `/mnt/memory/demo-memory/`. The exact path is returned in the `mount_path` field on the session's memory-store resource; read it from there rather than constructing it yourself. The agent reads and writes the store with the standard [agent toolset](https://platform.claude.com/docs/en/managed-agents/tools). Writes under the mount path are persisted back to the store and stay in sync across sessions that share it; writes to any other path under `/mnt/memory/` land in container-local scratch and are lost when the session ends. A short description of each mount (display name, mount path, access mode, store `description`, and any `instructions`) is automatically added to the system prompt.

380Each attached store is mounted inside the session's sandbox as a directory under `/mnt/memory/`. The directory name is the store's display name sanitized to a filesystem-safe slug (lowercased; non-alphanumeric runs become a single hyphen), so a store named "Demo Memory" mounts at `/mnt/memory/demo-memory/`. The exact path is returned in the `mount_path` field on the session's memory-store resource; read it from there rather than constructing it yourself. The agent reads and writes the store with the standard [agent toolset](https://platform.claude.com/docs/en/managed-agents/tools). Writes under the mount path are persisted back to the store and stay in sync across sessions that share it; writes to any other path under `/mnt/memory/` fail, because the sandbox mounts that parent directory read-only. A short description of each mount (display name, mount path, access mode, store `description`, and any `instructions`) is automatically added to the system prompt.

381381

382382`access` is enforced at the filesystem level: a `read_only` mount rejects writes, while writes to a `read_write` mount produce [memory versions](https://platform.claude.com/docs/en/managed-agents/memory#audit-memory-changes) attributed to the session.

383383

One read of Claude Developer Platformapi-20260820T170710Z

What this read moved

cli-sdks-libraries/cli/using Changed · +2 / -2 lines

get-started Changed · +2 / -2 lines

manage-claude/api-and-data-retention Changed · +2 / -2 lines

managed-agents/memory Changed · +2 / -2 lines