together-common-errors
Together AI common errors for inference, fine-tuning, and model deployment. Use when working with Together AI's OpenAI-compatible API. Trigger: "together common errors".
What this skill does
# Together AI Common Errors
## Overview
Together AI provides OpenAI-compatible inference, fine-tuning, and batch processing across 100+ open-source models (Llama, Mixtral, Qwen, FLUX). Common errors include model-not-available failures when requesting deprecated or gated models, token limit violations that differ per model architecture, and fine-tune job failures from dataset formatting issues. The API is compatible with any OpenAI client library at `base_url = 'https://api.together.xyz/v1'`. Model IDs use the full namespace format (e.g., `meta-llama/Meta-Llama-3.1-8B-Instruct`) and must match exactly. This reference covers inference, fine-tuning, and deployment errors.
## Error Reference
| Code | Message | Cause | Fix |
|------|---------|-------|-----|
| `401` | `Unauthorized` | Invalid or missing `TOGETHER_API_KEY` | Verify key at api.together.xyz > Settings |
| `400` | `Model not found` | Wrong model ID or model deprecated | Use `client.models.list()` to get valid model IDs |
| `400` | `Token limit exceeded` | Input + max_tokens exceeds model context | Reduce input length or lower `max_tokens` parameter |
| `400` | `Invalid fine-tune dataset` | JSONL format errors or missing required fields | Each line must be valid JSON with `messages` array |
| `402` | `Insufficient credits` | Account balance depleted | Add credits at api.together.xyz > Billing |
| `404` | `Fine-tune job not found` | Invalid job ID or job expired | List active jobs with `client.fine_tuning.list()` |
| `429` | `Rate limit exceeded` | Too many concurrent requests | Implement backoff; use batch API for 50% cost reduction |
| `500` | `Model overloaded` | High demand on specific model | Retry with backoff; try alternative model of same family |
## Error Handler
```typescript
interface TogetherError {
code: number;
message: string;
category: "auth" | "rate_limit" | "validation" | "billing";
}
function classifyTogetherError(status: number, body: string): TogetherError {
if (status === 401) {
return { code: 401, message: body, category: "auth" };
}
if (status === 402) {
return { code: 402, message: body, category: "billing" };
}
if (status === 429) {
return { code: 429, message: "Rate limit exceeded", category: "rate_limit" };
}
return { code: status, message: body, category: "validation" };
}
```
## Debugging Guide
### Authentication Errors
Together uses Bearer token authentication. Pass `TOGETHER_API_KEY` via `Authorization: Bearer` header or set it in the client constructor. Keys do not expire but can be revoked. If using the OpenAI client library, set `base_url='https://api.together.xyz/v1'` and pass the Together key as `api_key`.
### Rate Limit Errors
Rate limits vary by plan tier and are enforced per-key. Free tier allows 5 requests/second; paid tiers scale higher. Use the batch inference API (`/v1/batch`) for non-real-time workloads at 50% cost reduction. Check `X-RateLimit-Remaining` header to monitor quota.
### Validation Errors
Model IDs must match exactly (e.g., `meta-llama/Meta-Llama-3.1-8B-Instruct`). Use `client.models.list()` to enumerate available models. Token limits vary per model -- Llama 3.1 supports 128K context while older models may support only 4K. Fine-tune datasets must be JSONL with each line containing a `messages` array in chat format. Empty `messages` arrays or missing `role` fields cause silent validation failures. Validate each JSONL line independently before uploading.
## Error Handling
| Scenario | Pattern | Recovery |
|----------|---------|----------|
| Model deprecated | 400 with "not found" | Check model list; migrate to successor model |
| Token limit exceeded | 400 on long prompts | Truncate input or use model with larger context window |
| Fine-tune dataset rejected | JSONL validation errors | Validate each line independently; fix and re-upload |
| Credits depleted mid-batch | 402 after N successful calls | Add credits, resume from last successful request |
| Model overloaded at peak | 500 on popular models | Fall back to alternative model in same family |
## Quick Diagnostic
```bash
# Verify API connectivity and list available models
curl -s -o /dev/null -w "%{http_code}" \
-H "Authorization: Bearer $TOGETHER_API_KEY" \
https://api.together.xyz/v1/models
```
## Resources
- [Together AI Documentation](https://docs.together.ai/)
- [API Reference](https://docs.together.ai/reference/chat-completions-1)
- [Supported Models](https://docs.together.ai/docs/inference-models)
## Next Steps
See `together-debug-bundle`.
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.