canonical: https://jentic.com/apis/guildwars2.com/guild-wars-2 # Guild Wars 2 API The Guild Wars 2 API exposes data from ArenaNet's online RPG. Most of it is public game data: the item database, world and map lists, achievements, currencies, world-versus-world matches, and the trading-post commerce endpoints for listings and the gem-and-coin exchange. A smaller set of endpoints reads a player's own data, such as their account, bank, inventory, characters, and PvP stats, and these require a Guild Wars 2 API key tied to that account. Every resource is read-only, so the API is for reading game and account state rather than changing it. ## For AI agents Read Guild Wars 2 data: public item, world, map, achievement, currency, and trading-post commerce endpoints, plus account, character, and PvP endpoints that use a player API key. ## Scope Covers reading public game data and, with a player key, that player's own account, character, and PvP data. Every endpoint is read-only, so it cannot change items, currency, or characters in game. ## Capabilities - Look up items and the full item database by id - Read trading-post listings and the gem-and-coin exchange rates - List worlds, maps, achievements, and currencies - Read world-versus-world match state - Fetch a player's account, bank, and inventory with their API key - Read a player's characters and their details - Retrieve a player's PvP statistics ## Use cases ### AI Agent for Trading-Post Prices A game-companion agent answers questions about item prices and market activity. Through Jentic it reads the public trading-post listings and the gem-and-coin exchange endpoints, joins them to item details, and reports current buy and sell prices. Because these endpoints are public, the agent works without any key, and it discovers the commerce operations by intent rather than being wired to specific routes. Example prompt: Look up an item by name, read its trading-post listings, and report the current lowest sell and highest buy prices ### Account and Character Companion A player connects their Guild Wars 2 API key so an assistant can read their account. It fetches the account, bank, and inventory and lists characters with their details, letting the player ask what they own or how a character is equipped. The key stays scoped to that account and read-only, so the assistant can report but never change anything in game. Example prompt: With the player's API key, read the account bank and inventory and summarize the most valuable stored items ### World-versus-World and Achievement Tracking A community tool tracks WvW match standings and achievement data. It reads the public WvW matches, worlds, and achievements endpoints on a schedule and builds a live view of how servers are performing. No key is needed, so the tool can serve a whole community from public data alone. Example prompt: List the current WvW matches, resolve the world names, and report each match's server scores ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/items` | List item ids in the database | | GET | `/items/{id}` | Get details for one item | | GET | `/commerce/listings` | Read trading-post listings | | GET | `/commerce/exchange/coins` | Get the coin-to-gem exchange rate | | GET | `/worlds` | List worlds | | GET | `/account` | Read the authenticated player's account | | GET | `/characters` | List the authenticated player's characters | ## Key resources - **Items** — The public item database with per-item detail lookups - **Commerce** — Trading-post listings and the gem-and-coin exchange rates - **Game reference** — Public worlds, maps, achievements, currencies, and WvW matches - **Account** — A player's account, bank, and inventory, read with their API key - **Characters** — A player's characters and their details, read with their API key - **PvP** — A player's PvP statistics, read with their API key ## Why Jentic - **Setup:** Using the Guild Wars 2 API by hand means knowing which endpoints are public and which need a player key, and joining item and commerce data yourself. Through Jentic you install once, import the API from the Directory, and your agent calls the right endpoint, adding the key only where it is required. - **Permission scoping:** The Guild Wars 2 API is read-only, so you allow only the endpoints a task needs. A price bot can be limited to the public GET /items and GET `/commerce/listings`, while the account and character endpoints stay out of the allowed set unless the agent should read personal data. Rules run on your own instance and every call is logged. - **Credential handling:** The public game-data endpoints need no credential. When a workflow reads account or character data, its Guild Wars 2 API key is stored once, encrypted, by your own Jentic One instance and injected at execution time, so it never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get trading-post prices' or 'read my account', and Jentic returns the matching Guild Wars 2 operation with its input schema so the agent calls the right endpoint without reading reference docs. ## Related APIs - **Path of Exile API** — Online action-RPG data including items, characters, and stash tabs - **RAWG Video Games Database API** — Cross-title video game metadata, ratings, and release data - **Steam Web API** — Player, store, and platform data across Steam titles ## FAQ ### What authentication does the Guild Wars 2 API use? Most endpoints are public game data and need no credential. The account, character, and PvP-stats endpoints read a player's own data and require an HTTP bearer token, the Guild Wars 2 API key generated from the player's account. Through Jentic that key is stored encrypted on your own instance and injected at call time, so it never appears in the agent's prompt or logs. ### Which Guild Wars 2 endpoints work without an API key? The item database, worlds, maps, achievements, currencies, world-versus-world matches, and the trading-post commerce endpoints are all public. You can read prices, items, and match state without any credential. Only the account, character, and PvP endpoints require a key. ### How do I get trading-post prices from the Guild Wars 2 API? Call GET `/commerce/listings` for an item's buy and sell orders, and GET `/commerce/exchange/coins` for the coin-to-gem rate. Join the result to GET `/items/{id}` for the item's name and details. Through Jentic you search for the intent 'get trading-post prices' and the agent gets the operation and its input schema. ### Can the Guild Wars 2 API change my account or characters? No. Every endpoint is read-only, so an agent can report your account, bank, inventory, and characters but cannot move items, spend currency, or alter anything in game. The API key only grants read access to your own account data. ### What are the rate limits for the Guild Wars 2 API? The OpenAPI spec does not define numeric rate limits; ArenaNet applies its own limits and much of the reference data changes rarely. Cache stable data like items and worlds, and check https://wiki.guildwars2.com for current guidance. ### Can I limit what my agent is allowed to do with the Guild Wars 2 API? Yes. The API is read-only, so you allow only the endpoints a task needs, such as the public GET /items and GET `/commerce/listings`, and leave the account and character endpoints out of the allowed set if the agent should not read personal data. Through Jentic these rules run on your own instance and every call is logged. ### Is there a Guild Wars 2 MCP server? You don't need a separate MCP server to give your agent the Guild Wars 2 API. Jentic connects it directly from the API Directory: import the API and your agent reads items, prices, and account data on demand without loading another server's tool definitions into its context.