What Yuyu-tei sells a card for, how many it has, and what it pays for one
The Yuyu-tei API turns 遊々亭 (yuyu-tei.jp), a Japanese card shop that sells and buys singles for 24 games, into JSON in five actions.
5 active endpoints. Every call is 3 credits.
- POST/yuyu-tei/v1/search
- POST/yuyu-tei/v1/card
- POST/yuyu-tei/v1/buy_prices
- POST/yuyu-tei/v1/buy_card
- POST/yuyu-tei/v1/sets
What Yuyu-tei endpoints does ReefAPI ship?
5 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
Yuyu-tei API
3 of 5 endpoints, ready to run
Every product for a card name, set, rarity or type in one game: price, exact stock, rarity and card number.
// Press "Try it" and this pane shows exactly what the // live site returned this second — including an empty // result, if that is the truth. No key, no account.
How the Yuyu-tei API works
Yuyu-tei is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 530 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and cache hits cost nothing.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
Buy and sell spread for one card at Yuyu-tei
Two calls, from a card name to what the shop pays for it and what it sells it for.
Every SAR Pikachu on the buying list with buy_price_jpy, price_up and card_id.
The same card on the sell side: price in yen, exact stock, set name.
The gap between Yuyu-tei's buying price and its sale price for the same card, both read live.
curl -X POST https://api.reefapi.com/yuyu-tei/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"ピカチュウ","rarity":"SAR"}'{
"ok": true,
"data": { … },
"meta": {
"api": "yuyu-tei",
"endpoint": "search",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}What the shop prints, and the field it becomes
Yuyu-tei prints stock as a count only up to 10 and a circle above that. The API returns the exact count and keeps what the page shows next to it.
| on the page | field | value |
|---|---|---|
| 在庫 : 3 点 | stock_qty, stock_display, in_stock | 3, "3 点", true |
| 在庫 : ◯ | stock_qty, stock_display | the exact count (11 or more), "◯" |
| 在庫 : × (sold out, price still shown) | stock_qty, in_stock, price_jpy | 0, false, the last price |
| 500 円 with ~~680 円~~ (sale) | price_jpy, regular_price_jpy, on_sale | 500, 680, true |
| 買取 6,000 円, PRICE UP, ~~3,000 円~~ | buy_price_jpy, price_up, previous_buy_price_jpy | 6000, true, 3000 |
| 傷 (damaged copy) | damaged, product_id | true, "sv08a/10481/damage" |
| 236/187 · UR · [SV8a] | card_number, rarity, set_code | "236/187", "UR", "sv08a" |
Prices are yen as the shop prints them, with a thousands comma (5,980 円 = 5980). A buying price is never returned as price_jpy. Rarity '-' (no rarity) comes back as rarity null with rarity_raw '-'.
What Yuyu-tei publishes — measured 2026-10-15
One shop, one sell list and one buying list per game. These are the numbers measured on the live site.
24, from Pokémon (294 sets) and Yu-Gi-Oh! (463 sets) to Weiß Schwarz (416 sets). No Magic: The Gathering.
Price in yen, exact web-shop stock, regular price on sale items, damaged flag, rarity, card number, set code, image; card adds the set name, attribute table and kana reading.
Buying price in yen, PRICE UP flag with the earlier buying price, same card id as the sell side. No buying price for damaged copies.
600 products per page; last_page from the shop's pager, exact total on the last page, no rows past the end.
Price history, physical-store stock, English card names, a printed result count.
What people build with Yuyu-tei
The jobs this data is most often used for.
endpoints
credits per call
Price a Japanese collection across games: search each card and read price and exact stock.
Buy/sell spread: buy_prices for a set, then card on each card_id for the shop's sale price.
Watch buying-price jumps: buy_prices rows flagged price_up carry the earlier buying price.
Track a new set: search with its set code every day and follow stock_qty.
What Yuyu-tei data costs
The cheapest call here is 3 credits, so $15/mo (Pro) buys 3,333 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
Full pricing →- 1,000 free credits on signup, no card
- One key, all 530 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/yuyu-tei/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"query":"ピカチュウ","rarity":"SAR"}'import requests
r = requests.post(
"https://api.reefapi.com/yuyu-tei/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"query": "ピカチュウ",
"rarity": "SAR"
},
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up Yuyu-tei.
Get a free key →Which games does it cover?▾
24: Pokémon (default), Yu-Gi-Oh! OCG, Yu-Gi-Oh! Rush Duel, One Piece, Duel Masters, Weiß Schwarz, Weiß Schwarz Rose, Vanguard, Digimon, Union Arena, Battle Spirits, Gundam Card Game, hololive OCG, Shadowverse EVOLVE, WIXOSS, Z/X, Precious Memories, ChaosTCG, Rebirth for you, Lycee Overture, Fire Emblem Cipher, Xross Stars, Gundam Arsenal Base and Eiketsu Taisen. Magic: The Gathering is not sold by Yuyu-tei. The shop's own path codes (poc, ygo, opc, ws …) are accepted as game too; pm is Precious Memories, not Pokémon.
Is the buying price the price I pay?▾
No. buy_prices and buy_card return buy_price_jpy, what Yuyu-tei pays when you sell a card to the shop (買取). The sale price is price_jpy on search and card. Both sides carry the same card_id (for example sv08a/10481), so card and buy_card on one id give the spread.
How exact is the stock?▾
The page prints a count only up to 10 and a circle (◯) above that. stock_qty is the exact count the shop's cart works with; it matched the printed count on every product where a count is printed (83 of 83 in one measured list). stock_display keeps what the page shows. A sold-out product keeps its last price with stock_qty 0.
What are damaged copies?▾
Yuyu-tei sells scratched or worn copies (傷有り) as separate products at a lower price. damaged=true lists them; their product_id ends in /damage and card reads them. For example a UR Pikachu ex listed at 9,980 yen clean was 6,980 yen as a damaged copy on 2026-10-15. Damaged copies can be filtered by set, rarity and stock; the shop has no sale or card-type filter on that list.
How do I list one set?▾
sets returns every set of a game with its code (294 Pokémon sets, 463 Yu-Gi-Oh! sets on 2026-10-15). Pass the code as set to search or buy_prices, alone or with a name; several codes separated by commas work in one call. An unknown code, rarity or card type returns INVALID_PARAM with the valid values, not an empty list.
How far can I page?▾
The shop pages lists by 600 products. meta.last_page says how many pages the result has and has_more whether another follows; meta.total is exact on the last page (1,558 products for 'ex' on Pokémon on 2026-10-15, three pages). A page past the end returns no rows with past_last_page true.
Does the price depend on where I call from?▾
No. The same card, buying price and list were identical from four different countries in the same minute on 2026-10-15. Prices are yen.
What is the Yuyu-tei API?▾
Yuyu-tei API is a ReefAPI endpoint group for 遊々亭 (yuyu-tei.jp) trading-card prices as json: what one of japan's big multi-game card shops sells a card for and how many it has, what it pays for the same card (買取), and every set, for 24 games. It returns live JSON through POST requests under /yuyu-tei/v1.
Is the Yuyu-tei API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. Yuyu-tei calls use the same shared credit balance as every other ReefAPI engine.
Do I need a Yuyu-tei login or account?▾
No login to Yuyu-tei is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the Yuyu-tei data?▾
The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the Yuyu-tei API use?▾
Yuyu-tei actions currently cost 3 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
Can I call Yuyu-tei from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call yuyu-tei actions with the same key, credit pool and JSON envelope used by normal REST requests.
Is the Yuyu-tei API a Yuyu-tei scraper?▾
It is the managed alternative to a DIY Yuyu-tei scraper. Instead of building and maintaining your own scraper — proxies, headless browsers, captcha and constant breakage — you call one ReefAPI endpoint and get the same 遊々亭 (yuyu-tei.jp) trading-card prices as json: what one of japan's big multi-game card shops sells a card for and how many it has, what it pays for the same card (買取), and every set, for 24 games back as clean JSON.
266 E-commerce & Marketplaces APIs on the same key
One key, one credit pool, one response envelope. If you are pulling Yuyu-tei, you are one call away from the rest of the category — no second contract, no second integration.
Need something this API does not do?
Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 529 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-10-15.