Skip to content
Good for Bots

Manifolds

manifolds.run

Deanonymization and enrichment tool for high-volume product signups

Good for Bots: Fair, 61 of 100Get this badge →

On your homepage, it turns this report’s link to manifolds.run dofollow.

Scanned

What is Manifolds?

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.

Through a bot’s eyes

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

What it can read, and what stays hidden →

What a bot can read

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

Manifolds scores 61 of 100: 41 of the 50 base points, 20 of the 50 agent-layer points, no penalties.

Earned

41 of the 50 base points above the line, 20 of the 50 agent-layer points below it.

61

Still open

Behind the checks below, with prompts in Pro.

7
Penalties0
How scoring works · current methodology →

For the owner of manifolds.run

3 prompts, 32 points

They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.

Open the owner view →

Select a check to see what we found and how it is graded.

Readable base

41.2 / 50

Passes.

3.5 of 3.5 points.

robots.txt is valid, with 1 user-agent group.

Passes.

8.8 of 8.8 points.

Sitemap declared in robots.txt, listing 5 URLs.

Fails.

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.

Passes.

10.5 of 10.5 points.

All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.

Passes.

8.8 of 8.8 points.

21 of 21 assessed homepage navigation links expose usable destinations.

Passes.

4.4 of 4.4 points.

29 of 29 assessed homepage links and buttons have a nonempty accessible name.

Not applicable.

0 of 0 points.

No applicable form fields were observed in the homepage HTML.

Passes.

2.6 of 2.6 points.

42 of 42 assessed homepage controls and role declarations meet the static role, state and relationship checks.

Passes.

1.8 of 1.8 points.

All 4 pages read pass. The homepage declares itself as its canonical URL.

Agent layer

20 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 11 links across 5 sections.

Passes.

7.5 of 7.5 points.

/llms.txt is descriptive: a summary plus descriptions on 100% of links.

Fails.

0 of 12.5 points.

No /llms-full.txt and no markdown versions linked from llms.txt.

Fails.

0 of 10 points.

None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.

Fails.

0 of 5 points.

robots.txt names no AI crawlers, so every operator has to guess.

Prompt in Pro →
Fails.

0 of 2.5 points.

No usage declaration found in robots.txt or the final successful homepage response header.

Prompt in Pro →

Penalties

− 0

Passes.

Penalty: 0 of 15 points.

Our crawler reaches the page without being challenged.

Passes.

Penalty: 0 of 20 points.

Nothing on the homepage tells a crawler to skip it or to withhold its snippet.

Passes.

Penalty: 0 of 25 points.

The captured homepage HTML contains 1526 content words; completeness is not assessed.

Passes.

Penalty: 0 of 25 points.

robots.txt allows every known search and user-fetch crawler to reach the homepage.

Passes.

Penalty: 0 of 10 points.

The homepage is served over HTTPS and returns HTTP 200.

Passes.

Penalty: 0 of 3 points.

The homepage provides both a non-empty title and meta description.

Passes.

Penalty: 0 of 3 points.

The homepage is reached in 0 redirects.

Passes.

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.

Not applicable.

Adds +1 to the badge when found.

No API catalog published.

Not applicable.

Adds +1 to the badge when found.

No /auth.md published.

Not applicable.

Adds +1 to the badge when found.

No AI Catalog published, so no MCP server card can be discovered.

Not applicable.

Adds +1 to the badge when found.

No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No usable Agent Skills index was found at either well-known path or in the AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.

Not applicable.

Adds +1 to the badge when found.

No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.

Not applicable.

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.

Not applicable.

Adds +1 to the badge when found.

No ACP discovery declaration established at /.well-known/acp.json.

Not applicable.

Adds +1 to the badge when found.

No UCP discovery declaration established at /.well-known/ucp.

Not applicable.

Adds +1 to the badge when found.

No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.

Site profile

Login
Detected
A sign-in or sign-up link
API
Not established
Commerce
Not established

It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.

Access & usage policy

Who can read this page, and for what purpose?

GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.

Sampled URL: https://manifolds.run/

Declared crawling rules

No matching refusal for this URL was found for the listed identities.

Sources and scope: declared crawling rules
  • Declared allow · Scan admission

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    The recorded robots admission decision allowed our crawler to proceed.

    GoodForBotsBot admission along the homepage request chain

    https://manifolds.run/

    robots.txt is present and valid

  • Declared allow · robots.txt

    • goodforbotsbot (Site diagnostics)
    • * (Default robots group)
    • oai-searchbot (ai-search)
    • claude-searchbot (ai-search)
    • perplexitybot (ai-search)
    • mistralai-index (ai-search)
    • kimi-searchbot (ai-search)
    • amzn-searchbot (ai-search)
    • meta-webindexer (ai-search)
    • exasearchbot (ai-search)
    • aiwebindex (ai-search)
    • duckassistbot (ai-search)
    • shapbot (ai-search)
    • yandexadditional (ai-search)
    • yandexadditionalbot (ai-search)
    • gptbot (ai-training)
    • claudebot (ai-training)
    • mistralai-training (ai-training)
    • kimibot (ai-training)
    • ai2bot (Unknown)
    • applebot-extended (ai-training)
    • webzio-extended (ai-training)
    • chatgpt-user (user-fetch)
    • claude-user (user-fetch)
    • perplexity-user (user-fetch)
    • mistralai-user (user-fetch)
    • kimi-user (user-fetch)
    • amzn-user (user-fetch)
    • diffbot-user (user-fetch)
    • firecrawlagent (extraction)
    • webzio (extraction)
    • meta-externalfetcher (user-fetch, agent)
    • google-extended (ai-training, grounding)
    • meta-externalagent (ai-training, product-improvement)
    • amazonbot (ai-training, product-improvement)
    • ccbot (open-dataset, ai-training)
    • googlebot (search)
    • bingbot (search)

    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

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
Coverage and interpretation
  • Crawler coverage includes the registered identities and up to 50 user-agent entries from robots.txt. Source excerpts and detail groups are bounded; omissions are labelled.
  • Observed access describes GoodForBotsBot only. Other crawler entries describe declared rules, not tests of those operators' access.
  • Coverage is the sampled homepage response and collected robots.txt files. No indexing or citation is guaranteed. Usage preferences are declarations, not a legal determination of permission.
  • This explanation adds no points or penalties. Any score effects belong to the linked checks.
  • AIPREF and Content Signals keep their own definitions. AIPREF search can include processing used exclusively for search; training preferences are not a blanket ruling on every search process.

In its category

22nd of 42 in Developer Tools & APIs

  1. 1Good for Botsgoodforbots.com
  2. 2ProxyJamproxyjam.com
  3. 22Manifolds · this reportmanifolds.run

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.

Scan details

Every scan is kept. Pro draws the history as a chart →

Scanned
28 Oct 2026
Rubric
0.9.0
Requests
23
Fetched
706.6 KB
Took
13.9 s
Homepage
175 ms · direct
Pages read
4
robots.txt
allowed
Which pages the scan read

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.

  • Homepagealways read
  • /use-cases/productcollection · linked from the homepage · from the sitemap · read
  • /pricingpricing · linked from the homepage · from the sitemap · read
  • /use-cases/marketinglinked from the homepage · from the sitemap · read

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 →