Primcast live stock search

This endpoint answers in plain words. Add at least one filter to the URL.

NO FILTERS WERE APPLIED to this request, so what follows is NOT a list of matching
servers -- it is every value that exists in stock. If you meant to search, the filters
did not arrive -- and if your fetcher drops query strings, put them in the PATH instead.
These carry no "?", so there is nothing to strip:
  https://primcast.com/api/llm/readyservers/ram/64
  https://primcast.com/api/llm/readyservers/minram/64/location/Amsterdam
  https://primcast.com/api/llm/readyservers/gpu/NVIDIA/limit/40
  https://primcast.com/api/llm/readyservers/hdd/NVMe/location/Miami/format/json
Field then value, as many pairs as you like, in any order. Every filter below works in
either form and both answer the same.

In stock right now:
  location  Amsterdam, EU | Bucharest, EU | Miami, US | New York, US | San Francisco, US
  type      D103, D103D, D104, D105, D156, D157, D158, M300, M400, M510, M700, M710, M710p, M710x
  os        AlmaLinux 10, AlmaLinux 9, Ubuntu 18.04, Ubuntu 24.04, Ubuntu 26.04
  ram       8, 16, 32, 48, 64, 128, 256, 512  (GB)

Every filter and every value it accepts:
  https://primcast.com/api/llm/readyservers/filters
  https://primcast.com/llms.txt          the guide for agents
  https://primcast.com/mcp               same catalogue over MCP, no key, read only

You do not have to match those exactly. Amsterdam finds "Amsterdam, EU", Ubuntu finds
every Ubuntu release, NYC and Netherlands and Romania all work, and US or EU selects a
whole region. Anything unrecognised is named back to you rather than silently ignored.

Filters -- repeat a parameter, or comma-separate type/os/hdd/gpu/ram/traffic:
  location=Amsterdam       type=D105          os=Ubuntu
  ram=64                   minram=64          hasgpu=true
  maxprice=120             minprice=50        limit=10   (default 10, max 40)
  cpu= / gpu= / hdd= / traffic=   match part of a spec string
  format=json              machine-readable instead of prose

In format=json, price is what the buyer pays. A discounted machine also carries
listprice -- the struck-through figure -- and discount.percent. Quote price, not listprice.

maxprice and minprice compare what the buyer actually pays, discount included, and
results come back cheapest first.

For a GPU server use gpu=NVIDIA, not hasgpu=true. hasgpu also counts the Intel on-die
graphics on our M710 cartridges, which are the cheapest machines here, so cheapest-first
puts those at the top of a hasgpu search and they are not a card.

Example: https://primcast.com/api/llm/readyservers?location=Amsterdam&minram=64&maxprice=120
     or: https://primcast.com/api/llm/readyservers/location/Amsterdam/minram/64/maxprice/120