Raemer Studio — for agents

Read published studio services, portfolio projects and case studies. No API key is needed for these public, read-only interfaces.

JSON API: /api/public/studio, /api/public/services, /api/public/projects, /api/public/projects/{id}, /api/public/case-studies, /api/public/contact.

Search projects with query and category. Pagination uses offset (0–10000) and limit (1–20, default 10). Follow nextOffset until null.

MCP: POST /api/public/mcp using Streamable HTTP. Send Accept: application/json, text/event-stream and Content-Type: application/json. Initialize with your MCP client; this server is stateless and does not issue session IDs.

Tools: search_projects, get_project, list_services, list_case_studies, get_contact_guidance. Results include canonical source URLs. There are no write tools.

Markdown: request an approved public page with Accept: text/markdown. HTML is preferred for wildcard requests. Responses vary by Accept. Private pages are never converted.

Limits: public machine endpoints allow 60 requests per minute per IP per instance, alongside site-wide limits. MCP accepts one request at a time, up to 16 KiB, with a 10-second deadline. HTTP 429 includes Retry-After. JSON API errors use 400, 404, 405 or 503 as appropriate.

Information is studio-published, not independently certified. Project dates describe the work, not the last content review. We do not publish unverified review timestamps or endorsements.

Discovery uses the RFC 9727 API catalog; llms.txt is an optional convention, not a standard or a promise of search ranking. WebMCP, draft discovery formats and agent actions are not offered.