API

Every price on this site is also a file. No key, no account, no rate limit, no signup — just JSON on a CDN, rebuilt daily from the same snapshot that builds the pages.

If you can read a URL, you can use this.

The coverage numbers on this page are rendered from the current build. The example payloads are real responses, captured and pasted verbatim — the shapes are current, the values in them move daily.

First call

curl -s https://palworldprices.com/api/v1/index.json

{
 "source": "Palworld Prices",
 "url": "https://palworldprices.com/api/v1/index.json",
 "license": "free with attribution",
 "attribution": "Data: Palworld Prices (palworldprices.com) — completed-sale prices with confidence tiers",
 "terms": "Free to use, including commercially, with attribution and a link. Please do not imply endorsement, and please send a descriptive User-Agent. Card images are NOT part of this API.",
 "asOf": "2026-08-03T05:51:08.066Z",
 "stale": false,
 "honesty": "Prices are medians of COMPLETED SALES, never asking prices. …",
 "description": "A free, static, key-less JSON API over completed-sale prices for the Palworld trading card game. …",
 "endpoints": [ … ],
 "coverage": {
  "cardsTracked": 257,
  "withPublishedPrice": 126,
  "confidentlyPriced": 47,
  "note": "Most cards in a game this young have no completed sale yet. Those carry no price, by design."
 },
 "confidenceTiers": { … },
 "stability": "Additive changes only within v1: fields may be added, existing fields will not be removed or repurposed. Breaking changes get a new version prefix.",
 "updated": "Rebuilt daily. Every payload carries asOf and a stale flag — freshness is disclosed, never promised."
}

index.json describes itself. It is the only URL you need to memorise.

Endpoints

All served over HTTPS with Access-Control-Allow-Origin: *. Browser code can fetch them directly.

The envelope

Every JSON payload opens with the same block, so a response is self-describing no matter where it ends up.

Check stale before you publish anything. It is the site's own judgment on its own data.

The honesty contract, in JSON

This is the part that makes the API different from a price feed.

A card's price lives in headline, and headline.kind has exactly three values. The shape of the object changes with the tier — that is deliberate, so a naive read cannot produce a number the data does not support.

kind: "bare" — 4 or more completed sales

"headline": {
 "kind": "bare",
 "confidence": "HIGH",
 "window": "7d",
 "medianUsd": 35,
 "currency": "USD",
 "salesInWindow": 15
}

Safe to display as a plain number. confidence is HIGH (10+ sales) or MEDIUM (4–9).

kind: "thin" — 1 to 3 completed sales

"headline": {
 "kind": "thin",
 "confidence": "LOW",
 "window": "90d",
 "medianUsd": 39.9,
 "currency": "USD",
 "salesInWindow": 1,
 "qualifier": "Thin sample (1-3 completed sales) — a rough number, not a settled market price. Do not display this figure without this qualifier."
}

A number is present, and it arrives with a qualifier that is not optional. One sale is a data point, not a price. Display them together or display neither.

kind: "none" — no verified completed sale

"headline": {
 "kind": "none",
 "confidence": "NONE",
 "note": "No verified completed sales yet — tracking live."
}

There is no medianUsd key at all. Not 0, not null — absent. A naive card.headline.medianUsd read gets undefined, which is hard to accidentally render as a price.

131 of 257 printings are in this state. Show them as "no verified sales yet".

Today's census

Half the catalogue has never sold in a marketplace this project watches. That number is published rather than filled in.

/api/v1/cards.json

The envelope, plus count and a cards array. About 148 KB, one request, everything.

{
 "cardId": "pal-BP01-001-OSR",
 "code": "BP01-001",
 "set": "BP01",
 "number": "001",
 "variant": "OSR",
 "rarity": "OSR",
 "rarityTier": "chase",
 "names": {
  "en": "Jormuntide Ignis – Savage Lava Dragon",
  "jp": "荒ぶる溶岩竜 – アグニドラ"
 },
 "pageUrl": "https://palworldprices.com/cards/bp01/001-jormuntide-ignis-savage-lava-dragon-osr/",
 "headline": { … },
 "asks": { "n": 24, "lowUsd": 25 }
}

Printings are not interchangeable

BP01-001 exists four times, and the four price separately:

Note that the base printing and the -RR printing both carry printed rarity RR and differ by 4×. Key on cardId, never on code alone, and never average printings together.

/api/v1/cards/{cardId}.json

The card's identity and headline again, plus what sits underneath them.

curl -s https://palworldprices.com/api/v1/cards/pal-BP01-001-OSR.json

{
 "source": "Palworld Prices",
 …
 "cardId": "pal-BP01-001-OSR",
 "code": "BP01-001",
 "names": { "en": "Jormuntide Ignis – Savage Lava Dragon", "jp": "荒ぶる溶岩竜 – アグニドラ" },
 "pageUrl": "https://palworldprices.com/cards/bp01/001-jormuntide-ignis-savage-lava-dragon-osr/",
 "headline": {
  "kind": "bare",
  "confidence": "HIGH",
  "window": "7d",
  "medianUsd": 35,
  "currency": "USD",
  "salesInWindow": 15
 },
 "market": "Raw · US completed sales (English)",
 "confidence": "HIGH",
 "suspect": false,
 "windows": {
  "7d": {
   "sales": 15,
   "salesSettled": 15,
   "medianUsd": 35,
   "lowUsd": 20.5,
   "highUsd": 49.99,
   "iqrUsd": [29.99, 42.95],
   "lastSoldAt": "2026-08-01T12:00:00.000Z",
   "datePrecision": "exact",
   "suspect": false
  },
  "30d": { … },
  "90d": { … }
 },
 "receipts": {
  "count": 15,
  "note": "Individual completed-sale listings are linked on the card page."
 },
 "asks": { … }
}

Window fields

datePrecision: "observed" matters for JP marketplaces, which frequently do not publish a sale timestamp. Treat those dates as "no later than".

When a card has no verified sale, windows, receipts and market are all null and confidence is "NONE".

Asks — what sellers want

Everything above is a completed sale. asks is the one block on this site that is not, and it lives in its own top-level key for exactly that reason.

"asks": {
 "n": 24,
 "market": "Raw · US completed sales (English)",
 "lowUsd": 25,
 "highUsd": 99.99,
 "medianAskUsd": 40,
 "windowHours": 72,
 "basis": "first-seen",
 "asOf": "2026-08-02T20:58:09.650Z",
 "listings": [
  { "priceUsd": 25, "marketplace": "eBay", "url": "https://www.ebay.com/itm/398238804180", "firstSeenAt": "2026-08-01T17:18:10.382Z" }
 ],
 "spreadPct": -28.6,
 "soldMedianUsd": 35,
 "soldWindow": "7d",
 "note": "ASKING prices … NOT sales …"
}

basis: "first-seen" is load-bearing. A listing is recorded once, when it is first seen, and is not re-checked afterwards. Two departures are subtracted (we later captured the sale, or a recheck labelled it sold); everything else is bounded by the window alone. So this data supports *"24 listed from $25, seen in the last 3 days"*. It does not support "24 available now", "in stock", or "verified active" — and an ask is never a sale, so it must never fill an unpriced card, enter a price average, or be displayed as a price.

spreadPct appears only when the card has a bare-renderable sold median in the same market and at least two fresh asks. Missing means missing: no zero, no "flat", and do not re-derive it from the other fields. It is not a JP/US arbitrage spread — that does not exist on this site.

Missing cards

Ask for a cardId that does not exist and you get HTTP 404 with the site's HTML not-found page — served under this API's JSON content type, because the header rule matches the requested path and there is no application server here to notice the difference. The status is honest; the body is not JSON. So do not rely on the content type, and do not assume an error body you can parse. The reliable check is one line:

const r = await fetch(`https://palworldprices.com/api/v1/cards/${id}.json`);
const card = await r.json().catch(() => null);
if (!card || card.cardId !== id) throw new Error(`unknown cardId: ${id}`);

Parse, then check cardId matches what you asked for. That guard is correct whatever the host returns — today's 404 page, a future JSON error, or a stale edge copy — and it also catches the case where a card is retired between builds.

For a canonical example of the error shape, /api/v1/404.json is a real document describing exactly this convention.

Take valid cardIds from cards.json rather than constructing them.

Feeds

All three are RSS 2.0, application/rss+xml.

/feeds/latest-sales.xml — the newest individual completed sales. Each item links both the card page and the original listing.

<item>
  <title>$83.21 — Lyleen – Blessing of the Goddess (BP01-049 SSP)</title>
  <link>https://palworldprices.com/cards/bp01/049-lyleen-blessing-of-the-goddess-ssp/</link>
  <guid isPermaLink="false">pwp-sale-mercarijp-m49105711564</guid>
  <pubDate>Mon, 03 Aug 2026 01:33:10 GMT</pubDate>
  <description>Last verified 2026-08-03 (the marketplace did not state the sale time, so this is when we confirmed it) on Mercari JP for $83.21. This is ONE completed sale, not a price — a single data point. …</description>
</item>

Each item is one sale. The wording says so, because a feed of individual sales is the easiest thing in the world to misread as a feed of prices.

/feeds/movers.xml — cards whose 7-day median moved against their 30-day median, published only when both windows rest on enough dated, deduplicated sales.

<title>▼ 5.9% — Jormuntide – Surging Sea Serpent (BP01-027 OSR) at $40.00</title>
<description>7-day median $40.00 across 13 completed sales, against a 30-day median of $42.50 across 14. That is down 5.9%. A move is published only when both windows rest on enough dated, deduplicated sales to back it. …</description>

When nothing qualifies, the feed is not published at all. An empty movers feed would be a feed that says nothing; a missing one says the same thing honestly.

/feeds/changelog.xml — what changed on the site, in the same plain language as the changelog. Subscribe to it if you depend on this data and want to know when the way a number is made changes.

guids are stable and namespaced (pwp-sale-…, pwp-mover-…), so readers deduplicate correctly across rebuilds.

/llms.txt

Plain text, for assistants: what this source is, how it differs from asking-price sites, the rules for quoting a number, the key URLs, and what is deliberately absent.

curl -s https://palworldprices.com/llms.txt

Freshness and caching

Rebuilt daily. Every payload carries asOf and stale; nothing here promises to be current.

Cache-Control: public, max-age=0, s-maxage=3600, stale-while-revalidate=86400
ETag: "d8b7c81c6543e3fe10d7a480495bd0e5"

max-age=0 keeps browsers honest — a price must never be browser-stale — while the edge answers instantly and revalidates behind the request. Send If-None-Match with the ETag and you will get 304s between builds.

Please send a descriptive User-Agent. There is no rate limit and no key to revoke; the only thing making this sustainable is that it is cheap to serve.

Stability

Additive changes only within v1. Fields may be added; existing fields will not be removed or repurposed. A breaking change gets a new version prefix.

Write your parser to ignore unknown fields.

Attribution

Free with attribution, including commercial use. Publish this line verbatim wherever you display these numbers:

Data: Palworld Prices (palworldprices.com) — completed-sale prices with confidence tiers

Link back to the card's pageUrl so a reader can reach the receipts. Do not imply endorsement.

Card images are not part of this API, and there is no bulk image download. Card art is hosted under a publisher fan-content policy that does not extend to redistribution. Link to the card page instead.

This site is non-commercial: no ads, no affiliate links.

The one rule

If you take one thing from this page: never publish a thin median without its qualifier, never publish a number for a none card, and never publish an ask as a price. Everything else here is a detail.

Recipes

Five most valuable confidently-priced printings, from the current build:

curl -s https://palworldprices.com/api/v1/cards.json | node -e "
let s='';process.stdin.on('data',d=>s+=d).on('end',()=>{
const {cards}=JSON.parse(s);
cards.filter(c=>c.headline.kind==='bare')
     .sort((a,b)=>b.headline.medianUsd-a.headline.medianUsd)
     .slice(0,5)
     .forEach(c=>console.log(c.headline.medianUsd.toFixed(2).padStart(8), c.code, c.variant||'', '—', c.names.en));
})"

  975.75 ESOUL-002  — Soul
  800.00 BP01-025 SSP — Chillet – Dragon Whisperer
  475.00 BP01-001 SSP — Jormuntide Ignis – Savage Lava Dragon
  400.00 BP01-049 SSP — Lyleen – Blessing of the Goddess
  250.00 BP01-095 SP — Zoe's Strategy

Render a price the honest way, in any language — the branch is always the same three cases:

function priceLabel(card) {
  const h = card.headline;
  if (h.kind === 'none') return 'No verified sales yet';
  if (h.kind === 'thin') return `~$${h.medianUsd.toFixed(2)} (thin sample)`;
  return `$${h.medianUsd.toFixed(2)}`;
}

Three branches. Write them once and the qualifier can never go missing.

What is not here

Graded (PSA) values, pack expected-value, and JP/US arbitrage spreads. They do not exist on this site — absent rather than estimated.

Individual sale receipts are not in the JSON either. receipts.count gives the number; the sales themselves live on the card page, where the framing that belongs with them travels with them.

Questions

Something wrong, something missing, or a use case this does not cover: contact@palworldprices.com.

Prices are informational, from public completed-sale data. Not financial advice. Method: /methodology/. What we refuse to print and why: /accuracy/. Prices inside an assistant instead: the MCP server.