Parlour

Name: Parlour AI agent readiness scorecard
Item: Parlour
Rating: 48
Author: Stunt Double

heyparlour.app

Claim this domain

Overall score

48.0Poor

▲ 13.0

Rank

#488

Prev: #0 · top 74% of 655 tracked

Developer tools rank

#1 of 1

Sector average 48.0

Benchmark runs

1 domain on the index claimed by owners

A voice for your home. Private by design.

Markets: GB
Locales: en-gb

Category breakdown

Brand awarenessCan agents recognise you exist?

▲ 6.9

DiscoveryWill they pick you?

▲ 22.2

Information retrievalCan they read your site?

▲ 7.2

Market rankingWhere do you sit in the lineup?

▲ 12.0

AccuracyDo they tell the truth about you?

▼ 8.4

Task completionCan an agent complete a task on behalf of a user?

▲ 9.3

Delegated accessDo you let agents in, safely?

▲ 33.3

Contact & communicationCan an agent reach a human?

▲ 53.4

By agent provider

ChatGPT Agent
OpenAI
0.0

Session quality over a rolling 30 days, from at least 10 sessions per provider.

Where agents get stuck

The public summary. Verified owners can replay every session in full.

mediumBrand awareness

No Organization JSON-LD. Agents can’t tell who owns the site at a glance.

lowBrand awareness

Missing Open Graph tags. Link previews degrade in agent chats.

lowBrand awareness

Fewer than two social profiles linked. Agents struggle to triangulate the brand.

mediumDiscovery

No robots.txt. Agents fall back to defaults and may miss crawl hints.

mediumDiscovery

No sitemap.xml. Agents can’t enumerate indexable pages.

lowDiscovery

No canonical URL. Agents may conflate duplicate pages as separate entities.

mediumInformation retrieval

No JSON-LD structured data. Agents must infer entities from markup.

mediumMarket ranking

No Product/Service schema on the homepage. Agents can’t easily compare offerings.

lowMarket ranking

No review or aggregateRating schema. Agents have no signal for ranking vs peers.

mediumMarket ranking

No price visible to non-JS clients. Agents may report "pricing not disclosed".

lowAccuracy

No canonical URL. Agents may cite ephemeral query-string variants.

mediumAccuracy

No JSON-LD at all. Every factual claim must be inferred from prose.

highTask completion

No reachable entry point for delegated tasks: nothing at `/pricing`, `/signup`, `/cart`, `/book`, or similar responds without auth.

lowTask completion

No detectable agentic-commerce rail (Stripe SPT, Shopify/UCP, PayPal ACP). Agent-initiated payment needs custom work.

mediumTask completion

No mention of delegated auth primitives (passkey, OAuth, MCP). Agents must drive a full browser session.

highDelegated access

No discoverable MCP server. ChatGPT apps and Claude connectors have no scoped way to call your product; agents must drive a browser instead.

mediumDelegated access

No OAuth/OIDC discovery metadata. Agents cannot bootstrap a scoped, revocable session; any delegation falls back to password sharing.

highDelegated access

No public API docs detected. Agents have no scoped way in; they must drive a browser.

highContact & communication

No contact page linked or reachable. Agents acting on a user’s behalf have nowhere to send a message.

mediumContact & communication

No contact email visible in server-rendered HTML. Agents can’t fall back to email.

lowContact & communication

No help, support, or FAQ hub linked. Agents can’t self-serve an answer before reaching out.

Technical readiness

Protocol baseline by Is Agentic

Score

56 / 100

Important blockers remain

Essential

48.9 / 80

5 of 9 passing

Recommended

5.3 / 20

3 of 15 passing

Bonus

+1.6

7 positive signals

Fail
OpenAPI spec publishedessential
No OpenAPI/Swagger specification found
Fix: Publish an OpenAPI (Swagger) specification at /openapi.json or /api/openapi.yaml. This is how agents understand your API surface automatically.
Fail
JSON error responsesessential
API does not return JSON error responses (or no API detected)
Fix: Return structured JSON error responses with error codes, messages, and resolution hints. Agents can't parse HTML error pages.
Fail
Markdown content negotiation (acceptmarkdown.com)essential
Homepage https://heyparlour.app does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html; charset=utf-8; Vary header missing Accept (got "rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch")
Fix: Enable Markdown negotiation on the scanned homepage. Supporting it only on /docs or a separate .md URL does not satisfy this check. Requests with Accept: text/markdown must receive a nonempty Markdown body with Content-Type: text/markdown and Vary: Accept. Keep serving HTML for Accept: text/html. Adding Vary alone does not create a Markdown response. Verify both with `curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/` and `curl -sS -L -i -H 'Accept: text/html' https://yourdomain.com/`. Check the final response headers and body: Markdown with Vary: Accept for the first request, HTML for the second.
Fail
Developer resource discoverabilityrecommended
Agent searched for "parlour" developer resources but found nothing relevant
Fix: Check whether your developer resources (API docs, OpenAPI spec, auth docs, developer portal, MCP server, SDK documentation) surface in name-based searches. If they do not, use predictable URLs, link them in llms.txt, and include your product name in page titles and headings. This result reflects one search sample.
Fail
Brand name discoverabilityrecommended
"Parlour" search returned 10 results but domain did not appear - brand may be too generic or not indexed
Fix: Make sure a clean search for your brand name returns your own domain in the top results. If it does not, your brand may be too generic, conflict with a more established term, or not yet indexed. Strengthen brand-name search by claiming consistent NAP across listings, earning press mentions that link to the canonical domain, and avoiding redirect chains that mask the apex domain in search results.

24 checks · scanned 25 Sept 2026 · 11 more in the full report

Embed this score

A live badge for your site or README.