Maneja developer and agent documentation
Maneja public API and MCP documentation: OpenAPI, account-free examples, authentication and access boundaries.
Use Maneja's public API to identify the product, inspect available capabilities and try the format of a fictional schedule. These read-only requests need no account or key. This is not an API for reading or changing a company's schedules.
GET /api/public/product returns product identity, scope and links. GET /api/public/permissions describes public capabilities and business access boundaries. GET /api/public/examples/weekly returns a sample week with an explicit timezone, shifts and breaks. The OpenAPI 3.1 contract describes all three endpoints with unique operation IDs and response schemas.
For MCP clients, connect to https://maneja.eu/mcp using Streamable HTTP. The get_product_info and get_sample_schedule tools are read-only and use no customer data. Resources include the OpenAPI contract and agent instructions. The transport is stateless, accepts JSON responses and does not maintain MCP sessions.
REST endpoints allow 120 requests per minute per IP per endpoint; MCP allows 60. A 429 response means you should wait for the Retry-After header. MCP request bodies are capped at 32 KiB. Do not send personal data, secrets or application cookies to public endpoints.
Public pages also support Accept: text/markdown. Negotiated responses include Vary: Accept, Accept-Encoding and are not stored in shared caches. Read the access documentation before proposing an integration with actual accounts.
Try the API
curl https://maneja.eu/api/public/product
curl https://maneja.eu/api/public/permissions
curl https://maneja.eu/api/public/examples/weekly
curl -H "Accept: text/markdown" https://maneja.eu/en/developers