{"version":"2.1.228","anchor":"memory-store-requests-moved-to-a-new-beta-header-value","canonical_anchor":"memory-store-requests-moved-to-a-new-beta-header-value","heading":"Memory store requests moved to a new beta header value","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/memory-store-requests-moved-to-a-new-beta-header-value","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Memory store requests moved to a new beta header value\n\nMemory store calls send a new beta header value, so update any proxy allowlists.\n\n**What**\n\nRequests to the memory store API now send the beta value `agent-memory-2026-07-22` instead of `managed-agents-2026-04-01`. If your proxy, gateway or deployment allow-lists the old value for memory traffic, it needs updating.\n\n**Details**\n\n- Covers create, retrieve, update, list and delete for both memories and memory stores.\n- The old value no longer appears on any memory store path; roughly 99 call sites now carry the new one.\n- Other managed-agent endpoints keep the older beta value.\n\n**Evidence**\n\n`agent-memory-2026-07-22`, `managed-agents-2026-04-01`\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5"}