PokéAPI v2 operator

Design, inspect, revalidate, repair, and selectively evict a persistent PokéAPI v2 response cache, including canonical URL keys, query-aware list pages, atomic bodies and metadata, validators, last-known-good fallback, per-key single-flight, cross-process locks, negative entries, and request accounting. Use when adding cache behavior, investigating repeated requests or stale data, refreshing a resource, or cleaning specific cached entries.

Answer quick PokéAPI v2 questions with a compact reference for resource paths, named and unnamed identifiers, pagination, linked resources, language and version filtering, cache-first requests, and fair-use boundaries. Use when someone asks which PokéAPI v2 endpoint or query shape to use, or wants a fast lookup rather than a guided workflow.

Inspect a PokéAPI v2 client's base URL, HTTP stack, persistent cache directory, cache metadata, retry and concurrency policy, pagination bounds, and ability to read one known resource without changing configuration. Use before a PokéAPI operation, when request volume is uncertain, when cached data looks wrong, or when someone asks whether the client is configured for fair use.

Resolve PokéAPI v2 species to numeric evolution-chain resources, walk branching chain links, preserve alternative evolution-detail objects and nullable requirements, read evolution triggers, and cache every species, item, move, location, type, and chain link used in the answer. Use when building an evolution tree, explaining evolution conditions, or diagnosing a missing or incorrect branch.

Read and relate PokéAPI v2 generations, versions, version groups, Pokédexes, and languages while distinguishing their scopes, filtering localized names and flavor text, preserving regional Pokédex numbers, and caching each requested list or detail page. Use when selecting a game context, mapping resources across releases, reading Pokédex membership, or localizing API data.

Connect a cache-first PokéAPI v2 client to server applications, browser-facing APIs, static generation, background jobs, test suites, CI, and supported wrapper libraries while centralizing request budgets, observability, persistence, and same-origin URL validation. Use when wiring PokéAPI into an application stack, sharing cached data across processes, preventing per-browser amplification, or making builds and tests deterministic.

Read and relate PokéAPI v2 items, attributes, categories, pockets, fling effects, berries, berry firmnesses, and berry flavors while preserving version-specific values, item-to-berry links, localized text, and cache-first request accounting. Use when looking up item mechanics, organizing inventory metadata, resolving berries to items, or comparing fling and berry properties.

Read and relate PokéAPI v2 regions, locations, location areas, Pal Park areas, Pokémon encounter routes, encounter methods, conditions, and condition values while filtering nested encounter chances by version and caching each requested resource. Use when finding where a Pokémon appears, listing encounters in an area, resolving region geography, or interpreting encounter requirements.

Read and relate PokéAPI v2 moves, move ailments, battle styles, categories, damage classes, learn methods, targets, numeric machine records, contest types, contest effects, and super contest effects with version-aware filtering and cache-first links. Use when examining move mechanics, learnability, machines, targets, damage classes, or contest behavior.

Read and relate PokéAPI v2 Pokémon resources including battle instances, species, forms, abilities, types, stats, natures, characteristics, egg groups, growth rates, colors, habitats, and shapes while distinguishing identifiers and caching every followed link. Use when looking up a Pokémon, comparing forms or types, reading species lore or breeding data, or joining Pokémon metadata across resource families.

Set up a PokéAPI v2 client from zero with the official HTTPS base URL, GET-only transport, a persistent local response cache, normalized URL keys, atomic writes, per-key single-flight, bounded retries, pagination caps, request accounting, and a two-read cache verification. Use when an application has no PokéAPI v2 wiring, when its cache is only in memory, or when the user asks to configure a fair-use client.

Diagnose PokéAPI v2 failures by separating cache, URL, identifier, pagination, version filtering, response-shape, connectivity, retry, concurrency, and upstream behavior, while preserving exact errors and avoiding request amplification. Use when requests return 404 or 5xx, data appears stale or incomplete, the wrong form or version is shown, cache hits do not occur, or a client sends more network traffic than expected.