Novellum AI Crawl
Documented identityNovellum AI Crawl is listed here in the ai crawlers category and is associated with Novellum. Provides agent-oriented crawling through a Novellum MCP-related tool. This profile explains the identity and its documented scope so readers can distinguish it from a downloadable coding agent or a language model. It is an independent reference, not an operator endorsement.
What Novellum AI Crawl does
The display label differs from the documented Novellum request token. Cloudflare also links a published signature-agent directory for this identity.
Novellum AI Crawl user-agent identity
The request identifier recorded for this profile is Novellum. A display name, an HTTP user-agent string and a robots.txt product token can differ. Confirm the control spelling in the linked operator guidance before writing a rule. A name in a request header alone is not authentication: another client can copy it.
Automated web collection
Collection crawlers can visit pages without a person requesting each individual URL. Their purposes differ across operators, so the AI Crawler category should not be read as a universal technical specification. Keep the stated purpose and the evidence source together. A dashboard label is useful context, but it does not disclose an entire downstream data pipeline.
Separate the collection identity from related search or assistant identities when reviewing access. A setting for one name does not necessarily cover all services from the same company. Record which token a rule targets, where the rule is enforced and what behavior the operator documents. Do not assume that every crawler uses the same controls.
How to investigate a visit
Keep a representative log entry with the requested URL, timestamp, response code and source address. Compare it with current operator documentation and any published identity evidence. Use published IP ranges, DNS checks or request-signature verification only when the operator actually supports that method. This profile does not publish guessed address ranges or a universal allow rule.
Scope, costs and source limits
A recorded visit does not establish a model version, an API token price or a software license. These properties belong to separate products and agreements. The details below state the scope that was established for this identity; unconfirmed implementation information is identified as such. Any subscription, API or browser-service charge must be checked on the operator's current pricing pages.
Novellum AI Crawl questions
Can I install this crawler as an agent?
This is a web-identity reference. An operator-managed crawler or fetcher is not automatically available as self-hosted software. If the operator offers a separate SDK, API or browser product, use that product's documented installation and access process rather than assuming the crawler name is an installable package.
Where should I verify the details?
Review the source documentation for Novellum AI Crawl and the Novellum website. For related entries, browse the XPU Live agent and crawler directory. To compare inference services separately, visit the AI provider directory.
What it can do
- Provides agent-oriented crawling through a Novellum MCP-related tool.
- Request identity: Novellum
- Source-linked operator reference
- Distinct category: AI Crawlers
Where it fits
- Automated web collection
- Web traffic identification and log investigation
- Comparing crawler and assistant roles
Models & deployment
Model compatibility
Not a standalone model endpoint. A supported model list and model-specific prices do not follow from this web identity.
Where it runs
Operated through Novellum infrastructure or its managed services. This profile is not a self-hosted deployment recipe.
Cost model
No per-token tariff is assigned to this crawler identity. Operator services, if offered separately, have their own current access terms and pricing.
Limitations & scope
The display label differs from the documented Novellum request token. Cloudflare also links a published signature-agent directory for this identity. User-agent matching alone does not authenticate a request. Technical behavior not confirmed in the linked sources is not asserted here. Official operator logo could not be verified because the operator website was unavailable at review time. The initial is a neutral placeholder.