inkling-256k
requesty/inkling-256kBy requesty · released 2026-07-16
Prices in USD per 1M tokens. Unknown means the provider does not publish per-token pricing.
Capabilities
Model fit scores
0–100 · higher is betterThese scores reward declared capabilities, context size, price and provider availability — they are not benchmark results. Use them as a directional signal alongside your own evaluation.
Coding59
- Tool calling40/40
- Structured output0/20
- Reasoning10/10
- Context window (100K → 1M)8/20
- Provider availability1/10
Agents66
- Tool calling35/35
- Structured output0/25
- Reasoning15/15
- Output token limit15/15
- Provider availability1/10
JSON / structured output27
- Structured output / JSON mode0/50
- Tool calling20/20
- Temperature control0/10
- Price-friendly for high-volume7/20
Cost efficiency47
- Headline price (log-scaled)42/95
- Has prompt-cache pricing5/5
Long context61
- Context window (100K → 2M)51/90
- Has published price for full window10/10
Vision82
- Accepts image input50/50
- Context window (10K → 1M)21/30
- Has published price10/10
- Provider availability1/10
Production-readiness65
- Number of independent providers5/40
- Has published per-token price20/20
- Context window ≥ 8K15/15
- No data inconsistencies across providers10/10
- Official model (not derivative)15/15
Cost Efficiency Index
Open full calculator →Estimated cost using the recommended provider's headline rate. Each scenario fixes average input/output tokens — the assumptions are shown in the third column.
| Scenario | Cost | Assumption |
|---|---|---|
RAG answer per 1,000 RAG answers | $11.69 $0.01 per request | 5K input tokens (query + 4 retrieved chunks of ~1K each) and a 500-token answer. Typical SaaS knowledge-base bot. |
Support ticket triage per 10,000 tickets | $23.38 < $0.01 per request | 1K input tokens (ticket body + system prompt) and a 100-token JSON classification reply. High-volume customer support. |
Data extraction per 1,000 documents | $6.08 < $0.01 per request | 2K input tokens (a single document page) and a 500-token JSON extraction. ETL / invoice / form pipelines. |
Code review per 1,000 PRs | $19.64 $0.02 per request | 8K input tokens (diff + surrounding files) and a 1K-token review comment. PR-bot workloads. |
Agent step per 1,000 steps | $25.25 $0.03 per request | 12K input tokens (long-running tool history) and a 600-token tool-call decision. Cost per agent step. |
Pricing detail
Recommended pricing from requesty · inkling-256k
Available on 1 providers
| Provider | Provider model id | Input / 1M | Output / 1M | Context | Released |
|---|---|---|---|---|---|
| Requesty requesty | inkling-256k | $1.87 | $4.68 | 262K | 2026-07-16 |
Frequently asked questions
How much does inkling-256k cost?
inkling-256k costs $1.87 per 1M input tokens and $4.68 per 1M output tokens, sourced from requesty. Cache reads, audio tokens and >200K-context tiers (where applicable) are listed in the Pricing detail block above.
What is the context window of inkling-256k?
inkling-256k has a context window of 262K tokens, with a max output of 33K tokens per reply. This is the total combined size of prompt + completion.
Does inkling-256k support tool calling?
Yes. inkling-256k supports tool calling (function calling). This makes it suitable for production agent and automation workloads where the model has to invoke external functions reliably.
Does inkling-256k support structured output / JSON mode?
No. inkling-256k does not support structured output / JSON-schema-constrained decoding. If your workflow requires it, look at the /capabilities/structured-output list for alternatives.
Can inkling-256k accept image input?
Yes. inkling-256k accepts both text and image input. Vision pricing per image is usually billed on top of the regular token rate — check requesty's docs for the exact rule.
Is inkling-256k open-weight?
No. inkling-256k is a proprietary model — only requesty (and any approved hosting partners) can serve it. The pricing above reflects the cheapest API access.
What are the best alternatives to inkling-256k?
If inkling-256k doesn't fit, consider Seed 2.0 Code, Nano Banana Pro, seed-1.8. Each one targets the same use case — see the Related links below for direct head-to-head pages.
Where does this data come from?
All numbers are normalised into a single canonical model record and reconciled with each provider's official documentation. We re-pull daily and write any changes (price, context, capability) to the /changelog page.
Explore more
More requesty models
- Seed 2.0 Code$0.50 in / $3.00 out
- Nano Banana Pro$2.00 in / $12.00 out
- seed-1.8$0.25 in / $2.00 out
- ring-2.6-1t$0.30 in / $2.50 out
- leanstral-1-5@euUnknown pricing
Capability lists this model is in
Last updated:
Pricing and capabilities are refreshed daily and reconciled against each provider's official documentation. Always verify critical production decisions with the provider directly.