Price an architecture you can describe (no account needed)
estimate_costRead-only
Price a list of cloud components at real list prices. No account or signup.
Use this when the user can name the pieces: "two m5.large servers, a Postgres
database and a load balancer in Mumbai". If they cannot name the pieces, use
`describe_workload` instead, which asks in units a person actually has.
`items` is a list of `{"component": "<id>", "params": {...}}`. Get the ids and
each component's parameters from `list_cost_building_blocks` and use them
verbatim: a name you invent will be rejected, which is deliberate.
`region` is an AWS region id such as `ap-south-1`.
The reply is a RANGE, not a number: `monthly_total` has low, expected and high,
because several inputs are genuinely uncertain and a single figure would hide
that. `swing_factor` names the one input that most widens the range, which is
the most useful sentence in the reply: it tells the user what to go and measure.
`concentration` ranks the lines by share of the bill. `assumptions` lists every
value that was defaulted rather than given, and `traps` lists costs this
architecture usually incurs that the caller did not ask for, such as public IPv4
addresses or database storage billed apart from the database.
`gaps` lists anything that could not be priced. It is never silently treated as
zero. If a line is missing, the total is missing that line, and the gap says so.
These are AWS on-demand list prices before any discount, credit or committed-use
agreement, and they exclude tax. Treat the result as an upper bound on a real
bill and never as a quote.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| term | No | OnDemand | |
| items | Yes | ||
| region | Yes |