CronusMarket methodology: how we track prices and status

Every number on CronusMarket was read from a live vendor page or a publisher's patch notes by a person, and carries the date it was read. We record prices as displayed, assign one of four status labels from what the page says, list every vendor we can find on the same template, exclude anything we cannot read, and take no money from anyone we list. This post explains each of those rules.

What do we collect?

For each product: name, vendor, game, one-line description, feature list as the vendor words it, platforms, billing term, every storefront selling it with the price displayed there, the vendor's compare-at or regular price if shown, a status label, a date checked and the source URL.

For each vendor: name, site, checkout platform, what they sell, and a factual Notes section drawn from what their pages say and what we could not verify.

For each game: the current patch or season, its date, a source link, and a note on what changed.

The launch dataset covers 25 vendors, 55 products and 66 offers (48 with a readable price) across 12 game catalogs plus a script-libraries catalog, checked on Sep 2, 2026.

How are prices recorded?

We record the price a buyer would see on the page, in the currency shown (all USD at launch), with the billing term. If the page shows a struck-through higher figure, we record it as the vendor's regular or compare-at price and display it as such; we never treat it as a price someone paid. If the price is inside an embedded checkout widget or otherwise not readable in the page text, we record no price and the product shows "See vendor page". Unpriced products are excluded from lowest-price calculations, price gaps and best-value rankings.

Aggregator "value" labels (a dollar figure printed on a library page that is not a checkout) are recorded in the notes and never as a price.

Each check adds a point to the product's price history. At launch every product has one point.

What does each status mean?

• Updated: the vendor's page explicitly states support for the current title, patch or season as of the check date. We record the claim; we do not run the script.
• Awaiting update: the listing targets a superseded title or season (a 2K26 build after 2K27 launched; an S29 label during S30) and the vendor has not stated current support.
• Enforcement risk: the platform holder publicly enforces against Cronus-class devices in this game. At launch that is Epic for Fortnite and Activision for Call of Duty, each with a linked source. This is a game-level flag and overrides the other labels for every product in that game.
• Unknown: no current-support claim was visible on the page we checked.

The status board lists these definitions and the current patch or season per game with sources.

How do vendors get listed?

We list every vendor we can find selling a Cronus Zen script for a game we cover, including aggregators, resellers and vendors whose authorization we could not verify, on the same template with the same tone. Vendors do not apply to be listed and cannot opt out of factual listing. A vendor can request a correction or a new listing by emailing listings@cronusmarket.com with public URLs; we check the live page and update with a new date.

We do not accept screenshots, Discord messages or private communications as evidence of a price or a claim. If it is not on a public page, it is not on this site.

How do we handle vendors and claims we cannot verify?

We say so, in the Notes section, using the vendor's own words where possible and the phrase "we could not verify" where not. Examples from the launch dataset:

• A reseller offering many creators' named scripts at a flat price whose disclaimer describes summarizing "supplied script files": listed, with the note that creator authorization was not verified, and not shown as an offer on the creator's product.
• A Discord promising access to several premium scripts for a monthly fee: listed, with the note that authorization was not verified and that one named creator states no redistribution source is authorized.
• A product page crediting builders who are also connected to another vendor: noted as stated on the page, without asserting a corporate relationship.
• Review counts and ratings: reported as claims, not verified.

We describe; we do not accuse. Where the appropriate word is "appears", we use it.

What do we not do?

• We do not test scripts, and we do not report detection rates.
• We never describe a script or device as beyond detection, and we flag vendors who do.
• We do not accept payment for listings, rankings, placements or reviews.
• We do not use affiliate links or tracking parameters. Every outbound link is the plain URL.
• We do not describe bypass methods for platform enforcement.
• We do not treat any vendor differently from any other. Vendors connected to each other by shared builders or shared storefront technology are listed separately, on the same template, with the connection noted only where a public page states it.

How is the site sorted and ranked?

Catalog pages sort by status (Updated first) and then by lowest price. The home page's price-gap board is computed from products with two or more priced offers on the same term. The best-value board takes the cheapest Updated product per game. None of this is editable by hand; changing a price in the dataset changes the boards.

How often do we recheck?

Manually, as often as the desk can, with priority on the days after a patch or season launch: for the current cycle, Sep 3 (Fortnite v42.10), Sep 4 (NBA 2K27 worldwide launch), around Sep 17 (Call of Duty Season 06) and Oct 16 (NBA 2K27 Season 2). Every product page shows the date of its last check, and the public dataset at /api/status.json carries the same dates.

What is the public dataset?

Everything on the product, vendor and status pages is available at /api/status.json, cached for an hour, in the same schema the site renders from. It is free to read. If you build on it, link back to the product page so readers can see the date and source.

How to correct us

Email desk@cronusmarket.com with the URL of the page on this site, the URL of the public page that shows the correction, and what changed. We update the dataset, add a new date, and the price history records the change. If we were wrong, the page will say so.