Data & Downloads

Anime Vanguards Guide

Anime Vanguards Data Downloads

Download the current Anime Vanguards Guide datasets as JSON, then use the normal guide pages to inspect rows, calculators, and correction notes in context.

Last checked 2026-06-29 Update 13 Data & Downloads
Anime Vanguards gameplay media
Quick Facts Data & Downloads
  • JSON exports are for audits and spreadsheets.
  • Use guide pages for correction notes and context.
  • Check modified dates before reusing rows.

Citation facts

These dated facts are safe to cite with the source policy and JSON exports. They describe Anime Vanguards Guide coverage, not an official Roblox or Kitawari API.

Checked date

This static build uses 2026-06-29 as the current review date for pages and JSON exports.

Unit coverage

The unit stats export contains 369 rows, and the unit profile index contains 369 rows.

Mechanics coverage

The data layer covers 11 trait rows, 11 element rows, 12 familiar rows, and 4 evolution material routes.

Resource coverage

The guide exposes 12 item rows, 10 shop rows, 8 stat-rank rows, and 7 stat-chip income rows.

Unit stats JSON

369 rows with unit name, rarity, type, element, damage, SPA, range, and DPS fields.

Download units.json

Element coverage JSON

11 rows with element mechanics, team problem mapping, unit counts, top DPS samples, and top range samples.

Download elements.json

Familiars JSON

12 rows with familiar rarity, route type, role tags, mode tags, element tags, obtainment, corruption risk, and fit notes.

Download familiars.json

Items JSON

12 rows with item group, use case, source route, spend priority, and hold rule for resource planning.

Download items.json

Shops JSON

10 rows with shop group, currency, restock note, use case, purchase priority, and avoid rule.

Download shops.json

Traits JSON

11 rows with trait names, odds, pity context, reroll priority, and role-fit notes.

Download traits.json

Evolutions JSON

4 material routes with target units, required materials, route evidence, and spending checks.

Download evolutions.json

Stat ranks JSON

8 rows covering D through Godly stat-rank planning, stop rules, and target-rank cautions.

Download stat-ranks.json

Stat chip income JSON

7 rows covering reusable chip sources, one-time claims, budget guardrails, and screenshot evidence needs.

Download stat-chip-income.json

Trade values JSON

6 rows for Update 13 value-watch units, route context, demand signals, and trade-risk notes.

Download trade-values.json

Machine-readable data

These JSON files mirror the guide datasets used by the unit database, unit profile index, element planner, familiar optimizer, items database, shops guide, trait guide, evolution planner, stat-rank table, stat-chip income tracker, value list, trading calculator, and Dataset schema. They are useful for spreadsheet checks, correction audits, external notes, and comparing guide rows against current screenshots.

Field notes

  1. units.json is best for base-stat sorting, DPS checks, and identifying units that need calculator testing.
  2. unit-profile-index.json is best for role buckets, profile status, profile paths, and choosing which unit pages to deepen next.
  3. elements.json is best for element-team planning, coverage audits, top unit samples, and mapping team problems to element mechanics.
  4. familiars.json is best for familiar fit audits, corruption-risk checks, route availability, role tags, and comparing companion rows against screenshots.
  5. items.json is best for resource-priority audits, spend-or-hold notes, and mapping items to unit, stat, evolution, shop, and mode routes.
  6. shops.json is best for shop-priority checks, restock notes, currency planning, and deciding which current screenshot is needed before publishing exact prices.
  7. traits.json is best for reroll-priority notes, odds context, and role-fit audits.
  8. evolutions.json is best for material gap checks and route planning before spending scarce items.
  9. stat-ranks.json is best for deciding whether a current stat roll is filler, usable, or worth protecting.
  10. stat-chip-income.json is best for separating reusable chip routes, one-time claims, and screenshot-needed income rows before spending.
  11. trade-values.json is best for auditing value-list route context and checking why a unit is on the trade watchlist.

Correction notes

A useful correction names the JSON file, row, field, current value, suggested value, and source. Send screenshots or public source links through the contact page, and check the source policy for how claims are separated.

Guide path

What to open next

Use these links as the next step for the decision on this page.

Source check

Spot outdated game data?

Upload a screenshot or describe the issue. This page title and URL are attached automatically for review.