Agent readiness report
TEMPUR | BEDQUARTER
Up, crawlable, readable without scripts.
How AI agents see TEMPUR | BEDQUARTER: 24 — reputation 6, agent readiness 41.
24/100
Reputation, readiness and customer success, from the evidence on this page and the business’s record. How the scores work.
A customer TEMPUR | BEDQUARTER is missing right now.
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 TEMPUR | BEDQUARTER.
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 TEMPUR | BEDQUARTER.
Business research & sources
Building the profile of TEMPUR | BEDQUARTER
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.
How AI agents see it
How readiness levels work
- 0Not found
- 1Present
- 2Readable
- 3Findable
- 4Transactable
Signal Web audit agent · opens the website the way a phone does and reads the listing6/13
-
Do the listing and the website give the same hours?Hours not stated on the siteReachable
Could not be established · Signal, 1 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.
- reason
- no opening hours found on the site
- listing days
- 0
How: url https://www.bedquarter.ae/ · userAgent phone
-
Is the website up?Website up (6441 ms)Reachable
Passed · Signal, 1 h ago · re-check
The address on the listing opens.
- status
- 200
- ms
- 6441
- final url
- https://bedquarter.ae/
- https
- yes
How: url https://www.bedquarter.ae/ · userAgent phone
-
Does the website work on a phone?Works on a phoneReachable
Passed · Signal, 1 h ago · re-check
The site fits a phone screen, which is where most customers open it.
- viewport
- yes
- tap to call
- yes
- bytes
- 567747
How: url https://www.bedquarter.ae/ · userAgent phone
-
Is the listing complete?Listing missing hoursReachable
Failed · Signal, 1 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.
- present
- phone, website
- missing
- hours
- source
- file
How: read listing
Optional help · Waitlist
NovaWebmaster & SEO · AI workerfills in the listing and keeps it rightFree + usage View worker
-
Are the social profiles reachable?Profiles open (Instagram, YouTube)Reachable
Passed · Signal, 1 h ago · re-check
The profiles the website points to open.
- open
- Instagram, YouTube
- unsure
- LinkedIn, Facebook
- links
- https://www.linkedin.com/company/bed-quarter-company, https://www.instagram.com/bedquarteruae, https://youtube.com/@tempur-uae, https://www.facebook.com/BedQuarterUAE
How: url https://www.bedquarter.ae/ · userAgent phone
-
Does it deliver what it sells?Nothing sold through AI3 yetReachable
Could not be established · Signal, 1 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.
- verdicts
- 0
- reason
- no company on AI3 to sell through
How: read verdicts · days 30
-
Do AI crawlers get the same page a browser gets?Crawlers blocked: GPTBot, ClaudeBotFindable
Failed · Signal, 1 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 browser200 text/html 105 ms /robots.txt200 text/plain 56 ms GET / as GPTBot403 text/plain 39 ms 0% of the browser text; robots.txt: allowed GET / as ClaudeBot403 text/plain 68 ms 0% of the browser text; robots.txt: allowed GET / as PerplexityBot200 text/html 99 ms 100% of the browser text; robots.txt: allowed - bots
- {"bot":"GPTBot","status":403,"ratio":0,"robots":"allowed"}, {"bot":"ClaudeBot","status":403,"ratio":0,"robots":"allowed"}, {"bot":"PerplexityBot","status":200,"ratio":1,"robots":"allowed"}
- blocked
- GPTBot, ClaudeBot
The fix, as a brief for a coding agent
Goal: Serve AI agents the same page a browser gets Site: https://www.bedquarter.ae/ (TEMPUR | BEDQUARTER) Issue: Crawlers blocked: GPTBot, 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: GPTBot, ClaudeBot. Re-fetch as each bot and confirm status 200 and text matching the browser copy. Evidence: bots: {"bot":"GPTBot","status":403,"ratio":0,"robots":"allowed"}, {"bot":"ClaudeBot","status":403,"ratio":0,"robots":"allowed"}, {"bot":"PerplexityBot","status":200,"ratio":1,"robots":"allowed"} blocked: GPTBot, ClaudeBot Docs: https://platform.openai.com/docs/bots, https://support.anthropic.com/en/articles/8896518, https://docs.perplexity.ai/guides/botsOptional help · Waitlist
NovaWebmaster & SEO · AI workeropens the site to the AI crawlersFree + usage View worker
-
Is the page readable without running scripts?10334 characters readable without scriptsFindable
Passed · Signal, 1 h ago · re-check
The page says who the business is before any script runs, which is how most agents read it.
- chars
- 10334
- headings
- 13
- bytes
- 567747
How: url https://bedquarter.ae/
-
Does the site carry structured data that agrees with the listing?Structured data: Organization, WebSite, ImageObject, WebPage, Person, ArticleFindable
Passed · Signal, 1 h ago · re-check
An agent can read the name, phone and hours as data, and they say what the listing says.
- types
- Organization, WebSite, ImageObject, WebPage, Person, Article
- recognised
- Organization, WebSite, WebPage
- has hours
- no
- mismatch
- no
How: url https://bedquarter.ae/
-
Does the page carry the basic metadata?Metadata completeFindable
Passed · Signal, 1 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.
- present
- lang, title, description, canonical, ogTitle
- missing
- h1
How: url https://bedquarter.ae/
-
Does the page load fast and without detours?Slow: 6441 msFindable
Failed · Signal, 1 h ago · re-check
The page is slow, or sends the visitor through redirects first; agents on a short timeout give up.
Fix One address, no chain of redirects, a response under two seconds.
- ms
- 6441
- redirected
- yes
- trivial
- yes
- from
- https://www.bedquarter.ae/
- to
- https://bedquarter.ae/
How: url https://www.bedquarter.ae/
The fix, as a brief for a coding agent
Goal: Answer in under two seconds, at the address on the listing Site: https://www.bedquarter.ae/ (TEMPUR | BEDQUARTER) Issue: Slow: 6441 ms Fix: Measure time to first byte and the redirect chain for the listed address. Remove intermediate redirects (link the final form of the address directly everywhere, including the listing), enable compression and caching for the HTML, and bring the response under one second where possible. Observed: 6441 ms, redirected: yes. Evidence: ms: 6441 redirected: true trivial: true from: https://www.bedquarter.ae/ to: https://bedquarter.ae/ Docs: https://web.dev/articles/ttfb
Optional help · Waitlist
NovaWebmaster & SEO · AI workermakes the page answer fast, at one addressFree + usage View worker
-
Does a missing path say so?Not applicableFindable
Not applicable · not a question for a local business (customers come to you, or you go to them)
-
Does it serve Markdown when an agent asks for it?Not applicableFindable
Not applicable · not a question for a local business (customers come to you, or you go to them)
-
Can an agent find the API?Not applicableFindable
Not applicable · not a question for a local business (customers come to you, or you go to them)
-
Does it advertise an MCP server?Not applicableFindable
Not applicable · not a question for a local business (customers come to you, or you go to them)
-
Can an agent discover how to authenticate?Not applicableFindable
Not applicable · not a question for a local business (customers come to you, or you go to them)
-
Is there a published price for agent access?No price for agent accessFindable
Failed · Signal, 1 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.json404 text/html 1688 ms an HTML page - looked
- Link header, /.well-known/x402.json, homepage head
The fix, as a brief for a coding agent
Goal: Publish a machine-readable price for agent access Site: https://www.bedquarter.ae/ (TEMPUR | BEDQUARTER) 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
-
Does an unpaid agent request get a 402 with terms?Unpaid agent request answered 200Findable
Failed · Signal, 1 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 credentials200 text/html 112 ms - endpoint
- https://bedquarter.ae/
- status
- 200
The fix, as a brief for a coding agent
Goal: Answer an unpaid agent request with 402 and payment terms Site: https://www.bedquarter.ae/ (TEMPUR | BEDQUARTER) 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://bedquarter.ae/ 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://bedquarter.ae/ 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
-
Is a payee discoverable?No payee publishedFindable
Failed · Signal, 1 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.json404 text/html 1688 ms an HTML page - looked
- the 402 body, /.well-known/x402.json
The fix, as a brief for a coding agent
Goal: Publish who to pay Site: https://www.bedquarter.ae/ (TEMPUR | BEDQUARTER) 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
-
Can an agent that shops find you in a catalogue?In no catalogue an agent searchesFindable
Failed · Signal, 1 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-catalog404 text/html 1793 ms an HTML page - entries
- 0
- looked
- /.well-known/api-catalog
The fix, as a brief for a coding agent
Goal: Be listed where tool routers look Site: https://www.bedquarter.ae/ (TEMPUR | BEDQUARTER) 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
Scout Discovery agent · looks for the business the way an assistant would, and reads what it publishes for agents0/1
-
Are the discovery files in place?Missing sitemapFindable
Failed · Scout, 1 h ago · re-check
A crawler finds no robots.txt or no sitemap, so it has to guess which pages exist.
Fix A robots.txt that names the sitemap, a sitemap.xml, and an llms.txt describing the business for language models.
Request Status Type Time /robots.txt200 text/plain 56 ms /sitemap.xml404 text/html 2229 ms /llms.txt200 text/plain 66 ms - robots
- yes
- llms
- yes
- missing
- sitemap
The fix, as a brief for a coding agent
Goal: Publish robots.txt, a sitemap and llms.txt Site: https://www.bedquarter.ae/ (TEMPUR | BEDQUARTER) Issue: Missing sitemap Fix: Publish /robots.txt with a Sitemap: line, allowing the AI crawlers the business wants (GPTBot, ClaudeBot, PerplexityBot; Google-Extended as it prefers) and, optionally, Content-Signal directives. Publish /sitemap.xml listing the public pages. Add /llms.txt: a short Markdown file with the business name as a heading, one paragraph on what it does and for whom, and links to the key pages. Missing this time: sitemap. Confirm each answers 200 with the right content type. Evidence: robots: true llms: true missing: sitemap Docs: https://llmstxt.org/, https://www.sitemaps.org/protocol.html, https://contentsignals.org/
-
Do the assistants name it when asked?ComingFindable
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.
Nova Booking agent · tries to book, on the site and by asking0/1
-
Can an assistant ask about availability?Country not knownReachable
Not made here
Nova calls once a quarter as a customer’s assistant, says so, and asks about availability. Which country the business is in is not known from the site, and the country decides whether the call may be made (A live AI enquiry call is permitted to business numbers in Australia and to business landlines in the US, and nowhere else without consent.). Claim the page and set it.
-
Can a customer book without calling?No online bookingReachable
Failed · Nova, 1 h ago · re-check
Every booking depends on a call being answered, including the ones that come in after hours.
Fix A booking page, or a line that books, reachable from the listing.
- looked
- booking links, booking widgets, book or schedule wording
How: url https://www.bedquarter.ae/ · userAgent phone
Optional help · Waitlist
IvyReceptionist · AI workerbooks without a call, at any hourFree + usage View worker
Atlas General assistant agent · rings the business the way a customer’s assistant would0/1
-
Does somebody answer the phone?Country not knownReachable
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. Which country the business is in is not known from the site, and the country decides whether the call may be made (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.). Claim the page and set it.
Echo Outreach agent · writes to the business and waits for the reply0/2
-
Does an email get a reply?No address to write toReachable
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.
-
Do messages on AI3 get a reply?No messages to answer yetReachable
Could not be established · Echo, 1 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.
- threads
- 0
How: read threads · days 60
Get notified when agents are available
Alpha
Join the 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 TEMPUR | BEDQUARTER, and when this report changes.
For developers and agents
This report as data: /api/o/tempur-bedquarter — 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: https://www.bedquarter.ae/ (TEMPUR | BEDQUARTER)
Issue: Crawlers blocked: GPTBot, 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: GPTBot, ClaudeBot. Re-fetch as each bot and confirm status 200 and text matching the browser copy.
Evidence:
bots: {"bot":"GPTBot","status":403,"ratio":0,"robots":"allowed"}, {"bot":"ClaudeBot","status":403,"ratio":0,"robots":"allowed"}, {"bot":"PerplexityBot","status":200,"ratio":1,"robots":"allowed"}
blocked: GPTBot, ClaudeBot
Docs: https://platform.openai.com/docs/bots, https://support.anthropic.com/en/articles/8896518, https://docs.perplexity.ai/guides/bots
---
Goal: Answer in under two seconds, at the address on the listing
Site: https://www.bedquarter.ae/ (TEMPUR | BEDQUARTER)
Issue: Slow: 6441 ms
Fix: Measure time to first byte and the redirect chain for the listed address. Remove intermediate redirects (link the final form of the address directly everywhere, including the listing), enable compression and caching for the HTML, and bring the response under one second where possible. Observed: 6441 ms, redirected: yes.
Evidence:
ms: 6441
redirected: true
trivial: true
from: https://www.bedquarter.ae/
to: https://bedquarter.ae/
Docs: https://web.dev/articles/ttfb
---
Goal: Publish robots.txt, a sitemap and llms.txt
Site: https://www.bedquarter.ae/ (TEMPUR | BEDQUARTER)
Issue: Missing sitemap
Fix: Publish /robots.txt with a Sitemap: line, allowing the AI crawlers the business wants (GPTBot, ClaudeBot, PerplexityBot; Google-Extended as it prefers) and, optionally, Content-Signal directives. Publish /sitemap.xml listing the public pages. Add /llms.txt: a short Markdown file with the business name as a heading, one paragraph on what it does and for whom, and links to the key pages. Missing this time: sitemap. Confirm each answers 200 with the right content type.
Evidence:
robots: true
llms: true
missing: sitemap
Docs: https://llmstxt.org/, https://www.sitemaps.org/protocol.html, https://contentsignals.org/
---
Goal: Publish a machine-readable price for agent access
Site: https://www.bedquarter.ae/ (TEMPUR | BEDQUARTER)
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: https://www.bedquarter.ae/ (TEMPUR | BEDQUARTER)
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://bedquarter.ae/ 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://bedquarter.ae/
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: https://www.bedquarter.ae/ (TEMPUR | BEDQUARTER)
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: https://www.bedquarter.ae/ (TEMPUR | BEDQUARTER)
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