Klekktic

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

Passed · Signal, 4 h ago · re-check

The address on the listing opens.

status

200

ms

294

final url

https://klekktic.com/pages/visit-showroom?utm_source=google&utm_medium=organic&utm_campaign=gbp_profile

https

yes

How: url https://klekktic.com/pages/visit-showroom?utm_source=google&utm_medium=organic&utm_campaign=gbp_profile · userAgent phone

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

268459

How: url https://klekktic.com/pages/visit-showroom?utm_source=google&utm_medium=organic&utm_campaign=gbp_profile · userAgent phone

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

Passed · Signal, 4 h ago · re-check

The profiles the website points to open.

open

Instagram, TikTok

unsure

Facebook

links

https://www.instagram.com/klekktic, https://www.facebook.com/Klekktic, https://www.tiktok.com/@klekktic

How: url https://klekktic.com/pages/visit-showroom?utm_source=google&utm_medium=organic&utm_campaign=gbp_profile · userAgent phone

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

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.

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"}

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

4145

headings

13

bytes

268459

How: url https://klekktic.com/pages/visit-showroom?utm_source=google&utm_medium=organic&utm_campaign=gbp_profile

Failed · Signal, 4 h ago · re-check

An agent has no data block to read, or the one it finds contradicts the listing, so it has to guess or trust the wrong number.

Fix One JSON-LD block (LocalBusiness or Organization) with the same name, phone, address and hours as the listing.

has hours

no

mismatch

no

How: url https://klekktic.com/pages/visit-showroom?utm_source=google&utm_medium=organic&utm_campaign=gbp_profile

The fix, as a brief for a coding agent

Goal: Publish schema.org JSON-LD that matches the listing
Site: https://klekktic.com/pages/visit-showroom?utm_source=google&utm_medium=organic&utm_campaign=gbp_profile (Klekktic)
Issue: No structured data
Fix: Add a <script type="application/ld+json"> block to the homepage describing the business: @type LocalBusiness or the closest subtype (Plumber, Restaurant, Hotel…; Organization or SoftwareApplication for a software company), with name, url, telephone in E.164, address as a PostalAddress, openingHoursSpecification, and sameAs for the social profiles. Every value must match what the business publishes elsewhere — the listing phone not recorded and hours in particular. Validate at validator.schema.org and re-fetch.
Evidence:
  hasHours: false
  mismatch: false
Docs: https://schema.org/LocalBusiness, https://validator.schema.org/, https://developers.google.com/search/docs/appearance/structured-data/local-business

Copy prompt

Optional help · Waitlist

NovaWebmaster & SEO · AI workerpublishes structured data that matches the listingFree + usage View worker ↗

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, canonical, h1, ogTitle

missing

description

How: url https://klekktic.com/pages/visit-showroom?utm_source=google&utm_medium=organic&utm_campaign=gbp_profile

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

294

redirected

no

trivial

yes

from

https://klekktic.com/pages/visit-showroom?utm_source=google&utm_medium=organic&utm_campaign=gbp_profile

to

https://klekktic.com/pages/visit-showroom?utm_source=google&utm_medium=organic&utm_campaign=gbp_profile

How: url https://klekktic.com/pages/visit-showroom?utm_source=google&utm_medium=organic&utm_campaign=gbp_profile

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.

status

404

content type

application/json

final url

https://klekktic.com/.well-known/ai3-probe-tap79h6q.json

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.

content type

text/plain; charset=utf-8

The fix, as a brief for a coding agent

Goal: Offer Markdown to agents that ask for it
Site: https://klekktic.com/pages/visit-showroom?utm_source=google&utm_medium=organic&utm_campaign=gbp_profile (Klekktic)
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/plain; charset=utf-8
Docs: https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/

Copy prompt

Optional help · Waitlist

MateoDeveloper · AI workerserves Markdown to agents that ask for itFree + usage View worker ↗

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.

The fix, as a brief for a coding agent

Goal: Publish a machine-readable API description where agents look
Site: https://klekktic.com/pages/visit-showroom?utm_source=google&utm_medium=organic&utm_campaign=gbp_profile (Klekktic)
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

Copy prompt

Optional help · Waitlist

MateoDeveloper · AI workerpublishes the API description where agents lookFree + usage View worker ↗

Passed · Signal, 4 h ago · re-check

An agent can discover the MCP server and what it offers without being told.

endpoint

https://klekktic.com/api/ucp/mcp

name

universal-commerce

card

no

auth

no

Passed · Signal, 4 h ago · re-check

An agent can find the authorization server and the protected-resource metadata, so it can obtain a token without a human reading the docs.

authorization server

yes

issuer

https://shopify.com/authentication/48247373988

protected resource

yes

resource

https://klekktic.com

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.

looked

Link header, /.well-known/x402.json, homepage head

Goal: Publish a machine-readable price for agent access
Site: https://klekktic.com/pages/visit-showroom?utm_source=google&utm_medium=organic&utm_campaign=gbp_profile (Klekktic)
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, 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.

endpoint

https://klekktic.com/pages/visit-showroom?utm_source=google&utm_medium=organic&utm_campaign=gbp_profile

status

200

Goal: Answer an unpaid agent request with 402 and payment terms
Site: https://klekktic.com/pages/visit-showroom?utm_source=google&utm_medium=organic&utm_campaign=gbp_profile (Klekktic)
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://klekktic.com/pages/visit-showroom?utm_source=google&utm_medium=organic&utm_campaign=gbp_profile 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://klekktic.com/pages/visit-showroom?utm_source=google&utm_medium=organic&utm_campaign=gbp_profile
  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, 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.

looked

the 402 body, /.well-known/x402.json

Goal: Publish who to pay
Site: https://klekktic.com/pages/visit-showroom?utm_source=google&utm_medium=organic&utm_campaign=gbp_profile (Klekktic)
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, 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.

entries

0

looked

/.well-known/api-catalog

Goal: Be listed where tool routers look
Site: https://klekktic.com/pages/visit-showroom?utm_source=google&utm_medium=organic&utm_campaign=gbp_profile (Klekktic)
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, 4 h ago · re-check

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

robots

yes

sitemap

https://klekktic.com/sitemap.xml

llms

yes

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. 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.

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

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

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, 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