Loresta developer documentation
Build creator integrations, connect supporter communities, and use Loresta through permission-scoped APIs.
Start here
Section titled “Start here”- Make your first authenticated request
- Create and protect an API key
- Choose an integration
- Install the Discord integration
- Connect an MCP client
API surfaces
Section titled “API surfaces”| Surface | Contract |
|---|---|
| REST | OpenAPI 3.1 |
| MCP | Streamable HTTP at /mcp |
| Authentication | OAuth and bearer keys |
Safety boundary: The public Agent API can read approved creator context and prepare controlled actions. It never returns social provider credentials or sends a social reply directly.
How Loresta separates access
Section titled “How Loresta separates access”Loresta separates public creator experiences, provider connections, supporter records, and technical access. A connection only receives the permissions approved during its own installation flow.
Use the OpenAPI specification for machine-readable REST contracts or open Developer settings to manage workspace API access.
Public contract boundaries
Section titled “Public contract boundaries”The versioned REST routes under /api/v1/agent/*, the /mcp endpoint, and /openapi.json are the public developer contract. Dashboard, job, provider callback, and checkout routes are product internals and can change without public API versioning.
The public Agent API prepares a reply decision but never sends a social message. Creating a handoff requires an existing Loresta conversation and explicit confirmation. Implementation status lists what is available now and what is still planned.