#jhank0cean_best-practices
iron windBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1375275882238705725
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
chilly meadow
Am I correct to take this as, you want to bundle your request to Stripe server, and each of your request is about the usage of your users requests to your server?
elder crystal
Yes, essentially: a user would buy MyAPI request tokens through Stripe, then they would access MyAPI (anywhere from 1rps to +25rps), then I would like to bundle the Meter requests so to avoid hitting the 1000rps (& 1rps/customer) limits.
I've been following the "Alpaca AI" example. It's basically exactly what I would like to do with my API.
chilly meadow
I see. I think it's all up to you for the bundling logic 🙂 Stripe API doesn't work different as long as you don't hit the 1000 rps per your account.
I think either of your strategy works, just how semantic do you want your requests look like in request history
elder crystal
Ah I see
Okay that's fine, I was just curious on what a standard/best practice might be in terms of going about bundling.
I have another questions @chilly meadow about the V2:
Docs mention that there is a higher total request limit (10k per second instead of 1k) however it doesn't say if there is a "customer request per second limit".
Does the 1 concurrent call per customer per meter still apply to V2?
chilly meadow
Yes should be the same. V2 just upgrade that 1k to 10k