Public developer resources
Service guidance that agents can read directly.
Rossmann Repair Group publishes a small, unauthenticated, read-only API and MCP server for finding the relevant data recovery page, mail-in instructions, and contact information. Neither interface diagnoses a device, opens a case, collects personal data, quotes work, or guarantees recovery.
One versioned, read-only endpoint.
GET /api/v1/service-guide lists supported device categories and official service links. Add the optional device_type query parameter to request one category. The allowed values and every response field are defined in the OpenAPI contract.
No authentication is required. Responses include standard rate-limit headers. Invalid input and unknown API paths return typed application/problem+json errors with a stable code and a resolution hint.
curl "https://rossmanngroup.com/api/v1/service-guide?device_type=ssd"Three tools, all explicitly read-only.
find_recovery_service
Maps a supported device category to its official service page.
get_mail_in_instructions
Returns the current guide for sending a device to the Austin lab.
get_contact_information
Returns the official contact page and Austin lab address.
{
"mcpServers": {
"rossmann-service-guide": {
"url": "https://rossmanngroup.com/mcp"
}
}
}Predictable machine-readable entry points.
- /llms.txt gives agents the short site index and use guidance.
- /.well-known/api-catalog publishes an RFC 9727 API catalog.
- /.well-known/agent-skills/index.json publishes the data recovery guidance skill and its digest.
- /.well-known/mcp/server-card.json describes the MCP transport and its tools before connection.
Safe defaults and stable boundaries.
The public API and MCP server expose no write operations, credentials, webhooks, customer records, or case status. Because nothing can be created or changed, idempotency keys and OAuth scopes do not apply.
Version 1 lives under /api/v1. A future incompatible version will use a new path. Before removing a version, the documentation will publish a migration notice and responses will identify deprecation through standard HTTP headers.
For case-specific guidance, use the contact page. For current service terms or costs, follow the linked service and pricing pages instead of storing a copied value in an integration.