TackleKey
Model reference
moonshotai/kimi-k3:batch on TackleKey
Check this model ID and provider context, then confirm its current price and availability in the live marketplace before a larger test.
Model details
OpenAI-compatible request
Use the exact public model identifier moonshotai/kimi-k3:batch. Keep the API key in a server-side environment variable and start with a small response limit.
curl https://api.tacklekey.com/v1/chat/completions \
-H "Authorization: Bearer $TACKLEKEY_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "moonshotai/kimi-k3:batch",
"messages": [
{
"role": "user",
"content": "Reply with a one-sentence API health check."
}
],
"max_tokens": 64
}'How to use it
TackleKey is OpenAI-compatible for common chat completion workflows. Replace the base URL with the TackleKey endpoint, use an API key, and verify the moonshotai/kimi-k3:batch availability, endpoint support, request log, and balance record before scaling traffic.
This page is generated from a public model catalog snapshot. Live price, permissions, and route availability can change; check the model marketplace and a small request before scaling.
Related Moonshot models
~moonshotai/kimi-latest
moonshotai/kimi-k2.7-code
moonshotai/kimi-k2
moonshotai/kimi-k2-thinking
moonshotai/kimi-k2.6
moonshotai/kimi-k2.5
FAQ
What model ID should I send for moonshotai/kimi-k3:batch?
Use moonshotai/kimi-k3:batch exactly as shown in the current TackleKey pricing catalog, then confirm it is still available before a larger run.
Where can I find the moonshotai/kimi-k3:batch price?
Open the live model marketplace. Static pages do not reproduce token, fixed, or expression-based billing rules.
Is moonshotai/kimi-k3:batch the cheapest or best model?
This page does not make that claim. Compare live Moonshot and cross-provider prices, endpoint support, request success, and output quality for your workload.
Try TackleKey with one OpenAI-compatible change
Create an account, generate an API key, then replace your client base URL with the TackleKey endpoint. Keep keys server-side and verify live pricing before scaling traffic.