Agent readiness report

← Public business profile

MEROË - The Bed Boutique

Structured data agrees with the listing; metadata complete; AI crawlers get the same page.

meroe.me · checked 4 h ago · online business

How AI agents see MEROË - The Bed Boutique: 56 — reputation 45, agent readiness 67.

AI3 score · MEROË - The Bed BoutiqueFair

56/100

Reputation15–75 · 1 sample · early45
Agent readiness44–79 · 18 of 23 checks67

Reputation, readiness and customer success, from the evidence on this page and the business’s record. How the scores work.

Recommended improvements

1 suggested improvement. Start with the first, then inspect the evidence.

  1. 1
    Publish an MCP server card No MCP server card

    A server card at /.well-known/mcp/server-card.json (and /.well-known/mcp.json) naming the endpoint and its tools.

    View evidence

    Optional help · Waitlist
    AI engineer — illustrated AI agent
    SunAI engineer · AI workerpublishes the MCP server cardFree + usage View worker

Track your progress: claim your business to correct its details and re-check after changes.

Claim this business — free
Business research & sources

Building the profile of MEROË - The Bed Boutique

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

Reachable
AEasy to reach
Can a customer, or their assistant, get through? 3 of 3 checks passed; 7 apply.
Findable
2Readable
Structured data agrees with the listing; metadata complete; AI crawlers get the same page. 7 of 15 checks passed; 16 apply.
To reach Level 3 · Findable: 1 thing — what to do.
How readiness levels work
  1. 0Not found
  2. 1Present
  3. 2Readable
  4. 3Findable
  5. 4Transactable

Signal Web audit agent · opens the website the way a phone does and reads the listing9/17

  • Do the listing and the website give the same hours?Not applicableReachable

    Not applicable · not a question for an online business (no premises; customers find you on the web)

  • Is the website up?Website up (1116 ms)Reachable

    Passed · Signal, 4 h ago · re-check

    The address on the listing opens.

    status
    200
    ms
    1116
    final url
    https://meroe.me/
    https
    yes

    How: url https://www.meroe.me/ · userAgent phone

  • Does the website work on a phone?Works on a phoneReachable

    Passed · Signal, 4 h ago · re-check

    The site fits a phone screen, which is where most customers open it.

    viewport
    yes
    tap to call
    yes
    bytes
    85847

    How: url https://www.meroe.me/ · userAgent phone

  • Is the listing complete?Not applicableReachable

    Not applicable · not a question for an online business (no premises; customers find you on the web)

  • Are the social profiles reachable?Profiles open (Instagram, YouTube)Reachable

    Passed · Signal, 4 h ago · re-check

    The profiles the website points to open.

    open
    Instagram, YouTube
    unsure
    LinkedIn, Facebook
    links
    https://www.linkedin.com/company/meroe, https://www.instagram.com/meroelinens, https://www.youtube.com/@meroelinens, https://www.facebook.com/meroelinens

    How: url https://www.meroe.me/ · userAgent phone

  • Does it deliver what it sells?Nothing sold through AI3 yetReachable

    Could not be established · Signal, 4 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?Same page for 3 AI crawlersFindable

    Passed · Signal, 4 h ago · re-check

    An assistant that fetches the site gets what a customer gets, so it can read and cite the business.

    RequestStatusTypeTime
    GET / as a browser200text/html188 ms
    /robots.txt200text/plain177 ms
    GET / as GPTBot200text/html549 ms100% of the browser text; robots.txt: allowed
    GET / as ClaudeBot200text/html191 ms100% of the browser text; robots.txt: allowed
    GET / as PerplexityBot200text/html188 ms100% of the browser text; robots.txt: allowed
    bots
    {"bot":"GPTBot","status":200,"ratio":1,"robots":"allowed"}, {"bot":"ClaudeBot","status":200,"ratio":1,"robots":"allowed"}, {"bot":"PerplexityBot","status":200,"ratio":1,"robots":"allowed"}
  • Is the page readable without running scripts?10987 characters readable without scriptsFindable

    Passed · Signal, 4 h ago · re-check

    The page says who the business is before any script runs, which is how most agents read it.

    chars
    10987
    headings
    19
    bytes
    85847

    How: url https://meroe.me/

  • Does the site carry structured data that agrees with the listing?Structured data: WebPage, BreadcrumbList, WebSite, OrganizationFindable

    Passed · Signal, 4 h ago · re-check

    An agent can read the name, phone and hours as data, and they say what the listing says.

    types
    WebPage, BreadcrumbList, WebSite, Organization
    recognised
    WebPage, WebSite, Organization
    has hours
    no
    mismatch
    no

    How: url https://meroe.me/

  • Does the page carry the basic metadata?Metadata completeFindable

    Passed · Signal, 4 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, h1, ogTitle

    How: url https://meroe.me/

  • Does the page load fast and without detours?Loads in 1116 msFindable

    Passed · Signal, 4 h ago · re-check

    The page answers quickly at the address given, so an agent on a short timeout gets it.

    ms
    1116
    redirected
    yes
    trivial
    yes
    from
    https://www.meroe.me/
    to
    https://meroe.me/

    How: url https://www.meroe.me/

  • Does a missing path say so?Missing paths return 404Findable

    Passed · Signal, 4 h ago · re-check

    A path that does not exist says so, so an agent probing for a manifest is not misled by a page.

    RequestStatusTypeTime
    /.well-known/<a path that does not exist>.json404text/html1171 ms
    status
    404
    content type
    text/html; charset=utf-8
    final url
    https://meroe.me/.well-known/ai3-probe-5dq2c11k.json
  • Does it serve Markdown when an agent asks for it?No Markdown for agentsFindable

    Failed · Signal, 4 h ago · re-check

    An agent asking for Markdown gets the HTML, and has to strip it.

    Fix Content negotiation: Accept: text/markdown answered with a Markdown rendering of the page.

    RequestStatusTypeTime
    GET / with Accept: text/markdown200text/html190 ms
    content type
    text/html; charset=UTF-8

    The fix, as a brief for a coding agent

    Goal: Offer Markdown to agents that ask for it
    Site: https://www.meroe.me/ (MEROË - The Bed Boutique)
    Issue: No Markdown for agents
    Fix: Support content negotiation on public pages: when a request carries Accept: text/markdown, respond with Content-Type: text/markdown and a Markdown rendering of the page (headings, paragraphs, links), keeping HTML the default for browsers. On Cloudflare, enable Markdown for Agents; elsewhere add a middleware that converts the rendered HTML or renders from source. Confirm with curl -H "Accept: text/markdown".
    Evidence:
      contentType: text/html; charset=UTF-8
    Docs: https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/
    Optional help · Waitlist
    Developer — illustrated AI agent
    MateoDeveloper · AI workerserves Markdown to agents that ask for itFree + usage View worker
  • Can an agent find the API?No API description foundFindable

    Failed · Signal, 4 h ago · re-check

    No API description at the standard addresses, so an agent can read about the product but not use it.

    Fix An OpenAPI document at /openapi.json, linked by a Link header or /.well-known/api-catalog.

    RequestStatusTypeTime
    /.well-known/api-catalog404text/html1146 msan HTML page
    /openapi.json404text/html1167 msan HTML page
    /openapi.yaml404text/html1125 msan HTML page
    /swagger.json404text/html1145 msan HTML page
    /api-docs404text/html1114 msan HTML page

    The fix, as a brief for a coding agent

    Goal: Publish a machine-readable API description where agents look
    Site: https://www.meroe.me/ (MEROË - The Bed Boutique)
    Issue: No API description found
    Fix: Publish an OpenAPI 3.x document at /openapi.json (and/or /openapi.yaml); add a Link response header on the homepage — Link: </openapi.json>; rel="service-desc" — and publish /.well-known/api-catalog as application/linkset+json (RFC 9727) pointing at the spec and the docs. Confirm each address returns the right content type and not an HTML page.
    Docs: https://www.rfc-editor.org/rfc/rfc9727, https://spec.openapis.org/oas/latest.html, https://www.rfc-editor.org/rfc/rfc8288
    Optional help · Waitlist
    Developer — illustrated AI agent
    MateoDeveloper · AI workerpublishes the API description where agents lookFree + usage View worker
  • Does it advertise an MCP server?No MCP server cardFindable

    Failed · Signal, 4 h ago · re-check

    If there is an MCP server, nothing at the standard addresses says so.

    Fix A server card at /.well-known/mcp/server-card.json (and /.well-known/mcp.json) naming the endpoint and its tools.

    RequestStatusTypeTime
    /.well-known/mcp/server-card.json404text/html1153 msan HTML page
    /.well-known/mcp.json404text/html1146 msan HTML page
    POST https://mcp.meroe.me/mcp initialize—45 ms
    POST https://mcp.meroe.me/ initialize—32 ms
    POST https://meroe.me/mcp initialize404875 ms
    looked
    /.well-known/mcp/server-card.json, /.well-known/mcp.json, POST https://mcp.meroe.me/mcp initialize, POST https://mcp.meroe.me/ initialize, POST https://meroe.me/mcp initialize

    The fix, as a brief for a coding agent

    Goal: Publish an MCP server card
    Site: https://www.meroe.me/ (MEROË - The Bed Boutique)
    Issue: No MCP server card
    Fix: Publish /.well-known/mcp/server-card.json and /.well-known/mcp.json as application/json with serverInfo {name, version}, the transport endpoint (the Streamable HTTP URL), capabilities, and where the authorization metadata lives (the OAuth protected-resource URL). If there is no MCP server yet, build the card when there is one; do not serve a page in its place.
    Evidence:
      looked: /.well-known/mcp/server-card.json, /.well-known/mcp.json, POST https://mcp.meroe.me/mcp initialize, POST https://mcp.meroe.me/ initialize, POST https://meroe.me/mcp initialize
    Docs: https://modelcontextprotocol.io/specification/latest, https://github.com/modelcontextprotocol/modelcontextprotocol/pull/2127
    Optional help · Waitlist
    AI engineer — illustrated AI agent
    SunAI engineer · AI workerpublishes the MCP server cardFree + usage View worker
  • Can an agent discover how to authenticate?No OAuth discovery metadataFindable

    Failed · Signal, 4 h ago · re-check

    The OAuth discovery metadata is missing or does not validate, so an agent cannot work out how to obtain a token.

    Fix RFC 8414 metadata at /.well-known/oauth-authorization-server and RFC 9728 metadata at /.well-known/oauth-protected-resource, with resource on this origin.

    RequestStatusTypeTime
    /.well-known/oauth-authorization-server404text/html1155 msan HTML page
    /.well-known/openid-configuration404text/html1180 ms
    /.well-known/oauth-protected-resource404text/html1142 msan HTML page
    authorization server
    no
    protected resource
    no

    The fix, as a brief for a coding agent

    Goal: Publish OAuth discovery metadata that validates
    Site: https://www.meroe.me/ (MEROË - The Bed Boutique)
    Issue: No OAuth discovery metadata
    Fix: Serve /.well-known/oauth-authorization-server (RFC 8414) with issuer, authorization_endpoint, token_endpoint, registration_endpoint and code_challenge_methods_supported ["S256"]; and /.well-known/oauth-protected-resource (RFC 9728) with resource set to this origin — plus a path-suffixed copy for each protected resource, e.g. /.well-known/oauth-protected-resource/mcp with resource ending in /mcp — authorization_servers, scopes_supported and bearer_methods_supported. Return application/json with CORS open. Found this time: authorization server no, protected resource no.
    Evidence:
      authorizationServer: false
      protectedResource: false
    Docs: https://www.rfc-editor.org/rfc/rfc8414, https://www.rfc-editor.org/rfc/rfc9728
    Optional help · Waitlist
    Developer — illustrated AI agent
    MateoDeveloper · AI workerpublishes OAuth discovery metadata that validatesFree + usage View worker
  • Is there a published price for agent access?No price for agent accessFindable

    Failed · Signal, 4 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.

    RequestStatusTypeTime
    /.well-known/x402.json404text/html1129 msan 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.meroe.me/ (MEROË - The Bed Boutique)
    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, 4 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.

    RequestStatusTypeTime
    GET / with Accept: application/json, no credentials200text/html1156 ms
    endpoint
    https://meroe.me/
    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.meroe.me/ (MEROË - The Bed Boutique)
    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://meroe.me/ 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://meroe.me/
      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, 4 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.

    RequestStatusTypeTime
    /.well-known/x402.json404text/html1129 msan 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.meroe.me/ (MEROË - The Bed Boutique)
    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, 4 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.

    RequestStatusTypeTime
    /.well-known/api-catalog404text/html1126 msan 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.meroe.me/ (MEROË - The Bed Boutique)
    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 agents1/1

  • Are the discovery files in place?robots.txt, sitemap, llms.txtFindable

    Passed · Scout, 4 h ago · re-check

    A crawler finds robots.txt and a sitemap, so every page the business wants found can be found.

    RequestStatusTypeTime
    /robots.txt200text/plain177 ms
    /sitemap.xml200application/xml178 ms
    /llms.txt200text/plain342 ms
    robots
    yes
    sitemap
    https://meroe.me/sitemap.xml
    llms
    yes
  • 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?Not applicableReachable

    Not applicable · not a question for an online business (no premises; customers find you on the web)

Atlas General assistant agent · rings the business the way a customer’s assistant would0/0

  • Does somebody answer the phone?Not applicableReachable

    Not applicable · not a question for an online business (no premises; customers find you on the web)

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, 4 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 MEROË - The Bed Boutique, and when this report changes.

For developers and agents

This report as data: /api/o/meroe-the-bed-boutique — 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.