Current public developer surfaces
Developers can inspect the current public surfaces at /agents, /llms.txt, /.well-known/limowo-agent.json, /.well-known/limowo-mcp.json, /api/agent/v1/openapi.json, and /api/agent/v1/commands.
Developer API
Limowo publishes current agent and API discovery routes for technical integrators while keeping writes, MCP, payments, orders, and account actions behind explicit release gates.
Last updated: 1 July 2026
View agent docsCurrent
REST/OpenAPI discovery
MCP
Planned, not live
Writes
Feature-gated, scoped, and reviewed
Developers can inspect the current public surfaces at /agents, /llms.txt, /.well-known/limowo-agent.json, /.well-known/limowo-mcp.json, /api/agent/v1/openapi.json, and /api/agent/v1/commands.
The public contract is centered on the agent command API. Public discovery and read commands can be documented through OpenAPI, while draft preparation and state-changing behavior stay behind authentication, grants, feature flags, approvals, idempotency, and audit requirements.
The MCP readiness status exists so integrators can distinguish current REST/OpenAPI support from planned MCP support. Remote MCP, MCP writes, and any local stdio bridge must stay unavailable until authorization, durable runtime, protocol conformance, and production rollout gates pass.
No arbitrary shell, SQL, GraphQL, filesystem, or unrestricted HTTP access is exposed. Developer integrations must not enable autonomous publishing, offers, orders, payments, account administration, dispute handling, or private data access outside documented authorization scopes.
Before Limowo promotes broader developer API access, it should complete ZITADEL/OpenFGA authorization, durable command state, idempotency, approval records, rate limits, audit logs, compatibility policy, abuse monitoring, conformance tests, and production acceptance records.
Developer support requests should include endpoint path, command name, request ID, response code, idempotency key where relevant, locale, client metadata, and a minimal reproduction without API keys, session tokens, passwords, or payment secrets.
We use cookies for analytics so we can understand how you use limowo.ch. You can accept to help us improve, or reject if you prefer.