Raj Nagulapalle

Raj Nagulapalle

FetchSandboxFetchSandbox
Runnable API integrations for agents

About

Founder of FetchSandbox. Ex Meta, PayPal, Pinterest, and IBM. After spending 15+ years building APIs and developer platforms at Meta, PayPal, Pinterest, and IBM, I kept seeing the same problem: integration tests stop at 200 OK, but production failures happen in webhooks, retries, state transitions, and async workflows. I'm building FetchSandbox to help developers and AI agents verify real integration behavior before shipping. Today it powers runnable environments for APIs like Stripe, Clerk, Resend, Twilio, and more through MCP, CLI, and the web. Always happy to chat with founders, developer tooling teams, API companies, and engineers building for the agent era.

Badges

Plugged in 🔌
Plugged in 🔌
Thought Leader
Thought Leader

2

Top 5 Launch
Top 5 Launch
Tastemaker
Tastemaker
View all badges

Maker History

Forums

Agent-written webhook handlers keep breaking in prod. How are you testing them?

Spent way too long this week watching devs debug Paddle billing issues that never reproduced locally.

The pattern keeps repeating: subscription.activated arriving before subscription.created in prod, about 30% of the time. Handlers look clean, pass unit tests, handle retries correctly. But they assume events arrive in order. Paddle's sandbox just doesn't reproduce that chaos.

Make this Lovable app survive in prod

Most Lovable apps I've seen ship with integrations that were never actually run end to end.

What's usually happening?

The Stripe webhook is wired, the retry logic is there, but nobody ran a confirm capture webhook fire sequence before going live. Testing is either skipped or scripted in isolation against mocked responses that don't reflect real API behavior.

How do you test the "book a flight to London" agent workflow

How do you test a workflow that spans four services?

Been hitting the same wall for a while and curious how others handle it.

What's the failure shape?

Someone books a flight to London. Four things have to happen: confirm the booking, send a Slack message, fire a confirmation email, block the calendar. Travel is one vendor, messaging is another, email is another, calendar is another.

View more