# API Reference

Use the public `melder` namespace in applications. Detailed reference pages
connect those public objects to their contracts, examples, and source.

Choose a topic, then an object. Use the guides for complete application workflows
and these references for signatures, parameters, return values, and lifecycle contracts.

Some exports identify objects you receive from a facade rather than construct
yourself. Follow the documented ownership and registration contract; a type being
importable does not mean it can be bound as an application spell.

[Beginner](../beginner/index.md) · [Intermediate](../intermediate/index.md) ·
[Advanced](../advanced/index.md) · [Expert](../expert/index.md)

- [Binding and registration](api/binding.md)

- [Resolution, scopes, and lifetimes](api/resolution.md)

- [Book, frame, and root configuration](api/configuration.md)

- [Connections and permissions](api/connections.md)

- [Nexus, Rifts, workstations, and views](api/inspection.md)

- [Persistence, restore, and storage integration](api/persistence.md)

- [Research, versions, and comparisons](api/research.md)

- [Public helpers](api/helpers.md)

- [Public errors](api/errors.md)

- [Package metadata and self-documents](api/metadata.md)


The inventory reconciles every package export and identifies additional returned surfaces. Contracts below are rendered from their Python docstrings.

{download}`Download the API inventory <../downloads/api-inventory.json>`


```{toctree}
:hidden:

Binding and registration <api/binding>
Resolution, scopes, and lifetimes <api/resolution>
Book, frame, and root configuration <api/configuration>
Connections and permissions <api/connections>
Nexus, Rifts, workstations, and views <api/inspection>
Persistence, restore, and storage integration <api/persistence>
Research, versions, and comparisons <api/research>
Public helpers <api/helpers>
Public errors <api/errors>
Package metadata and self-documents <api/metadata>
```