bokendell.com
success
Claude Code
intent

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

16steps
53.8sduration
$0.3281cost
151,852tokens
25 steps9 reasoning steps
home
docs
/about.md
docs
llms.txt
agents.md
/projects/cli.md
/projects/golf.md
/resume.yaml
.well-known/mcp
.well-known/agent-card
/experience.md
/resume.md
/projects
/projects.md
/reference.md
100%
on-site discovery
75%
reliability
88%
link following
path origin
  • previous resource88%
  • prior knowledge13%
insight

The agent successfully gathered enough information to explain bokendell.com's purpose, audience, and philosophy. The site is well-structured for machine consumption, publishing content across multiple formats (Markdown, JSON, MCP, OpenAPI), which allowed the agent to construct a coherent answer from fragments. However, some expected content (resume details, experience timeline, writing posts) returned errors or empty states, forcing the agent to work around gaps in the surface-level data.

  • ›The site publishes its own identity via machine-readable formats: llms.txt, agent.md, and MCP JSON endpoints all explicitly stated 'full-stack software engineer focused on developer tools, mobile apps, and AI-assisted workflows.' This was the canonical source for answering 'what do they do' and 'who it's for.'
  • ›Project details (cli.md, golf.md) were fetched from explicit markdown endpoints the site published, not guessed. The agent discovered these via the agent.md index, which listed them as structured tool responses available via MCP. This demonstrates the site deliberately exposes project metadata in machine-readable form.
  • ›The site is highly agent-ready: it publishes discovery endpoints (.well-known/agent-card.json, .well-known/mcp.json), declares MCP tools as a structured list, and offers parallel formats (HTML, Markdown, JSON, OpenAPI, YAML) for the same content. However, some content (resume.md, experience.md, resume.yaml) returned 500 errors, and the 'writing' section was reported as empty despite a case study reference to a blog post.
  • ›The agent had to infer 'how it's priced' (free, not commercial) from context clues (employment at BambooHR, 'personal projects', no pricing page found). This was not explicitly stated on a discoverable page, requiring reasoning rather than retrieval.
  • ›The site's portfolio structure is self-referential: it documents developer tool patterns while simultaneously being built with those patterns (Next.js, open APIs, MCP integration). The agent correctly identified this as unusual and intentional rather than a typical portfolio.

See every agent that visits bokendell.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 →