relayto.com
Finalizing the report
Preparing the stored Is Agentic score
relayto.com
Preparing the stored Is Agentic score
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.
No material issues were found in the applicable checks.
Checks are grouped by relevance for App sites.
Homepage: 13699 chars, semantic headings (1 H1 + 10 H2s + 29 H3s), 11.7% content ratio. 5 of 5 sampled inner pages have text without JavaScript.
Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot).
No meta-refresh or JavaScript-redirect stubs across 12 checked pages
All 5 sampled pages are publicly readable (4 with substantive content)
OpenAPI spec found at https://relayto.com/openapi.json (version: 3.1.0)
Canonical URL serves text/markdown and text/html via Accept negotiation with Vary: Accept
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)
API returns JSON error responses (400 at GET https://relayto.com/api/site/v1/search, an operation in the OpenAPI spec)
MCP server exposes 10 resource(s) via resources/list
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://relayto.com/sitemap.xml with multiple sitemaps entries
Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (2 blocks)
Pricing page found at /pricing
API/docs link found on homepage and resolves: /developers
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 11 measured pages fit an agent context budget (largest ~5K tokens)
REST API from the OpenAPI spec is live: GET https://relayto.com/api/site/v1/ answered 200 without credentials. NLWeb /ask endpoint returns valid response (type: failure, version: 0.55, via GET). Best-of-protocols score: 7/7.
Zero-friction onboarding verified live: keyless API surface fetched without credentials - no signup step exists
MCP server connected via Streamable HTTP - com.relayto/docs v1.0.0 (protocol 2025-11-25)
The live API operation https://relayto.com/api/site/v1/ returns IETF RateLimit headers: ratelimit, ratelimit-limit, ratelimit-policy.
OpenAPI uses application/problem+json (RFC 7807) for 4xx/5xx responses
API versioning strategy found (URL versioning) with Deprecation and Sunset headers documented at https://relayto.com/openapi.json
CLI package found on npm: relayto
90% of operations define typed response schemas, 90% use application/json
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
10/10 resources read with valid mimeType and non-empty content
ARD catalog valid at /.well-known/ard.json (spec 1.0) - 14/14 entries, trustManifest present
Valid AI Catalog at /.well-known/ai-catalog.json (spec 1.0) - 14/14 entries
All 14 entries valid with domain-anchored urn:air identifiers (catalog at /.well-known/ard.json)
14 of 14 manifests in trustManifest valid (catalog at /.well-known/ard.json)
In a search for your API docs, your docs came up at #1 (https://relayto.com/developers). In a search for your MCP server, SDK or CLI, we found your MCP server at #1 (https://relayto.com/hub/api), SDK at #1 (https://relayto.com/hub/api), CLI at #1 of the docs search (https://relayto.com/developers)
relayto.com ranks #1 for "RELAYTO" (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."
Agent config found: github.com/relayto/relayto-mcp/blob/main/AGENTS.md
Agent Plugins manifest found: github.com/relayto/relayto-mcp/blob/main/plugin.json
MCP manifest has full branding (name, icon, description) at https://relayto.com/.well-known/mcp/server-card.json
Agent Skills index (agentskills.io) found at /.well-known/agent-skills/index.json with 5 skill(s)
Index v0.2.0 conformant; verified SHA-256 of "relayto-analytics" (skill-md); 4 other skills present; not fetched
A2A Agent Card found: "RELAYTO docs"
Structured pricing.md found at /pricing.md (409 lines)
MCP server discoverable via server-card.json at /.well-known/mcp/
Rich agent mode view at ?mode=agent with 4 agent signals and navigation links
RFC 8288 Link header advertises: sitemap, describedby, service-desc, service-doc, api-catalog, alternate(markdown)
Full markdown fallback support. Homepage (https://relayto.com/index.md) and all 3 sampled content pages return markdown: https://relayto.com/explore/02-how-to-use-auto-animations-ubf71xfh4qwgs.md, https://relayto.com/explore/distributing-relayto-experiences-via-mass-email-with-personalized-tracking-6859303790b7d.md, https://relayto.com/explore/infocomm-brand-book-9h997ttcyiae5.md
Modular llms.txt files found for sections: developers, pricing, platform, ai, enterprise
100% of 500 sampled sitemap entries carry lastmod; newest is 1 day(s) old
Found the llms.txt at https://relayto.com/llms.txt.
The llms.txt is well-formatted: 69 lines with markdown links, 9,402 characters in total.
Agent Skill "relayto-analytics" says when to use it at /.well-known/agent-skills/index.json - description: "Use when the user asks how a deck, report, proposal or hub performed, who viewed it, which..."
Strong entity linking via sameAs: linkedin.com, github.com, crunchbase.com
Schema types that match what the homepage shows: FAQPage. Lists on the homepage with no schema type: "For the communications that can’t afford to be misread" (5 items), "Interactive experiences in place of PDF attachments" (5 items), "Built for regulated, high-stakes industries" (5 items)
All 5 probed llms.txt links resolve to real content
Markdown alternate advertised and verified: https://relayto.com/index.md serves markdown
Frontmatter with title + description and canonical on /mcp.md
Code fences balanced across 2 markdown documents
Developer portal found at /developers
RFC 9727 api-catalog with 2 API link(s) and rfc9727 profile
Path-suffix markdown docs served with text/markdown content-type: /llms.md, /mcp.md, /developers.md, /auth.md, /index.md
https://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/docs" 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
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
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://relayto.com/auth.md served as text/markdown; charset=utf-8 (4251 chars)
WorkOS auth.md structure at https://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
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 /_astro/webmcp-tools.ctfGOsB4.js).
REST Idempotency-Key header referenced on POST /exports via #/components/parameters/IdempotencyKey
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
SDK package found only in npm
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)
docs MCP: 3/3 tools have behavioral annotations
MCP server card found at https://mcp.relayto.com/mcp/server-card (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://relayto.com/mcp) for documentation.
Sandbox environment found at https://relayto.com/docs/sandbox
Server HTML is a well-structured document (main=true, landmarks=4/4, h1=1, maxHeadingSkip=1).
189 native controls, 0 non-native div-soup affordances (100% native).
189/189 interactive elements have a computable accessible name (100%).
18/18 form controls have an associated label (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
What does 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 relayto.com do and who is it for? Explain it back to me.
14 steps3 reasoning steps2 searches
The agent successfully gathered a comprehensive overview of RELAYTO's core offering, target audiences, and pricing tiers by combining homepage meta descriptions, direct navigation to pricing pages, and web search results for competitive context. The site exposed key information through semantic HTML (title tags, meta descriptions) and dedicated pricing pages, though detailed feature matrices and plan differentiation remained partially obscured behind dynamic page rendering or incomplete content access.