71 pages for historical.

ticket-routing Claude Developer Platform · in the page about-claude/use-case-guides/ticket-routing …iarity with, your existing support ticketing system * A sample set of historical support tickets for testing ## Define whether to use Claude for ticket routing Here are some key indicators that you… PDF Processing Claude Developer Platform · in the page agents-and-tools/agent-skills/best-practices …o longer supported. </details> ``` The old patterns section provides historical context without cluttering the main content. ### Use consistent terminology Choose one term and use it throughout the… advisor-tool Claude Developer Platform · in the page agents-and-tools/tool-use/advisor-tool …dvisor_tool_result` blocks. The API accepts the request and keeps the historical blocks, but the model cannot call the advisor in that request. Two conditions apply: * **No advisor call is still pend… Beta Claude Developer Platform · in the page api/beta …inference requests naming it fail. It remains in the catalogue as the historical record of its retirement. default: active - `"active"` - `"deprecated"` - `"retired"` - `line: B… Models Claude Developer Platform · in the page api/beta/models …inference requests naming it fail. It remains in the catalogue as the historical record of its retirement. default: active - `"active"` - `"deprecated"` - `"retired"` - `line: B… List Models Claude Developer Platform · in the page api/beta/models/list …inference requests naming it fail. It remains in the catalogue as the historical record of its retirement. default: active - `"active"` - `"deprecated"` - `"retired"` - `line: B… Get a Model Claude Developer Platform · in the page api/beta/models/retrieve …inference requests naming it fail. It remains in the catalogue as the historical record of its retirement. default: active - `"active"` - `"deprecated"` - `"retired"` - `line: B… Compliance API Claude Developer Platform · in the page api/compliance …or path was updated. - `"platform_memory_version_redacted"` A historical version of an agent memory document was redacted. Redaction scrubs the stored content of a specific version while prese… Activities Claude Developer Platform · in the page api/compliance/activities …or path was updated. - `"platform_memory_version_redacted"` A historical version of an agent memory document was redacted. Redaction scrubs the stored content of a specific version while prese… Query compliance activities Claude Developer Platform · in the page api/compliance/activities/list …or path was updated. - `"platform_memory_version_redacted"` A historical version of an agent memory document was redacted. Redaction scrubs the stored content of a specific version while prese… Models Claude Developer Platform · in the page api/models …inference requests naming it fail. It remains in the catalogue as the historical record of its retirement. default: active - `"active"` - `"deprecated"` - `"retired"` - `line: M… List Models Claude Developer Platform · in the page api/models/list …inference requests naming it fail. It remains in the catalogue as the historical record of its retirement. default: active - `"active"` - `"deprecated"` - `"retired"` - `line: M… Get a Model Claude Developer Platform · in the page api/models/retrieve …inference requests naming it fail. It remains in the catalogue as the historical record of its retirement. default: active - `"active"` - `"deprecated"` - `"retired"` - `line: M… access-transparency-log Claude Developer Platform · in the page manage-claude/access-transparency-log …ays extends to the latest published checkpoint. This API never serves historical checkpoints: you keep the ones you are served. * A `from` equal to the latest checkpoint’s tree size returns the empty… First request Claude Developer Platform · in the page manage-claude/claude-code-analytics-api …om/docs/en/monitoring-usage). ### What’s the data retention period? Historical Claude Code analytics data is retained and accessible through the API. There is no specified deletion period for this d… compliance-org-data Claude Developer Platform · in the page manage-claude/compliance-org-data …anization. Removed users are dropped from the list immediately. Their historical activity remains queryable through the Activity Feed for the full retention window, indexed by the same `user_...` ID.… usage-cost-analytics-api Claude Developer Platform · in the page manage-claude/usage-cost-analytics-api …the Claude Console. </Tip> The Usage and Cost Analytics API reports historical token usage and cost for your organization, broken down by the dimensions you choose, such as model, workspace, API key… First request Claude Developer Platform · in the page manage-claude/usage-cost-api …Usage and Cost Admin API provides programmatic and granular access to historical API usage and cost data for your organization. This data is similar to the information available on the [Usage](https:/… workspaces Claude Developer Platform · in the page manage-claude/workspaces …three dots) and select **Archive workspace**. Archiving: * Preserves historical data for reporting * Deactivates the workspace and archives every API key created for it * Cannot be undone <Warning>… DCF Model Rubric Claude Developer Platform · in the page managed-agents/define-outcomes …ubric: ```markdown # DCF Model Rubric ## Revenue Projections - Uses historical revenue data from the last 5 fiscal years - Projects revenue for at least 5 years forward - Growth rate assumptions are… memory Claude Developer Platform · in the page managed-agents/memory …esponse schema. ### Redact a version Redact scrubs content out of a historical version while preserving the audit trail (who did what, when). Use it for compliance workflows such as removing leaked… claude-sonnet-3-5 Claude Developer Platform · in the page release-notes/system-prompts/claude-sonnet-3-5 …information about controversial topics and research areas, explaining historical atrocities, describing tactics used by scammers or hackers for educational purposes, engaging in creative writing that… Explore the .claude directory Claude Code CLI · in the page claude-directory …eckpoint restore for past sessions | | `~/.claude/stats-cache.json` | Historical totals shown by `/usage` | | `~/.claude/usage-data/` | Past [`/insights`](/docs/en/costs#analyze-your-usage-patterns) r… Configure your terminal for Claude Code Claude Code CLI · in the page terminal-config …ing for this is usually labeled "Use Option as Meta Key"; Meta is the historical Unix name for the key now labeled Option or Alt. > [tab] Apple Terminal > > Open Settings → Profiles → Keyboard and ch… Design Principles Model Context Protocol · in the page community/design-principles …r serves the ecosystem. This means accepting some inconsistency, some historical accidents, and some decisions we might make differently with hindsight. ## Standardization over innovation MCP standa… Example Servers Model Context Protocol · in the page examples …ervers that are no longer actively maintained. They are provided for historical reference only. ## More servers Visit the MCP Registry at [registry.modelcontextprotocol.io](https://registry.modelco… SEP-1024: MCP Client Security Requirements for Local Server Installation Model Context Protocol · in the page seps/1024-mcp-client-security-requirements-for-local-server- …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-1034: Support default values for all primitive types in elicitation schemas Model Context Protocol · in the page seps/1034--support-default-values-for-all-primitive-types-in …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-1036: URL Mode Elicitation for secure out-of-band interactions Model Context Protocol · in the page seps/1036-url-mode-elicitation-for-secure-out-of-band-intera …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-1046: Support OAuth client credentials flow in authorization Model Context Protocol · in the page seps/1046-support-oauth-client-credentials-flow-in-authoriza …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-1302: Formalize Working Groups and Interest Groups in MCP Governance Model Context Protocol · in the page seps/1302-formalize-working-groups-and-interest-groups-in-mc …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-1303: Input Validation Errors as Tool Execution Errors Model Context Protocol · in the page seps/1303-input-validation-errors-as-tool-execution-errors …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-1319: Decouple Request Payload from RPC Methods Definition Model Context Protocol · in the page seps/1319-decouple-request-payload-from-rpc-methods-definiti …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-1330: Elicitation Enum Schema Improvements and Standards Compliance Model Context Protocol · in the page seps/1330-elicitation-enum-schema-improvements-and-standards …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-1577: Sampling With Tools Model Context Protocol · in the page seps/1577--sampling-with-tools …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-1613: Establish JSON Schema 2020-12 as Default Dialect for MCP Model Context Protocol · in the page seps/1613-establish-json-schema-2020-12-as-default-dialect-f …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-1686: Tasks Model Context Protocol · in the page seps/1686-tasks …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-1699: Support SSE polling via server-side disconnect Model Context Protocol · in the page seps/1699-support-sse-polling-via-server-side-disconnect …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-1730: SDKs Tiering System Model Context Protocol · in the page seps/1730-sdks-tiering-system …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-1850: PR-Based SEP Workflow Model Context Protocol · in the page seps/1850-pr-based-sep-workflow …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-1865: MCP Apps - Interactive User Interfaces for MCP Model Context Protocol · in the page seps/1865-mcp-apps-interactive-user-interfaces-for-mcp …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-2085: Governance Succession and Amendment Procedures Model Context Protocol · in the page seps/2085-governance-succession-and-amendment …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-2106: Tools `inputSchema` & `outputSchema` Conform to JSON Schema 2020-12 Model Context Protocol · in the page seps/2106-json-schema-2020-12 …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-2127: MCP Server Cards - HTTP Server Discovery Model Context Protocol · in the page seps/2127-mcp-server-cards …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-2133: Extensions Model Context Protocol · in the page seps/2133-extensions …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-2148: MCP Contributor Ladder Model Context Protocol · in the page seps/2148-contributor-ladder …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-2149: MCP Group Governance and Charter Template Model Context Protocol · in the page seps/2149-working-group-charter-template …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-2164: Standardize Resource Not Found Error Code Model Context Protocol · in the page seps/2164-resource-not-found-error …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-2207: OIDC-Flavored Refresh Token Guidance Model Context Protocol · in the page seps/2207-oidc-refresh-token-guidance …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to… SEP-2243: HTTP Header Standardization for Streamable HTTP Transport Model Context Protocol · in the page seps/2243-http-standardization …> [!NOTE] > > This SEP has reached Final status and is preserved as a historical record of > the design as accepted. Changes made to the protocol after finalization are > not reflected here. Refer to…