Prompt: price a planned stack on ird before building it

Have an agent turn a list of resources you intend to run on ird — domains, DNS zones, IPFS storage and traffic, tunnels, servers, one-click apps, p2p apps, snapshots and volumes — into a monthly cost table from the live price book, compare two options, check your runway, and point out the cheaper way to get the same result. Nothing is created.

Needs: ird access (MCP server or the ird CLI, logged in) Costs: none in the price book — only credits_prices, vps_tiers, apps_catalog, credits_balance (and optionally ird credits ledger) are read Group: housekeeping

Paste everything below the line into a fresh conversation. Fill in the FILL IN block first.

Task

Price OPTION_A (and OPTION_B if given) per month from the current price book, compare, and report runway at my current balance. Do not create, change or delete any resource — this is planning only.

FILL IN

OPTION_A:                                   # one resource per line
  domains:     2 × .ro, 1 year each
  dns_zones:   3 zones, ~20 records each
  ipfs:        800 MB pinned, 20000 MB served per month
  tunnels:     1
  vps:         1 × tier 2x, 1 × tier 0x
  apps:        none                         # one-click apps, e.g. ird_gitlab on an eligible tier
  p2p:         1 app, 5000 MB relayed per month, mailbox 50 MB held
  snapshots:   2 × 40 GB
  volumes:     1 × 100 GB
OPTION_B:    none                           # same shape, or "none"
HORIZON_MONTHS: 12                          # runway/comparison horizon

Non-negotiable rules

Rates from the price book, never from memory. Every number comes from credits_prices (CLI: ird credits prices --json) and vps_tiers (ird vps tiers --json) read in this conversation. Quote the key next to each rate.
Hourly → monthly is × 730. State the assumption. Yearly items (registrations, renewals) are ÷ 12 for the monthly column and shown in full in an "upfront" column.
No resources. No register_domain, ipfs_add, create_tunnel, vps_create, apps_deploy, p2p_create_app — not even "to check". If a line is ambiguous, ask; don't probe.
Unknown usage is a range. Traffic and relayed bytes are guesses: price them at the given figure and at ×3, and say which lines are usage-driven.

Steps

A. Read the price book. credits_prices → keep, per resource type:

domains: domains.register.per_year, domains.renew.per_year
zones: recurring.dns-zone-hourly → per_hour per zone plus per_record_hour per record
IPFS: recurring.ipfs-pin-hourly → per_mb_hour (storage) and per_mb_served (traffic, per MB, not hourly)
tunnels: recurring.tunnel-hourly.per_hour
servers: recurring.vps-hourly.<tier id> — only ids that vps_tiers lists (it also gives vCPU / RAM / disk per tier); the object carries other entries such as per_hour that are not tiers — never price a server from them
one-click apps: same tier rate as a server (apps_catalog → eligible_tier_ids per app)
p2p: recurring.p2p-app-hourly → per_hour per app, per_mb_relayed (TURN and libp2p relay), per_mb_hour_cached (mailbox storage); signaling is currently free
snapshots: recurring.image-hourly.per_gb_hour; volumes: recurring.volume-hourly.per_gb_hour

If a line in OPTION_A has no matching key, say so instead of inventing a rate. With the CLI, ird credits ledger --limit 200 --kind charge shows what similar lines cost me last month — a sanity check on the estimate.

B. Compute per line. monthly = rate × quantity × 730 for hourly items; rate × MB for served/relayed traffic; yearly ÷ 12 for domains. Keep full precision, round only in the table. Sum per option.

C. Compare. If OPTION_B: same table side by side, difference per line and total, and the total over HORIZON_MONTHS including upfront costs.

D. Runway. credits_balance (CLI: ird credits) → the balance; runway = balance ÷ monthly total for the chosen option, in months; flag it if it is under HORIZON_MONTHS and say how many credits close the gap.

E. Cheaper alternatives — propose only where the requirement allows it, each with its own priced line:

static content on a server → an IPFS site (per_mb_hour × MB plus traffic) instead of a tier; the site needs no server
an app that already runs on a machine you own → a tunnel (recurring.tunnel-hourly) instead of a server
the smallest tier that fits the RAM/disk in vps_tiers, and the 0x-family tiers next to the 1x-family at the same size
snapshots kept "just in case" → count them; each 40 GB image bills every hour
own TURN/signaling server → one p2p app plus relayed MB

F. Sanity check the traffic lines. Restate every usage-driven line (served MB, relayed MB, mailbox MB held) with the ×3 figure so the worst case is visible.

Deliverable

One table per option: line, quantity, price key, rate, monthly credits, upfront credits; totals; the comparison and HORIZON_MONTHS total if OPTION_B; balance, runway in months; the alternatives table with the saving per month; and the list of assumptions (730 h, usage figures, tiers chosen). End with the prompt to use next for each line (register-domain, static-site-ipfs, expose-local-app, vps-server, one-click-app, p2p-app at https://ird.cod-sursa.ro/prompts/).

static mirror of HEAD · about · clone: git clone https://ird.cod-sursa.ro/prompts.git