Skip to main content

​
API Overview

The Syntropy Health platform exposes two API surfaces:

​
Extension API (/api/ext/*)

REST endpoints consumed by the Chrome extension and mobile app. All endpoints require Clerk JWT authentication. Key endpoints:
  • GET /api/ext/profile — User profile and health data
  • POST /api/ext/checkin — Log a health check-in
  • POST /api/ext/food — Log food with AI analysis
  • GET /api/ext/diet/score — Current diet score and gaps
  • POST /api/ext/chat — Chat with Shrine AI
See the Extension Contract for the full OpenAPI specification.

​
MCP Server (/mcp)

Model Context Protocol endpoint for AI client integrations. Exposes 10 Shrine AI tools via Streamable HTTP transport with Clerk JWT auth. See the MCP Developer Guide for setup and tool documentation.

​
Authentication

All API endpoints use Clerk JWT tokens. Include the token in the Authorization header: 
curl -H "Authorization: Bearer <clerk-jwt>" \
  https://syntropyhealth.bio/api/ext/profile
For MCP connections, configure your client’s authentication with the same Clerk JWT.