Original Summary

I've been building domscout, a capture API: it loads the page in Chromium, then returns the Markdown, the page's links, some metadata (final URL, title, OG tags, word count) and a screenshot in a single JSON response. As of now, there is no-key demo available, 3 captures per hour per IP. The demo accepts a small set of options: format (png/jpeg/webp), viewport size (320–1600 px), mobile/touch emulation, and "semanticNodes": true for the page's element structure. To test it, ask your agent to "read https://www.domscout.io/llms.txt and turn https://www.wikipedia.com into Markdown with the demo." Throw hard pages at it: SPAs, infinite scroll, weird tables. I have been able to get a few initial set of users since the launch a few days back. But I am still looking/searching for the cases where my app fails. I added crawling of website and extracting pages as per the json schema required recently. And two things, one I would love to know if anyone have implemented websearch without relying on SERP-API. THe other thing is I am a bit scared if my app would fail any of these existing users and I honestly dont want that. So I am being over consious now, and I would love to see what breaks my app, like what all the literal fallbacks would be. Any sort of suggestions from any of you fellow developers in this regard and if you all could try the app and give me some honest review, I would be greatly happy and sort of help me get an idea where I am positioned. Thank you!   submitted by   /u/TraditionalPitch1666 [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/9/27 20:44:08