RustClash APIru-wiki.rustclash.com ↗
Access Rust game item stats, loot tables, craft/recycle data, and 6,000+ skin prices from ru-wiki.rustclash.com via a structured JSON API.
What is the RustClash API?
The RustClash Rust Wiki API exposes 5 endpoints covering the full item and skin catalogue from ru-wiki.rustclash.com. Use get_item to retrieve a single item's stat map, loot sources, craft recipes, recycle output, and associated skins in one round trip. Use list_skins to page through roughly 6,000 skins with price data sourced from RustClash.com, the Steam Community Market, and the Rust Item Store.
curl -X GET 'https://api.parse.bot/scraper/f7060e62-00c3-46ae-98be-95978a7f4896/search?query=rifle' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace ru-wiki-rustclash-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: RustWiki SDK — browse items, search, drill into skins."""
from parse_apis.ru_wiki_rustclash_com_api import RustWiki, SkinSort, InputNotFound
client = RustWiki()
# List weapons and drill into the first item's full detail page.
weapon = client.item_summaries.by_group(group="weapons", limit=3).first()
if weapon is not None:
item = weapon.details()
print(item.name, item.stats)
for source in item.loot[:3]:
print(f" loot: {source.container} — {source.amount} ({source.chance_percent}%)")
# Browse skins sorted by price, then fetch full detail for the first hit.
skin_summary = client.skin_summaries.list(
query="assault", sort=SkinSort.PRICE_DESC, limit=5
).first()
if skin_summary is not None:
skin = skin_summary.details()
print(skin.name, skin.rarity)
for p in skin.prices:
print(f" {p.source}: ${p.price_usd}")
# Navigate to the base item the skin applies to.
if skin.skin_for:
base = client.items.get(slug=skin.skin_for[0].slug)
print(f"Base item: {base.name} — {len(base.craft)} recipe(s)")
# Point lookup by slug when you already know the identifier.
try:
ak = client.items.get(slug="assault-rifle")
print(ak.name, ak.description)
except InputNotFound:
print("Item not found")
# Search returns items and skins together in one call.
result = client.search_results.find(query="rifle")
for s in result.skins[:3]:
print(s.name, s.skin_id)
print("exercised: item_summaries.by_group / skin_summaries.list / skins.get / items.get / search_results.find")
Searches the wiki for items and skins whose names contain the query text. Returns two lists in one round trip: matching items (with the slug accepted by get_item) and matching skins (with the slug accepted by get_skin). Item names are returned as the site shows them in search (English). A query the site has nothing for returns both lists empty with a success status.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Free-text search term matched against item and skin names, e.g. rifle. |
{
"type": "object",
"fields": {
"items": "array of matching game items: name, slug (for get_item), image_url",
"query": "the search term as applied",
"skins": "array of matching skins: name, slug (for get_skin), skin_id (numeric Steam workshop item id as string), image_url"
},
"sample": {
"data": {
"items": [
{
"name": "Assault Rifle",
"slug": "assault-rifle",
"image_url": "https://ru-wiki.rustclash.com/img/items40/rifle.ak.png"
}
],
"query": "rifle",
"skins": [
{
"name": "Crystal Assault Rifle",
"slug": "crystal-assault-rifle",
"skin_id": "10560",
"image_url": "https://ru-wiki.rustclash.com/img/skins/40/10560.png"
}
]
},
"status": "success"
}
}About the RustClash API
Item Data
The get_item endpoint accepts a slug (obtained from search or list_items) and returns a single item's full wiki entry. The stats field is a flat object mapping Russian-language stat labels to display strings — covering values like damage, fire rate, and magazine capacity depending on the item type. The loot array lists every container that drops the item, with condition, amount, and chance_percent per source. The craft array includes full ingredient lists (name, slug, quantity, chance_percent), time_seconds, and workbench_level. The recycle array gives guaranteed and probabilistic output per recycler type, plus efficiency_percent.
Skin Catalogue
list_skins covers the entire skin catalogue (~6,000 skins) and supports client-side pagination via page and per_page (capped at 200 per page). An optional query parameter does case-insensitive substring matching against both the skin name and the Russian base-item name. The sort parameter accepts newest, price_desc, and price_asc. Each skin entry includes price_usd, skin_id (Steam workshop numeric ID), is_new, discount_percent, and image_url.
Skin Detail and Pricing
get_skin returns a skin's full detail: English name, rarity label as stated by the site (or null), a prices array with one entry per source (RustClash.com, Steam Community Market, Rust Item Store), each carrying price_usd (null when unlisted) and a relative updated timestamp. The break_down field lists the Steam inventory items produced by breaking the skin down, with name, slug, and quantity. The skin_for array links back to base items via slugs compatible with get_item.
Search and Browse
The search endpoint accepts a free-text query and returns two parallel arrays — items and skins — in a single call, each with slugs ready for downstream get_item or get_skin calls. list_items accepts a group slug (e.g. weapons) and returns every item in that category without pagination, including each item's Russian display name, kind (item or building), and image_url.
The RustClash API is a managed, monitored endpoint for ru-wiki.rustclash.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when ru-wiki.rustclash.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official ru-wiki.rustclash.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a Rust loadout calculator by pulling weapon stats from
get_item'sstatsmap. - Track Steam Community Market and RustClash.com price spreads for arbitrage using
get_skin'spricesarray. - Populate a crafting cost tool by iterating
craft[].ingredientsfromget_itemfor any weapon or tool. - Index the full skin catalogue with
list_skinsand filter by base item name to show all skins available for a specific weapon. - Display loot-table odds for containers by reading
loot[].chance_percentandloot[].containerfromget_item. - Identify newly listed skins via the
is_newflag anddiscount_percentfield returned bylist_skins. - Build a recycle-yield reference by reading
recycle[].guaranteed_outputandextra_outputfor any scrap-able item.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does ru-wiki.rustclash.com have an official developer API?+
What price sources does `get_skin` return, and are they always populated?+
prices array contains one entry each for RustClash.com, the Steam Community Market, and the Rust Item Store. price_usd is null for any source where the skin is not listed or the price is unavailable. The updated field is a relative timestamp string (e.g. "2 hours ago") or null.What group slugs are valid for `list_items`, and does the API list them?+
weapons, but the API does not currently expose a dedicated endpoint that enumerates all valid group codes. You can discover slugs via search results or site navigation, then fork this API on Parse and revise it to add a group-listing endpoint.Are item names and stat labels returned in English?+
list_items and get_item return Russian-language name, description, and stat labels as shown on ru-wiki.rustclash.com. The search endpoint returns names as the site displays them, which are also Russian. get_skin returns an English skin name. The API does not currently provide translated English labels for item stats or descriptions. You can fork it on Parse and revise it to map labels to English equivalents.