Edited.. check this links

https://arnabdzns.vercel.app

https://arnabdzns.vercel.app/about

there is a friend of mine wanted something wild shit... I thought maybe i should try the liquid glass theme , and I did somewhat with CSS only but not works in iphone so i added fallback to frosty glass theme... While on other devices it worked, even on android.. I dont know why Apple Iphones are so bad at keeping themselves update..

I want a review on the portfolio and how can i enhance and make it better..

I kept hitting a really annoying problem while building AI apps:

Everything works perfectly…
Then suddenly requests start failing.

Not because of the model.
Not because of the code.
Just because the API key got rate-limited.

After this happened a few times (including demos breaking 😅), I realized:

We’re all managing API keys like it’s 2018.

Most setups are:

• One key → 💥 hits limit
• Multiple providers → unable to manage automatically
• Multiple keys → manually rotated
• Retry logic everywhere → messy

None of this actually solves the problem.

⚡ So I built this:

A rate-limit aware API key scheduler

👉 https://amon20044.github.io/AI-Key-Scheduler/

🧠 What’s different?

Instead of reacting to failures, it tries to avoid them completely:

• Switches keys before hitting limits
• Tracks cooldowns automatically
• Distributes load across keys
• Works across AI providers

💡 The idea

Most systems do:

>

This does:

>

🎯 Goal

Make API key handling invisible.

No broken demos.
No random rate limit errors.
No manual key juggling.

Would love honest feedback:

• Would you actually use this?
• What’s missing?
• How are you solving this today?