Skip to content
Good for Bots

ProfitBot

profitbot.ai

Locally run trading automation for meme coins, prediction markets and NFTs

Good for Bots: Good +3, 89 of 100Get this badge →

On your homepage, it turns this report’s link to profitbot.ai dofollow.

Scanned

What is ProfitBot?

ProfitBot is trading automation software that is installed and run locally on the user's computer or a VPS. The input describes it as a non-custodial desktop app for macOS, Windows and Linux that trades meme coins on Solana, BSC, Base, Robinhood, Ethereum and Hyperliquid, prediction markets on Polymarket and Kalshi, and NFTs on OpenSea, using strategies and risk rules the user configures. It is aimed at people who want to automate trading across these markets. Access is sold as time-based licenses from 30 to 180 days, priced in USDC, with a lifetime option and an annual plan mentioned in the llms.txt. Each license covers all nine markets. The homepage states that no ProfitBot trading fee is charged, while network gas, market fees and optional AI provider costs still apply, and that the user's keys stay on their own device.

Through a bot’s eyes

“ProfitBot is downloadable desktop software that automates trading of meme coins on six blockchains, Polymarket and Kalshi prediction markets, and OpenSea NFTs, running locally on the user's computer under a time-limited license.”

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 model reading this homepage learns that the site sells automated trading software across meme coins, prediction markets and NFTs, and that it is non-custodial and runs locally. The text covers the nine markets, the token safety checks, four setup steps, a comparison table with manual and Telegram bot trading, the license tiers with USDC prices and day counts, and a short FAQ on fees, key safety, coding skills, operating systems and supported markets. Contact details and a download link are not present in the homepage text. The Markdown version carries the same copy with absolute links but drops the license prices, which appear as dashes, and omits the simulated dashboard. The llms.txt adds product facts: the software is desktop-only, strategy limits, AI options, Ethereum payment steps, a support email and community address, the list of website languages and a risk statement. The JSON-LD block names the product, gives a short description and the site URL, and adds no further facts.

What stays hidden

No company name, legal entity or jurisdiction appears anywhere in the input, so who operates the software cannot be determined. The lifetime license price is not stated in any part of the input, and the Markdown version shows no license prices at all. Real trading results are not available, since the dashboard and strategy activity are labelled simulated.

Good for Bots report

ProfitBot scores 89 of 100: 45 of the 50 base points, 44 of the 50 agent-layer points, no penalties.

Earned

45 of the 50 base points above the line, 44 of the 50 agent-layer points below it.

89
Penalties0
How scoring works · current methodology →

For the owner of profitbot.ai

3 prompts, 11 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

45 / 50

Passes.

3.3 of 3.3 points.

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

Passes.

8.3 of 8.3 points.

Sitemap declared in robots.txt, listing at least 1000 URLs.

Passes.

8.3 of 8.3 points.

All 4 pages read pass. The homepage describes itself to machines as Product, Brand, AggregateRating in valid schema.org JSON-LD.

Half passes.

5 of 10 points.

2 of 4 pages read pass; 2 partly. The homepage is partly structured: The outline jumps from h1 to h3, which the standard forbids.

Passes.

8.3 of 8.3 points.

27 of 27 assessed homepage navigation links expose usable destinations.

Passes.

4.2 of 4.2 points.

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

Passes.

2.5 of 2.5 points.

3 of 3 assessed homepage form fields meet the static naming and field-semantics checks.

Passes.

2.5 of 2.5 points.

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

Passes.

1.7 of 1.7 points.

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

Agent layer

43.8 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 1147 links across 2 sections.

Passes.

7.5 of 7.5 points.

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

Passes.

12.5 of 12.5 points.

/llms-full.txt serves the site's content as markdown (at least 64 KB).

Passes.

10 of 10 points.

All 4 pages read pass. The homepage serves markdown on `Accept: text/markdown`.

Fails.

0 of 5 points.

robots.txt states AI usage preferences, but names no AI crawler individually.

Passes.

2.5 of 2.5 points.

Declares AI usage preferences via Content-Signal (robots.txt): ai-train, ai-input, search.

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 1116 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 74 ms.

Agent capabilities

3 of 11 · no points

Each one found adds +1 to the badge.

Passes.

+1 on the badge.

Publishes an API catalog describing 2 APIs.

Not applicable.

Adds +1 to the badge when found.

No /auth.md published.

Half passes.

Adds +1 to the badge when found.

The AI Catalog lists an MCP server card, but the card has no name.

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.

Passes.

+1 on the badge.

Publishes an Agent Skills index with 3 usable entries. Skill artifacts and digests were not verified.

Passes.

+1 on the badge.

Found 4 static WebMCP tool declarations in the collected HTML. Browser registration and execution were not verified.

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
Not established
API
Detected
A link to a machine-readable API description
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://profitbot.ai/

Measured, our crawler
HTTP 200
GoodForBotsBot received HTTP 200 via a direct request.
Search and user-fetch crawlers refused
0 of 20
robots.txt refuses none of them.
Training crawlers refused
0
Refusing training would not change the score.

Crawlers and what robots.txt declares for them

Rules for the sampled URL, read the way RFC 9309 reads them. These are declarations, not access tests.

Crawlers and what robots.txt declares for them on the sampled URL
CrawlerPurposeDeclared accessScore effectRule that applies
Our crawler, measured
GoodForBotsBotGood for BotsSite diagnosticsFetchedHTTP 200, directNot scoredrobots.txt admitted our crawler
Search and AI answers
OAI-SearchBotOpenAIAI searchAllowedNoneNot named; User-agent: * applies
Claude-SearchBotAnthropicAI searchAllowedNoneNot named; User-agent: * applies
PerplexityBotPerplexityAI searchAllowedNoneNot named; User-agent: * applies
GooglebotGoogleSearchAllowedNot scoredNot named; User-agent: * applies
, all allowed
Fetches a person asked for
ChatGPT-UserOpenAIUser fetchAllowedNoneNot named; User-agent: * applies
Claude-UserAnthropicUser fetchAllowedNoneNot named; User-agent: * applies
Perplexity-UserPerplexityUser fetchAllowedNoneNot named; User-agent: * applies
, all allowed
Model training, never scored
GPTBotOpenAIAI trainingAllowedNoneNot named; User-agent: * applies
ClaudeBotAnthropicAI trainingAllowedNoneNot named; User-agent: * applies
Google-ExtendedGoogleAI training, GroundingAllowedNoneNot named; User-agent: * applies
, all allowed
Agents, extraction and others
, all allowed

The robots.txt groups behind this table

User-agent: *
Allow: /

https://profitbot.ai/robots.txt

How to read this table

Each row says what robots.txt asks of that crawler. It does not show whether the crawler obeys, or how a firewall treats it. We measured only our own request.

Refusing search or user-fetch crawlers costs points under AI crawler access. Refusing training crawlers costs nothing.

Indexing directives, Content-Signal and AIPREF preferences are in the tabs below.

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
  • 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://profitbot.ai/

    robots.txt is present and valid

  • Observed · Direct request

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

    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://profitbot.ai

    HTTP 200

    Serves the homepage over HTTPS with HTTP 200

  • Observed · Final homepage response

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

    GoodForBotsBot received HTTP 200 via a direct request.

    homepage response

    https://profitbot.ai/

    HTTP 200
    Transport: direct

    Serves the homepage over HTTPS with HTTP 200Serves our crawler without a challenge

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

5th of 111 in SaaS & Web Apps

  1. 1Appnaryappnary.com
  2. 2BulkSharebulkshare.cloud
  3. 5ProfitBot · this reportprofitbot.ai

The prompts in the owner view would take ProfitBot to 100, first in its category.

To the prompts →

Category average 58. 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
20 Nov 2026
Rubric
0.9.0
Requests
29
Fetched
3.5 MB
Took
26.2 s
Homepage
74 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
  • /blogcollection · linked from the homepage · from the sitemap · read
  • /affiliateslinked from the homepage · from the sitemap · read
  • /contactcontact · linked from the homepage · from the sitemap · read

More like ProfitBot:SaaS & Web AppsFintechBlockchain & CryptoSelf-hosted

Same category

vouchgeo.com

Tracks how AI assistants mention a brand across multi-question buying conversations

Same category

talhabashir.com

Free online calculators and tools for US taxes, mortgages, business and personal finance

Also Good

saascubes.com

Curated SaaS directory offering permanent do-follow backlinks for modern software products

Also Good

dolaai.pro

AI agent that edits Unreal Engine 5.7 Blueprints, C++ and levels in the open editor

brivoy.com

Community site where makers launch new products and early adopters discover them

contentspilot.com

AI co-pilot that plans, drafts and schedules Instagram carousels and posts in brand style

Do you run profitbot.ai? Open the owner view → Removing the listing is free. Remove →