Editorial methodology

A product is eligible when prediction markets are a primary use case or a clearly supported workflow. This includes market interfaces, discovery and research tools, analytics, alerts, portfolio products, developer infrastructure and automation.

General-purpose products are included only when their prediction market capability is documented and meaningfully usable. Inactive, unverifiable, deceptive or purely promotional pages are excluded.

We prefer the product’s official website, documentation, pricing page, application interface, developer references and official announcements. Reputable secondary reporting may add context but does not replace a first-party source for a product claim.

Community posts and social media can identify a candidate or a recent change. They are treated as leads unless the account is demonstrably official and the claim is sufficiently specific.

An editor checks the official domain, core product description, access status, supported platforms, pricing representation and relevant prediction market workflows. Source links and the date of the review are stored with the profile.

Publication requires a stable identity, at least one working authoritative source and enough evidence to describe the product without inference presented as fact.

PredAtlas uses consistent fields so readers can compare products without translating marketing language. When a value is not publicly documented, we use an explicit unknown or qualified description instead of guessing.

Descriptions are written in our own words. A product’s self-description may inform the profile, but it is not automatically adopted as an editorial conclusion.

Availability labels describe what an editor could verify at review time. A live marketing page does not necessarily mean that registration, data access or every feature is available.

Waitlists, invitation requirements, regional limits and account or wallet prerequisites are recorded when material and publicly documented.

Each tool receives one primary category and may be mapped to multiple user tasks. Assignments reflect the product’s documented function, not its branding.

General lists may be ordered by name, verification date or addition date. Use-case pages may apply editorial relevance. Neither placement nor appearance constitutes a rating, endorsement or estimate of investment performance.

Automated checks can identify unreachable sources or unusual changes, but they do not publish material edits on their own. Significant facts are manually reviewed before a profile is updated.

Readers and product teams can report changes through the submission form. Corrections are evaluated against the same source standard as initial publication.

A profile is published only when required identity, description, classification, source and verification fields are complete. Editorial status is separate from source health, so a temporary outage does not silently rewrite a profile.

This methodology may evolve as the market changes. Material revisions are dated on this page.

PredAtlas publishes a concise discovery map, a full catalog context file and a versioned bilingual JSON catalog. These exports use the same publication gate as the visible HTML profiles and never include unpublished records.

When citing a PredAtlas conclusion, use the canonical profile URL and preserve its review date and limitations. For a provider’s own product claim, cite the first-party evidence URL listed in the profile. Machine-readable exports are retrieval aids, not a substitute for checking current official terms.