Jagex
Jagex is a British video game developer and publisher headquartered in Cambridge, England, best known as the studio behind RuneScape and Old School RuneScape - persistent, community-shaped online worlds that have run for over two decades. Beyond the games, Jagex operates a set of public, read-only RuneScape web-data APIs: the Grand Exchange item price and catalogue endpoints (for both RuneScape and Old School RuneScape), the RuneScape and Old School RuneScape Hiscores, and the RuneMetrics player-profile service. These unauthenticated JSON and CSV endpoints power a large third-party ecosystem of price trackers, fan sites, clan tools, and community applications. Jagex was surfaced as a portfolio company of Insight Partners.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Jagex the way a machine reads it — 7 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Jagex scores 19.5/100 (emerging), with a separate agent-readiness read of 7/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Jagex
Each block below is one kind of artifact we hold for Jagex. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 5
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
RuneScape Grand Exchange API
Read-only JSON endpoints for the RuneScape (RS3) Grand Exchange item database - item detail (price, trend, 30/90/180-day movement), category listings, and daily price-history gr...
Old School RuneScape Grand Exchange API
Read-only JSON endpoints for the Old School RuneScape (OSRS) Grand Exchange item database - item detail, category listings, and price-history graphs. Unauthenticated GET.
RuneScape Hiscores API
Player skill and activity rankings for RuneScape (RS3). The index_lite endpoint returns rank, level, and experience per skill as CSV; unauthenticated GET keyed by player display...
Old School RuneScape Hiscores API
Player skill and activity rankings for Old School RuneScape (OSRS). The index_lite endpoint returns rank, level, and experience per skill as CSV; unauthenticated GET keyed by pl...
RuneMetrics Profile API
Public player-profile service for RuneScape (RS3), exposing summary statistics, skill levels, quest progress, and recent activity for accounts that have opted their profile publ...
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Jagex — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Access & Security 4
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/jagex · machine-readable index on apis.io