---
title: "Discussion on \"Cursor Generated HTTP Client vs an SDK: Which to Use\" | Hashnode"
description: "Discussion on \"Cursor Generated HTTP Client vs an SDK: Which to Use\". Thin generated calls for scripts, a maintained SDK for a large surface."
url: "https://hashnode.com/posts/cursor-generated-http-client-vs-an-sdk/6b01d466cac530afa7abf2ba"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Cursor Generated HTTP Client vs an SDK: Which to Use](https://blogs.powerduck.com/cursor-generated-http-client-vs-an-sdk?utm_source=hashnode&utm_medium=feed)

Thin generated calls for scripts, a maintained SDK for a large surface.

3h ago · 5 min read · blogs.powerduck.com  
Read the article

-   [#ai](https://hashnode.com/tag/ai)
-   [#api](https://hashnode.com/tag/api)
-   [#tools](https://hashnode.com/tag/tools)
-   [#programming](https://hashnode.com/tag/programming)

## Written by

[Powerduck](https://hashnode.com/@powerduck)

@powerduck · hon

  
[View profile](https://hashnode.com/@powerduck)

## Responses 1

Markdown supported · ⌘↵ to post

[Olivia](https://hashnode.com/@oliviacreates)

[1h ago](https://hashnode.com/posts/cursor-generated-http-client-vs-an-sdk/6b01d466cac530afa7abf2ba/comment/6b01ed40206ff08361e5e66b)

Really clear way to frame the trade-off. The part about verifying generated calls against the live API before production stood out to me.
