Same category
goodforbots.com
Evaluates website readability for AI crawlers and language models with a scoring rubric

Deanonymization and enrichment tool for high-volume product signups
Manifolds is a deanonymization and enrichment tool built for companies with high signup volume, ranging from 1,000 to 1,000,000 signups per month. It allows organizations to send email addresses via an API or webhook and receive detailed information about the users, including their real name, job role, and company data. The service helps sales, growth, and product teams identify valuable signups, find enterprise opportunities, and broadcast the enriched data to destinations like CRMs, data warehouses, Slack, or email automation tools.
“Manifolds is a deanonymization and enrichment tool that matches user email addresses to real people, roles, and companies via API for high-volume signup companies.”
Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.
A language model reading the provided homepage and llms.txt files learns about the core functionality of Manifolds, which matches submitted email addresses to real people, roles, and companies using web crawling, proprietary data, and language models. The text covers use cases for sales, growth, and product teams, and details integration options including webhooks and an API base URL with bearer authentication. The llms.txt file significantly expands on the homepage by supplying concrete usage-based pricing details ranging from $0.75 down to $0.35 per successful match, enterprise volume tiers, OpenAPI specification references, and links to documentation for PostHog integrations and webhooks.
Good for Bots report
robots.txt is present and valid. robots.txt is valid, with 1 user-agent group.
Sitemap is present and parses. Sitemap declared in robots.txt, listing 5 URLs.
Content is marked up so a reader can find it. All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.
Navigation links expose usable destinations. 21 of 21 assessed homepage navigation links expose usable destinations.
Links and buttons have accessible names. 29 of 29 assessed homepage links and buttons have a nonempty accessible name.
Controls expose roles, states and relationships. 42 of 42 assessed homepage controls and role declarations meet the static role, state and relationship checks.
Each page declares one usable canonical URL. All 4 pages read pass. The homepage declares itself as its canonical URL.
Section links reach an element on the page. Both pages read pass. The homepage has 3 section links, and every one reaches an element on the page.
Describes itself to machines with schema.org JSON-LD. 1 of 4 pages read pass. The homepage publishes no structured data at all: no JSON-LD, no microdata, no RDFa. +8.8 with its prompt.
llms.txt is present and well formed. /llms.txt is well formed: 11 links across 5 sections.
llms.txt is descriptive, not a bare link list. /llms.txt is descriptive: a summary plus descriptions on 100% of links.
Advertises machine-readable resources with typed links. All 4 pages read pass. The homepage points at a markdown version of itself through the page markup.
Serves markdown at its own URL. No /llms-full.txt and no markdown versions linked from llms.txt. +12.5 with its prompt.
Serves markdown when asked for it. None of the 4 pages read pass. Asking the homepage for markdown still returns text/html. +10 with its prompt.
States a position on AI crawlers. robots.txt names no AI crawlers, so every operator has to guess. +5 with its prompt in Pro.
Declares AI usage preferences. No usage declaration found in robots.txt or the final successful homepage response header. +2.5 with its prompt in Pro.
Earned
41 of the 50 base points above the line, 20 of the 50 agent-layer points below it.
3 prompts away
Still open
Behind the checks below, with prompts in Pro.
For the owner of manifolds.run
They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.
Select a check to see what we found and how it is graded.
Readable base
41.2 / 50
3.5 of 3.5 points.
robots.txt is valid, with 1 user-agent group.
8.8 of 8.8 points.
Sitemap declared in robots.txt, listing 5 URLs.
0 of 8.8 points.
1 of 4 pages read pass. The homepage publishes no structured data at all: no JSON-LD, no microdata, no RDFa.
10.5 of 10.5 points.
All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.
4.4 of 4.4 points.
29 of 29 assessed homepage links and buttons have a nonempty accessible name.
0 of 0 points.
No applicable form fields were observed in the homepage HTML.
2.6 of 2.6 points.
42 of 42 assessed homepage controls and role declarations meet the static role, state and relationship checks.
1.8 of 1.8 points.
All 4 pages read pass. The homepage declares itself as its canonical URL.
0.9 of 0.9 points.
Both pages read pass. The homepage has 3 section links, and every one reaches an element on the page.
Agent layer
20 / 50
11.3 of 11.3 points.
/llms.txt is well formed: 11 links across 5 sections.
7.5 of 7.5 points.
/llms.txt is descriptive: a summary plus descriptions on 100% of links.
0 of 12.5 points.
No /llms-full.txt and no markdown versions linked from llms.txt.
0 of 10 points.
None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.
0 of 5 points.
robots.txt names no AI crawlers, so every operator has to guess.
0 of 2.5 points.
No usage declaration found in robots.txt or the final successful homepage response header.
1.3 of 1.3 points.
All 4 pages read pass. The homepage points at a markdown version of itself through the page markup.
Penalties
− 0
Penalty: 0 of 15 points.
Our crawler reaches the page without being challenged.
Penalty: 0 of 20 points.
Nothing on the homepage tells a crawler to skip it or to withhold its snippet.
Penalty: 0 of 25 points.
The captured homepage HTML contains 1526 content words; completeness is not assessed.
Penalty: 0 of 25 points.
robots.txt allows every known search and user-fetch crawler to reach the homepage.
Penalty: 0 of 10 points.
The homepage is served over HTTPS and returns HTTP 200.
Penalty: 0 of 3 points.
The homepage provides both a non-empty title and meta description.
Penalty: 0 of 3 points.
The homepage is reached in 0 redirects.
Penalty: 0 of 3 points.
The homepage reached a plain crawler in 175 ms.
Agent capabilities
0 of 11 · no points
Each one found adds +1 to the badge.
Adds +1 to the badge when found.
No API catalog published.
Adds +1 to the badge when found.
No /auth.md published.
Adds +1 to the badge when found.
No AI Catalog published, so no MCP server card can be discovered.
Adds +1 to the badge when found.
No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.
Adds +1 to the badge when found.
No usable Agent Skills index was found at either well-known path or in the AI Catalog.
Adds +1 to the badge when found.
No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.
Adds +1 to the badge when found.
No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.
Adds +1 to the badge when found.
No HTTP 402 payment challenge on the homepage or robots.txt, and no manifest at /.well-known/x402.
Adds +1 to the badge when found.
No ACP discovery declaration established at /.well-known/acp.json.
Adds +1 to the badge when found.
No UCP discovery declaration established at /.well-known/ucp.
Adds +1 to the badge when found.
No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.
It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.
Access & usage policy
GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.
Sampled URL: https://manifolds.run/
No matching refusal for this URL was found for the listed identities.
Declared allow · Scan admission
The recorded robots admission decision allowed our crawler to proceed.
GoodForBotsBot admission along the homepage request chain
https://manifolds.run/
Declared allow · robots.txt
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://manifolds.run/
https://manifolds.run/robots.txt
User-agent: * allow: /
robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers
GoodForBotsBot received HTTP 200 via a direct request.
Observed · Direct request
Our request received HTTP 200. A status alone does not identify a WAF.
Our recorded direct transport attempt; intermediate attempt URLs are not retained
https://manifolds.run
HTTP 200
Observed · Final homepage response
GoodForBotsBot received HTTP 200 via a direct request.
homepage response
https://manifolds.run/
HTTP 200 Transport: direct
Serves the homepage over HTTPS with HTTP 200Serves our crawler without a challenge
No indexing restriction was observed in the supported homepage directives.
Not observed · Homepage directives
No indexing restriction was observed in the supported homepage directives.
homepage response
https://manifolds.run/
No snippet restriction was observed in the supported homepage directives.
Not observed · Homepage directives
No snippet restriction was observed in the supported homepage directives.
homepage response
https://manifolds.run/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: search; applicable robots group/path and this response's header
https://manifolds.run/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: ai-use; applicable robots group/path and this response's header
https://manifolds.run/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: train-ai; applicable robots group/path and this response's header
https://manifolds.run/
In its category
The prompts in the owner view would take Manifolds to 93, 4th in its category.
To the prompts →Category average 62. The percentile appears once the catalogue holds a few hundred sites.
Every scan is kept. Pro draws the history as a chart →
The homepage and up to three pages from the sitemap and homepage links. Structured data, page structure, Markdown negotiation and typed links check each page read and take the median page; other checks read the homepage.
More like Manifolds:Developer Tools & APIsSalesData & DatabasesB2B
Same category
goodforbots.com
Evaluates website readability for AI crawlers and language models with a scoring rubric
Same category
contacts.wawebplus.com
Chrome extension to export WhatsApp Web group contacts and phone numbers to Excel or CSV
Same category
appbanana.io
Real human testers for Android apps to pass Google Play closed testing requirements
Same category
huntbug.com
Crowdsourced bug bounty platform connecting security researchers with companies
Same category
emailyy.online
Free browser-based email tools for signatures, subject lines, HTML previews, and header analysis
Same category
vavahost.com
Fast web hosting with cPanel, LiteSpeed, NVMe storage, and 1-click WordPress
Do you run manifolds.run? Open the owner view → Removing the listing is free. Remove →