Discover/decomp API
live

decomp APIdecomp.me

Access decomp.me decompilation projects, user contributions, and site statistics via 4 endpoints. Retrieve scratch details, source code, compiler flags, and scores.

Endpoint health
verified 16h ago
get_scratch_detail
get_recent_scratches
get_user_contributions
get_stats
4/4 passing latest checkself-healing
Endpoints
4
Updated
26d ago

What is the decomp API?

The decomp.me API exposes 4 endpoints for querying decompilation scratch projects, user contributions, and site-wide statistics on decomp.me. The get_scratch_detail endpoint returns full project data including C source code, compiler flags, target platform, match score, and version family history — giving programmatic access to the same data visible on individual scratch pages.

Try it
Opaque pagination cursor for fetching subsequent pages.
Sort order for results.
Filter for scratches with a registered owner. Accepted values: 'true', 'false'.
Number of results per page.
api.parse.bot/scraper/28e2a231-d752-4389-890d-c31ca235a587/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/28e2a231-d752-4389-890d-c31ca235a587/get_recent_scratches?ordering=-creation_time&has_owner=true&page_size=5' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

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 decomp-me-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.

from parse_apis.decomp_me_api import DecompMe, ScratchOrdering

client = DecompMe()

# Get site-wide statistics
stats = client.statses.get()
print(stats.scratch_count, stats.asm_count, stats.github_user_count)

# Browse recent scratches sorted by newest first
for scratch in client.scratchsummaries.list_recent(ordering=ScratchOrdering.NEWEST, page_size="5", limit=5):
    print(scratch.slug, scratch.name, scratch.platform, scratch.score, scratch.max_score)
    # Drill into full details for the first one
    detail = scratch.details()
    print(detail.source_code[:80], detail.compiler_flags, detail.language)
    break

# Look up a specific user's contributions
user = client.user(username="sonicdcer")
for contrib in user.contributions(ordering=ScratchOrdering.RECENTLY_UPDATED, limit=3):
    print(contrib.slug, contrib.name, contrib.compiler, contrib.creation_time)
All endpoints · 4 totalmissing one? ·

Retrieve the latest decompilation projects and site activity. Returns a paginated list of scratch projects sorted by the specified ordering. Each result is a summary containing slug, owner, name, platform, compiler, score, and timestamps. Paginates via cursor.

Input
ParamTypeDescription
cursorstringOpaque pagination cursor for fetching subsequent pages.
orderingstringSort order for results.
has_ownerstringFilter for scratches with a registered owner. Accepted values: 'true', 'false'.
page_sizestringNumber of results per page.
Response
{
  "type": "object",
  "fields": {
    "next": "string or null, cursor URL for next page of results",
    "results": "array of ScratchSummary objects",
    "previous": "string or null, cursor URL for previous page of results"
  },
  "sample": {
    "data": {
      "next": "https://decomp.me/api/scratch?cursor=cD0yMDI2LTA2LTEwKzIwJTNBMTAlM0EyOC4zOTUyMDElMkIwMCUzQTAw&has_owner=true&ordering=-creation_time&page_size=5",
      "results": [
        {
          "name": "func_8009D2B0",
          "slug": "ypP2f",
          "owner": {
            "id": 8750703,
            "is_admin": false,
            "username": "roengstrom",
            "github_id": 26772201,
            "is_online": true,
            "is_anonymous": false
          },
          "score": 2425,
          "parent": null,
          "preset": null,
          "compiler": "gcc2.7.2-cdk",
          "platform": "ps1",
          "best_fork": null,
          "libraries": [],
          "max_score": 28700,
          "last_updated": "2026-06-11T05:33:12.816621+09:00",
          "creation_time": "2026-06-11T05:32:52.091966+09:00",
          "match_override": false
        }
      ],
      "previous": null
    },
    "status": "success"
  }
}

About the decomp API

Endpoints and Data Coverage

The API covers four areas of decomp.me. get_recent_scratches returns a paginated list of scratch projects sortable by -creation_time or -last_updated, with optional filtering by whether a scratch has a registered owner via the has_owner parameter. Each result includes the scratch slug, owner, name, platform, compiler, score, max_score, creation_time, and last_updated. The page_size parameter controls how many results appear per page.

Scratch Detail

get_scratch_detail accepts a slug (obtainable from get_recent_scratches results) and returns the complete record for that project: the source_code string containing the C decompilation attempt, the context header used for compilation, the compiler identifier, the platform tag (e.g. n64, gc_wii), and a family array listing related scratch version summaries. The score and max_score integers together indicate how closely the compiled output matches the target assembly.

User Contributions and Site Stats

get_user_contributions takes a GitHub/decomp.me username and returns that user's scratch projects in the same paginated format as get_recent_scratches, with the same ordering and page_size controls. get_stats requires no parameters and returns three site-wide counters: asm_count (total assembly instructions across all scratches), scratch_count (total projects), and github_user_count (registered users). These are useful for tracking platform growth over time.

Reliability & maintenanceVerified

The decomp API is a managed, monitored endpoint for decomp.me — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when decomp.me 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 decomp.me 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.

Last verified
16h ago
Latest check
4/4 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Monitor newly created or recently updated decompilation scratches using get_recent_scratches with -last_updated ordering.
  • Build a leaderboard by collecting score and max_score fields from multiple scratches to rank contributors by match quality.
  • Audit a specific contributor's output by fetching all their scratches via get_user_contributions with their GitHub username.
  • Diff decompilation approaches across related scratch versions using the family array returned by get_scratch_detail.
  • Track platform-specific activity by filtering get_recent_scratches results by the platform field (e.g. n64, gc_wii).
  • Aggregate site growth metrics over time by polling get_stats for changes in scratch_count and github_user_count.
  • Extract C source code and compiler context from a scratch using source_code and context fields for offline analysis.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo1005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min

One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does decomp.me have an official developer API?+
decomp.me exposes a public API documented at https://decomp.me/api — it covers scratches, users, and compiler listings. The Parse API surfaces a practical subset of that data focused on recent activity, scratch details, user contributions, and site statistics.
What does `get_scratch_detail` return beyond what the list endpoints show?+
get_scratch_detail adds four fields not present in list results: source_code (the full C decompilation text), context (the C header context passed to the compiler), the family array of related scratch version summaries, and the compiler string. The list endpoints only carry summary fields like slug, name, score, max_score, platform, and timestamps.
Can I filter scratches by platform or compiler?+
Not directly via a query parameter. get_recent_scratches supports filtering by has_owner and sorting by ordering, but platform and compiler filtering is not exposed as a parameter. You can retrieve paginated results and filter on platform or compiler client-side using the fields present in each result object. You can also fork this API on Parse and revise it to add a platform or compiler filter endpoint.
Is assembly output or diff data available from the API?+
Not currently. The API returns source_code (C source), context, score, and max_score, but does not expose the compiled assembly output or the line-by-line diff between the attempt and the target. You can fork this API on Parse and revise it to add an endpoint that surfaces assembly diff data if decomp.me exposes it via their public API.
How fresh is the data returned by these endpoints?+
Results reflect the current state of decomp.me at request time. get_recent_scratches sorted by -last_updated returns projects in the order they were most recently edited, so the freshness of any given scratch depends on when its author last saved changes. There is no delta or webhook mechanism — callers need to poll periodically to detect updates.
Page content last updated . Spec covers 4 endpoints from decomp.me.
Related APIs in Developer ToolsSee all →
crash.pmmp.io API
Search and browse crash reports for PocketMine-MP, view detailed information about specific crashes, and submit new crash reports to the archive. Keep your server stable by accessing a centralized database of known issues and their solutions.
deepwiki.com API
Search and retrieve documentation for any GitHub repository indexed on DeepWiki, including wiki pages, table of contents, and source file references in markdown format. Look up repository profiles, discover featured projects, and access complete wiki content all in one place.
codechef.com API
Access competitive programming data from CodeChef by retrieving problem lists, contest information with details, user profiles, and recent submission history. Explore coding challenges across multiple contests and browse problems by difficulty rating.
protondb.com API
Search for game compatibility information and check how well games run on Linux and Steam Deck, including user reports, performance statistics, and official verification status. Explore detailed game data, platform analytics, and community feedback to evaluate compatibility across titles.
thunderstore.io API
Browse and search thousands of mods across Thunderstore gaming communities. Retrieve mod metadata, version history, dependencies, download URLs, and decompiled source code files for any listed mod.
dumpspace.spuckwaffel.com API
Access detailed technical data for Unreal Engine and Unity games, including class structures, functions, enums, memory offsets, and inheritance hierarchies to support reverse engineering and modding projects. Search across thousands of game dumps to find specific classes, structs, and functions along with their documentation and offset information.
curseforge.com API
Search and explore CurseForge game mods and projects, retrieve detailed information about specific mods, access file listings and versions, and track dependencies between projects. Find mods across different games and categories to discover exactly what you need for your gaming setup.
openclipart.org API
Search and discover clipart from OpenClipart, explore collections by tag, and retrieve detailed metadata including artist profiles, engagement metrics, and download URLs. Also exposes site-wide statistics such as total clipart count, artist count, and recent upload activity.