bbki.ng
partial
Claude Code
intent

What does bbki.ng do and who is it for? Explain it back to me.

39steps
154.6sduration
$2.5717cost
648,967tokens
42 steps3 reasoning steps23 searches
home
docs
docs
/help
.well-known
docs
/api
search
search
search
search
/api
search
search
cf.home
search
search
/org/bbki.ng
/package/@bbki.ng/bbimg
search
search
/bbb0ttle
search
search
/bbb0ttle/gblog
/bbb0ttle/gblog/main/r…
search
search
search
search
search
/micropub/servers
search
search
search
search
search
search
/micropub
81%
on-site discovery
81%
reliability
44%
link following
path origin
  • previous resource44%
  • web search19%
  • prior knowledge31%
  • other6%
insight

The agent gathered partial information about bbki.ng but could not complete the task due to the site's minimal documentation and lack of accessible marketing material. It identified the service as an IndieWeb Micropub platform from technical endpoint inspection and external reference documentation, but found no pricing information, clear feature list, target audience positioning, or competitive differentiation on the site itself. The site proved difficult to navigate because it renders as a client-side single-page application with no accessible HTML content.

  • ›Step [37] (cf.bbki.ng/micropub endpoint) returned machine-readable Micropub configuration (media-endpoint, post-types: article/note), the only substantive technical data the site exposed directly. This was content-bearing and allowed identification of the protocol foundation.
  • ›Step [31] (indieweb.org/Micropub/Servers) was cited as a source but did not mention bbki.ng by name—the agent inferred the connection from protocol knowledge rather than discovering it listed there.
  • ›All direct bbki.ng fetches ([1], [2], [3], [4], [6], [7], [38]) returned identical truncated HTML (client-side app shell), providing zero machine-readable content about what the service does, costs, or who it's for. The agent could not extract an 'about,' 'pricing,' 'help,' 'docs,' or 'api' page.
  • ›The agent relied heavily on prior knowledge (31% of fetch sources) and assembled fragments from external sources (GitHub profile of creator bbb0ttle, IndieWeb protocol documentation) rather than discovering information on bbki.ng itself.
  • ›Search attempts yielded no blog posts, reviews, testimonials, or third-party coverage of bbki.ng that would clarify pricing, features, or positioning. The service has virtually no online presence beyond its own domain.
  • ›The site is not agent-ready: it publishes no machine-readable metadata (structured data, llms.txt, API documentation endpoints), no pricing page, no comparison against alternatives, and no public feature list. A human visiting the site would face the same information gaps.

Help the next agent finish on bbki.ng

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 →