Sato Hub
API / SDK

PMXT

Open-source unified prediction-market API with a hosted MCP: market search, events, order books, and prices across venues.

  • Sato Score77
  • ChainsMultichain
ActiveSelf-ReportedActive · 14d ago

PMXT is an open-source API or SDK by pmxt-dev, with last code activity on 2026-09-30 (Active). Latest release on 2026-07-18. Sato Score 77/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-14. How the score works →

See how to install PMXT →

Last commit Sep 30, 2026 · Last release Jul 18, 2026 (v2.54.0f) · ★ 2,167

Listed from github.com/pmxt-dev/pmxt on 2026-07-13. Install: reproduced by Sato Hub on 2026-07-21. Evidence →

Next step

Watch PMXT

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on pmxt-dev/pmxt before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

PMXT is an open-source unified API over prediction markets, exposing market search, events, order books, and pricing through one interface, with a hosted MCP endpoint (api.pmxt.dev/mcp) and a local @pmxt/mcp package. An agent builder plugs it in to give an agent cross-venue prediction-market data without integrating each market's API separately.

Sato Score

77/100· High

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
35/35
Code transparency
20/20
Interface verifiability
8/10
Docs & demo
0/10
Listing transparency & provenance
11/15
Independent verification
3/10

Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).

Sato Check

v2.54.0 · as of 2026-09-26
Does it take your key?
No key read found
Does your key leave?
Not observed
Can it move funds on its own?
Unknown
Full profile, evidence and limits →

A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".

Evidence — listed vs checked · what the words mean

Listed from github.com/pmxt-dev/pmxt on 2026-07-13. Install: reproduced by Sato Hub on 2026-07-21.

ClaimValueEvidenceSourceChecked
Chains supportedMultichainself-reportedgithub.com/pmxt-dev/pmxtas of 2026-10-14
Verification statusSelf-Reported — not independently reviewedself-reportedgithub.com/pmxt-dev/pmxtas of 2026-10-14
Recent activitylast release 2026-07-18 · last commit 2026-09-30observedgithub.com/pmxt-dev/pmxt2026-10-14
Install worksreproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour✓ reproducedgithub.com/pmxt-dev/pmxt2026-07-21
Website answersanswered (HTTP 200)observedgithub.com/pmxt-dev/pmxt2026-10-14
Daily check record90 of 90 daily checks since 2026-07-16 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-13
Takes your keyno private-key read found in what we readtracedsatohub.ai2026-09-26
Key leaves the machinenot observed during install and start-uplater or triggered code paths are not coveredobservedsatohub.ai2026-09-26
Moves funds on its ownunknown — could not read what it exposestracedsatohub.ai2026-09-26
Deploys asHosted, Self-hostedconfidence 0.90self-reportedgithub.com/pmxt-dev/pmxtas of 2026-09-27
Works withClaude, Cursor, MCPconfidence 0.85self-reportedgithub.com/pmxt-dev/pmxtas of 2026-09-27
Sato Score77/100 (High)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-14

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — reproduced in a container Jul 21, 2026

Runtime: node

npx -y @pmxt/mcp
See github.com/pmxt-dev/pmxt-mcp for Claude/Cursor MCP client config.

You supply: pmxt_api_key + wallet_address (pmxt.dev/dashboard) for read access, private_key additionally required for trade execution — the SDK auto-wraps it into an EIP-712 signer, so treat as a hot-wallet key

Add to CursorAdd to VS Code
claude mcp add satohub-pmxt -- npx -y @pmxt/mcp

A local server: your client runs this command on your machine. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.

Read from the project’s own docs as of 2026-07-21. What a deploy spec is →

Observed record — 90 daily checks since 2026-07-17

100%of 90 checks since 2026-07-17 succeeded
Currently responding for 90 days
Succeeded
90
Failed
0
Their error
0
Unattributed
0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-14, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
77
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Multichain
Agent types
MCP Server, Data Provider
Open source
Yes
Deploys as
Hosted, Self-hosted
Works with
Claude, Cursor, MCP
Last checked
2026-10-14

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#prediction-markets#market-data#order-books#api#mcp
See something inaccurate or outdated?Submit a correction →

Recent Activity

All news →

Releases and posts from PMXT, pulled from its GitHub and X.

Listing History

Recorded changes to PMXT's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Oct 4, 2026
    Sato Score tier: Medium → High
    Score 67 → 77.
  2. Sep 27, 2026
    Auto-enriched: deployment options, supported integrations
  3. Aug 17, 2026
    Sato Score tier: High → Medium
    Score 70 → 60.
  4. Jul 21, 2026
    Verified: deploy spec
  5. Jul 20, 2026
    Sato Score tier: Medium → High
    Score 62 → 70.
  6. Jul 18, 2026
    New release published
  7. Jul 17, 2026
    Sato Hub began tracking this listing
  8. Jul 14, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about PMXT

Is PMXT open source?
Yes. PMXT is open source under the MIT license; the repository is https://github.com/pmxt-dev/pmxt. Checked as of 2026-10-14.
Which chains does PMXT support?
PMXT lists support for Multichain as of 2026-10-14.
Is PMXT still maintained?
The most recent code activity Sato Hub observed was on 2026-09-30 (last commit 2026-09-30, last release 2026-07-18), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run PMXT?
node. Install: npx -y @pmxt/mcp. Entry: See github.com/pmxt-dev/pmxt-mcp for Claude/Cursor MCP client config.. Sato Hub reproduced this install in a container on 2026-07-21. It runs as an MCP server (npx -y @pmxt/mcp).
Is PMXT verified on Sato Hub?
Sato Hub holds one earned check for PMXT: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 77 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "PMXT — Sato Hub." Sato Hub, updated 2026-10-14, accessed 2026-10-15. https://satohub.ai/resources/pmxt

Data last refreshed 2026-10-14; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.