Huntera's imbuements as the game publishes them — 69 on the capture being
served, each keyed on the id the game files it under.

filter[material] asks which imbuements a given item feeds, named by the game's
item id or by slug: ?filter[material]=5877 and
?filter[material]=green-dragon-leather are one query, and answer 3. 69 items feed
the 138 recipe lines and an item usually feeds all three tiers of one effect.

They are 23 effects at three tiers each, and the tier decides the price:
price, protection_price, gold_token_price and success_percent each take
exactly three distinct values across the whole table, one per tier. The 69
group into 19 category values, because elemental-damage holds five effects
— electrify, frost, reap, scorch and venom — and the other 18 categories hold
one each.

materials is the recipe, inline on both endpoints rather than behind
?include=: a recipe is two lines on average, and the tier decides that too —
23 imbuements need one material, 23 need two, 23 need three, with a tier's list
being the tier below plus exactly one item. Each line carries the game's own
item id and the item it points at on this surface.

Nothing here is borrowed from tibia.dev, so fallbacks is empty on every row.
The tibia object beside it is the widest on this surface — the counterpart's
name, its sprite, its effect and the two lists of gear it goes on — and it
carries no quantity at all, Tibia publishing no price and no success chance
for an imbuement anywhere. tibia.effect is the one field the two games both
answer, and they answer it differently: "Club fighting +1" against this game's
"Raises club fighting by 1.", on all 69 rows. Both are printed, each under the
name of whoever wrote it, which is what saying so without quoting either as
the other looks like.

tibia.slots and tibia.equipment_slots are the one thing this endpoint says
about gear, and they are in there rather than at the top level because the
capture publishes no slot field on any of the 69 rows. All 69 resolve to a
Tibia counterpart, so the answer exists — it is just Tibia's, and a top-level
copy would read as Huntera's own rule for where the imbuement applies.

category and tier are objects now and type is new, which is a breaking change
on this endpoint. category was the bare slug and is {slug, name}, the slug
unchanged; tier was the bare integer and is {slug, name, rank}, the integer now at
tier.rank. type is the name with its tier word removed. Nothing else moved, and
?filter[category]= and ?filter[tier]= take exactly what they took before.