Show HN: Sosumi.ai – Convert Apple Developer docs to AI-readable Markdown (sosumi.ai)

133 points by _mattt ↗ HN
I got tired of Claude hallucinating Swift APIs. It does a good job at Python and TypeScript, but ask it about SwiftUI and it's basically guessing.

The problem? Apple's docs are JavaScript-rendered, so when you paste URLs into AI tools, they just see a blank page. Copy-pasting works but... c'mon.

So I built something that converts Apple Developer docs to clean markdown. Just swap developer.apple.com with sosumi.ai in any Apple docs URL and you get AI-readable content.

For example:

- Before: https://developer.apple.com/documentation/swift/double

- After: https://sosumi.ai/documentation/swift/double

The site itself is a small Hono app running on Cloudflare Workers. Apple's docs are actually available as structured data, but Apple doesn't make it obvious how to get it. So what this does is map the URLs, fetch the original JSON, and render as Markdown.

It also provides an MCP interface that includes a tool to search the Apple developer website, which is helpful.

Anyway, please give this a try and let me know what you think!

35 comments

[ 3.8 ms ] story [ 64.9 ms ] thread
Very interesting. You have any before and after examples?

Curious how it handles some of the concurrency stuff. Actors, async/await etc..

As someone who is currently building my first iOS app, I am extremely happy to have this. This will be much nicer doing my animation documentation.
Do you have a public repo? Would love to see how it's working.
Could you share what is your motivation behind doing whole domain and web hosting ?

Personally I feel that this whole AI induced problem should even exist in the first place, but even then it is ridiculous, that you have to query some web api to solve this problem, why not just publish parsed and converted to .md set of local files and be done with it.

I think it's safe to assume most big players have browser rendering enabled (I hope so). imo AI is struggling with a lot of languages that are not as popular as javascript, mostly because it's more niche and you don't get a lot of good examples on the web.
This is awesome and timely for me...going to give it a whirl. Thanks for building. Also, there should totally be an easter egg where clicking something somewhere plays the sound!
"AI-readable Markdown" — can't we just say "Markdown"? I'm serious about this, why are we focussing on making things accessible to AI when they should just be machine-readable and accessible to human beings in the first place? No need to taint this by bringing AI into it.
I don't even bother trying to render docc catalogs into JS. It's a royal pain that breaks easily.

If GitHub could support .docc files, that would be great. Otherwise, I still use Jazzy Docs.

> "Ever notice Claude struggling to write Swift code?"

Yes, that is why I quit using Claude and swapped to ChatGPT about a year ago. I've had substantially less issues with GPT.

Just saying, sites like these are also pretty great for accessibility, screen reader users in particular.

I think this one would be slightly better if it rendered that Markdown as simple HTML if accessed through a real browser, but I can imagine even this version being pretty useful.

I think it could also make the "Small web" crowd pretty happy too.

Amen to that. It's funny how virtues like accessibility and good API design matter just as much as ever in this new era. Good ideas don't go out of style.
An “AI” that makes text “AI”-readable. How does that make any sense?
It is for the same reasons LLM are struggling to produce something that compile in Rust? I was under the impression that most of Rust documentation was plain HTML.
Wasn’t one of the benefits of AI that we don’t need special documents for AI to understand the data?
How to reliably HTML to MD for any page on the internet? I remember struggling with this in the past

How hard would it be to build an MCP that's basically a proxy for web search except it always tries to build the markdown version of the web pages instead of passing HTML?

Basically Sosumi.ai but instead of working on only for Apple docs it works for any web page (including every doc on the internet)

I think HTML -> Markdown is a bit of a red herring.

In many cases, a Markdown distillation of HTML can improve the signal-to-noise ratio — especially for sites mired in <div> tag soup (intentionally or not). But that's an optimization for token efficiency; LLMs can usually figure things out.

The motivation behind Sosumi is better understood as a matter of accessibility. The way AI assistants typically fetch content from the web precluded them from getting any useful information from developer.apple.com.

You could start to solve the generalized problem with an MCP that 1) used a headless browser to access content for sites that require JS, and 2) used sampling (i.e. having a tool use the host LLM) to summarize / distill HTML.

Another awesome project that does this for Apple's docs: https://llm.codes/

Also, Apple has started shipping docs like this, too. They are a bit hidden but you can find them here:

/Applications/Xcode-beta.app/Contents/PlugIns/IDEIntelligenceChat.framework/Versions/A/Resources/AdditionalDocumentation

Just wondering - can't AI read HTML? If so how are we training our models?
Great promise; sometimes need to reference docs to build context.

I looked at the examples you posted and did a quick glance. For example

'''init?(exactly: Float80)'''

the tool converted it to

'''- [initexactly-63925](/documentation/Swift/Double/init(exactly:)-63925)'''

To achieve its goal I would be worried that it dropped the verbatim function signature. Claude still figured it out, but for more obscure stuff that could be an issue.

Hope this make apple's Xcode team realize they should do this, especially with all the recent AI integration.
Can't wait to use this. Its awesome!
This is awesome; great work.
sosumi.md seems to be a better fit domain-wise, no?