Does FirmlyAI Bot respect robots.txt?

Cloudflare's record marks FirmlyAI Bot as not following robots.txt. The record also lists no stable user-agent pattern, so robots.txt is not a reliable control for this bot.

Does FirmlyAI Bot affect AI search results or model training?

Its documented purpose is agentic commerce. The available operator material does not say that it determines public AI search inclusion or supplies model-training data.

What happens if I block FirmlyAI Bot?

Blocking it can prevent Firmly-connected agents from navigating the site's commerce flow. It is not documented as an opt-out control for general AI search or model training.

FirmlyAI Bot: AI Crawler Guide & robots.txt

Q: How can I verify FirmlyAI Bot is genuine?

Verify its Web Bot Auth HTTP message signature with Firmly's keys at https://api.firmly.online/.well-known/http-message-signatures-directory. The bot has no stable user-agent token to use as identity proof.

What is FirmlyAI Bot?

FirmlyAI Bot is an automated commerce bot operated by Firmly. Firmly describes it as a bot that navigates e-commerce websites for agentic commerce workflows. Its stated purpose is shopping activity, not ordinary search-engine crawling.

Firmly's platform connects merchants with AI agents and other sales channels. The company's published flow runs from product discovery through checkout, while its APIs provide standardized access to merchant carts. FirmlyAI Bot is the website-facing part of that commerce setting.

The available record does not give FirmlyAI Bot a crawl schedule or say that it builds a general web index. A visit should be read as agentic commerce traffic. Site owners can assess it by whether the request needs the public shopping flow it is trying to use, rather than assuming it is an SEO crawler.

Allowing FirmlyAI Bot can make a merchant's site usable through Firmly-connected shopping agents. It does not establish that a page will appear in public AI search results, and the supplied operator material does not say that fetched content is used for model training. Commerce access, AI search inclusion, and training are separate questions here.

FirmlyAI Bot has no published stable user-agent token. Cloudflare's bot record instead provides a Web Bot Auth signature directory at https://api.firmly.online/.well-known/http-message-signatures-directory. A valid HTTP message signature checked against those keys offers stronger identity evidence than a self-declared user-agent string.

Cloudflare's bot directory lists Firmly at https://www.firmly.ai/, supplies no user-agent patterns for this bot, and marks it as not following robots.txt. There is therefore no dependable bot-specific robots.txt rule. If a site needs to allow or deny FirmlyAI Bot, the practical control point is signature validation at the CDN or application edge.

Relevant for AI search

Is FirmlyAI Bot relevant for AI search?

Yes. FirmlyAI Bot collects pages for an AI product, so what it can crawl influences how AI systems describe your brand.

FirmlyAI Bot crawls and indexes pages so the AI search or assistant behind it can retrieve them at answer time. A page it has never fetched cannot be quoted, summarized, or linked in that product's answers, so most sites keep it allowed to stay citable. Blocking it removes your pages from that AI surface and hands those citations to competitors.

How to handle FirmlyAI Bot

Base the decision on commerce policy. Merchants that want Firmly-connected agents to use their shopping flow can admit authenticated FirmlyAI Bot traffic to the routes that workflow needs. Sites that do not support automated shopping can reject it at the edge.

Do not invent a user-agent rule for this bot. Cloudflare publishes no stable user-agent pattern and marks the bot as not following robots.txt, so a robots.txt entry would neither identify it reliably nor provide an assured block.

Validate Web Bot Auth HTTP message signatures with the keys at https://api.firmly.online/.well-known/http-message-signatures-directory. Apply the allow or block decision only after signature verification. Requests that merely claim to be FirmlyAI Bot should receive the same treatment as other unverified automation.

Keep account, administration, and other non-public routes behind their normal authorization checks regardless of the bot decision. Signature validation confirms the requesting agent's identity; it does not grant that agent permission to every URL.

Examples

A merchant allows a correctly signed FirmlyAI Bot request to use the public shopping flow needed by a Firmly-connected agent.
An edge rule rejects an unsigned request that claims to be FirmlyAI Bot instead of trusting its request headers.
A commerce team investigating an interrupted agent checkout checks whether signature verification or route policy stopped the request.

Frequently asked questions about FirmlyAI Bot

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

Firmly operates the bot to navigate e-commerce sites for agentic commerce workflows. Firmly's platform supports shopping activity from discovery through checkout.

Related bots

Amazon Kendra

Amazon Kendra is a managed information retrieval and intelligent search service that uses natural language processing and advanced deep learning model.

AI Assistant