Agent readiness report
24 Hour Emergency Plumber NYC - Brooklyn
Up, crawlable, readable without scripts.
How AI agents see 24 Hour Emergency Plumber NYC - Brooklyn: 54 — reputation not yet scored, agent readiness 54. Biggest weakness: No online booking.
54/100
Biggest weakness: No online booking.
Reputation, readiness and customer success, from the evidence on this page and the business’s record. How the scores work.
A customer 24 Hour Emergency Plumber NYC - Brooklyn is missing right now.
From the first check that failed, and the agent that takes it on.
Without Nova: An assistant looks for a plumber. It can’t read the site. It recommends another one. With Nova: Nova opens the site to agents. The assistant names 24 Hour Emergency Plumber NYC - Brooklyn.
An assistant looks for a plumber. It can’t read the site. It recommends another one.
Nova opens the site to agents. The assistant names 24 Hour Emergency Plumber NYC - Brooklyn.
Business research & sources
Building the profile of 24 Hour Emergency Plumber NYC - Brooklyn
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/12
-
Do the listing and the website give the same hours?Hours not stated on the siteReachable
Could not be established · Signal, 7 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
- 7
How: url https://www.24houremergencyplumbernyc.com/brooklyn/ · userAgent phone
-
Is the website up?Website up (3245 ms)Reachable
Passed · Signal, 7 h ago · re-check
The address on the listing opens.
- status
- 200
- ms
- 3245
- final url
- https://www.24houremergencyplumbernyc.com/brooklyn/
- https
- yes
How: url https://www.24houremergencyplumbernyc.com/brooklyn/ · userAgent phone
-
Does the website work on a phone?Works on a phoneReachable
Passed · Signal, 7 h ago · re-check
The site fits a phone screen, which is where most customers open it.
- viewport
- yes
- tap to call
- yes
- bytes
- 90687
How: url https://www.24houremergencyplumbernyc.com/brooklyn/ · userAgent phone
-
Is the listing complete?Listing completeReachable
Passed · Signal, 7 h ago · re-check
A customer finds a phone number, a website and opening hours on the listing.
- present
- phone, website, hours
- source
- file
How: read listing
-
Are the social profiles reachable?No social profiles linkedReachable
Could not be established · Signal, 7 h ago · re-check
The website points to no social profile, so there was none to open.
What would settle it Remove the dead link, or bring the profile back.
- reason
- no social profile linked from the site
How: url https://www.24houremergencyplumbernyc.com/brooklyn/ · userAgent phone
-
Does it deliver what it sells?Nothing sold through AI3 yetReachable
Could not be established · Signal, 7 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, ClaudeBot, PerplexityBotFindable
Failed · Signal, 7 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 787 ms /robots.txt200 text/plain 1025 ms GET / as GPTBot403 text/plain 26 ms 0% of the browser text; robots.txt: blocked GET / as ClaudeBot403 text/plain 76 ms 0% of the browser text; robots.txt: blocked GET / as PerplexityBot403 text/plain 18 ms 0% of the browser text; robots.txt: allowed - bots
- {"bot":"GPTBot","status":403,"ratio":0,"robots":"blocked"}, {"bot":"ClaudeBot","status":403,"ratio":0,"robots":"blocked"}, {"bot":"PerplexityBot","status":403,"ratio":0,"robots":"allowed"}
- blocked
- GPTBot, ClaudeBot, PerplexityBot
- robots blocks
- GPTBot, ClaudeBot
- content signals
- search=yes,ai-train=no,use=reference
The fix, as a brief for a coding agent
Goal: Serve AI agents the same page a browser gets Site: https://www.24houremergencyplumbernyc.com/brooklyn/ (24 Hour Emergency Plumber NYC - Brooklyn) Issue: Crawlers blocked: GPTBot, ClaudeBot, PerplexityBot 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, PerplexityBot. Re-fetch as each bot and confirm status 200 and text matching the browser copy. Evidence: bots: {"bot":"GPTBot","status":403,"ratio":0,"robots":"blocked"}, {"bot":"ClaudeBot","status":403,"ratio":0,"robots":"blocked"}, {"bot":"PerplexityBot","status":403,"ratio":0,"robots":"allowed"} blocked: GPTBot, ClaudeBot, PerplexityBot robotsBlocks: GPTBot, ClaudeBot contentSignals: search=yes,ai-train=no,use=reference 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?1732 characters readable without scriptsFindable
Passed · Signal, 7 h ago · re-check
The page says who the business is before any script runs, which is how most agents read it.
- chars
- 1732
- headings
- 4
- bytes
- 90687
How: url https://www.24houremergencyplumbernyc.com/brooklyn/
-
Does the site carry structured data that agrees with the listing?Structured data: WebPage, WebSite, OrganizationFindable
Passed · Signal, 7 h ago · re-check
An agent can read the name, phone and hours as data, and they say what the listing says.
- types
- WebPage, WebSite, Organization
- recognised
- WebPage, WebSite, Organization
- has hours
- no
- mismatch
- no
How: url https://www.24houremergencyplumbernyc.com/brooklyn/
-
Does the page carry the basic metadata?Metadata completeFindable
Passed · Signal, 7 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, canonical, h1, ogTitle
- missing
- description
How: url https://www.24houremergencyplumbernyc.com/brooklyn/
-
Does the page load fast and without detours?Slow: 3245 msFindable
Failed · Signal, 7 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
- 3245
- redirected
- no
- trivial
- yes
- from
- https://www.24houremergencyplumbernyc.com/brooklyn/
- to
- https://www.24houremergencyplumbernyc.com/brooklyn/
How: url https://www.24houremergencyplumbernyc.com/brooklyn/
The fix, as a brief for a coding agent
Goal: Answer in under two seconds, at the address on the listing Site: https://www.24houremergencyplumbernyc.com/brooklyn/ (24 Hour Emergency Plumber NYC - Brooklyn) Issue: Slow: 3245 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: 3245 ms, redirected: no. Evidence: ms: 3245 redirected: false trivial: true from: https://www.24houremergencyplumbernyc.com/brooklyn/ to: https://www.24houremergencyplumbernyc.com/brooklyn/ 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, 7 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 599 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.24houremergencyplumbernyc.com/brooklyn/ (24 Hour Emergency Plumber NYC - Brooklyn) 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, 7 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 /brooklyn/ with Accept: application/json, no credentials200 text/html 529 ms - endpoint
- https://www.24houremergencyplumbernyc.com/brooklyn/
- 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.24houremergencyplumbernyc.com/brooklyn/ (24 Hour Emergency Plumber NYC - Brooklyn) 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.24houremergencyplumbernyc.com/brooklyn/ 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.24houremergencyplumbernyc.com/brooklyn/ 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, 7 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 599 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.24houremergencyplumbernyc.com/brooklyn/ (24 Hour Emergency Plumber NYC - Brooklyn) 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, 7 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 524 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.24houremergencyplumbernyc.com/brooklyn/ (24 Hour Emergency Plumber NYC - Brooklyn) 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, sitemapFindable
Passed · Scout, 7 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.txt200 text/plain 1025 ms http://www.24houremergencyplumbernyc.com/sitemap_index.xml200 text/xml 855 ms /llms.txt404 text/html 540 ms - robots
- yes
- sitemap
- http://www.24houremergencyplumbernyc.com/sitemap_index.xml
- llms
- no
- missing
- llms.txt
- content signals
- search=yes,ai-train=no,use=reference
-
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?Not made in United StatesReachable
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.
-
Can a customer book without calling?No online bookingReachable
Failed · Nova, 7 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.24houremergencyplumbernyc.com/brooklyn/ · 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?Not made in United StatesReachable
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.
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, 7 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 24 Hour Emergency Plumber NYC - Brooklyn, and when this report changes.
For developers and agents
This report as data: /api/o/org-24-hour-emergency-plumber-nyc-brookl — 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.24houremergencyplumbernyc.com/brooklyn/ (24 Hour Emergency Plumber NYC - Brooklyn)
Issue: Crawlers blocked: GPTBot, ClaudeBot, PerplexityBot
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, PerplexityBot. Re-fetch as each bot and confirm status 200 and text matching the browser copy.
Evidence:
bots: {"bot":"GPTBot","status":403,"ratio":0,"robots":"blocked"}, {"bot":"ClaudeBot","status":403,"ratio":0,"robots":"blocked"}, {"bot":"PerplexityBot","status":403,"ratio":0,"robots":"allowed"}
blocked: GPTBot, ClaudeBot, PerplexityBot
robotsBlocks: GPTBot, ClaudeBot
contentSignals: search=yes,ai-train=no,use=reference
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.24houremergencyplumbernyc.com/brooklyn/ (24 Hour Emergency Plumber NYC - Brooklyn)
Issue: Slow: 3245 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: 3245 ms, redirected: no.
Evidence:
ms: 3245
redirected: false
trivial: true
from: https://www.24houremergencyplumbernyc.com/brooklyn/
to: https://www.24houremergencyplumbernyc.com/brooklyn/
Docs: https://web.dev/articles/ttfb
---
Goal: Publish a machine-readable price for agent access
Site: https://www.24houremergencyplumbernyc.com/brooklyn/ (24 Hour Emergency Plumber NYC - Brooklyn)
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.24houremergencyplumbernyc.com/brooklyn/ (24 Hour Emergency Plumber NYC - Brooklyn)
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.24houremergencyplumbernyc.com/brooklyn/ 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.24houremergencyplumbernyc.com/brooklyn/
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.24houremergencyplumbernyc.com/brooklyn/ (24 Hour Emergency Plumber NYC - Brooklyn)
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.24houremergencyplumbernyc.com/brooklyn/ (24 Hour Emergency Plumber NYC - Brooklyn)
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