fume.finance
success
Claude Code
intent

What does fume.finance do and who is it for? Explain it back to me.

13steps
41.9sduration
$0.0552cost
85,493tokens
19 steps6 reasoning steps
home
docs
docs
/index.md
docs
/tokenization-engine.md
/features
/ai-agent-funds.md
/solutions.md
/omniclear.md
.well-known
docs
/docs.md
100%
on-site discovery
77%
reliability
38%
link following
path origin
  • previous resource38%
  • prior knowledge62%
insight

The agent successfully assembled a comprehensive explanation of Fume's business model, products, pricing, and differentiation by fetching markdown documentation directly. The site is moderately agent-ready: it publishes detailed product descriptions and pricing tables in machine-readable markdown format, but critical information (AI agent pricing, OmniClear standalone costs, competitive positioning) remains opaque or absent, requiring the agent to acknowledge gaps rather than fill them with speculation.

  • ›Steps [7, 11, 13, 15, 17] returned well-structured markdown pages with product descriptions, pricing tables, and use-case workflows. These were the primary content sources for the final answer and demonstrate the site publishes substantive information in a machine-readable format.
  • ›The agent discovered these markdown pages by prior knowledge guessing of URL patterns (e.g., `/index.md`, `/pricing.md`, `/ai-agent-funds.md`) rather than being guided by navigation links from the homepage. This indicates the site does not surface its own markdown documents through visible navigation—they exist but are not discoverable without knowing the URL convention.
  • ›Step [15] returned a pricing table for tokenization products (free tier, $179/month platform fee, 0.1% protocol fee) but explicitly states AI agent pricing has 'no public price list' and requires booking a call. The agent correctly reported this opacity and did not fabricate pricing.
  • ›Steps [5, 12, 16] returned 404s for `/features`, `/solutions`, and `/resources/pricing`, indicating either incomplete site structure or deliberate pruning. The agent noted that `/solutions` was referenced but unavailable, limiting ability to show real implementation examples.
  • ›The site is agent-ready for commodity/transparent products (tokenization, registry, platform fee structure) but deliberately opaque for high-touch services (AI agents, private deployments, settlement pricing). This is a business-motivated design choice, not a navigation failure, but it prevented the agent from fully answering the 'how is it priced' question.

Want to run your own?

Join the waitlist for early access to point your own agents at any domain, with the intents you choose.

or talk to us about agent readiness →