Prediction-market directory

Evidence history

Browse retained website observations, catalogue snapshots, Git commits, package releases and dependency changes. Source-event dates and collection dates are shown separately.

The Git and registry history was backfilled into the October 2026 collection. An earlier commit or release date does not mean Vultax observed it then. The two catalogue snapshots are mostly unchanged; genuine differences are identified as catalogue changes, without inventing daily business activity.

14,339 matching evidence events. Website and metadata records without a source publication date use their collection date for filtering.

  1. Collected:

    First-party page observed

    This is our dated page observation, not a verified company identity, prediction-market classification, current service-health claim or API benchmark.

  2. Collected:

    First-party page observed

    This is our dated page observation, not a verified company identity, prediction-market classification, current service-health claim or API benchmark.

  3. Collected:

    Unassigned website observation

    https://www.sei.io/

  4. Collected:

    Profile URL in page metadata

    ["https://x.com/seekerlabsai"]

  5. Collected:

    First-party page observed

    This is our dated page observation, not a verified company identity, prediction-market classification, current service-health claim or API benchmark.

  6. Collected:

    Retained homepage researched

    Product research source; retained body SHA-256 e11caa15fc6ab6e79b8dcbf5d4ff0f774ab4a3b0b4d667b138a53d80d0a3e728. Collection is not an assessment or product launch date.

  7. Collected:

    Retained homepage researched

    Product research source; retained body SHA-256 e11caa15fc6ab6e79b8dcbf5d4ff0f774ab4a3b0b4d667b138a53d80d0a3e728. Collection is not an assessment or product launch date.

  8. Collected:

    First-party page observed

    This is our dated page observation, not a verified company identity, prediction-market classification, current service-health claim or API benchmark.

  9. Collected:

    First-party page observed

    This is our dated page observation, not a verified company identity, prediction-market classification, current service-health claim or API benchmark.

  10. Collected:

    First-party page observed

    This is our dated page observation, not a verified company identity, prediction-market classification, current service-health claim or API benchmark.

  11. Collected:

    Operator name in page metadata

    Runtil Technologies Ltd

  12. Collected:

    Founding date in page metadata

    2026-08-06

  13. Collected:

    Location in page metadata

    London, GB

  14. Collected:

    Profile URL in page metadata

    ["https://discord.gg/ufpDKJGku5","https://x.com/runtiler"]

  15. Collected:

    First-party page observed

    This is our dated page observation, not a verified company identity, prediction-market classification, current service-health claim or API benchmark.

  16. Collected:

    Profile URL in page metadata

    ["https://t.me/tryrumor","https://x.com/tryrumor"]

  17. Collected:

    First-party page observed

    This is our dated page observation, not a verified company identity, prediction-market classification, current service-health claim or API benchmark.

  18. Collected:

    First-party page observed

    This is our dated page observation, not a verified company identity, prediction-market classification, current service-health claim or API benchmark.

  19. Collected:

    Retained homepage researched

    Product research source; retained body SHA-256 27634a85155a494960f813e34dd0acd7b597101bd1cf870ede01b835d2fad3dc. Collection is not an assessment or product launch date.

  20. Collected:

    First-party page observed

    This is our dated page observation, not a verified company identity, prediction-market classification, current service-health claim or API benchmark.

  21. Collected:

    First-party page observed

    This is our dated page observation, not a verified company identity, prediction-market classification, current service-health claim or API benchmark.

  22. Collected:

    First-party page observed

    This is our dated page observation, not a verified company identity, prediction-market classification, current service-health claim or API benchmark.

  23. Collected:

    Profile URL in page metadata

    ["https://github.com/joinringo","https://kick.com/joinringo","https://www.linkedin.com/company/join-ringo/","https://www.youtube.com/@joinringo","https://x.com/joinringo"]

  24. Collected:

    Operator name in page metadata

    Ringo Labs, Inc.

  25. Collected:

    Profile URL in page metadata

    ["https://www.predictionmarket.tools/tools/rivomarkets","https://www.reddit.com/r/rivomarkets/"]

  26. Collected:

    Profile URL in page metadata

    ["https://github.com/joinringo","https://kick.com/joinringo","https://www.linkedin.com/company/join-ringo/","https://www.youtube.com/@joinringo","https://x.com/joinringo"]

  27. Collected:

    Operator name in page metadata

    Ringo Labs, Inc.

  28. Collected:

  29. Collected:

    Operator name in page metadata

    Ringo Labs, Inc.

  30. Collected:

    Application category

    SocialNetworkingApplication

  31. Collected:

    Profile URL in page metadata

    ["https://github.com/joinringo","https://kick.com/joinringo","https://www.linkedin.com/company/join-ringo/","https://www.youtube.com/@joinringo","https://x.com/joinringo"]

  32. Collected:

    First-party page observed

    This is our dated page observation, not a verified company identity, prediction-market classification, current service-health claim or API benchmark.

  33. Collected:

  34. Collected:

    Profile URL in page metadata

    ["https://www.predictionmarket.tools/tools/rivomarkets","https://www.reddit.com/r/rivomarkets/"]

  35. Collected:

    Application category

    FinanceApplication

  36. Collected:

    First-party page observed

    This is our dated page observation, not a verified company identity, prediction-market classification, current service-health claim or API benchmark.

  37. Collected:

    Application category

    Sports Analytics Software

  38. Collected:

    Profile URL in page metadata

    ["https://www.instagram.com/rithmm_ai/","https://x.com/rithmm_ai"]

  39. Collected:

    Operating systems

    Web, iOS, Android

  40. Collected:

    First-party page observed

    This is our dated page observation, not a verified company identity, prediction-market classification, current service-health claim or API benchmark.

Historical descriptions and catalogue claims: Kairos contributors, CC BY 4.0. Vultax adds source matching, presentation and factual comparisons. Attribution, licences and coverage.