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.

How can crawlers and AI agents read the whole site?

Fetch https://myorbithealth.com/llms-full.txt for the full corpus in one markdown file, or the scoped indexes at /blog/llms.txt, /compare/llms.txt and /solutions/llms.txt. Append .md to any blog post, comparison, solution, and the platform, pricing, FAQ, labs, LegitScript, provider network, compliance and developers pages for a markdown copy. New articles appear in the RSS feed at /feed.xml, and the MCP server is described at /.well-known/mcp.json and /.well-known/mcp/server-card.json.

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, and — with the user’s permission — ask our team to get in touch. Building a product on MyOrbitHealth? That’s the platform API.

Connect an agent OpenAPI contract

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/mcp

Claude Code

claude mcp add --transport http myorbithealth https://myorbithealth.com/mcp

npm CLI npmjs.com/package/myorbithealth

npx myorbithealth --help

npx myorbithealth state TX

npx myorbithealth compare myorbit-vs-openloop

The same CLI also runs a stdio MCP proxy for stdio-only MCP clients — point a client at npx -y myorbithealth mcp instead of the remote HTTP endpoint.

20 tools — 18 read, 2 action

MCP tools
Tool	Type	What it does
get_overview	Read	What MyOrbitHealth is, the canonical facts, the products, compliance posture, and the canonical FAQ. Start here.
get_pricing_model	Read	How pricing works: our model, market models, what's included, what drives your quote, and FAQ.
get_facts	Read	The owner-confirmed canonical facts: network size, specialties, response time, fee model, labs, LegitScript, storefront and app, compliance.
get_fee_model	Read	The fee model in short: flat scoped platform fee, 0% medication markup, no revenue share, you are merchant of record, no exit fee.
get_labs	Read	Orbit Labs: labs drawn three ways, the patient self-order catalog, result states, and the labs API.
get_legitscript_process	Read	Managed LegitScript certification: steps, timelines, what it checks, cost, and staying certified.
get_provider_network	Read	The provider network: credentialing, coverage by category, routing, and bringing your own providers.
get_compliance	Read	Telehealth compliance: who holds what, CPOM and MSO, licensure, DEA, HIPAA, SOC 2 Type II, and a vendor checklist.
get_platform	Read	Product detail for OrbitOS, Orbit Intake, OrbitRx, the Provider Network, and Orbit Labs.
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.
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.

Agent API endpoints
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.

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.

Discovery

Files for crawlers and AI agents

Everything here is generated from the same content as the pages, so the numbers never drift. Start with /llms.txt, or fetch /llms-full.txt for the whole corpus in one file.

Discovery files
/llms.txttext/plain	A plain-text guide to the site for language models: facts, key pages, comparisons, solutions and articles.
/llms-full.txttext/markdown	The full corpus in one file: llms.txt, the canonical facts, platform, pricing, labs, LegitScript, provider network, compliance, every solution, every comparison and every article.
/blog/llms.txttext/markdown	Scoped index of every blog article with slug, category, date and URL.
/compare/llms.txttext/markdown	Scoped index of every comparison page with its as-of date.
/solutions/llms.txttext/markdown	Scoped index of every solution page.
/feed.xmlapplication/rss+xml	RSS 2.0 feed of blog articles, newest first.
/.well-known/mcp.jsonapplication/json	MCP registry-style server manifest: remote endpoint plus the npm stdio package.
/.well-known/mcp/server-card.jsonapplication/json	MCP server card: transport, authentication (none) and every tool with its input schema.
/.well-known/ai-catalog.jsonapplication/json	AI catalog pointing at the MCP manifest, OpenAPI contract, llms.txt, llms-full.txt and the RSS feed.
/.well-known/api-catalogapplication/linkset+json	RFC 9727 linkset pointing at the OpenAPI contract, MCP server, llms.txt, llms-full.txt, feed and sitemap.
/.well-known/agent-skills/index.jsonapplication/json	Agent skills index: when to use MyOrbitHealth and three skill guides under /skills/.
/sitemap.xmlapplication/xml	Every indexable page.

Markdown mirrors

Append .md to a page URL for the same content as markdown. Each page advertises its twin with <link rel="alternate" type="text/markdown">.

/blog/<slug>.md
/compare/<slug>.md
/solutions/<slug>.md
/platform.md
/pricing.md
/faq.md
/labs.md
/legitscript.md
/provider-network.md
/compliance.md
/developers.md

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.

API documentation

REST endpoints, bearer-token auth, rate limits, and signed webhooks.

Telehealth API & React SDK

Integration patterns: full API, SDK embed, hosted clinic plus API, and EHR sync.

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.
How can crawlers and AI agents read the whole site?: Fetch https://myorbithealth.com/llms-full.txt for the full corpus in one markdown file, or the scoped indexes at /blog/llms.txt, /compare/llms.txt and /solutions/llms.txt. Append .md to any blog post, comparison, solution, and the platform, pricing, FAQ, labs, LegitScript, provider network, compliance and developers pages for a markdown copy. New articles appear in the RSS feed at /feed.xml, and the MCP server is described at /.well-known/mcp.json and /.well-known/mcp/server-card.json.

Questions about integrating? Email tech@myorbithealth.com or read llms.txt.