Your agent owns fifteen API keys and uses one. That one hits a rate limit and the turn ends, while fourteen healthy keys sit there untouched. KAME picks a key per call, and a failed call moves to the next key instead of ending your turn.

Shared rotation principles, native integration per host, independently verified releases.

Release-specific evidence, limits and complete version history live in each port's Agent Zero / Hermes documentation. Native transport fixtures are not new live-provider guarantees.

No provider allowlist anywhere in it. Every decision is made on evidence in the response, never on who the provider is — so a provider that does not exist yet is already covered.

I work on two things besides rotation, and they will land here as they become worth other people's time:

• Chemistry — the field I actually come from, and the reason I care whether a long unattended run survives the night.
• AI agents — the tooling around them: what makes one reliable enough to leave alone, and what quietly makes one useless.

Nothing ships here until it has been run against something real. Every project above was built while using it daily and fixed from its own logs.

Discord — kame055856

Bug report, a log that looks wrong, or an idea for a port to another host: all welcome. If a plugin of mine broke your agent, I would genuinely rather hear it than not.

Free, MIT, no telemetry, nothing to upsell — written by one person against a real free tier, on real quotas that really run out.

Bitcoin — 36BGYhMEVFgY8PLGMVux93pjGt92KVM6dJ

Any amount helps, genuinely. And a ⭐ costs nothing and helps someone else find the fix for a problem they are currently blaming on themselves.