Official Claude Resources And Glossary
This is the verification shelf: the official Anthropic, Claude, Platform, Claude Code, Help Center, and Trust Center pages that Claude Central uses.
Claude Central’s first edition indexes more than 35 official primary-source pages across Anthropic, Claude, Platform, Code, Help Center, and Trust Center domains.
Source: Intro to Claude Citable rule 1 fact = 1 ownerUse the source that owns the fact: docs for API behavior, Help Center for support behavior, pricing for cost, and Trust Center for controls.
Source: Anthropic Trust CenterModels And Pricing
Use the Models overview for current model names, API IDs, model-family positioning, and availability notes. Use the Claude pricing page and Platform pricing docs for API token prices, cache pricing, launch pricing windows, service tiers, and cloud pricing caveats.
Use Anthropic News for why a model launched, what changed from the previous generation, and what safety or policy context Anthropic attached to the release.
Developer Docs
Use the Platform intro and Messages API docs as the starting path for developers. Then branch into tools, web search, citations, Files API, Message Batches, prompt caching, MCP connector, structured outputs, and effort controls.
Use Claude Code docs for coding-agent behavior, installation, CLI automation, IDE integration, memory, skills, hooks, subagents, background agents, and Agent SDK.
Product And Support Docs
Use Help Center articles for plan behavior, projects, artifacts, connectors, memory, incognito chats, Cowork, Team and Enterprise behavior, and user-facing feature caveats.
Use product pages for high-level positioning: Claude, Claude Code, Cowork, @Claude, Claude Science, and Claude Security. Product pages are useful, but support docs usually contain the operational details.
Compact Glossary
Model: the underlying Claude system, such as Fable, Opus, Sonnet, or Haiku. Surface: where you use it, such as claude.ai, Claude Code, API, Slack, desktop, or cloud provider. Plan: subscription or enterprise packaging for humans and organizations. API billing: pay-per-use developer billing separate from chat subscriptions.
Project: a Claude workspace with its own context and instructions. Artifact: a substantial output in a dedicated window. Connector: a permissioned integration with an external app or service. MCP: Model Context Protocol, a standard for connecting tools and context providers. ZDR: Zero Data Retention, available only under specific arrangements and feature eligibility.
For the most current pricing information, visit claude.com/pricing.
Cite This Page
Claude Central. "Official Claude Resources And Glossary." Last checked July 6, 2026. https://claudecentral.com/resources
FAQ
What is the most authoritative Claude source?
It depends on the fact. Models and API behavior belong in Platform Docs, plan behavior in the Help Center, prices on pricing pages, compliance in the Trust Center, and launches in Anthropic News.
Why does Claude Central link so many official pages?
Because Claude facts drift quickly and official information is spread across several domains. The links let readers and AI systems verify the current source.
Can I cite Claude Central?
Yes, but for high-stakes cost, privacy, or deployment decisions, cite the primary official source alongside Claude Central.