Skip to content

Kiro pricing: plans, credits and which steps use them

Kiro plans and credits, plus a real Kiro workflow showing which steps used the credits and why.

See how far each plan's credits go

A credit is Kiro’s billing unit: about $0.02 each when included in a plan, $0.04 each as extras (our reading of kiro.dev/pricing, 9 November 2026). Pro includes 1,000 credits a month and Power 10,000; for Free, see Kiro’s pricing page.

Included credits per month by plan, vs extra credits for the same money (derived)

Free
$0
Pro
$20/mo
Pro+
$40/mo
Pro Max
$100/mo
Power
$200/mo
Included credits per monthSee Kiro's pricing page1,0002,0005,00010,000
Extra creditsSee Kiro's pricing page$0.04 each$0.04 each$0.04 each$0.04 each

See which steps your credits went to

A turn is one time the model thinks and decides, and a tool call is an action such as a read. In our Kiro workflow, the busiest worker took 44 turns and 111 tool calls for 12.05 credits, against 7 turns and 1.07 credits for the step that split the list.

Share of 31.3 credits by step, one Kiro workflow of ours (agent analysis, 4 Nov 2026)

Find the step that kept the others waiting

In our workflow the work was split by count, not effort: the slowest worker took 436 seconds, about 100.7 seconds longer than the average worker (335 seconds).

Seconds per parallel worker vs the average worker, one Kiro workflow of ours (agent analysis, 4 Nov 2026)

Find out where a workflow's credits went, from your agent

These are the real findings for that workflow; the prompt is an example and the calls are condensed.
Agent
engineer: where did this workflow's 31.3 credits go? (example prompt; one Kiro workflow of ours)
> check_trace_eligibility, upload the trace from disk, analyze_graph_start (steps condensed)
> analyze_graph
uneven work split: workers 12.05 / 11.26 / 4.97 credits -- costs time, about 100.7 s
caused by an earlier step: the step that split the work by count, not effort
more turns than needed: worker 1, 44 turns against 23 -- costs money
same documents read by every step: about 1.07 credits across the five steps -- costs money

Spend fewer Kiro credits on the same work

See Pro

Your agent gets a recommended fix for each finding

These are the analysis’s recommended fixes for the three credit findings above, which your agent can apply with your OK; the prompt is an example.
Agent
engineer: what should I change? (example prompt)
uneven work split: split work by effort, not by count, or process results as they arrive
same documents read by every step: read shared documents once and pass the content (or a summary) to the steps that need it
more turns than needed: tighten the step's instructions (clear stop condition, fewer optional checks), or rebalance hard items

On Pro: for Kiro users

  • Analyse your Kiro workflows step by step
  • See which steps used the credits, and why
  • Compare models on your own task before you spend Kiro credits on one
  • Get alerted when a model you rely on gets worse

Use it from Kiro, over MCP (the protocol agents use to call outside tools)

  • Ask from inside Kiro and get the findings back in chat
  • Also reads Claude Code sessions

$129/mo $10 for your first week

Then $129/mo. Cancel anytime.

Plan names and prices are from Kiro's pages; included credits are derived from our reading of kiro.dev/pricing (9 November 2026) at $0.02 per included credit. Workflow figures are from an agent analysis of one Kiro workflow of ours (4 November 2026).

Questions

What is a Kiro credit?
It is Kiro’s billing unit. On paid plans, included credits work out at about $0.02 each and extra credits cost $0.04 each (our reading of kiro.dev/pricing, 9 November 2026).
How many credits does each Kiro plan include?
Pro includes 1,000 credits a month, Pro+ 2,000, Pro Max 5,000 and Power 10,000, derived from our reading of kiro.dev/pricing (9 November 2026) at $0.02 per included credit. For the Free plan, see Kiro’s pricing page.
What happens when I run out of Kiro credits?
On paid plans, extra credits cost $0.04 each, double the included rate (our reading of kiro.dev/pricing, 9 November 2026).
How does Kiro compare with Claude Code?
Kiro bills in credits and splits a job into workflow steps, while Claude Code counts use against 5-hour and weekly windows and hands side tasks to subagents; Kiro vs Claude Code sets the plans, features and real costs side by side.
How do I see which steps of a Kiro workflow used my credits?
Ask your agent for an agent analysis over MCP (the protocol agents use to call outside tools). It reads the trace of a Kiro workflow or a Claude Code session and shows what each step cost, which steps wasted credits or time, and why; on Pro and above, see agent evaluation.