colibrios.com
partial
Claude Code
intent

What does colibrios.com do and who is it for? Explain it back to me.

33steps
137.7sduration
$2.6268cost
376,277tokens
37 steps4 reasoning steps20 searches
home
docs
/api/pricing
docs
search
search
search
search
docs
/help
/features
/faq
/api/products
/index.json
search
search
/p/10018513/colibri
search
search
search
search
search
search
search
search
/demo
search
search
/product/441632-colibri
search
search
search
search
85%
on-site discovery
85%
reliability
38%
link following
path origin
  • previous resource38%
  • web search15%
  • prior knowledge46%
insight

The agent gathered a partial understanding of Colibri OS by fetching the homepage and several key pages (pricing, features, about, blog, help, faq, demo), but could not access the actual content because the site is a client-side-rendered React application. The agent was forced to rely on metadata, page titles, and prior knowledge to infer what the product does, who it's for, and how it's priced — but could not retrieve specific pricing tiers, feature breakdowns, or concrete details from the site itself. The site is poorly navigable for agents: it renders no meaningful content in the HTML response, offers no API endpoints with data, and publishes no machine-readable documentation or structured data.

  • ›Every HTML fetch from colibrios.com returned only boilerplate React scaffolding (head, link tags, Brand Kit v2 notice) with no rendered content, indicating the site relies entirely on client-side JavaScript to display product information.
  • ›The agent correctly identified the site's rendering strategy and attempted workarounds by guessing API routes (/api/pricing, /api/products, /index.json) and searching for external reviews on Capterra and SoftwareAdvice, but those review sites were blocked by Cloudflare.
  • ›The agent's final answer relied almost entirely on inferences from page URLs, meta descriptions, and 15% web search results — not from the actual website. No primary data about pricing amounts, tier names, feature details, or differentiators came from the site itself.
  • ›The site offers no fallback formats: no static text documentation, no JSON API, no sitemap with metadata, and no open graph / schema.org structured data in the HTML head that would help agents parse the product positioning.
  • ›Web search results did not return any relevant reviews, G2 entries, or Capterra pages for colibrios.com specifically; most results were for unrelated products (KolibriOS, Colibri.ai, Colibri CRM, etc.), making external validation impossible.
  • ›The agent correctly concluded it could identify the *category* of product (all-in-one coaching/retreat platform) and the *approach* (free trial, month-to-month billing, three tiers called Serve/Gather/Lead), but could not provide specific pricing, feature comparisons, or use cases.

Help the next agent finish on colibrios.com

Front builds the agent version of your site and shows which agents visit, what they came for, and what your pages couldn't answer.

or talk to us about agent readiness →