$250 → $500 of credit, then a hard limit per key.
Give each agent its own key with a $20 limit. When one loops, that key returns 402 at $20 and the other $480 is untouched. Nothing goes negative, nothing to pay off.
Kimi K3.1 Pro
OpenRouter: $2 / $10 + 5.5% on every top-up
RouterPlex: $2 / $10 + $0, and $25 loads as $50
Same list price. 5M output tokens of Kimi for $50. Which cost you $25.
$25 of API credit.
OpenRouter: $25 of credit costs $26.38 (5.5% top-up fee).
RouterPlex: $25 buys $50 of credit. $0 fee.
Same vendor list prices on the models both of us route. The difference is what happens to the money before it reaches a token.
The match is applied on the billing page when you top up. Match credit works on the open-source models, not the abliterated ones.
https://t.co/X7u2y6oqq4
Top-up match on RouterPlex.
Load $25 → $50 of credit.
Load $250 → $500 of credit.
One match per customer. $0 top-up fee. Credit never expires. Balance stops at $0, never goes negative.
One key, ~40 open-source models at the vendor's list price.
Kimi K3's 1M-token context is useful for coding agents—but token limits are not spend limits.
At Moonshot's published rates:
• cached input: $0.30/M
• fresh input: $3/M
• output: $15/M
Give each agent key a hard dollar cap before long runs.
Using Kimi K3 from @KimiDevs in @cline is a configuration change, not an SDK rewrite.
Choose OpenAI Compatible, enter the RouterPlex /v1 endpoint, and use model ID kimi-k3.
Give the Cline key a hard budget before letting an agent run.
Moonshot's published Kimi K3 API rates:
Cached input: $0.30 / 1M
Input: $3 / 1M
Output: $15 / 1M
1,048,576-token context. Vision. OpenAI-compatible.
RouterPlex uses the same rates under model ID kimi-k3.
Try in Cline with model id: moonshotai/kimi-k3
To install Cline in your CLI: npm i -g cline
Available as an extension for VS Code and JetBrains as well!
(Free, open source, bring your own API key and use any model)
https://t.co/2PULMWjvkz