by Bastion HelixCommunityFree checks before AgentOne uses a web page. They cover whether it is allowed (robots.txt, AI rules), what the site offers agents, and a warning when the page holds instructions aimed at AI.
Agent Lens helps AgentOne decide whether and how to use a web page before relying on it. It has two free, read-only tools:
site: a card for any website. It shows the site's llms.txt (and llms-full.txt), sitemap (page count and first addresses), feeds, language versions, Content Signals, and which known AI crawlers and agents its robots.txt allows.
preflight: a check of one page. It shows whether AgentOne may use the page (robots.txt for Agent Lens and, if you name your own bot, for that bot too; Content Signals such as ai-input and ai-train; meta robots), whether a bot check or sign-in stands in the way, which engine reading it would need (plain fetch, a lightweight browser or Chromium), and a warning when the page contains text that looks like instructions aimed at AI agents (possible prompt injection), including whether it was hidden from human readers.
Both tools only read public web pages. Agent Lens obeys robots.txt and Content Signals, never signs in, and never tries to get past bot checks or human checks. It keeps no request logs and does not store page addresses or page content. No account or key is needed. Calls are rate-limited.
Example prompts:
Made by Bastion Helix (bastionhelix.com).
monday.com project management and CRM for projects, tasks, portfolios, boards, workflows, milestones, dependencies, forms, dashboards, cross-project portfolio status, and critical paths.
by monday.com
Manage databases, authentication, and storage
by Supabase
Access and create new content on Miro boards
by Miro