Does CledaraBot affect AI search or model training?

No direct effect is documented. CledaraBot carries out SaaS administration rather than building a public search index or collecting a general training corpus.

Will CledaraBot obey robots.txt?

Its robots.txt behavior is unknown, and Cloudflare's agent directory marks it as not following robots.txt. Use the token-specific rule to state a preference, but protect administrative pages with application and edge controls.

Should a SaaS vendor allow CledaraBot?

Allow it when your customers use Cledara workflows that need your service, and limit it to the required routes and permissions. Block it if you do not support those automated tasks or if a request fails identity and authorization checks.

Cledara SaaS Management Agent AI Crawler Guide

Q: How do I verify a CledaraBot request?

Validate the Web Bot Auth HTTP message signature with the directory at `https://gerard.cledara.ai/.well-known/http-message-signatures-directory/`. The `CledaraBot/1.0` header can be copied and is not proof on its own.

What is Cledara SaaS Management Agent?

Cledara SaaS Management Agent performs administrative work approved by a Cledara customer. Cledara is a platform for managing software subscriptions, payments, access, budgets, contracts, and invoices. Within that setting, the agent is identified as automating tasks such as invoice collection and user management.

This traffic has no direct role in public AI search visibility. Letting CledaraBot reach a billing or administration page does not make that page eligible for a search answer, and blocking it does not opt a site out of model training. The practical effect is whether a Cledara customer's requested administrative workflow can finish.

The agent uses the stable token CledaraBot; Cloudflare's bot directory records the full user agent as CledaraBot/1.0. It also supports Web Bot Auth. Cledara's signature keys are published at https://gerard.cledara.ai/.well-known/http-message-signatures-directory/, which allows an edge service to verify the request without trusting the name in the header.

A request from this agent should belong to a specific SaaS administration workflow, not an attempt to assemble a public web index. For a software vendor, that may mean the agent is reaching a page or flow needed to carry out a customer's approved task. The customer and the permissions attached to that workflow determine what it can do.

Cledara's wider product automates recurring operational work around software, including access requests and invoice handling. Its official site is https://www.cledara.com. The bot record is narrower: it establishes that this agent performs customer-approved SaaS tasks, but it does not document every action, page sequence, or credential method the agent may use.

Robots.txt support is unknown in this catalog, and Cloudflare's bot directory lists the agent as not following robots.txt. That makes a robots entry useful as a preference, not as an access-control boundary. Authentication, authorization, and signature-aware edge rules remain the appropriate controls for SaaS administration pages.

Relevant for AI search

Is Cledara SaaS Management Agent relevant for AI search?

Yes. Cledara SaaS Management Agent collects pages for an AI product, so what it can crawl influences how AI systems describe your brand.

Cledara SaaS Management Agent 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 Cledara SaaS Management Agent

If your service expects Cledara-driven administration, allow only the routes and actions needed for that integration and keep normal account authorization in place. A verified bot identity tells you who sent the request; it does not replace the customer's permission to change users or collect an invoice.

You can publish this crawler preference for the stable token:

User-agent: CledaraBot
Disallow: /

Cledara has no confirmed robots.txt commitment for this agent, so do not depend on that rule for protected screens. Validate Web Bot Auth against https://gerard.cledara.ai/.well-known/http-message-signatures-directory/ and enforce any allowlist, rate limit, or denial at the edge or in the application.

Examples

A SaaS vendor sees CledaraBot during an approved invoice collection workflow and permits access only to the relevant account area.
An IT team uses Cledara to carry out a user-management task, while the target application still checks the customer's account permissions.
A gateway rejects a request claiming to be `CledaraBot/1.0` when its Web Bot Auth signature does not validate against Cledara's keys.

Frequently asked questions about Cledara SaaS Management Agent

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

It automates SaaS administration tasks approved by a Cledara customer. The documented examples are invoice collection and user management within Cledara's software management workflow.

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