Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tryhoard.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Your first agent-driven price change

You’ve connected Claude and your permission grants are on the defaults. You want to bump your Mythic rule from a 1.10x multiplier to 1.15x. This is the walkthrough for what that actually feels like the first time you do it. The flow has three beats: you ask, Claude shows you the preview, you click to approve. Total time, maybe 30 seconds.

​
Before you start

  • Pro subscription, Claude connected via the OAuth connector
  • At least one pricing rule that targets Mythic rarity (or substitute whichever rule you actually want to edit)
  • Permission grants left on defaults. The relevant one here is pricing.edit_rule: ask_for_mutations. If you tightened that to always_ask, the flow is the same; you just get one prompt regardless of risk score.

​
Step 1: Ask Claude

Open Claude.ai with the Hoard connector enabled. Type:
“Bump my Mythic rule from 1.10x to 1.15x.”
Claude calls the preview endpoint behind the scenes. It does not commit yet. The server returns a plan: how many cards would shift, what the projected aggregate change in listed value is, the risk classification, and a confirmation URL. Claude shows the price change preview with risk pill and dollar impact What you should see in the response:
  • Cards affected. Something like “180 cards.” This is the count of inventory rows the rule currently selects.
  • Projected change. Something like ”+$72.40 listed value.” Positive because you’re raising the multiplier. If it were negative and big enough, a hard floor might trip, see When the agent says no.
  • Risk pill. Probably “low risk.” A 1.10 → 1.15 change is a +4.5% multiplier move, well under most sellers’ change_cap_pct.
  • Confirmation link. A URL like https://www.tryhoard.com/agent/plans/<plan_id>.
If you ever see “high risk” or “critical risk” on a small-looking edit, stop and read what Claude wrote. Risk scoring is user-relative, see Picking the right permission mode for what tightens it. Click the link Claude gave you. It opens in whichever browser you’re already signed in to Hoard with. No second login. You land on a plan detail page that shows the same information Claude saw, plus:
  • The exact diff: rule name, old multiplier, new multiplier
  • A sample of 5–10 affected cards with their before/after listed prices
  • The full risk breakdown (which factors pushed the score up or kept it down)
  • An Approve button and a Reject button
Plan detail page with diff, sample cards, and Approve button Read the diff. If anything looks off, wrong rule, wrong direction, way more cards than you expected, click Reject. The plan dies, Claude gets told, nothing committed. If it looks right, click Approve.

​
Step 3: Claude commits

Approving issues a short-lived confirmation token (60 seconds). Claude picks up the token, retries the commit, and the change applies. Back in your Claude chat, you’ll see something like:
“Done. Updated your Mythic rule from 1.10x to 1.15x. 180 cards repriced. Your next sync will push these to TCGplayer.”
The change is now live in Hoard. Your next sync cycle pushes it to TCGplayer. Claude reports the committed change with card count and next-sync note

​
Where the change shows up later

Two places. Your dashboard. The rule now reads 1.15x where it used to read 1.10x. Repricing has either already happened (if you’re on autonomous sync) or is queued for your next confirm-mode sync. Your agent activity log. This is the audit trail. The easiest way to find this specific change later is to ask Claude: “what did you change for me today?” — it pulls from the activity feed at GET /api/v1/agent/activity and summarizes. Filter by namespace=pricing.edit_rule&outcome=committed&since=<date> if you’re hitting the endpoint directly. The row tells you the before/after multiplier in params_summary, what the risk score was, and links back to the plan detail page via agent_action_plan_id if you want to re-read it. A dedicated Activity tab in Settings → Assistants is on the roadmap. For a full tour of the activity log including every outcome type, see Reading your agent activity log.

​
What if you’d loosened the grant?

If you’d set pricing.edit_rule to auto_low_risk, this exact edit would have skipped steps 2 and 3 entirely. Claude would have called preview, seen the low-risk classification, called commit on the same turn, and reported back “done” in one round trip. No confirmation link, no click-through. You’d still see it in the activity log. Floors still gate. Risk scoring still runs, if the same conversation had asked for a 5.0x multiplier, the call would have escalated to confirmation regardless of the loosened grant. That’s the trust progression: start with confirmations, watch the patterns, loosen the dials once you trust them. See Going from cautious to confident.