Skip to content
Developer Portal & Agent Discovery

Smash House Developer Resources

Complete technical documentation, machine-readable specifications, Model Context Protocol (MCP) endpoints, and REST APIs for autonomous agents and developer integrations. No API key required — the public API is read-only and self-serve.

OpenAPI 3.1.0 Specification

Full interactive machine specification defining all Smash House v1 public endpoints, parameters, schemas, and dietary models.

/api/openapi.jsonView JSON

Model Context Protocol (MCP)

JSON-RPC 2.0 MCP server with live tools (get_menu, get_locations, check_allergens) and resources (smashhouse://menu, smashhouse://locations).

Agent Skills Discovery Index

Autonomous agent capability registry for Claude Code, Codex, ChatGPT, and Cursor agent frameworks.

/.well-known/agent-skills/index.jsonIndex JSON

RFC 9727 API Catalog

Standardized well-known link-set catalog associating all authoritative metadata, OAuth specifications, and API endpoints.

/.well-known/api-catalogAPI Catalog

REST API Endpoints (v1)

MethodEndpointDescriptionResponse Format
GET/api/v1/menuList all 25+ dishes, categories, GBP prices, and tags.application/json
GET/api/v1/locationsRetrieve Manchester & London addresses, transit, and hours.application/json
GET/api/v1/allergensFull UK Food Standards Agency (FSA) 14 major allergen matrix.application/json
GET/api/healthService health check and runtime status report.application/json
POST/.well-known/mcpStreamable HTTP JSON-RPC 2.0 MCP endpoint (initialize, tools/list, resources/list).application/json
POST/api/mcpJSON-RPC 2.0 Model Context Protocol endpoint for LLMs.application/json

Content Negotiation (RFC 8288)

All public routes support clean Markdown responses via standard HTTP content negotiation for autonomous agents:

curl -H "Accept: text/markdown" https://smashhouse.co.uk/menu

Error Handling (RFC 7807)

All API error responses return structured Problem Details JSON with actionable error codes, messages, hints, and doc URLs:

{"status": 404, "error": {"code": "NOT_FOUND"}}

Versioning & Deprecation Policy

  • The API is versioned in the URL path (/api/v1/*).
  • Within a version all changes are backward compatible — fields are only ever added.
  • Deprecations are signalled with Deprecation: true and a Sunset header (RFC 8594) at least 180 days before removal.
  • No versions are currently scheduled for deprecation.

Rate Limits & Onboarding

  • No API key, account, or approval needed — start calling immediately.
  • All endpoints return standard RateLimit-Limit / -Remaining / -Reset / -Policy headers (120 requests/minute per IP).
  • Exceeding the limit returns 429 application/problem+json with a Retry-After header so agents can self-throttle.