hi,
I am using langgraph to build agents, so far it has been working fine for me (mostly demo apps with a complex workflow) . I have been going through other threads on the forum and observing that langgraph has some performance and build issues.
can you help me understand what is the problem and what are you using to build reliable agents, any best practice or tips will be very helpful.
Hi everyone,
I wanted to give agents the capability of calling any tools in a deterministic, safe and compliant manner, using the product we built at Swytchcode.
I looked around and thought integrating Langgraph with Swytchcode will be awesome as it can handle complex workflows. This was my first attempt building something after a long time.
I used gemini to create the prompt and flow of the integration. Then I used claude code to build this integration and test it. Once done I built couple of agents myself. To my surprise they both worked flawlessly ,I built one apartment hunting agent and another to process B2B invoices.
You can use the open source repo to build agents that will be able to connect with 2000+ APIs with minimum effort. Please do share feedback.
Github repo- https://github.com/swytchcodehq/langswytch
Swytchcode stops agents from breaking tool calls in production.
Langgraph helps in building agents that can run complex workflows.
Hi everyone,
I wanted to give agents the capability of calling any tools in a deterministic, safe and compliant manner, using the product we built at Swytchcode.
I looked around and thought integrating Langgraph with Swytchcode will be awesome as it can handle complex workflows. This was my first attempt building something after a long time.
I used gemini to create the prompt and flow of the integration. Then I used claude code to build this integration and test it. Once done I built couple of agents myself. To my surprise they both worked flawlessly ,I built one apartment hunting agent and another to process B2B invoices.
You can use the open source repo to build agents that will be able to connect with 2000+ APIs with minimum effort. Please do share feedback.
Link to repo in comments.
Hey all — I open-sourced a few single-file TypeScript helpers for Stripe subscriptions that keep coming up in real projects:
invoice.paid)requires_action, requires_payment_method)past_due, unpaid → grace vs lock)Each file is small and framework-agnostic: you can drop it into a Node/TS codebase or wire it into an agent.
Repo: https://github.com/swytchcodehq/Stripe-Subscriptions
These helpers were built on top of Swytchcode (CLI for API integrations), but the Stripe logic is kept in plain TypeScript so you can also use them without Swytchcode by swapping the Swytchcode calls for your own Stripe client with minor changes in one place.
Curious what people here think:
We built a CLI that sits between AI agents and production APIs — handles auth, retries, compliance, and idempotency automatically across 2,000+ APIs. Give your agents capability of multi-tool calls with 100% accuracy.
Swytchcode sits between your AI agent and production APIs. It handles auth, retries, idempotency, policy enforcement, and compliance automatically — across 2,000+ APIs. The agents never touch live keys or raw sensitive data. What hits production is always accurate and safe. Swytchcode also keeps track of all the services and auto updates services to prevent any breaking changes/update
It's not a wrapper. It's the reliability layer agent stack is missing.
Who it's for:
Community feedback can be very helpful in improving the product you're exactly the people who'd have opinions on this.
how are you guys building integrations of your Agents with different APIs? Do you just add a md file or llms.txt or give them access to official MCP/CLI? what is the best way to make sure the integration works? wh