Skip to main content
A card list is a hand-picked set of cards — the box going to a show, this week’s sell-through pile, whatever you’re keeping together. Your assistant can build and manage lists directly, no approval step required.

​
Step 1: Create a list

“Make a new list called Con Box.”
This is a write, and it applies immediately. Unlike a pricing change, there’s no preview or review link — the list exists as soon as you ask.

​
Step 2: Add or remove cards

“Add these three cards to Con Box: [names].” “Remove [card] from my Sell This Now list.”
You can also ask the assistant to build a list from a description rather than naming cards one by one:
“Add all my Illustration Rare Pokemon over $20 to a new list called Show Pile.”

​
Step 3: Rename or delete a list

“Rename Con Box to Convention Q1.” “Delete the PSA Submission list, I already shipped those.”

​
Why this skips the approval flow

Pricing changes go through a propose-review-apply flow because they carry money risk — a wrong multiplier can move real listed prices. A list carries none of that. Adding a card to a list doesn’t touch its price, and creating or deleting a list doesn’t touch your inventory count. That’s why hoard.lists.* writes commit directly instead of generating a review link. If you’re used to seeing a review link after a pricing ask, don’t expect one here — list writes and pricing writes are different kinds of action, not two modes of the same one.