odiga.io
partial
Claude Code
intent

What does odiga.io do and who is it for? Explain it back to me.

8steps
45.7sduration
$0.5312cost
32,272tokens
10 steps2 reasoning steps2 searches
home
docs
docs
home
home
search
search
/en/b/207481822794220918
60%
answer from your site
50%
answer efficiency
80%
followed site links
answer sources
  • from this site60%
  • from agent knowledge40%
url discovery
  • given in the task17%
  • followed a link67%
  • found via web search17%
insight

The agent assembled a partial but usable explanation of odiga.io by fetching the homepage and following a search-discovered board example, but could not find pricing, business model, or company background information — these sections relied on noting their absence rather than retrieving facts. The site exposed its core curation and discovery features directly but buried essential business/positioning context.

  • ›Step [1] and [4] (homepage fetches) provided the foundation: geographic scope, recognition categories (Michelin, TV shows, heritage designations), and the board/curation feature. This core answer came directly from the site's public homepage.
  • ›Steps [2] and [3] (404s for /pricing and /about) immediately revealed critical gaps — the site has no discoverable pricing page or company information section, forcing the agent to declare uncertainty rather than guess.
  • ›Step [7] (search for 'odiga Korean Japanese restaurant curation platform') returned a search snippet describing odiga as 'an opinionated index for Korean mat-jib' — this characterization appears in the agent's final answer but was extracted from a search result, not the site's own homepage, indicating the site may not clearly state its positioning on its own pages.
  • ›Step [8] (fetching a specific board URL from search results) showed the user-created curation feature in action but was discovered via search, not site navigation — the homepage did not surface a link to example boards or feature documentation.
  • ›The agent correctly identified that the platform is primarily Korean/Japanese-language and oriented toward those markets, explaining the sparse English-facing business documentation, but this observation relies on model inference about missing content rather than explicit site statements.

Help the next agent finish on odiga.io

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 →