Raw AI Engine Response (JSON)
{
"taxonomy": {
"country": "United States",
"categories": [
"Healthcare & Wellness",
"SaaS & Software",
"Developer Tools",
"Documentation",
"Blog"
],
"tags": [
"API-First Architecture",
"Model Context Protocol (MCP)",
"Machine-to-Machine",
"RAG-Ready",
"Auto-Discovery Enabled",
"Schema-Enriched",
"Real-Time Feed",
"Tool-Use-Ready",
"Machine-Legibility",
"High-Density Facts"
],
"topics": [
"Healthcare Clearinghouse",
"EDI Transactions",
"Revenue Cycle"
],
"category_suggestions": [],
"tag_suggestions": []
},
"brand": {
"name": "Stedi",
"description": "Stedi provides an API-first, programmable healthcare clearinghouse with AI-ready APIs for eligibility checks, claims processing, payer connectivity, and transaction enrollment.",
"type": "company",
"industry": "Healthcare IT / Revenue Cycle Management (RCM)",
"business_model": "SaaS (APIs and platform)",
"target_audience": "Health tech companies, providers, and developers integrating U.S. healthcare EDI transactions (eligibility, claims, remittance, enrollment).",
"tone_voice": [
"technical",
"developer-focused",
"product-led",
"trust-and-security-oriented"
],
"contact_email": null,
"uniqueness": "Positions itself as \"the only programmable healthcare clearinghouse\" with JSON-native APIs and an MCP server for AI agent access to clearinghouse workflows.",
"market_position": "Specialized healthcare clearinghouse positioned for modern, API-first integrations and AI agent automation."
},
"languages": {
"primary": "en",
"others": [],
"localization": "US-focused (explicitly references U.S. payers and U.S. healthcare transactions)"
},
"analysis": {
"robots": {
"sentiment": "positive",
"observation": "robots.txt allows all user agents (Allow: /) and lists multiple sitemaps including /sitemap.xml, /docs/sitemap.xml, and healthcare/network sitemap.",
"tip": "Add explicit AI crawler guidance (e.g., dedicated rules for common AI user agents) and align with llms.txt by referencing key doc sections and any licensing/usage terms.",
"facts": [
"User-agent: *",
"Allow: /",
"Sitemap index includes: https://www.stedi.com/sitemap.xml, https://www.stedi.com/docs/sitemap.xml, https://www.stedi.com/healthcare/network/sitemap.xml, and others"
],
"issues": [
"No explicit AI/TDM policy directives in robots.txt (only general allow)."
]
},
"llms": {
"sentiment": "positive",
"observation": "llms.txt is present and provides a large, structured list of deep links to developer docs and API reference pages across healthcare, providers, and EDI platform sections, plus an optional changelog link.",
"tip": "Add an explicit license/usage policy section (training vs. retrieval), a canonical API spec link (OpenAPI) if available, and highlight the MCP endpoint and authentication requirements in llms.txt for agent builders.",
"facts": [
"llms.txt includes sections: \"Docs\" and \"Optional\"",
"Links include \"Model Context Protocol (MCP)\" docs page: https://www.stedi.com/docs/healthcare/mcp-server",
"Includes extensive API reference deep links for healthcare and EDI platform"
],
"issues": [
"No explicit content license or AI usage permissions stated in llms.txt.",
"No direct OpenAPI/JSON schema spec URL provided in llms.txt (only doc links)."
]
},
"jsonld": {
"sentiment": "positive",
"observation": "JSON-LD includes WebSite and Organization entities plus a BreadcrumbList; it provides basic brand identity and social profiles but lacks richer product/service schemas.",
"tip": "Add SoftwareApplication/Product/Service schema (e.g., clearinghouse APIs), and consider adding Organization contactPoint and address to structured data for stronger entity resolution.",
"facts": [
"Schema types found: WebSite, Organization, BreadcrumbList",
"Organization sameAs includes LinkedIn and X (Twitter)"
],
"issues": [
"No Product/Service/SoftwareApplication schema present.",
"No contactPoint/email in JSON-LD."
]
},
"website": {
"sentiment": "positive",
"observation": "Homepage content is strongly product- and developer-oriented, emphasizing \"AI-ready\" JSON-native APIs, payer coverage (\"over 3,400\" U.S. payers), and includes example API calls and an MCP configuration snippet with an MCP server URL.",
"tip": "Provide a dedicated, crawlable \"API overview\" page summarizing endpoints and objects (with stable anchors) and publish an OpenAPI spec URL to improve machine extraction and RAG reliability.",
"facts": [
"Value proposition: \"The only programmable healthcare clearinghouse\"",
"Claims AI readiness: \"JSON-native. AI-ready. Well-documented APIs\"",
"Mentions MCP: \"The Stedi MCP server gives your AI agents plug-and-play access to Stedi\"",
"MCP snippet includes URL: https://mcp.us.stedi.com/2025-07-11/mcp",
"Mentions payer coverage: \"over 3,400\" and \"virtually every U.S. healthcare payer\"",
"Lists major transactions: 270/271, 837P/837D/837I, 275, 277CA, 276/277, 835",
"Security claims: HIPAA compliant, HITRUST certified, SOC 2 compliant (reports in Trust Center)"
],
"issues": [
"Some homepage text is repetitive (likely due to navigation/section duplication in scrape), which can add noise for embeddings.",
"No explicit AI/TDM usage policy visible in provided homepage text."
]
},
"policy": {
"stance": "open",
"observation": "Signals indicate broad crawl access (robots.txt Allow: /) and llms.txt is provided for AI-friendly discovery; no restrictive headers (e.g., X-Robots-Tag) or TDM reservation signals were provided.",
"license": null,
"allowed": [],
"denied": [],
"issues": [
"No explicit license or text/data-mining (TDM) reservation policy found in provided data.",
"No AI-specific policy headers (e.g., x-robots-tag, tdm-reservation) were present in the provided headers."
]
}
},
"ai_content": {
"json_feeds": [
"https://api.feedifyrss.com/stedi-platform-partners/partners/feed.json",
"https://api.feedifyrss.com/stedi-blog/blog/feed.json",
"https://api.feedifyrss.com/changelog/changelog/feed.json"
],
"mcp_server": "https://mcp.us.stedi.com/2025-07-11/mcp",
"api_endpoints": [
"https://healthcare.us.stedi.com/2024-04-01/change/medicalnetwork/professionalclaims/v3/submission",
"https://enrollments.us.stedi.com/2024-09-01/enrollments"
],
"structured_data": [
"WebSite",
"Organization",
"BreadcrumbList"
],
"machine_readable": [
"llms.txt",
"robots.txt",
"sitemap.xml (and additional sitemaps)",
"JSON Feed (via feedifyrss)",
"JSON-LD"
],
"data_exports": [
"CSV (mentioned for transaction enrollment: \"API or a CSV\")",
"Payers CSV (doc link: \"List Payers CSV\")",
"Payers JSON (doc link: \"List Payers JSON\")"
],
"embeddings_ready": true,
"crawl_friendly": true,
"notes": "Strong machine-discovery posture: llms.txt + multiple sitemaps + JSON feeds. MCP endpoint is explicitly shown on the homepage snippet; authentication via API key is indicated in the example config."
},
"strategic": {
"rag_quality": {
"assessment": "High suitability for RAG on developer documentation and product capabilities; content is link-rich and structured, with llms.txt providing deep-link coverage.",
"strengths": [
"llms.txt provides extensive, curated deep links into docs and API references.",
"Multiple sitemaps suggest comprehensive URL discovery.",
"Developer-focused content includes concrete transaction types and example requests.",
"JSON feeds available for blog/partners/changelog updates."
],
"weaknesses": [
"No explicit license/AI usage terms provided in the captured llms.txt or homepage text.",
"Homepage scrape includes repeated blocks that may add noise without deduplication."
]
},
"privacy": {
"rating": "Moderate-to-High (enterprise/security-forward signals)",
"assessment": "Homepage claims HIPAA compliance, HITRUST certification, and SOC 2 compliance with reports in a Trust Center, indicating mature security posture; however, no privacy policy text was provided in the dataset.",
"signals": [
"Strict-Transport-Security enabled (includeSubDomains; preload)",
"Security claims: HIPAA compliant, HITRUST certified, SOC 2 compliant",
"Trust Center referenced in navigation and llms.txt"
],
"concerns": [
"Privacy Notice URL is referenced in page text but not provided as a scraped policy document in this dataset.",
"No DNS verification or external trust attestations included in provided DNS data (dns_txt is empty)."
]
},
"update_cycle": {
"predicted": "Weekly to monthly",
"reasoning": "Presence of a changelog section and dedicated changelog feeds suggests ongoing product updates; blog and partners feeds also indicate regular publishing.",
"signals": [
"Changelog link in llms.txt",
"Feed endpoints for changelog/blog/partners (XML/Atom/JSON)"
]
}
},
"insights": {
"summary": "Stedi is a US-focused, API-first healthcare clearinghouse with strong AI/developer affordances (llms.txt, multiple sitemaps, JSON feeds) and an explicitly advertised MCP server endpoint for agent integration.",
"highlights": [
"robots.txt allows full crawling and enumerates multiple sitemaps.",
"llms.txt is comprehensive and heavily deep-linked into docs and API references.",
"MCP server endpoint is explicitly provided for AI agent access.",
"JSON feeds exist for blog, partners, and changelog (including JSON Feed)."
],
"anomalies": [
"Homepage includes an MCP configuration snippet but the provided mcp_config_url field is empty (config is embedded in page text rather than linked as a standalone file)."
],
"opportunities": [
"Add explicit AI/TDM licensing and permitted uses to llms.txt (and/or a dedicated policy page).",
"Publish and link an OpenAPI spec URL for the APIs to improve machine consumption.",
"Enrich JSON-LD with Product/Service schema and contactPoint/address for stronger entity resolution."
],
"concerns": [
"AI usage rights are not explicitly stated in the provided materials; downstream reuse should be treated as unspecified.",
"Some scraped homepage content is duplicated, which may require cleaning for best embedding quality."
]
},
"quality": {
"trust_signals": [
"Organization JSON-LD with official site and logo",
"Security posture claims: HIPAA, HITRUST, SOC 2; Trust Center referenced",
"HTTPS with HSTS enabled",
"Developer documentation and API references extensively linked in llms.txt",
"Multiple sitemaps and JSON feeds for updates"
],
"tech_stack": "Vercel hosting; Framer (framerusercontent.com / framerstatic.com); Algolia (search); Segment; HubSpot; Google Analytics/Tag Manager (from CSP/connect-src).",
"assessment": "High-quality, machine-discoverable developer and product source with explicit MCP endpoint and strong documentation footprint; policy/licensing for AI/TDM is the main missing piece in the provided dataset.",
"recommendation": "Include in directory (strong AI-accessible documentation and machine-readable discovery via llms.txt/sitemaps/feeds; note that AI usage license is not specified)."
}
} 