benefits.relayto.com
Finalizing the report
Preparing the stored Is Agentic score
benefits.relayto.com
Preparing the stored Is Agentic score
benefits.relayto.com
These checks describe whether an ordinary agent can enter, read, and operate the public site.
Agents can reach the site
Crawler access and bot defenses.
Core content is available
Useful content remains accessible without a fragile browser-only path.
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
Controls are understandable
Forms and interactive controls expose usable names and structure.
The public website is always evaluated. Optional surfaces appear when the scan finds positive evidence that they apply.
Strong
Weighted across 17 applicable checks
Strong
Weighted across 12 applicable checks
Strong
Weighted across 3 applicable checks
Strong
Weighted across 3 applicable checks
Critical access gaps come first, followed by other applicable readiness gaps.
Serve at least 500 characters of meaningful homepage content in raw HTML. Add a clear H1, keep deeper heading levels sequential, and remove excessive non-content markup. Inner pages need their main text in the raw HTML too, not only after JavaScript runs.
Checks are grouped by relevance for Docs & content sites.
Homepage: 14115 chars, semantic headings (1 H1 + 118 H2s), 7.4% content ratio. Sampled pages with almost no text without JavaScript (4 of 5): https://benefits.relayto.com/e/foam-rolling-circuit-qspn8rw4iieg4 (119 chars), https://benefits.relayto.com/e/meditation-break-chance-p5nvz8z6wttvn (116 chars), and https://benefits.relayto.com/e/prescription-drug-rebates-explained-o02v2hdj4xupw (178 chars).
How to pass
Serve at least 500 characters of meaningful homepage content in raw HTML. Add a clear H1, keep deeper heading levels sequential, and remove excessive non-content markup. Inner pages need their main text in the raw HTML too, not only after JavaScript runs.
Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot).
No meta-refresh or JavaScript-redirect stubs across 16 checked pages
All 5 sampled pages are publicly readable (1 with substantive content)
Canonical URL serves text/markdown and text/html via Accept negotiation with Vary: Accept
Nonexistent paths return HTTP 404 with markdown guidance for agents - the strongest 404 contract
No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search.
Valid sitemap found at https://benefits.relayto.com/sitemap.xml with 135 entries
Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (1 block)
All metadata signals present: canonical URL, lang="en", og:image, og:type
Organization schema complete with contactPoint and address
All trust anchor pages verified: About, Contact, Privacy
All 9 measured pages fit an agent context budget (largest ~7K tokens)
ARD catalog valid at /.well-known/ard.json (spec 1.0) - 11/11 entries, trustManifest present
Valid AI Catalog at /.well-known/ai-catalog.json (spec 1.0) - 11/11 entries
All 11 entries valid with domain-anchored urn:air identifiers (catalog at /.well-known/ard.json)
11 of 11 manifests in trustManifest valid (catalog at /.well-known/ard.json)
benefits.relayto.com ranks #1 for "RELAYTO AI for Benefits" (searched your brand name alone: no main product term from your homepage qualified)
Verified in 2 registries: the official MCP Registry (com.relayto/mcp) [domain-namespace], npm (relayto-mcp) [package-owner]
NPM package found: relayto - "Official RELAYTO SDK and CLI: search and read the pages, hubs and documents of any site published with RELAYTO through its public API. No API key."
MCP manifest has full branding (name, icon, description) at https://benefits.relayto.com/.well-known/ai-catalog.json
Agent Skills index (agentskills.io) found at /.well-known/agent-skills/index.json with 1 skill(s)
Index v0.2.0 conformant; verified SHA-256 of "benefits-relayto-com" (skill-md)
MCP server card listed in /.well-known/ai-catalog.json
Agent mode view found at ?mode=agent (3 signals: openapi, mcp, api)
How to pass
Add a ?mode=agent query parameter to your homepage that returns a structured, machine-readable view with API endpoints, authentication info, and key capabilities instead of marketing HTML.
RFC 8288 Link header advertises: service-desc, service-doc, api-catalog, alternate(markdown)
Full markdown fallback support. Homepage (https://benefits.relayto.com/index.md) and all 3 sampled content pages return markdown: https://benefits.relayto.com/e/2024-pet-webinar-flyer-7sd07sksjm7bt.md, https://benefits.relayto.com/e/foam-rolling-circuit-qspn8rw4iieg4.md, https://benefits.relayto.com/e/meditation-break-chance-p5nvz8z6wttvn.md
Modular llms.txt files found for sections: developers, docs/sandbox
100% of 135 sampled sitemap entries carry lastmod; newest is 0 day(s) old
Found the llms.txt at https://benefits.relayto.com/llms.txt.
The llms.txt is well-formatted: 160 lines with markdown links, 29,812 characters in total.
Pricing page found at /pricing
Documentation found at /docs but not linked from homepage
How to pass
Publish API documentation at a discoverable URL (/docs, /api, /developers). Include authentication, endpoints, and example requests.
Agent Skill "benefits-relayto-com" says when to use it at /.well-known/agent-skills/index.json - description: "Use when a question is about RELAYTO AI for Benefits or its published material, or when th..."
Strong entity linking via sameAs: linkedin.com, github.com
All 5 probed llms.txt links resolve to real content
Markdown alternate advertised and verified: https://benefits.relayto.com/index.md serves markdown
Frontmatter with title + description, canonical, and last-updated on /index.md
Code fences balanced across 1 markdown document
OpenAPI spec found at https://benefits.relayto.com/openapi.json (version: 3.1.0)
Developer portal found at /developers
RFC 9727 api-catalog with 1 API link(s) and rfc9727 profile
Path-suffix markdown docs served with text/markdown content-type: /developers.md, /auth.md, /index.md
https://benefits.relayto.com serves markdown to the ChatGPT-User User-Agent even with Accept: text/html - UA-sniffed agent responses in place
All 3 tools on docs MCP have detailed descriptions (>= 30 chars)
3/3 tools on docs MCP have parameter schemas
docs MCP identifies as "com.relayto/site-content" v1.0.0 with instructions
docs MCP exposes 3 tool(s) - focused docs surface
All 3 tool names follow consistent convention, descriptive, and non-generic
REST API documentation found at /docs/api. Best-of-protocols score: 7/7.
OAuth authorization server metadata at https://mcp.relayto.com (issuer=https://mcp.relayto.com)
scopes_supported declares 1 scope(s) in RFC 9728 metadata (e.g. email)
product MCP requires authentication with OAuth metadata discovery
RFC 8414 OAuth metadata for product MCP: issuer=https://mcp.relayto.com, auth and token endpoints present; client registration: CIMD (client_id_metadata_document_supported)
OAuth metadata for product MCP supports PKCE S256 code challenge
Zero-friction onboarding verified live: keyless API surface fetched without credentials - no signup step exists
RFC 9728 metadata at https://mcp.relayto.com: resource=https://mcp.relayto.com/mcp, authorization_servers (1), scopes_supported (1), bearer_methods_supported
auth.md at https://benefits.relayto.com/auth.md served as text/markdown; charset=utf-8 (5000 chars)
WorkOS auth.md structure at https://benefits.relayto.com/auth.md - 7/8 walkthrough sections (found Discover, Pick a method, Register, Claim, Use credential, Errors, and Revocation); anchors: oauth-protected-resource, oauth-authorization-server, and agent_auth; register shapes: id-jag shape
Static fallback: PRM + AS metadata both reachable but AS metadata lacks an agent_auth block; walkthrough cannot identify a registration template
How to pass
Make your published auth-discovery chain traversable end to end: an agent starting at /auth.md (or your protected-resource metadata) should be able to follow the links to your authorization-server metadata and registration endpoint without hitting a dead link. Test the whole path, not just each file in isolation.
PRM + AS metadata both present (PRM discovered at https://mcp.relayto.com) (AS metadata fetched from advertised origin https://mcp.relayto.com) but AS metadata has no agent_auth block
How to pass
Publish RFC 9728 protected-resource metadata at /.well-known/oauth-protected-resource on your resource server (the host that actually serves the API, e.g. api.<apex>) with resource and authorization_servers. Publish RFC 8414 authorization-server metadata at /.well-known/oauth-authorization-server on the AS origin, and include the WorkOS auth.md agent_auth block with identity_endpoint, identity_types_supported drawn from the spec enum (anonymous, identity_assertion, service_auth - the assertion variant, the ID-JAG URN urn:ietf:params:oauth:token-type:id-jag, belongs inside identity_assertion.assertion_types_supported, not at the top level), and the identity_assertion.assertion_types_supported block when you advertise that type, so agents can check their assertion shape is accepted before minting. Cross-link by listing the AS origin in PRM authorization_servers, and point agent_auth.skill back at your published /auth.md. Spec: https://github.com/workos/auth.md.
401 at https://mcp.relayto.com at /mcp with spec-shaped WWW-Authenticate hint: Bearer realm="OAuth", resource_metadata="https://mcp.relayto.com/.well-known/oauth-protected-resource/mcp", error="inval
MCP server detected at https://mcp.relayto.com/mcp; it requires authentication. Presence is verified (5/6), but Ora could not inspect its tools or verify access scopes without credentials.
How to pass
Keep authentication enabled. Verify tool listing with an authorized MCP client. This unauthenticated scan cannot establish whether protected tools are missing or unusable.
docs MCP returns structured JSON-RPC errors with code and message
docs MCP uses modern Streamable HTTP transport
Imperative WebMCP API detected (document.modelContext.registerTool in script bundle /webmcp/workspace-tools-v2.js).
The live API operation https://benefits.relayto.com/api/site/v1/ returns IETF RateLimit headers: ratelimit, ratelimit-limit, ratelimit-policy.
REST Idempotency-Key header referenced on POST /exports via #/components/parameters/IdempotencyKey
API returns JSON error responses (400 at GET https://benefits.relayto.com/api/site/v1/search, an operation in the OpenAPI spec)
OpenAPI uses application/problem+json (RFC 7807) for 4xx/5xx responses
API versioning found (URL versioning (servers or paths)) but no deprecation or sunset policy detected - add Sunset/Deprecation headers or a deprecation policy page
How to pass
Declare a versioning policy agents can rely on: version your API (in the URL path or a version header) and publish how you signal deprecation (a Sunset/Deprecation header or a documented timeline). Agents avoid integrating against a surface that can change without warning.
Cursor-based pagination found in OpenAPI spec response schemas or query parameters
Async job pattern detected: 202 Accepted with a Location header or job-tracking fields on the 202 body
CLI package found on npm: relayto
SDK found in npm, additional SDKs mentioned at https://benefits.relayto.com/developers.md
How to pass
Publish official SDK packages across multiple language ecosystems (npm, PyPI, Go modules, RubyGems). Auto-generate them from your OpenAPI spec using tools like openapi-generator. For each package set the project URL or homepage to your product domain (package.json repository/homepage, PyPI Home-Page or project_urls, RubyGems homepage_uri) - this is how agents verify the package is your official SDK.
NLWeb /ask endpoint returns valid response (type: failure, version: 0.55, via GET)
NLWeb /ask supports SSE streaming with valid event data (via GET)
90% of operations define typed response schemas, 90% use application/json
docs MCP: 3/3 tools have behavioral annotations
MCP server card found at https://benefits.relayto.com/.well-known/ai-catalog.json (server-card extension, all required fields)
You run both: a product MCP server (https://mcp.relayto.com/mcp) for actions and a docs MCP server (https://benefits.relayto.com/mcp) for documentation.
Sandbox environment found at https://benefits.relayto.com/docs/sandbox
MCP server exposes 2 resource(s) via resources/list
Server HTML is a well-structured document (main=true, landmarks=3/4, h1=1, maxHeadingSkip=1).
256 native controls, 0 non-native div-soup affordances (100% native).
256/256 interactive elements have a computable accessible name (100%).
4/4 form controls have an associated label (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
REST: agent-friendly schema (10 operations, 100% with operationIds, 100% documented by description or summary)
Compatible: 10/10 ops with IDs, 9/10 with typed schemas
2/2 resources read with valid mimeType and non-empty content
What does benefits.relayto.com do and who is it for? Explain it back to me.
Sign me up for Vercel product updates and marketing emails.
Unsubscribe anytime. Privacy Notice
Source: Ora API
What does benefits.relayto.com do and who is it for? Explain it back to me.
6 steps1 reasoning step
The agent read the benefits subdomain, its sitemap, and the main relayto.com pricing page, producing a solid account of the product, audience, and pricing, though it could not address competitive differentiation. Navigation was workable: the sitemap and linked pages surfaced the key content, but the subdomain itself has no pricing or about page, forcing the agent to the main site.