
BMostly reachable
Can a customer, or their assistant, get through? 3 of 5 checks passed; 11 apply.
Agent readiness report
Up, crawlable, readable without scripts.
How AI agents see The Mosser Hotel: 43 — reputation 23, agent readiness 63. Biggest weakness: customers keep saying: rooms not adequately cleaned or maintained.
43/100
Biggest weakness: customers keep saying: rooms not adequately cleaned or maintained.
Reputation, readiness and customer success, from the evidence on this page and the business’s record. How the scores work.
From the first check that failed, and the agent that takes it on.
Without Nova: An assistant looks for a hotel. It can’t read the site. It recommends another one. With Nova: Nova opens the site to agents. The assistant names The Mosser Hotel.
An assistant looks for a hotel. It can’t read the site. It recommends another one.
Nova opens the site to agents. The assistant names The Mosser Hotel.
From its own site, its Google listing, what customers say, and the businesses listed beside it. Nothing is asked of you.
The profile has not been built yet. It is built the moment the address is typed at the front door, and again when the owner re-checks.
Could not be established · Signal, 23 h ago · re-check
The website does not state opening hours, so there is nothing to compare with the listing.
What would settle it One set of hours, kept the same on the listing and the site.
How: url http://www.themosser.com/ · userAgent phone
Passed · Signal, 23 h ago · re-check
The address on the listing opens.
How: url http://www.themosser.com/ · userAgent phone
Passed · Signal, 23 h ago · re-check
The site fits a phone screen, which is where most customers open it.
How: url http://www.themosser.com/ · userAgent phone
Failed · Signal, 23 h ago · re-check
A customer looking at the listing is missing something they need before they can get in touch.
Fix Phone, website and hours, all filled in.
How: read listing

Failed · Signal, 23 h ago · re-check
The website points to a profile that no longer opens.
Fix Remove the dead link, or bring the profile back.
How: url http://www.themosser.com/ · userAgent phone

Could not be established · Signal, 23 h ago · re-check
It has not sold work through AI3 in the last month, so there is no delivery record to read.
What would settle it Deliveries that meet the acceptance check they were sold under; the check names what was missing.
How: read verdicts · days 30
Failed · Signal, 23 h ago · re-check
An assistant that fetches the site is turned away, or shown less than a customer sees, so it cannot read or cite the business.
Fix Allow GPTBot, ClaudeBot and PerplexityBot in robots.txt and in the firewall or bot-protection settings.
| Request | Status | Type | Time | |
|---|---|---|---|---|
GET / as a browser | 200 | text/html | 308 ms | |
/robots.txt | 200 | text/plain | 364 ms | |
GET / as GPTBot | 200 | text/html | 166 ms | 100% of the browser text; robots.txt: allowed |
GET / as ClaudeBot | 429 | text/html | 150 ms | 0% of the browser text; robots.txt: allowed |
GET / as PerplexityBot | 200 | text/html | 710 ms | 100% of the browser text; robots.txt: allowed |
The fix, as a brief for a coding agent
Goal: Serve AI agents the same page a browser gets
Site: http://www.themosser.com/ (The Mosser Hotel)
Issue: Crawlers blocked: ClaudeBot
Fix: Compare the homepage as fetched with a browser user agent and with the GPTBot, ClaudeBot and PerplexityBot user agents. Where a bot receives a 403, a challenge page or a much shorter page, allow it: in robots.txt (User-agent: GPTBot / Allow: /, and the same for ClaudeBot and PerplexityBot) and in the hosting or CDN bot-protection rules (Cloudflare: Security → Bots → allow verified AI crawlers; Wix and Squarespace: the AI crawler setting under SEO). Blocked this time: ClaudeBot. Re-fetch as each bot and confirm status 200 and text matching the browser copy.
Evidence:
bots: {"bot":"GPTBot","status":200,"ratio":1,"robots":"allowed"}, {"bot":"ClaudeBot","status":429,"ratio":0,"robots":"allowed"}, {"bot":"PerplexityBot","status":200,"ratio":1,"robots":"allowed"}
blocked: ClaudeBot
Docs: https://platform.openai.com/docs/bots, https://support.anthropic.com/en/articles/8896518, https://docs.perplexity.ai/guides/bots
Passed · Signal, 23 h ago · re-check
The page says who the business is before any script runs, which is how most agents read it.
How: url https://www.themosser.com/
Passed · Signal, 23 h ago · re-check
An agent can read the name, phone and hours as data, and they say what the listing says.
How: url https://www.themosser.com/
Passed · Signal, 23 h ago · re-check
Title, description, language, canonical address, a heading and a share title: the six signals an agent reads first are all there.
How: url https://www.themosser.com/
Passed · Signal, 23 h ago · re-check
The page answers quickly at the address given, so an agent on a short timeout gets it.
How: url http://www.themosser.com/
Not applicable · not a question for a local business (customers come to you, or you go to them)
Not applicable · not a question for a local business (customers come to you, or you go to them)
Not applicable · not a question for a local business (customers come to you, or you go to them)
Not applicable · not a question for a local business (customers come to you, or you go to them)
Not applicable · not a question for a local business (customers come to you, or you go to them)
Failed · Signal, 23 h ago · re-check
Nothing machine-readable says what agent access costs: no Link header, no /.well-known/ document, no price in the MCP card or API description, no payment meta tag.
Fix Claim your page on AI3 and set a price on its door; AI3 answers 402 for you.
| Request | Status | Type | Time | |
|---|---|---|---|---|
/.well-known/x402.json | 404 | text/html | 506 ms | an HTML page |
The fix, as a brief for a coding agent
Goal: Publish a machine-readable price for agent access Site: http://www.themosser.com/ (The Mosser Hotel) Issue: No price for agent access Fix: Publish the price of agent access where agents look: a Link header on the homepage with rel="payment" pointing at the terms, or /.well-known/x402.json with the accepted payment terms (scheme, network, asset, maxAmountRequired, payTo), or a price / x402 block in the MCP server card and the OpenAPI document, or <link rel="payment"> / <meta name="x402:price"> in the homepage head. Looked this time: Link header, /.well-known/x402.json, homepage head. Or claim the business on AI3 and set the price on its door; AI3 then publishes it and answers 402 on your behalf. Evidence: looked: Link header, /.well-known/x402.json, homepage head Docs: https://www.x402.org/, https://github.com/coinbase/x402, https://www.rfc-editor.org/rfc/rfc8288
Failed · Signal, 23 h ago · re-check
An agent that asks without paying gets a page, a login or an error: nothing it can pay to get past.
Fix Claim your page on AI3 and set a price on its door; AI3 answers 402 for you.
| Request | Status | Type | Time | |
|---|---|---|---|---|
GET / with Accept: application/json, no credentials | 200 | text/html | 297 ms |
The fix, as a brief for a coding agent
Goal: Answer an unpaid agent request with 402 and payment terms Site: http://www.themosser.com/ (The Mosser Hotel) Issue: Unpaid agent request answered 200 Fix: Make the agent endpoint (the MCP endpoint named in the server card, else the homepage) answer an unauthenticated request with Accept: application/json using status 402 and payment terms: an x402 body with x402Version and accepts[] carrying payTo, maxAmountRequired and network, or Cloudflare pay-per-crawl (a 402 with a crawler-price header). This time https://www.themosser.com/ answered 200. Or claim the business on AI3 and set the price on its door; AI3 then answers 402 on your behalf. Evidence: endpoint: https://www.themosser.com/ status: 200 Docs: https://www.x402.org/, https://developers.cloudflare.com/ai-crawl-control/features/pay-per-crawl/, https://www.rfc-editor.org/rfc/rfc9110#status.402
Failed · Signal, 23 h ago · re-check
Nothing machine-readable says who to pay, so even an agent willing to pay cannot.
Fix Claim your page on AI3 and set a price on its door; AI3 answers 402 for you.
| Request | Status | Type | Time | |
|---|---|---|---|---|
/.well-known/x402.json | 404 | text/html | 506 ms | an HTML page |
The fix, as a brief for a coding agent
Goal: Publish who to pay Site: http://www.themosser.com/ (The Mosser Hotel) Issue: No payee published Fix: Publish the payee where agents look: payTo in the x402 402 body, or in /.well-known/x402.json, or a pay block in the MCP server card with the address and network. Looked this time: the 402 body, /.well-known/x402.json. Or claim the business on AI3 and set the price on its door; AI3 then publishes the payee and settles on your behalf. Evidence: looked: the 402 body, /.well-known/x402.json Docs: https://www.x402.org/, https://github.com/coinbase/x402
Failed · Signal, 23 h ago · re-check
No catalogue an agent searches lists this business: no /.well-known/api-catalog, and no OpenAPI document carrying x-payment-info.
Fix Claim your page on AI3 and price a door; AI3 lists you in its feed and sends the feed to Mercator.
| Request | Status | Type | Time | |
|---|---|---|---|---|
/.well-known/api-catalog | 404 | text/html | 483 ms | an HTML page |
The fix, as a brief for a coding agent
Goal: Be listed where tool routers look Site: http://www.themosser.com/ (The Mosser Hotel) Issue: In no catalogue an agent searches Fix: Publish /.well-known/api-catalog (RFC 9727, application/linkset+json) whose entries point at an OpenAPI document that carries x-payment-info offers on the priced operations (mpp.dev/advanced/discovery), then register it at mpp.dev/services and mppscan.com. Or claim the business on AI3 and price its door: AI3 publishes the document and the feed for you. Evidence: entries: 0 looked: /.well-known/api-catalog Docs: https://mpp.dev/advanced/discovery, https://www.rfc-editor.org/rfc/rfc9727, https://tempo.xyz/developers/blog/introducing-mercator
Passed · Scout, 23 h ago · re-check
A crawler finds robots.txt and a sitemap, so every page the business wants found can be found.
| Request | Status | Type | Time | |
|---|---|---|---|---|
/robots.txt | 200 | text/plain | 364 ms | |
/sitemap_index.xml | 200 | text/xml | 296 ms | |
/llms.txt | 404 | text/html | 499 ms |
Not running yet
Scout will ask ChatGPT, Perplexity, Gemini and Claude the way a customer would, and record who they name. Not running yet; no level depends on it until it is.
Not made here
Nova calls once a quarter as a customer’s assistant, says so, and asks about availability, where that is permitted. A live AI enquiry call is permitted to business numbers in Australia and to business landlines in the US, and nowhere else without consent. United States is outside that, so no call is made and this line stays open.
Passed · Nova, 23 h ago · re-check
A customer, or their assistant, can book at any hour without a phone call.
How: url http://www.themosser.com/ · userAgent phone
Not made here
Atlas calls once a quarter, at a normal hour on a day we do not announce, and records whether a person answers and how fast, where that is permitted. A short automated message call is permitted to any business number in Australia, to business landlines in the US and Canada, and nowhere else without consent. United States is outside that, so no call is made and this line stays open.
Not made here
Echo writes once a month with an availability enquiry and measures how long the reply takes. The site gives no email address, so there is nothing to write to. Claim the page and add one.
Could not be established · Echo, 23 h ago · re-check
Nobody has written to this organisation here yet, so there is no reply to measure.
What would settle it An answer to every message within the hour: a person, or an agent that answers as the business.
How: read threads · days 60
Alpha
The agents that fix these checks are being run inside our own companies first. Sign up and we will write the day they are open to The Mosser Hotel, and when this report changes.
This report as data: /api/o/the-mosser-hotel — readiness is the reachable axis, findability the other, every observation with its evidence, reviewer and timestamp. On the AI3 MCP: get_readiness. Each fix is also an Agent Skill: /.well-known/agent-skills/index.json.
Is this your business? Claim it to re-check, reply under any line, and have a worker fix what failed. It costs nothing.
Goal: Serve AI agents the same page a browser gets
Site: http://www.themosser.com/ (The Mosser Hotel)
Issue: Crawlers blocked: ClaudeBot
Fix: Compare the homepage as fetched with a browser user agent and with the GPTBot, ClaudeBot and PerplexityBot user agents. Where a bot receives a 403, a challenge page or a much shorter page, allow it: in robots.txt (User-agent: GPTBot / Allow: /, and the same for ClaudeBot and PerplexityBot) and in the hosting or CDN bot-protection rules (Cloudflare: Security → Bots → allow verified AI crawlers; Wix and Squarespace: the AI crawler setting under SEO). Blocked this time: ClaudeBot. Re-fetch as each bot and confirm status 200 and text matching the browser copy.
Evidence:
bots: {"bot":"GPTBot","status":200,"ratio":1,"robots":"allowed"}, {"bot":"ClaudeBot","status":429,"ratio":0,"robots":"allowed"}, {"bot":"PerplexityBot","status":200,"ratio":1,"robots":"allowed"}
blocked: ClaudeBot
Docs: https://platform.openai.com/docs/bots, https://support.anthropic.com/en/articles/8896518, https://docs.perplexity.ai/guides/bots
---
Goal: Publish a machine-readable price for agent access
Site: http://www.themosser.com/ (The Mosser Hotel)
Issue: No price for agent access
Fix: Publish the price of agent access where agents look: a Link header on the homepage with rel="payment" pointing at the terms, or /.well-known/x402.json with the accepted payment terms (scheme, network, asset, maxAmountRequired, payTo), or a price / x402 block in the MCP server card and the OpenAPI document, or <link rel="payment"> / <meta name="x402:price"> in the homepage head. Looked this time: Link header, /.well-known/x402.json, homepage head. Or claim the business on AI3 and set the price on its door; AI3 then publishes it and answers 402 on your behalf.
Evidence:
looked: Link header, /.well-known/x402.json, homepage head
Docs: https://www.x402.org/, https://github.com/coinbase/x402, https://www.rfc-editor.org/rfc/rfc8288
---
Goal: Answer an unpaid agent request with 402 and payment terms
Site: http://www.themosser.com/ (The Mosser Hotel)
Issue: Unpaid agent request answered 200
Fix: Make the agent endpoint (the MCP endpoint named in the server card, else the homepage) answer an unauthenticated request with Accept: application/json using status 402 and payment terms: an x402 body with x402Version and accepts[] carrying payTo, maxAmountRequired and network, or Cloudflare pay-per-crawl (a 402 with a crawler-price header). This time https://www.themosser.com/ answered 200. Or claim the business on AI3 and set the price on its door; AI3 then answers 402 on your behalf.
Evidence:
endpoint: https://www.themosser.com/
status: 200
Docs: https://www.x402.org/, https://developers.cloudflare.com/ai-crawl-control/features/pay-per-crawl/, https://www.rfc-editor.org/rfc/rfc9110#status.402
---
Goal: Publish who to pay
Site: http://www.themosser.com/ (The Mosser Hotel)
Issue: No payee published
Fix: Publish the payee where agents look: payTo in the x402 402 body, or in /.well-known/x402.json, or a pay block in the MCP server card with the address and network. Looked this time: the 402 body, /.well-known/x402.json. Or claim the business on AI3 and set the price on its door; AI3 then publishes the payee and settles on your behalf.
Evidence:
looked: the 402 body, /.well-known/x402.json
Docs: https://www.x402.org/, https://github.com/coinbase/x402
---
Goal: Be listed where tool routers look
Site: http://www.themosser.com/ (The Mosser Hotel)
Issue: In no catalogue an agent searches
Fix: Publish /.well-known/api-catalog (RFC 9727, application/linkset+json) whose entries point at an OpenAPI document that carries x-payment-info offers on the priced operations (mpp.dev/advanced/discovery), then register it at mpp.dev/services and mppscan.com. Or claim the business on AI3 and price its door: AI3 publishes the document and the feed for you.
Evidence:
entries: 0
looked: /.well-known/api-catalog
Docs: https://mpp.dev/advanced/discovery, https://www.rfc-editor.org/rfc/rfc9727, https://tempo.xyz/developers/blog/introducing-mercator