Recourse

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

Passed · Signal, 19 h ago · re-check

The address on the listing opens.

status

200

ms

111

final url

https://recourse.so/

https

yes

How: url https://recourse.so/ · userAgent phone

Passed · Signal, 19 h ago · re-check

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

viewport

yes

tap to call

no

bytes

34481

How: url https://recourse.so/ · userAgent phone

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

Could not be established · Signal, 19 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://recourse.so/ · userAgent phone

Could not be established · Signal, 19 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, 19 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, 19 h ago · re-check

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

chars

8078

headings

24

bytes

34481

How: url https://recourse.so/

Passed · Signal, 19 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

recognised

Organization, WebSite

has hours

no

mismatch

no

How: url https://recourse.so/

Passed · Signal, 19 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://recourse.so/

Passed · Signal, 19 h ago · re-check

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

ms

111

redirected

no

trivial

yes

from

https://recourse.so/

to

https://recourse.so/

How: url https://recourse.so/

Passed · Signal, 19 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

text/html; charset=utf-8

final url

https://recourse.so/.well-known/ai3-probe-i2u3gt8y.json

Failed · Signal, 19 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/html; charset=utf-8

The fix, as a brief for a coding agent

Goal: Offer Markdown to agents that ask for it
Site: https://recourse.so/ (Recourse)
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/

Copy prompt

Optional help · Waitlist

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

Failed · Signal, 19 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://recourse.so/ (Recourse)
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, 19 h ago · re-check

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

endpoint

https://recourse.so/mcp

name

recourse

card

no

auth

no

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

authorization server

no

protected resource

no

The fix, as a brief for a coding agent

Goal: Publish OAuth discovery metadata that validates
Site: https://recourse.so/ (Recourse)
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

Copy prompt

Optional help · Waitlist

MateoDeveloper · AI workerpublishes OAuth discovery metadata that validatesFree + usage View worker ↗

Failed · Signal, 19 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://recourse.so/ (Recourse)
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, 19 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://recourse.so/

status

200

Goal: Answer an unpaid agent request with 402 and payment terms
Site: https://recourse.so/ (Recourse)
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://recourse.so/ 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://recourse.so/
  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, 19 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://recourse.so/ (Recourse)
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, 19 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://recourse.so/ (Recourse)
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, 19 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://recourse.so/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. The listing has no phone number, so there is nothing to call. Claim the page and add one.

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