Implementation status
Use this page to distinguish a supported public contract from product infrastructure or planned work.
Public developer contracts
Section titled “Public developer contracts”| Surface | Status | Contract |
|---|---|---|
| Agent REST API | Available | Versioned /api/v1/agent/* routes |
| MCP server | Available | Streamable HTTP JSON-RPC at /mcp |
| OpenAPI | Available | OpenAPI 3.1 at /openapi.json |
| Scoped API keys | Available | Created, rotated, and revoked in Developer settings |
| Signed outgoing webhooks | Available | Creator-approved contribution, supporter, goal, and membership events configured in Developer settings |
Dashboard-managed connections
Section titled “Dashboard-managed connections”| Surface | Status | Boundary |
|---|---|---|
| X inbox | Available when provider configuration is enabled | Creator installs through Loresta OAuth |
| Instagram professional inbox | Available through approved SocialAPI capabilities | Creator installs through Loresta Connections |
| Messenger Page inbox | Available through approved SocialAPI capabilities | Creator installs through Loresta Connections |
| Discord | Available when the Discord application is configured | Creator installs the app into a managed server |
These installation and callback routes are Loresta product infrastructure, not reusable third-party OAuth APIs.
Limited surfaces
Section titled “Limited surfaces”Threads, LinkedIn, and YouTube are not general private-inbox connections. TikTok DM and comment access is not available in the current surface. Google Business is oriented around approved review replies. Publishing availability is provider and application dependent.
Not public yet
Section titled “Not public yet”- A public creator profile-list endpoint
- Public dashboard, checkout, job, or provider-callback APIs
Do not build production integrations against undocumented /api/dashboard/*, /api/jobs/*, /api/webhooks/*, or other unversioned product routes.
Compatibility policy
Section titled “Compatibility policy”The /api/v1/agent/* path is the current REST version boundary. Additive response fields can appear without a new version, so clients should ignore unknown fields. Breaking request or response changes require a new public contract or versioned migration guidance.
MCP currently prefers protocol 2025-06-18 and accepts the documented compatibility versions on the MCP server page.