/vendor/ro/AgentRouting.json or
/vendor/ro/AgentContext.json directly.
ro.co
Overview
Does ro.co support MCP?
No confirmed MCP support was found for ro.co as of 2026-07-01.
What agentic protocols does ro.co support?
No confirmed agentic protocol support was found for ro.co as of 2026-07-01.
Is ro.co's API publicly accessible or partner-gated?
Access tier information is not available for ro.co.
Does ro.co explicitly prohibit automated access?
Yes. ro.co's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is ro.co agent-ready?
Not currently. No confirmed agent-callable interface was found for ro.co as of 2026-07-01.
Protocols
No evidence found that ro.co (the telehealth/digital health company) appears in any A2A launch partner lists or has adopted the Agent2Agent protocol. Named A2A launch partners include Atlassian, Box, Cohere, Intuit, Langchain, MongoDB, PayPal, Salesforce, SAP, ServiceNow, UKG, and Workday — all enterprise software/cloud vendors with no connection to ro.co's domain. Second search returned results about unrelated entities ('Roo Code,' an IDE agent tool) and confirmed ro.co is a consumer digital health company with no identified A2A engagement.
No evidence found that ro.co (a domain registrar/brand platform) has any involvement with the Agentic Commerce Protocol. Known ACP launch partners as of the protocol's beta release include URBN, Coach, Kate Spade, Revolve, and Ashley Furniture — ro.co appears in none of the official OpenAI, Stripe, or GitHub ACP documentation. This is not_found rather than confirmed_absent because ro.co has not itself issued any statement about the protocol.
No evidence found that ro.co has adopted, piloted, or is listed as a launch partner for AP2 (Agent Payments Protocol, now under FIDO Alliance stewardship). Searches surfaced the official ap2-protocol.org documentation and Google/FIDO Alliance announcements but no mention of ro.co in any partner, participant, or adopter context. Chosen not_found rather than confirmed_absent because no vendor-specific statement from ro.co either affirming or denying AP2 adoption was found.
Ro (ro.co) is a direct-to-patient telehealth company offering services in weight loss, sexual health, and hair loss. No evidence of any MCP server, MCP endpoint, or Model Context Protocol integration was found across searches targeting ro.co's developer surface, API documentation, and technology integrations. Note: search results surfaced 'Roo Code' (an IDE extension) and 'Roam' (ro.am) as unrelated MCP-implementing entities — neither is ro.co.
No evidence that ro.co has adopted or integrated MPP. Known launch partners and early ecosystem participants include Visa, Mastercard, Cloudflare, Anthropic, OpenAI, MultiversX, and Monad — ro.co does not appear in any MPP partner list, launch hackathon coverage, or protocol documentation. Status is not_found rather than confirmed_absent because no ro.co-specific statement about MPP was located.
No evidence found that ro.co (Ro, a telehealth company) is a NLWeb pioneer or adopter. The confirmed launch partners listed by Microsoft are Tripadvisor, Delish, O'Reilly Media, Qdrant, Inception, Chicago Public Media, Common Sense Media, DDM (Allrecipes & Serious Eats), Milvus, Shopify, and Snowflake — none of which are ro.co. Ro operates in telehealth (weight loss, sexual health, hair), a segment with no confirmed NLWeb presence.
Ro (ro.co) is a US telehealth company offering online medical services (weight loss, sexual health, hair, etc.) — not an e-commerce or retail merchant. No evidence was found of Ro adopting or implementing the Universal Commerce Protocol. UCP is primarily targeting retail/merchant checkout contexts; Ro's prescription-based healthcare model and regulatory environment make it a highly unlikely adopter. No vendor-specific announcements, documentation, or partner listings mentioning Ro and UCP were found.
Two searches covering WebMCP launch partners and ro.co specifically returned no mentions of ro.co (a domain registrar) in any WebMCP context. Named WebMCP early adopters and implementers include Cloudflare (via its Browser Run product) but not ro.co. WebMCP itself remains an early-preview protocol gated behind a Chrome flag and sign-up program, with no evidence that ro.co has enrolled or exposed any window.AICommands tooling.
No evidence found of ro.co appearing in any x402 launch partner list, ecosystem announcement, or documentation. Named x402 launch/ecosystem partners include Coinbase, Cloudflare (x402 Foundation), Stellar, Solana, Zuplo, and Eco.com — ro.co is absent from all search results reviewed. This is not_found rather than confirmed_absent because no vendor-specific statement from ro.co addresses x402 adoption or rejection.
Ro (ro.co) is a direct-to-patient telehealth company. No evidence was found of Ro building or publishing an app on OpenAI's ChatGPT Apps platform using the Apps SDK. Searches returned OpenAI's own Apps SDK documentation and unrelated results for 'Roo Code' (a developer tool), but nothing connecting ro.co to the ChatGPT Apps ecosystem. Confirmed absent was not selected because no vendor-specific statement or deprecation notice from Ro exists — the finding is simply an absence of evidence.
Ro (ro.co) is a direct-to-patient telehealth company offering nationwide telehealth, pharmacy, and lab services. No publicly documented proprietary API or developer-facing integration interface was found across searches targeting their developer documentation, partner programs, and integration surfaces. The Wikipedia entry and company profiles confirm a vertically integrated consumer-facing platform but no externally callable API. No developer portal, API reference, or partner API program was identified.
Direct HTTP fetches to ro.co for /llms.txt, /.well-known/agent, /.well-known/ai-catalog.json, /AGENTS.md, and /agents.md all timed out at DNS resolution — the sandbox environment has no outbound network access to ro.co. Web searches returned no indexed evidence of any self-declaration files published at ro.co. Because the domain itself could not be reached and no cached or indexed copies of these files were found, the check is structurally blocked rather than producing a clean negative.
Summary
Has agent interface: false
Monitor ro.co for any future developer portal, partner API program, or agentic protocol adoption announcements; no actionable integration surface exists today.
AgentContext
Verified discrepancies
Vendor claim: Ro advertises a low introductory price (e.g., $39 for the first month) for access to its telehealth programs, presenting this as the cost of treatment during the checkout flow.
What actually happens: Multiple independently-documented consumer complaints confirm that the advertised program fee does not include the cost of the prescribed medication itself, and that a separate mandatory recurring membership or program fee (reported at $145/month by multiple complainants) is not clearly disclosed before checkout. Consumers only discover the true total cost after being charged, sometimes disputing what appear to be duplicate charges.
Agent guidance: Before completing any Ro transaction, explicitly verify the full out-of-pocket total by navigating to the final checkout confirmation screen and confirming that both the program/membership fee AND the medication cost are itemized separately. Do not treat the first advertised price as the total; add up all line items and confirm the recurring monthly total before submitting payment.
- A BBB consumer review states that during intake and checkout Ro did not clearly disclose that the program charges are 'merely fees paid to Ro for access to the program and do not contribute toward the cost of the medication itself,' with the full cost only discovered after disputing an apparent duplicate charge.
- Multiple BBB complaints describe an undisclosed mandatory $145/month recurring charge applied on top of the advertised program price, with consumers stating they were not advised of this additional monthly charge before being billed.
Vendor claim: Ro presents itself as the platform through which consumers purchase medications, collecting payment directly at checkout. The checkout and product pages give the impression that Ro is the party responsible for the transaction.
What actually happens: Ro's own Terms of Use state that for certain products (specifically LillyDirect partner pharmacy purchases), 'Ro may collect payment in connection with your purchase on behalf of the LillyDirect partner pharmacy.' The same terms state that 'Any refunds, replacements, or disputes related to Products are subject to the policies and review of the dispensing pharmacy and, where applicable, Lilly.' This means Ro collects payment but acts as a payment agent for a third-party pharmacy, and redirects dispute and refund responsibility to that pharmacy or Lilly — not to Ro itself.
Agent guidance: Before completing any medication purchase transaction on ro.co, an agent must check at checkout whether the purchase is routed through a LillyDirect partner pharmacy. If so, the agent should surface to the user that Ro is acting as a payment collector only — not the merchant of record — and that any refund or dispute must be directed to the dispensing pharmacy or Lilly, not Ro. The agent should not represent Ro as the responsible party for post-purchase issues on such orders.
- Ro's published Terms of Use explicitly state that Ro may collect payment on behalf of the LillyDirect partner pharmacy and that refunds and disputes are governed by the dispensing pharmacy's policies and Lilly — not Ro.
- BBB profile for Ro (Roman Health Ventures, Inc.) shows numerous consumer complaints about refunds not being received and unclear billing, consistent with consumers being unable to identify who is responsible for resolving disputes.
Human handoff required for
Escalate to a human before completing checkout when the total displayed price appears to cover only the program or membership fee but does not visibly itemize the medication cost as a separate line item — specifically when the checkout confirmation screen does not show both a program/membership fee and a medication cost as distinct charges adding up to the recurring monthly total.
Escalate to a human when a medication purchase on ro.co is routed through a LillyDirect partner pharmacy — identifiable because Ro's Terms of Use state it collects payment 'on behalf of the LillyDirect partner pharmacy' in such cases — since Ro is not the merchant of record and any refund, replacement, or dispute must be directed to the dispensing pharmacy or Lilly rather than to Ro.
Escalate to a human when a post-purchase refund or dispute is raised on a LillyDirect-routed order where the user expects Ro to process the resolution — since Ro's Terms explicitly redirect dispute and refund responsibility to the dispensing pharmacy or Lilly, and Ro will not act as the responsible counterparty, creating ambiguity about where to direct the claim.
Five categories were checked for ro.co. Pricing discrepancy: multiple BBB consumer complaints were found documenting a pattern of undisclosed mandatory fees beyond Ro's advertised introductory price, with the medication cost not itemized at checkout — a finding was recorded. Availability discrepancy: isolated billing complaints were found on Trustpilot but no documented systemic pattern of advertised inventory being unavailable or bait-and-switch conditions was identified — no finding. Identity/merchant-of-record discrepancy: Ro's own published Terms of Use confirmed that for LillyDirect partner pharmacy purchases Ro acts only as a payment agent, with dispute and refund responsibility redirected to the dispensing pharmacy or Lilly — a finding was recorded. Policy enforcement discrepancy: BBB complaint threads showed case-by-case customer service friction but Ro's responses reflected its published non-refund policy; no systematic enforcement gap was found — no finding. Undisclosed platform constraints: Ro's Terms of Use disclose the pay-first/evaluate-later model for its Body Program, and no regulatory action or complaint pattern documenting hidden mid-transaction constraints was found — no finding. All five categories were actively searched; no scans were blocked or missing.