Find the API for your task
Each package has an entry page and focused reference topics. Choose the responsibility first, then the API family. Complex packages have deeper navigation; small packages stay compact.
| Package | Responsibility | Topics |
|---|---|---|
| fetcher | HTTP requests | 6 |
| decorator | Declarative services | 3 |
| eventbus | Event delivery | 2 |
| eventstream | SSE consumption | 3 |
| storage | Stored values | 2 |
| openapi | OpenAPI type contracts | 3 |
| generator | Generated clients | 5 |
| openai | Chat and token streams | 2 |
| cosec | Authentication and refresh | 3 |
| react | Component request state | 8 |
| wow | Commands and queries | 9 |
| viewer (deprecated) | Data views and persistence | 8 |
| view-engine | Headless engine, component configuration and shadcn/Base UI | 5 |
Use the right depth
Entry pages explain purpose, prerequisites, and topic choices; each package ends with a complete symbol index. Topic pages explain parameters, defaults, results, failures, and lifecycle. Use Guides for end-to-end work and Start for your first integration.
Reference follows current public exports and implementations. A source file inside a package does not imply a public package import.