hessian.sh

Whether agents can crawl you, find you in the registries and searches they check, and trust what they find.

• ◐Sitemap present & freshrequired2/4

  Sitemap at https://hessian.sh/sitemap.xml is valid XML with 1 entries but contains no <lastmod> dates

  fix → Publish /sitemap.xml, reference it from robots.txt, and include <lastmod> dates so agents can tell what's current. Freshest lastmod seen: none.

  Resolved the sitemap from robots.txt or /sitemap.xml, validated XML, and checked lastmod freshness

  spec ↗report issue
• ◐Brand search discoverabilityrequired2/4

  Search "Hessian agent tools" cited hessian.sh (https://hessian.sh/, https://internal.hessian.sh/), but search "Hessian" did not cite your domain

  fix → Your domain doesn't surface when agents search "Hessian". Strengthen brand pages, structured data, and third-party citations (docs portals, GitHub, directories).

  Ran clean brand-name web searches and checked whether your domain is cited in the results

  report issue
• —MCP registry listingsrecommendedna

  No MCP server detected for this product

  Queried the official MCP registry, Smithery, Glama, and PulseMCP for servers matching your domain

  spec ↗report issue

Whether your robots policy, bot protection, and agent guidance actively admit AI agents instead of blocking them.

• ✓robots.txt present & parseablerequired2/2

  /robots.txt parses: 11 User-agent group(s), 1 Sitemap line(s)

  Fetched /robots.txt and validated it parses as a robots policy

  spec ↗report issue
• ✗AI crawler policyrequired0/5

  robots.txt blocks 6 of 12 AI crawler user-agents from /: GPTBot, ClaudeBot, Google-Extended, CCBot, meta-externalagent, Bytespider

  fix → robots.txt blocks GPTBot, ClaudeBot, Google-Extended, CCBot, meta-externalagent, Bytespider. Add explicit `User-agent: <bot>` / `Allow: /` groups for the AI agents you welcome; a blanket Disallow makes you invisible to them.

  Evaluated robots.txt groups for the major AI agent user-agents (GPTBot, ClaudeBot, PerplexityBot, …)

  report issue
• ◐Content Signals directivesemerging1/2

  1 Content-Signal line(s) found in robots.txt but none parse as `key=yes|no` pairs (e.g. `search=yes,ai-train=no,use=reference`)

  fix → Fix the Content-Signal syntax to comma-separated `key=yes|no` pairs, e.g. `Content-Signal: search=yes, ai-train=no`.

  Looked for Content-Signal lines in robots.txt

  spec ↗report issue
• ✓Agent user-agent paritybetarequired4/4

  All three UAs get HTTP 200; bot bodies are ClaudeBot 100%, GPTBot 100% of the browser response (158661 bytes)

  Compared responses served to browser and AI-agent user-agents (informational while in beta)

  report issue
• ✗agents.mdrecommended0/3

  No agents.md: https://hessian.sh/agents.md → HTTP 200, https://hessian.sh/AGENTS.md → HTTP 200

  fix → Add /agents.md: what agents may do on your site, key URLs, auth, rate limits, and who to contact.

  Fetched /agents.md and checked for substantive agent guidance

  spec ↗report issue

Whether your pages carry machine-readable identity: structured data, llms.txt, clear copy an agent can quote.

• ✓Homepage states what you arerequired3/3

  Homepage clarity rated 5/5 — an agent can confidently say what this company does (model's one-sentence read: "Hessian automates business operations for companies by deploying AI agents and providing a platform to build, run, and monitor these agentic workflows.")

  An LLM read your homepage as an agent would and rated how confidently it could say what you do

  report issue
• ✓OpenGraph / social metadatarecommended2/2

  Homepage has og:title, og:description, and og:image (twitter:card="summary_large_image" present)

  Parsed homepage og:title / og:description / og:image and twitter:card meta tags

  spec ↗report issue
• ✗llms.txtrecommended0/4

  /llms.txt returned HTML (content-type text/html), not markdown

  fix → Serve /llms.txt as plain markdown — an HTML page there is a routing catch-all, not an llms.txt.

  Fetched /llms.txt and validated it against the llmstxt.org shape (H1, summary, curated links)

  spec ↗report issue
• ✗llms-full.txtbonusrecommended0/2

  /llms-full.txt returned HTML (content-type text/html), not markdown

  fix → Serve /llms-full.txt as plain markdown, not an HTML page.

  Fetched /llms-full.txt and checked for substantial inline markdown content

  spec ↗report issue
• ✓JSON-LD structured datarequired4/4

  4 JSON-LD block(s) on homepage and pricing page (types: Organization, SoftwareApplication); Organization block is well-formed

  Extracted and validated application/ld+json blocks on the homepage and pricing page

  spec ↗report issue
• ✗Markdown content negotiationrecommended0/3

  GET / with `Accept: text/markdown` returned HTTP 200 text/html; no .md twins found (2 probed)

  fix → Serve text/markdown when clients send `Accept: text/markdown` (or expose .md twins of key pages) — agents get far more signal per token.

  Requested key pages with Accept: text/markdown and probed .md twin URLs

  report issue

Whether the artifacts an agent needs to build on you — docs, API specs, SDKs, MCP servers — exist and are findable.

• ◐Developer resource discoverabilityrecommended1/3

  Search "Hessian API documentation" cited no hessian.sh URL — only third-party content describes your API: https://hessian.caucho.com/doc/hessian-overview.xtp, http://wiki.caucho.com/Hessian, http://hessian.caucho.com/, http://hessian.caucho.com/doc/asdoc/hessian/io/Hessian2Input.html, http://www.caucho.com/resin-3.1/doc/hessian-1.0-spec.xtp

  fix → Create a crawlable /docs or developers.hessian.sh hub and link it from your homepage footer so search-grounded agents find your official API docs.

  Searched for your brand with developer-keyword suffixes and checked which official resources are cited

  report issue
• ✗OpenAPI spec discoverablerequired0/5

  No OpenAPI spec found: checked docs-page links and /openapi.json, /openapi.yaml, /swagger.json, /api/openapi.json, /docs/openapi.json, and api-subdomain locations

  fix → Publish your OpenAPI spec at /openapi.json and link it from docs — it's the single highest-leverage artifact for agent integration.

  Probed standard OpenAPI locations and docs links for a fetchable, parseable spec

  spec ↗report issue
• ✓Docs discoverablerequired4/4

  Docs found at https://hessian.sh/docs (via path probe, 4744 chars of readable text)

  Followed homepage nav/footer links and probed /docs, /developers, docs.{domain}

  report issue
• ✗MCP server discoveryrequired0/5

  No MCP evidence found: probed /.well-known/mcp/server-card.json, /.well-known/mcp.json, /mcp.json and scanned llms.txt, agents.md, and docs for endpoints or install commands

  fix → Publish /.well-known/mcp/server-card.json describing your MCP endpoint so agents can autodiscover it. Evidence found: none.

  Probed /.well-known/mcp/server-card.json, mcp.json, and docs mentions for an MCP endpoint

  spec ↗report issue
• ✗npm SDKrecommended0/2

  No official npm SDK found: probed 6 candidate(s) (@hessian/sdk, @hessian/hessian, hessian, hessian-sdk, hessian-api, hessian-js) — found but not domain-verified: hessian

  fix → Publish an official npm SDK (suggest @hessian/sdk) with your domain in package.json homepage so agents can verify it's official.

  Searched the npm registry for an official, domain-verified SDK package

  report issue
• ✗PyPI SDKrecommended0/2

  No official PyPI SDK found: probed 4 candidate(s) (hessian, hessian-sdk, hessianapi, hessian-python)

  fix → Publish an official Python SDK (suggest "hessian") with your domain in the project URLs so agents can verify it's official.

  Searched PyPI for an official, domain-verified SDK package

  report issue

Whether your specs, docs, and tools are complete and descriptive enough for an agent to use them without guessing.

• —OpenAPI validity & qualityrecommendedna

  No OpenAPI spec found — nothing to lint

  Linted the spec: descriptions, operationIds, securitySchemes, servers

  report issue
• ✗Docs qualityrecommended0/3

  Docs at https://hessian.sh/docs scored clarity 2/5, completeness 1/5, runnable examples 0/5, agent-friendliness 1/5 (mean 1.0/5)

  fix → Docs scored 0/5 on runnable examples. The documentation is a marketing page and provides no technical details or API specifications for an agent to integrate with.

  An LLM rated your docs for clarity, completeness, runnable examples, and agent-friendliness

  report issue
• ✗Quickstart / getting startedrecommended0/2

  No quickstart/getting-started link or heading found on docs page https://hessian.sh/docs (searched 74 links)

  fix → Add a copy-pasteable quickstart (auth → first API call) — agents follow it literally.

  Looked for a quickstart/getting-started guide containing code blocks

  report issue
• —MCP tool qualityrecommendedna

  No MCP endpoint known — tool lint requires a tools/list

  Linted listed tools for descriptions, typed input schemas, and naming

  report issue

Response hygiene, TLS and redirect discipline, and security contact channels agents depend on at runtime.

• ✓TLS & redirect hygienerequired2/2

  http://hessian.sh/ upgrades to https in 1 hop(s), 1 redirect(s) total, final HTTP 200; no HSTS header

  Checked http→https redirect behavior, chain length, and TLS health

  report issue
• ✓Response speed & weightrequired1/1

  Homepage TTFB 65ms, payload 155KB, Content-Encoding: br

  Measured homepage TTFB, payload size, and compression

  report issue
• ✗security.txtrecommended0/1

  https://hessian.sh/.well-known/security.txt returned HTML, not a plaintext security.txt

  fix → Publish RFC 9116 /.well-known/security.txt with a Contact and a future Expires.

  Fetched /.well-known/security.txt and validated Contact + Expires

  spec ↗report issue

Whether agents can discover your auth model machine-readably (OAuth metadata) and follow documented steps to credentials.

• ✗OAuth authorization server metadatarecommended0/3

  Neither /.well-known/oauth-authorization-server nor /.well-known/openid-configuration resolved (HTTP 200 / HTTP 200)

  fix → Serve RFC 8414 metadata at /.well-known/oauth-authorization-server with PKCE (S256) and a registration_endpoint so agents can self-onboard.

  Fetched /.well-known/oauth-authorization-server (and openid-configuration fallback)

  spec ↗report issue
• ✗OAuth protected resource metadatarecommended0/2

  No RFC 9728 metadata: https://hessian.sh/.well-known/oauth-protected-resource → HTTP 200

  fix → Serve RFC 9728 metadata at /.well-known/oauth-protected-resource naming your authorization servers so agents can discover how to authenticate.

  Fetched /.well-known/oauth-protected-resource

  spec ↗report issue
• ◐Auth documentationrecommended1/2

  Auth page https://hessian.sh/api_keys exists but contains no code examples

  fix → Add a runnable example (key creation → header format → example call) to your auth docs — agents follow it literally.

  Looked for /auth.md or an authentication docs page with code examples

  report issue

Whether pricing is discoverable and machine-readable, and whether you support agent payment protocols.

• ◐Pricing discoverablerequired2.5/5

  Pricing page found at https://hessian.sh/pricing (via path probe) but no legible price signals in 4744 chars of page text — no currency amounts, "per month"/"/mo", or "free plan" terms (reads as contact-sales only).

  fix → Add literal plan prices to https://hessian.sh/pricing; 'Contact sales'-only pricing means agents can't complete a purchase evaluation.

  Followed nav/footer links and probed /pricing for a page with legible price signals

  report issue
• ✗Machine-readable pricingrecommended0/5

  No pricing plans could be extracted from https://hessian.sh/pricing (extraction confidence 0.00); no Offer JSON-LD on the page.

  fix → Add Offer JSON-LD per plan (name, price, priceCurrency, billing period) to https://hessian.sh/pricing so pricing parses without inference.

  Looked for Offer JSON-LD, then had an LLM attempt structured extraction of your plans

  spec ↗report issue
• ✗x402 payment supportbonusrecommended0/2

  /.well-known/x402 returned HTTP 200 but not JSON. No x402 support detected (bonus check — absence costs nothing).

  fix → Support x402: serve payment requirements at /.well-known/x402, or answer unauthenticated API calls with HTTP 402 plus an x402 payment-requirements payload (x402Version, accepts[]).

  Probed /.well-known/x402 and API endpoints for HTTP 402 payment-required envelopes

  spec ↗report issue
• ✗AP2 readinessemerging0/1

  No AP2 hints found — scanned llms.txt, agents.md, docs page (https://hessian.sh/docs); /.well-known/ap2 returned HTTP 200.

  fix → Adopt AP2 to accept delegated agent payments — see https://ap2-protocol.org.

  Scanned fetched artifacts and well-known paths for AP2 hints

  spec ↗report issue
• ✗Agentic Commerce Protocolemerging0/1

  No Agentic Commerce Protocol hints found — scanned llms.txt, agents.md, docs page (https://hessian.sh/docs); /.well-known/acp returned HTTP 200.

  fix → Adopt the Agentic Commerce Protocol so agent checkouts can complete against your store — see https://developers.openai.com/commerce.

  Scanned docs and specs for agentic checkout endpoints

  spec ↗report issue
• ✗Other agent payment protocolsbonusemerging0/1

  No UCP/MPP hints found — scanned llms.txt, agents.md, docs page (https://hessian.sh/docs).

  fix → Track emerging agent payment protocols (UCP, MPP) and adopt the ones your buyers' agents use.

  Scanned fetched artifacts for UCP/MPP protocol hints

  report issue

Whether an end user's agent can operate on their behalf: working MCP tools, published skills, agent configs.

• —Agent skill publishedbonusemergingna

  Requires the analysis phase — not yet evaluated

  Checked /skill.md, /.well-known/skills/, and skills.sh for published agent skills

  report issue
• —MCP handshake & tools listrequiredna

  No MCP endpoint known — nothing to handshake with

  Performed a streamable-HTTP initialize + tools/list against the MCP endpoint

  spec ↗report issue
• —Agent configs in public repobonusemergingna

  Requires the analysis phase — not yet evaluated

  Checked your public GitHub org's main repos for AGENTS.md / .claude / .cursor configs

  report issue

Whether the site itself is legible to non-rendering and browser agents: semantic HTML, no JS walls, accessibility.

• ✗NLWeb endpointemerging0/1

  No NLWeb endpoint detected: /.well-known/nlweb.json returned HTTP 200 (text/html); GET /ask?query=hello returned HTTP 200 (text/html)

  fix → Consider exposing an NLWeb /ask endpoint (and /.well-known/nlweb.json) for conversational access to your content.

  Probed /.well-known/nlweb.json and the /ask endpoint

  spec ↗report issue
• ◐Semantic HTML structurerequired1.5/3

  4/6 semantic signals present on the homepage (missing: exactly one <h1> (found 2), text-to-markup ratio ≥ 0.10)

  fix → Add the missing structure: exactly one <h1> (found 2), text-to-markup ratio ≥ 0.10. Agents parse structure, not pixels.

  Scored landmark elements, heading hierarchy, and text-to-markup ratio on the homepage

  report issue
• ✓Content readable without JavaScriptrequired2/2

  Homepage raw HTML contains 4744 chars of visible text without JavaScript

  Measured visible text in the raw, unrendered homepage HTML

  report issue
• ✓Accessibility basicsrequired2/2

  Homepage accessibility: 5/5 checks passed

  Static checks: lang attribute, title, alt coverage, labeled inputs, landmarks

  report issue
• ✗WebMCPemerging0/1

  No WebMCP evidence on homepage: no application/webmcp script and no navigator.modelContext reference

  fix → Consider WebMCP to expose page actions as tools to browser agents.

  Looked for WebMCP script declarations on the homepage

  spec ↗report issue