Developers · AI agents · Free, no auth
MyOrbitHealth for developers & AI agents
Point any AI assistant at our public MCP server and it can answer questions about MyOrbitHealth from the site’s own content, check peptide and GLP-1 rules by state, estimate launch costs, and — with the user’s permission — ask our team to get in touch. Building a product on MyOrbitHealth? That’s the platform API.
MCP server
Connect in one line
Streamable HTTP, JSON-RPC 2.0, protocol 2025-06-18. Stateless, POST only, JSON responses. Works with Claude, ChatGPT, and any client that supports remote MCP servers.
Endpoint
https://myorbithealth.com/mcpClaude Code
claude mcp add --transport http myorbithealth https://myorbithealth.com/mcp15 tools — 13 read, 2 action
| Tool | Type | What it does |
|---|---|---|
| get_overview | Read | What MyOrbitHealth is, the four products, network stats, compliance posture, and the canonical FAQ. Start here. |
| get_pricing_model | Read | How pricing works: models, what's included, cost drivers, and how to get a scoped quote. |
| get_platform | Read | Product detail for OrbitOS, Orbit Intake, OrbitRx, and the Provider Network. |
| list_comparisons | Read | Every MyOrbitHealth-vs-competitor page with a one-line summary and as-of date. |
| get_comparison | Read | A full comparison as markdown: side-by-side table, where each fits, and FAQ. |
| list_articles | Read | Blog articles, newest first, optionally filtered by category. |
| get_article | Read | The full text of one article. |
| list_solutions | Read | Live solution pages, such as white-label peptide telehealth programs. |
| get_solution | Read | A full solution page as markdown. |
| get_state_rules | Read | Peptide and GLP-1 telehealth rules for any US state or DC. General information, not legal advice. |
| estimate_startup_costs | Read | Directional, itemized launch-cost ranges: white-label vs building in-house. |
| search_site | Read | Keyword search across pages, tools, comparisons, and articles. |
| get_booking_info | Read | How discovery calls work, what to prepare (vertical, target states, timeline), and the booking link. |
| request_demo | Action · consent | Sends the user's name and email to the MyOrbitHealth team, who will email them. Returns the booking link for self-scheduling. |
| request_callback | Action · consent | Sends the user's name and phone number to the team, who will call them. |
Consent rule for action tools
request_demo and request_callback send a person’s contact details to our team. An assistant must show the exact details first and only call them after the user clearly says yes — never inferred, never for someone else. They’re limited to 5 requests per 10 minutes per client, and input that looks like spam or an injection attempt is refused with an error and a hint. People who just want to pick a time can go straight to /book.
Agent API
REST and discovery endpoints
Read-only JSON over HTTPS, no key required, CORS open. Actions are MCP-only — there are no REST equivalents.
| GET/openapi.json | OpenAPI 3.1 contract for every endpoint on this page. |
|---|---|
| GET/ask?query=… | Natural-language site search. Ranked JSON results with url, name, description, and score. |
| GET/api/articles | Blog articles, newest first. Paginated with limit (1–50) and offset. |
| GET/api/comparisons | Comparison pages. Paginated with limit (1–50) and offset. |
| GET/api/health | Health check. Returns {"status":"pass"} as application/health+json. |
| GET/.well-known/api-catalog | RFC 9727 linkset pointing at the OpenAPI contract, MCP server, llms.txt, and sitemap. |
| GET/blog/<slug>.md | Raw markdown for any blog post: append .md to the post URL. |
| GET/llms.txt | A plain-text guide to the site for language models. |
Rate limits
120 requests per minute per client across the agent endpoints. Over the limit you get HTTP 429 with a Retry-After header.
Errors
REST errors are application/problem+json (RFC 9457) with type, title, status, and detail. MCP errors are standard JSON-RPC error objects.
Platform API
Building a product? That's a different API.
Everything above is a free, no-auth information and booking layer over this website. The MyOrbitHealth product — creating patients, running intake, routing to licensed providers, and e-prescribing — is the platform REST API with signed webhooks and a React SDK, available to partners with bearer-token keys and a BAA.
Frequently asked questions
- Does MyOrbitHealth have an MCP server?
- Yes. A public Model Context Protocol server runs at https://myorbithealth.com/mcp (streamable HTTP, JSON-RPC 2.0, protocol 2025-06-18). Connect Claude Code with one command: claude mcp add --transport http myorbithealth https://myorbithealth.com/mcp. Any MCP client that supports remote servers can use the same URL.
- Is authentication required?
- No. The site MCP server and agent API are free and need no API key or sign-in. They are limited to 120 requests per minute per client, and the two contact tools to 5 requests per 10 minutes. The product platform API for building on MyOrbitHealth is separate and uses bearer-token authentication.
- What can AI agents do with it?
- Agents can answer questions about MyOrbitHealth from the site's own content — products, pricing model, comparisons, articles, peptide and GLP-1 rules by state, and directional startup costs — and, with the user's explicit consent, ask the team to email or call the user about a demo. Anyone can also book a discovery call directly at https://myorbithealth.com/book.
Questions about integrating? Email tech@myorbithealth.com or read llms.txt.