Deep Singhvi

@asmeurer @openrouter @asmeurer one of the founders of fern here. We're tracking a fix to make sure that the response body is a JSON Schema. If you're curious, here's our implementation of the llms.txt route (github.com/fern-api/fern-…)

I know this is "for LLMs", but have you considered actually reading it? Here's the text for the /generation endpoint vs. the actual docs. "// ... additional stats" is not something that should appear in documentation. The LLM will just hallucinate the rest. To be useful, the LLM needs to see the *exact, full documentation*. Your llms.txt is even less useful. I'm guessing you tried the same thing I did and used some shitty HTML to markdown converter, but didn't bother checking the outputs. (by the way, the real issue seems to be the Fern documentation generator you're using. It buries the documentation text in some minified Javascript code on the page, making it impossible for most converters to properly see it). I'm sorry to be salty here. Your core product is great. But having quality developer documentation is really important when your product is an API.

I love @openrouter but they have some of the worst docs out there. Just spent half an hour trying to convert a docs page into something suitable for input to an LLM.

@jlengrand @jlengrand give buildwithfern.com a spin. We want OpenAPI to be easy.

@NickFisherAU It generates both the SDK and documentation, so if you change your API definition (OpenAPI spec) then both the sdks and documentation will update.

@DeepSinghvi This is just generating the presentation of the documentation though, right? It’s not like if I change void foo(int bar) to int foo(int bar), it’s going to change the content of my documentation to say “foo returns an integer of 0 for failure and 1 for success”?

Every company offering an SDK/API/etc as their core product - I beg you, please try something like training a custom LLM on both your code and your docs to ensure they stay consistent. It's really aggravating when the documentation is out of sync with the API.

@NickFisherAU buildwithfern.com :)

(this would actually make for a good business idea)

@i_gassmann @meijer_s @buildwithfern 👋 Hey there, one of the founders of Fern here. Sorry about the lackluster experience -- we're actively trying to improve our OpenAPI import story. Up to file a bug report on the repo (github.com/fern-api/fern/…) so that I can take a look?

@meijer_s @buildwithfern Oops 🫠 My experience with OpenAPI generators was always disappointing. Generators are often too brittle.

Do you use a codegen to generate sdks from your openapi spec? The ones I see, still require a serious amount of manual labor. This must exist right?!

One of the best products I've used in a while is @buildwithfern 🔥 I've been using it generate the Superagent Python SDK which is now live : github.com/homanp/superag… They have some other fancy stuff cooking for documentation as well 🥷🥷

@permutans @permutans Looks like you're trying to generate a Python client / Pydantic models for your OpenAPI spec? Give Fern a spin: #fern-python-sdk" target="_blank" rel="nofollow noopener">buildwithfern.com/docs/compiler/….

Fun: if you use the YAML version of the official OpenAPI schema-of-schemas you get the various Operation methods as individual keys, whereas the JSON schema represents them as a single regex, and datamodel-code-generator doesn't interpret regexes so just drops paths' HTTP methods

I wanted to extract the 'call signature' of the TfL API's various routes (the path name itself contains the required parameters, but not the optional ones, or types) and it said "No models found" so I don't really know what I make of it any more Maybe I should package my version

Today me and President @ZelenskyyUa hosted Alex Karp CEO @PalantirTech. Alex is the first CEO, who came to Kyiv after the start of the full-scale war. Impressive support and faith in credibility of investments: agreed on office opening and digital support of Army.