{"name":"BackResto Partner API","description":"Read-only access to a restaurant's own HACCP compliance records kept in BackResto, as 26 record collections: goods-in checks with per-product temperatures and their photographs, temperatures, cooling, freezing, reheating, transport, cleaning, fryer oil, surface analyses, traceability labels and drive files.","authentication":"Every request needs a partner key, sent as `Authorization: Bearer brp_<prefix>.<secret>`. Keys are issued by hand, scoped to named restaurants, once those restaurants have agreed. There is no sign-up. MCP clients that connect by URL alone (claude.ai and Claude Desktop custom connectors) run the authorization code flow: they register themselves, and the person pastes the key on a BackResto page. OAuth 2.0 clients can also run the client credentials grant against the token endpoint, with the part of the key before the dot as client_id and the part after it as client_secret: the access token it returns is that same key.","documentation":"https://developers.backresto.com/en/docs","mcp":"https://api-dev.backresto.com/mcp","mcpServerCard":"https://api-dev.backresto.com/.well-known/mcp/server-card.json","openApi":"https://api-dev.backresto.com/openapi.json","apiCatalog":"https://api-dev.backresto.com/.well-known/api-catalog","llmsText":"https://api-dev.backresto.com/llms.txt","status":"https://api-dev.backresto.com/health/ready"}