PVPWire.
Competitive gaming data for humans and AI agents. Structured game stats, builds, and mechanics, served as browsable tables and a free JSON API.
The mission
Game data lives scattered across wikis, forum threads, and spreadsheets, most of it unstructured and none of it built for machine consumption. Players hand-copy numbers into build calculators. AI agents scrape prose and guess at the schema. Nobody publishes the raw facts as a clean, queryable source.
PVPWire fills that gap. Runewords, cube recipes, breakpoints, and other verified game mechanics are hand-compiled, structured, and served through both browsable tables and a free JSON API with no auth wall. The catalog surface still spans the full breadth of competitive PvP across genres, and the archive preserves the guild history the genre was built on, but the core of the platform is structured data that a human can read and an agent can call.
Editorial standards
PVPWire reports facts: what data is verified, what patch it applies to, and where a number came from. When the desk takes a position, it is short and specific, never padded.
Every API response ships with a disclaimer, a data version, and the game patch it was compiled against, so nothing is presented as more authoritative than it is. We correct errors visibly, with a note and a date.
New reporting publishes under PVPWire Editorial. Archive editorial preserves its original bylines (Flosium, Og, Flipper) for historical accuracy.
The guild database is community-fed. Submissions go through editorial review before publication. We cite sources and timestamp everything we verify.
Contact
Tips, corrections, guild submissions: /submit.
PVPWire is an independent publication.