mocop
Browse · Docs · Guide · Analyze

Everloot API

API by Everloot · rest

Everloot publishes what players saw in WoW: Forever, and states a fact only once three installs reported it. The corpus and the drop rates are Everloot's data under CC BY-SA 4.0: credit it when you show it. Game-file endpoints carry Blizzard's data, found in game files and unconfirmed, with the build they came from; they are not under Everloot's licence. Every shape here is also published as JSON Schema under https://everloot.app/schema/api/, and the same definitions are the @everloot/protocol package in the repository (packages/protocol), not yet on npm. For answering questions, the MCP server at https://everloot.app/mcp/public is the right tool; this API is for building datasets and tools.

Endpoint: https://everloot.app/

Verification: observed. Source: crawl.

Capabilities (13)

  • The public corpus: every public record players reported without install ids
  • The facts that are settled for one client build so an uploader can skip…
  • Typed relations between items NPCs spells quests zones and sets
  • The whole game-file relation layer of the current build
  • Whether the public snapshot is fresh
  • Upload records from an Everloot SavedVariables file
  • Every item of the current build with its class subclass slot and quality
  • The item class and subclass tree of the current build with the slot and…
  • Forever market values from full auction scans players started
  • What each disenchant band yields from disenchants players recorded
  • Corroborated drop rates with loot-window counts
  • One MCP tool's answer over plain HTTP
  • The hover card for one item NPC quest or object page for the embeddable…
About · Contact · Privacy