Where Does PokeList Get Its Pokémon Data, and Which Pokémon Are Covered?

Updated

PokeList (pokemonlist.netlify.app) states that its Pokémon list is built with Gatsby and the graphql-pokemon endpoint, so its data comes from that GraphQL Pokémon API rather than from an in-house database. Coverage follows whatever that endpoint returns; the visible catalog starts at Bulbasaur (#001) and runs through consecutive National Pokédex numbers, including the early Kanto entries shown on the page.

Data source: what the site says

The site's own description is the main evidence: "Pokemons list built with gatsby and graphql-pokemon endpoint." That tells you two things:

  • Build tool: Gatsby generates the site, which typically means the list is compiled from data fetched at build time rather than queried live on every page load.
  • Data provider: the graphql-pokemon endpoint supplies the records. The site does not claim to maintain its own dataset, so accuracy and completeness depend on that API.

Because the site does not publish a separate data-maintenance statement, treat the API as the single upstream source. If a Pokémon is missing or a value looks off, the likely place to check is the endpoint, not the site's front end.

Which Pokémon are covered

The page shows a numbered list in National Pokédex order. The excerpt visible in the site's page evidence includes:

# Pokémon # Pokémon
001 Bulbasaur 011 Metapod
002 Ivysaur 012 Butterfree
003 Venusaur 013 Weedle
004 Charmander 014 Kakuna
005 Charmeleon 015 Beedrill
006 Charizard 016 Pidgey
007 Squirtle 017 Pidgeotto
008 Wartortle 018 Pidgeot
009 Blastoise 019 Rattata
010 Caterpie 020 Raticate

What this confirms:

  • Continuous numbering from #001. The list begins with the Kanto starters and proceeds without gaps in the visible range, so you can expect a full sequential catalog rather than a curated selection.
  • Early Kanto is definitely included. Everything from Bulbasaur through Raticate appears, covering the first 20 National Pokédex entries.
  • Beyond #020 is not confirmed by the visible excerpt. The page evidence stops at Raticate, so the safest statement is that coverage extends at least through the early Kanto numbers and follows the API's data for the rest.

How to judge whether it fits your use

Use these conditions to decide:

  • Good fit: you want a quick, browsable list of Pokémon in Pokédex order with basic stats, and you don't need a guarantee of completeness beyond what the API provides.
  • Check first: if you need a specific Pokémon outside the early Kanto range, confirm it appears on the site before relying on it.
  • Not a fit: if you need an authoritative, versioned dataset with a published update schedule — the site doesn't document one, and its data is only as current as the graphql-pokemon endpoint at build time.

Reading entries alongside the data question

Each row pairs a name and number with two numbers and an icon, for example "Bulbasaur - 001 👊 7 - 70." The site presents these as part of the list itself; the page evidence does not label the columns, so interpret the values against the API's field definitions rather than assuming what each number means. If exact stat meanings matter for your task, cross-check the same Pokémon on the graphql-pokemon endpoint.