allium.so
success
Claude Code
intent

What does allium.so do and who is it for? Explain it back to me.

13steps
80.9sduration
$0.8314cost
127,015tokens
17 steps4 reasoning steps5 searches
home
docs
docs
search
search
/compare
/compare/allium-vs-dune
search
/product/allium-develo…
/product/real-time-str…
search
search
docs.home
50%
on-site discovery
100%
reliability
25%
link following
path origin
  • previous resource25%
  • web search50%
  • prior knowledge13%
  • other13%
insight

The agent successfully assembled a comprehensive explanation of Allium by fetching the homepage, pricing page, about page, comparison pages, and product pages. The site was navigable and clearly structured around use cases and product offerings, but pricing itself remains deliberately opaque—the agent had to work around the lack of public pricing tiers by acknowledging what it could not find and inferring from context. The agent fulfilled the task by explaining what Allium does, who it serves, how it's priced (with caveats), and how it differs from alternatives, all grounded in the site's own content.

  • ›Steps [1], [4], [12], [13] returned product pages with clear positioning: Allium positions itself as 'system of record' for on-chain data, serving enterprise institutions with audit-grade requirements. Each product page (Developer APIs, Real-Time Streaming, Datashares, About) reinforced this messaging consistently.
  • ›Steps [3], [8], [10] reveal the site's comparison-focused navigation: Allium hosts /compare pages directly on-site comparing itself to Dune, SQD, and others. This surfaced the key differentiators (SOC 2 certification, 0.000011% data deviation, 150+ chains, multiple delivery methods) without requiring external knowledge.
  • ›Pricing information (step [3]) leads to a 'Request a Demo' page rather than a pricing matrix. The agent correctly identified this as a friction point and noted it as 'confusing'—the site deliberately obscures public pricing, forcing enterprise sales-driven discovery. The agent worked around this by citing what could be inferred (free tier, custom enterprise quotes) from the site's positioning.
  • ›Product boundaries required assembly: steps [12] and [13] showed 'Allium Developer' (APIs) and 'Real-Time Streaming' as separate offerings. The agent had to synthesize across multiple pages to understand these are complementary delivery methods within one platform, not distinct products—the site doesn't publish a crisp product matrix.
  • ›The site is agent-ready for discovery and identity (clear positioning, use-case pages, comparison pages exist and are linked), but not for billing discovery—no pricing calculator, no tier comparison table, no entry-level offer visibility. This is intentional SaaS strategy but creates opacity for autonomous agents.

See every agent that visits allium.so

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 →