Hearthstone API
Official vendor OpenAPI document · agent-readyMediaContent DeliveryRapidAPI key (X-RapidAPI-Key header)11 EndpointsREST
For Agents
Retrieve Hearthstone card data by name or filtered by class, set, race, quality, type, and faction, plus card backs and game metadata.
Use for: Get the card details for a specific Hearthstone card by name, Find all Legendary quality cards, List every card in a given set, Search for cards whose name contains a keyword
Not supported: Does not track player accounts, match history, or live game state, and does not modify card data. Use for reading Hearthstone card, card back, and metadata only.
The Hearthstone API returns card data for Blizzard's Hearthstone collectible card game, including individual cards, card backs, and game metadata. Cards can be retrieved by name or filtered by class, set, race, quality, type, and faction, or found through a partial-name search. The API is served through RapidAPI and authenticated with a RapidAPI key.
Install Jentic One Beta
Connect the Hearthstone API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Hearthstone API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhearthstoneapi.com%2Fhearthstoneapi" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fhearthstoneapi.com%2Fhearthstoneapi" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Hearthstone API.
Retrieve the full card list or a single card by name
Filter cards by class, set, race, quality, type, or faction
Search for cards by a partial name match
Fetch all card backs available in the game
Read game metadata such as classes, sets, and factions
Use Cases
Patterns agents use Hearthstone API for, with concrete tasks.
★ Agent-Powered Hearthstone Card Lookup
An AI agent building a deck helper or answering card questions retrieves Hearthstone card data on demand through Jentic. The Hearthstone API returns a card's stats, text, and image by name, or a filtered list by class or set, so the agent grounds its answers in real card data rather than guessing.
Look up a card by name and return its mana cost, attack, health, and card text
Card Collection and Set Browsing
A companion app lists cards by set, class, or rarity for browsing and filtering. The Hearthstone API exposes retrieval by class, set, race, quality, type, and faction, so a client can build filtered views without maintaining its own card database.
Retrieve all cards in a given set and group them by rarity
Card Search Feature
A search box needs to match partial card names as a user types. The Hearthstone API's partial-name search returns matching cards, so an app can offer autocomplete-style lookups backed by live card data.
Search for cards whose name contains a typed substring and return the top matches
Key Endpoints
11 endpoints — the hearthstone api returns card data for blizzard's hearthstone collectible card game, including individual cards, card backs, and game metadata.
METHOD
PATH
DESCRIPTION
GET
/cards
Get all cards
GET
/cards/{name}
Get a card by name
GET
/cards/classes/{class}
Get cards by class
GET
/cards/sets/{set}
Get cards by set
GET
/cards/search/{name}
Search cards by partial name
GET
/cardbacks
Get all card backs
GET
/info
Get game metadata
GET
/cards
Get all cards
GET
/cards/{name}
Get a card by name
GET
/cards/classes/{class}
Get cards by class
GET
/cards/sets/{set}
Get cards by set
GET
/cards/search/{name}
Search cards by partial name
GET
/cardbacks
Get all card backs
GET
/info
Get game metadata
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Hearthstone by hand means signing up on RapidAPI, sending your key in the X-RapidAPI-Key header, and mapping each filter endpoint yourself. Through Jentic you install once, import the Hearthstone API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Card filters put the value in the URL path (/cards/classes/{class}), so a rule can pin your agent to specific lookups, and every operation is read-only. You choose the operations it may call, so it retrieves and searches card data and nothing else.
Credential isolation
Your RapidAPI key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get a hearthstone card' or 'find cards by class', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Hearthstone API through Jentic.
What authentication does the Hearthstone API use?
The Hearthstone API is served through RapidAPI and authenticates with a RapidAPI key sent in the X-RapidAPI-Key header, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected when your agent calls the API.
Is there a Hearthstone API MCP server?
You don't need an MCP server to give your agent the Hearthstone API. Jentic connects it directly from the API Directory: import it, store your RapidAPI key once, and your agent looks up and filters card data as it needs to. Nothing extra is loaded into the agent's context until a call is made.
Can I limit what my agent is allowed to do with the Hearthstone API?
Yes. Every operation here is a read-only card lookup, and you choose which ones your agent may call, so you can allow card retrieval and search and nothing else. Every call it makes is logged for review.
Can I filter Hearthstone cards by class or set?
Yes. The API exposes retrieval by class, set, race, quality, type, and faction, each as its own operation, so an agent can request just the Mage cards or just the cards in one set.
How do I look up Hearthstone cards through Jentic?
Search Jentic for 'get a hearthstone card', which returns the card lookup operation with its input schema. Add the Hearthstone API from the Jentic API Directory, store your RapidAPI key once, and your agent can fetch card data. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED