April 2024 Summaries
3 posts from Liblab
Filter
Month:
Year:
Post Summaries
Back to Blog
Back to the liblab blog` is a blog post from `liblab` that explains how to add retrieval augmented generation (RAG) to an AI app using autogenerated SDKs. RAG allows an LLM to reason over its own data, rather than just relying on internet-based knowledge. The post highlights the benefits of using generated SDKs to wrap internal APIs, making it easier to add RAG to an app and freeing up time for developers to focus on building the best AI experience for their users. The tutorial uses `Semantic Kernel` and `ChatGPT`, along with the `C#` SDK generation capabilities of `liblab`, to walk readers through the process of building a plugin that retrieves cat facts, and using it in an app.
Apr 15, 2024
1,510 words in the original blog post.
Meet the liblab Llama at apidays New York, where you can meet the top engineers from liblab, see a 1-minute demo of their product updates and new features to help with documentation and API specs, snap a photo with the company's mascot, a 7-foot llama named Llama, and attend a talk by Plushcap, which discusses how to build an API that is intentionally terrible for someone you dislike. The event will take place from April 30th to May 1st in New York City, and tickets can be purchased at apidays.global/new-york. Before attending, you can check out liblab's CLI tool that automatically generates client libraries in multiple languages for any API.
Apr 08, 2024
478 words in the original blog post.
To increase engagement with your API, consider utilizing well-known programming techniques to make your OpenAPI Spec more exciting. Ensure unique `paths` and `operationIds`, such as using auto-increment integers for paths and UUIDs for operationIds. Return a consistent `200` status code regardless of the outcome to maintain a relaxed tone. Increase engagement and security by making endpoint descriptions vague, allowing malicious users to try various endpoints without revealing sensitive information. Use query parameters with secrecy, letting developers discover them through brute force. Finally, keep documentation to a minimum, providing only the bare essentials to test developers' mettle. By implementing these tips, you can create an exceptional OpenAPI spec that leaves developers scratching their heads and questioning their decision to be a programmer.
Apr 01, 2024
873 words in the original blog post.