access-transparency-log changedmanage-claude/access-transparency-log
Nearest release: v2.1.308, published 2 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+5added
Lines−5removed
From line
148
where the diff opens
First seen
28 Sep 2026
this site's first read of the page
Recorded edits4to this page, all time
The whole hunk
from line 148, old and new numbered
/
from line 148
148148 -H "anthropic-version: 2023-06-01"
149149```
150150
151```json
151```text
152152{
153153 "type": "transparency_log_keys",
154154 "origin": "axt.anthropic.com/25f6429a-3293-49bf-afed-cb312911554b",
from line 193
193193
194194A planned rotation is announced on this page at least 30 days before the new key signs its first checkpoint. During that notice period the new key is listed in `log_keys` and in this table with its switch date. Retired keys stay listed with their service dates. A key that does not appear in this table is not legitimate, whatever `GET /keys` returns. Treat a checkpoint that verifies under no listed key as a verification failure, and report it to your Anthropic account representative or [Anthropic support](https://support.claude.com).
195195
196[`axt-verify`](https://platform.claude.com/docs/en/manage-claude/access-transparency-log#verify-with-axt-verify) carries the current key in each release and never reads a key from the API. Each release carries exactly one key. On the switch date, Anthropic starts signing with the new key and publishes the `axt-verify` release that carries it. On the same date Anthropic re-issues every organization's latest checkpoint under the new key, even for a log that has not grown. Upgrade on the switch date. Running the old release after the switch fails with exit status `1`, and so does running the new release before it. Either failure clears once you run the matching release. A verifier you maintain yourself needs the new fingerprint, with its switch date, added before that date.
196`axt-verify` carries the current key in each release and never reads a key from the API (see [Verify with axt-verify](https://platform.claude.com/docs/en/manage-claude/access-transparency-log#verify-with-axt-verify)). Each release carries exactly one key. On the switch date, Anthropic starts signing with the new key and publishes the `axt-verify` release that carries it. On the same date Anthropic re-issues every organization's latest checkpoint under the new key, even for a log that has not grown. Upgrade on the switch date. Running the old release after the switch fails with exit status `1`, and so does running the new release before it. Either failure clears once you run the matching release. A verifier you maintain yourself needs the new fingerprint, with its switch date, added before that date.
197197
198198### Fetch an inclusion proof
199199
from line 212
212212 -H "anthropic-version: 2023-06-01"
213213```
214214
215```json
215```text
216216{
217217 "type": "transparency_log_inclusion_proof",
218218 "leaf_index": 41,
from line 258
258258 -H "anthropic-version: 2023-06-01"
259259```
260260
261```json
261```text
262262{
263263 "type": "transparency_log_consistency_proof",
264264 "hashes": [
from line 337
337337
338338For example, this access event as the Activity Feed serves it:
339339
340```json
340```text wrap
341341{
342342 "id": "activity_01GPXmAhizavrUuoXNn3tzeA",
343343 "type": "anthropic_access",
No line in this hunk matches that.