Documentation architecture
The documentation follows AgentCore as the main line, TokenHub as the model Gateway, and separate capability and API layers. Readers understand the platform boundary before they encounter implementation details.
Directory shape
| Layer | Question answered | Main content |
|---|---|---|
| AgentCore concepts | What makes up the agent platform? | Agent API, Runtime, Gateway, LTM, access surfaces, and governance |
| AgentCore components | What does each component own? | TokenHub Gateway, Tool Gateway, LTM, and Managed Chat |
| TokenHub APIs | How are models accessed and governed? | Protocols, model capabilities, tokens, reliability, usage, and billing |
| Integration guides | How should an application integrate? | Public API, Managed Chat, CLI + Skills, and Developer Platform |
| API reference | What are the fields and statuses? | OpenAPI-generated endpoints, schemas, responses, and errors |
Classification rules
- Classify by AgentCore or TokenHub first, then by concept, capability, or integration guide.
- TokenHub's model Gateway is an AgentCore component, but TokenHub keeps an independent entry because ordinary applications can use it directly.
- LTM, Tool Gateway, Agent API, and Runtime describe agent state and execution; protocols, models, tokens, and call governance describe TokenHub.
- Keep API reference field-precise; put context, trade-offs, and complete workflows in concept or integration guides.
- Mark available, in-development, and planned capabilities explicitly.
- Preserve existing URLs and migrate through sidebars and cross-links rather than needless breaking changes.
Where existing content belongs
| Existing content | Primary home |
|---|---|
| Core APIs, generation endpoints, and model capabilities | TokenHub |
| Billing, token counting, rate limits, and fallbacks | TokenHub / governance |
| LTM, Managed Chat, and CLI + Skills | AgentCore / components and integrations |
| Function calling, MCP, and external tool access | AgentCore / Gateway |
| General troubleshooting, migration, and SDKs | Shared integration and operations |
| OpenAPI endpoints and fields | API reference |
Migration order
- Use the AgentCore overview as the platform entry point and explain component relationships.
- Define TokenHub as AgentCore's model Gateway while retaining its standalone path.
- Place LTM, Gateway, and future Agent API / Runtime under AgentCore components.
- Place model protocols, capabilities, tokens, reliability, and billing under TokenHub.
- Unify titles, cross-links, and examples last while keeping old URLs available.