On this page
Read the API reference
Find compiled public contracts and connect them to task guides and versioned downloads.
The package pages in this section describe the compiled public API of version 0.19.0. Use them alongside a task guide: signatures identify available contracts, while guides explain ordering, authority, ownership and failure behavior.
Find the right package
| Task | Guide | Reference |
|---|---|---|
| Start an HTTP host | First API | Kernel ASP.NET Core, OpenAPI |
| Browser/native sessions | Choose authentication | Authentication, HTTP adapter |
| Provider sign-in | BFF integration | OIDC adapter |
| Runtime outgoing mail | Mail setup | MailKit, Graph |
| Module model/factory | Persistence composition | Infrastructure |
| Locale, timezone and JSON | Presentation | Kernel, HTTP registration |
Interpret what is generated
Each package page lists compiler-resolved kinds and signatures, available XML summaries, parameter descriptions and return documentation. An empty description means no authored summary exists; the generator does not invent behavior. A type appearing here does not mean every surrounding product workflow is implemented.
For example, mailbox reader contracts exist without incoming synchronization, and confirmation errors exist without a generic destructive-action endpoint. Check the guide's availability and ownership statements before building on a DTO.
Keep versions aligned
The package family versions together while major is zero. Keep the reference, NuGet dependencies and running host on the intended release. Preserve older version routes when publishing a new portal version; a link to a previous contract must not silently open the newest one.
The versioned catalog, API, search and example JSON downloads are available under
/foundation/releases/0.19.0/. They are public documentation data, not an
application authorization endpoint. See the export contract
for schemas, hashes and renderer responsibilities.