The wiki database is readable over a public REST API. Every category follows the same two-endpoint shape, so once you have used one you have used all of them.
These endpoints are read-only and need no credentials. Writing to the wiki happens through the site, and requires maintainer access. See creating and editing wiki entries.
All paths below are relative to https://api.entropiacentral.com.
The shape of every category
GET /{category} list, filtered and paginated
GET /{category}/{slug} a single entryEntries are addressed by slug, never by internal id, and slugs match the ones in the site's own URLs. If you can see it at entropiacentral.com/wiki/creatures/atrox, then GET /creatures/atrox is the same entry.
Categories
| Path | Contents |
|---|---|
/weapons | Weapons with damage, DPS, DPP, range, decay and efficiency |
/weapon-attachments | Scopes, sights and amplifiers |
/creatures | Creatures with health and level data |
/armors | Armour sets |
/armor-parts | Individual armour pieces |
/armor-platings | Plating |
/materials | Ores, enmatters and loot materials |
/tier-materials | Tiering components |
/blueprints | Crafting recipes and their requirements |
/finders, /finder-amplifiers | Mining finders and amplifiers |
/excavators | Excavators |
/healing-tools | Healing tools |
/enhancers | Weapon and tool enhancers |
/fishing-rods, /fishing-rod-attachments, /fish | Fishing |
/cooking-stoves, /consumables | Cooking and consumables |
/mindforce-implants | Mindforce |
/pets | Pets |
/clothes | Clothing |
/effects | Effects applied by items |
/codexes | Codex entries |
/landareas, /planets, /asteroids | Locations |
The site's wiki hub is the authoritative list if a new category appears.
Listing parameters
Shared by every category:
| Parameter | Type | Notes |
|---|---|---|
search | string | Matches within the category |
sortBy | string | Category-specific field. Defaults to Name |
sortOrder | string | asc or desc. Defaults to asc |
pageNumber | number | Defaults to 1 |
pageSize | number | Defaults to 20, maximum 50 |
Each category adds its own filters. Weapons, for example, accept type, class, source, limited, and range filters minDamage, maxDamage, minRange, maxRange, minDps, maxDps, minDpp, maxDpp, and sort on Name, Damage, Range, Dps, Dpp, Decay, TT, Efficiency, Type or Class.
Invalid combinations are rejected with 400 rather than corrected, including a minimum above its matching maximum, a page size over 50, or a sortBy the category does not recognise.
curl "https://api.entropiacentral.com/weapons?class=Rifle&minDps=100&sortBy=Efficiency&sortOrder=desc"A single entry
GET /weapons/{slug}
GET /creatures/{slug}Returns the full entry including its relationships, so a creature carries its loot and a blueprint carries its materials. Unknown slugs return 404.
Extras worth knowing
A few categories expose more than the standard pair:
| Endpoint | Returns |
|---|---|
GET /weapons/types | The distinct weapon types, for building a filter UI |
GET /weapons/skill-tree?type= | The skill tree, optionally narrowed to one weapon type |
GET /creatures/{slug}/stats | Aggregate statistics for a creature |
GET /creatures/{slug}/activity | Recent activity involving that creature |
Search across everything
GET /search?q=atrox&limit=20One call across every indexed category, rather than per-category search.
| Parameter | Notes |
|---|---|
q | Required, minimum 2 characters. Shorter returns 400 |
limit | 1 to 50, defaults to 20. Out-of-range values fall back to 20 rather than erroring |
Results come back grouped by entity type, each with a slug, name, description and a relevance rank. Names are weighted above descriptive text, so an exact item name outranks a passing mention.
Build links from results client-side by pairing the entity type with the slug, which is how the site's own search does it. That keeps URL structure in one place instead of baked into responses.
Practical notes
Slugs are the contract. They are stable and they are what the site links to. Store slugs rather than internal ids, which are not part of the public surface and carry no guarantee.
Empty is not missing. Wiki entries are community maintained and fields are filled in as they are verified. A blank field means nobody has confirmed that number yet, not that it is zero. Treat missing values as unknown rather than defaulting them.
Page size caps at 50. Mirroring a whole category means paging. Sort by a stable field, since paging through a result set ordered by something that changes will skip and repeat rows.