@pipeworx/price-history

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/price-history’s. Install: one-click buttons

Connect to just the @pipeworx/price-history pack

https://gateway.pipeworx.io/price-history/mcp — only @pipeworx/price-history’s own tools, nothing else in the catalog.

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 4

Pipeworx’s own recorded history of data that only exists as history if somebody records it: GPU rental prices and Apple App Store top charts, kept as one row per change from the day recording began.

Tools

  • price_history_feeds() — the recorded feeds, each with its publisher, what is compared, cadence, first_observed (the date its history begins) and data_as_of.
  • price_history_latest(feed, group?, query?, limit?) — current value of every entity in a feed, with the date each value has held since.
  • price_history_entity(feed, entity_id, limit?) — every recorded change for one entity, oldest first, including when it entered or left the listing.
  • price_history_movers(feed, from, to?, group?, limit?) — what moved between two dates: entities whose compared value changed (largest move first), entities that appeared, entities that left.

Every response carries history_begins and a coverage_note. History starts the day the feed’s recorder first ran; nothing earlier is held and nothing is backfilled, so an absence before that date means nothing.

Feeds (first two)

gpu-rental — $/hr, daily.

  • Microsoft Azure, public retail price list: Linux pay-as-you-go ND- and NC-series GPU VMs, East US and West Europe.
  • Amazon Web Services, EC2 on-demand list prices (us-east-1) for the p5, p4d, p4de, p3, g6e, g6 and g5 families, read through a public price relay.
  • RunPod, GPU cloud: lowest on-demand price per GPU type.
  • Vast.ai marketplace: cheapest and median rentable single-GPU offer per model (H200, H100 SXM and PCIE, A100 SXM4 and PCIE, L40S, RTX 5090, RTX 4090, RTX 3090). Marketplace figures are the cheapest listing, not a posted rate.

appstore-charts — chart rank, daily. Apple, App Store top free and top paid app charts, top 50, for six storefronts: US, GB, DE, JP, BR, IN (the largest English, European, Asian and Latin American markets, kept to six so the row count stays small). Apple’s feed carries two app charts and no category split, so there are no category charts. A row is written when an app changes rank, enters or leaves a chart.

How history is recorded

A recorder (scripts/snapshot-store/record.mjs) polls each source once a day and compares every entity with its latest stored value. It inserts a row only when the value changed, or the entity appeared or left a complete fetch. An unchanged entity writes nothing. There is no per-entity last-seen column: a run log holds one row per feed run, and an entity is considered still listed at a time T if its latest observation at or before T is a value (not a removal) and a successful run exists at or after T. A group whose fetch failed is never marked as removed, and a fetch returning under half of a group’s prior entities is treated as broken, not as a market collapse.

Adding a feed is one config object plus a fetcher in scripts/snapshot-store/feeds.mjs. The tables (snapshot_feeds, snapshot_observations, snapshot_runs, function snapshot_as_of) do not change.

Budget (fleet #4701)

Store: tables in the existing Supabase Postgres (migration 289). No new Cloudflare binding, no D1/KV/DO/R2 use, no per-row billing. Worst case, every one of ~600 App Store entities and ~160 GPU entities changes every day: ~760 rows/day, ~280k rows/year, ~250 bytes each, ~70 MB/year against an 8 GB plan. One-time load: $0. Steady state: $0 marginal on the database; one scheduled workflow run a day (~2 minutes of runner time). Measured on 2026-11-20: first run wrote 156 GPU rows and 547 chart rows (one of twelve charts timed out and was left untouched, not marked removed); a second run 90 seconds later wrote 13 GPU rows (RunPod stock listings appearing and leaving, Vast.ai cheapest-offer moves, one Azure SKU) out of 154 entities and 49 chart rows, all from the chart that had timed out, with the 547 unchanged chart entities writing nothing. Steady state is expected well under the worst case. Cheaper alternatives considered: R2 JSONL (no migration, but history and as-of queries need a read-modify-write per feed and a scan per question) and D1 (priced per row written, and needs a new binding on a gateway at 243 of 250). Neither meets the need more cheaply.

Auth

Keyless. The sources are public and keyless; the recorder identifies itself with an honest User-Agent and reads each source once a day, serially.

Data sources

  • Microsoft, Azure retail price list (virtual machines).
  • Amazon Web Services, EC2 on-demand list prices, via a public price relay.
  • RunPod, GPU cloud public GPU-type pricing.
  • Vast.ai, public marketplace listings.
  • Apple, App Store top charts (Apple Marketing Tools).

The figures are the publishers’ listed prices and chart positions at the time of each daily read. They are not quotes, and marketplace entries move between reads.

Tools

  • price_history_feeds — List the feeds Pipeworx records over time (GPU rental prices, Apple App Store top charts), each with its publisher, what is compared, how often it is recorded, and first_observed, the date its history
  • price_history_latest — Current values of one recorded feed, with the date each value has held since. gpu-rental: $/hr per GPU instance or marketplace GPU model across Azure, AWS, RunPod and Vast.ai. appstore-charts: Apple t
  • price_history_entity — Every recorded change for one entity of a feed, oldest first: when a price or chart position changed, or when the entity entered or left the listing. Each row holds until the next. History begins at t
  • price_history_movers — What changed in a feed between two dates: entities whose compared value moved (largest absolute move first, with before, after, delta and percent), entities that appeared, and entities that left. Date

Tools

  • price_history_entity — Every recorded change for one entity of a feed, oldest first: when a price or chart position changed, or when the entity entered or left the listing. Each row holds until the next. History begins at t
  • price_history_feeds — List the feeds Pipeworx records over time (GPU rental prices, Apple App Store top charts), each with its publisher, what is compared, how often it is recorded, and first_observed, the date its history
  • price_history_latest — Current values of one recorded feed, with the date each value has held since. gpu-rental: $/hr per GPU instance or marketplace GPU model across Azure, AWS, RunPod and Vast.ai. appstore-charts: Apple t
  • price_history_movers — What changed in a feed between two dates: entities whose compared value moved (largest absolute move first, with before, after, delta and percent), entities that appeared, and entities that left. Date

Regenerated from source · build November 21, 2026