ayushrodrigues

we have so many problems with MCP related to auth, scopes etc... how do you guys help solve that?

congrats on the launch Arlan! Nia is a lifesaver when we're coding :)

This is the most fun I've had on the internet in a long time.

I've been interested in a tool like this for a while. I currently have tried whisprflow and aqua voice but wanted to use my API key and store more context locally. How does all the data get stored and how can I access it?

Ah yes. Interestingly most of our users don't set this up in the early stage. But for the ones that do, they need webhooks for this. We have a single webhook that fires whenever a customer's state is updated (eg subscription started, cancelled, downgraded, expired) etc, that the downstream functions you talk about rely on.

This is really helpful context. Thanks for sharing!

Ah shame we missed you! Glad to hear it resonates :)

We have react hooks so we try and make the majority of the integration lift on the frontend. One of our contributors is helping us launch a python SDK soon too !

Adapty looks cool! Kind of similar to Revenuecat?

I think the offering is similar -- both manage entitlements and paywalls. And while we do have a proportion of users that use us for mobile apps we're pretty focused on SaaS / web.

I can imagine Adapty would go deeper on features like AB testing, paywall designing etc

Our users handle lower volume of subscriptions but require more flexibility and depth on the pricing models they want to support.

Thanks Eric!

We are pretty tightly coupled with Auth. Part of setting it up is resolving your internal customer (or org) ID from your auth JWT and passing it into an autumnHandler function, which then makes calls to the Autumn API.

This means you don't need to store any additional IDs for billing -- just make calls to Autumn with your exiting auth uuids.