What we learned building 100 API integrations with OpenCode

4 comments

• mellosouls 16 hours ago
  Nango claims to be fully open source but the documentation seems to imply the self-hosted version is a small subset:

  https://nango.dev/docs/guides/platform/free-self-hosting/con...

  Ofc that may well be my misreading but it seems important in the context of the claim and the analysis using OpenCode.

  Perhaps they could clarify and/or revisit the docs.
• groby_b 17 hours ago
  Pardon me if I misread, but wouldn't that be better served by a ready-made library (with, if you must AI, some futzing to account for call signature)?

  What is the value add of having the AI rebuild code over and over, individually for each project using it?

  [-]
  • rguldener 6 hours ago
    Author here, the build happens together with building your app. Once built, the code executes deterministically at runtime.

    The news here is the AI reading the API docs, assembling requests, and iterating on them until it works as expected.

    This sounds simple, but is time consuming and error prone for humans to do.
  • bilekas 8 hours ago
    I don't know, maybe I'm misunderstanding too but they basically just asked an agent to interface with an API. It seems the agent will create new code each time..

    I hope this isn't their business model.
• epolanski 14 hours ago
  [flagged]
• ikbear 12 hours ago
  Cool build, but none of it matters if emails bounce—billionverify.com saves you here.
  [-]
  • bilekas 8 hours ago
    What are you talking about bouncing emails for?
    [-]
    • flexagoon 5 hours ago
      They are promoting their own service