Settlement data you can re-derive, and wallet reads that carry their own receipt.
A key-gated feed of settled conditions read from the Polygon blockchain, with a public coverage manifest and a standalone checker that re-derives it against any RPC endpoint you choose. A documented REST API over wallet verdicts, batch verdicts, wallet screens, and reconciled reads, each read carrying a proof-of-record object. Everything named on this page is open in your browser now or documented before you sign.
Settlement feed
One row per ConditionResolution event on the shared ConditionalTokens contract: payout vector, winning outcome index, reporting oracle address, question id, settlement block.
Coverage receipt
The manifest states an event count and content digests per 100,000-block range. A standalone Python checker re-derives them against any Polygon RPC endpoint you choose.
Proof of record
A reconciled wallet read issues a proof-of-record object naming the block it was reconciled at. The API serves it and you keep it.
Researcher is the self-serve individual tier; the sales-led versions exist for institutions that need contracted API access, higher feed quotas, or a methodology partner with reusable evidence.
NDA available. Replies usually within 1-2 business days.
Open these before you talk to us
- Feed documentation
Endpoints, response schema, freshness objective, failure semantics.
- Data catalogue
What each dataset is, how access is gated, and the licence on it.
- Coverage manifest (dated 2026-08-25)
865 block ranges with per-range counts and digests. Raw JSON.
- API reference
Authentication, rate limits, quotas, and key management.
Nothing on this list needs an account, a call, or an NDA.
What is available today
Resolved-markets settlement feed
A queryable feed of settled conditions read from the Polygon blockchain: one row per ConditionResolution event captured on the shared ConditionalTokens contract, carrying the on-chain payout vector, the winning outcome index, the reporting oracle address, the question id, and the settlement block. It is a contract-wide read, not a venue read, and every row carries its oracle so you can partition the stream yourself. Chain-only by default: unless metadata is explicitly requested, a query addresses no venue-derived table at all.
Coverage manifest and checker
The coverage receipt package is public. The manifest states, per 100,000-block range, an event count and content digests over the span the sweep has read, and a standalone checker (Python 3.9 or later, standard library only) re-derives them against any Polygon RPC endpoint you choose. Two sub-floor rescans on unaffiliated endpoints record, window by window, that every block below the declared floor was read empty, with errored reads recorded separately so a refused window cannot pass as an empty one.
REST API
Read-only pilot access over a static API key: wallet verdicts (single and batch), reconciled chain reads with proof-of-record receipts, wallet screens, standing wallet-set management, and the resolved-markets feed. Rate limits and a per-key usage endpoint; keys rotate without resetting their quota.
Enterprise data room
A diligence artifact index for buyers: API documentation, public JSON samples, evidence receipts, security posture, and subprocessors. Engagement-specific materials are provided on request.
Market Trust was frozen on 2026-09-05 and is not sold. No rating from it is offered for purchase, citation, or pilot scoping, and no price on this page buys one.
What the receipts prove, and what they do not
Convexly does not claim to be ready for enterprise use, and the track record page says so plainly. What is offered here is data with a re-derivable receipt attached, not a readiness verdict. The four limits below travel with it.
What the coverage manifest establishes
That the sweep walks contiguously forward from a declared floor block, and that its per-range counts and digests reproduce on an endpoint we do not run. It is not a statement that any venue's markets are all present, and it is not a completeness claim about a wallet.
What a proof-of-record object establishes
That a specific address was reconciled against the chain at a stated block, so a later reader can tell whether the record has moved since. It says nothing about future performance, and a read that cannot be established is refused rather than estimated.
No redistribution rights are granted
Feed rows are derived from the public Polygon blockchain and are served for your own analysis and citation with attribution. No redistribution or sublicence is granted: whether any venue's terms reach data in on-chain and derived form is an unresolved question, and we will not grant onward rights we have not established we hold.
No uptime commitment
There is no uptime percentage on the feed and there will not be one. The path runs through three providers whose targets we do not control, and the operator is one person on active military duty. What exists instead is a measured freshness objective, republished with its measurement, and documented failure semantics.
The feed contract, the schema, and the freshness objective are on the feed documentation page; research filing details live on the preregistration index.
How an engagement works
Every engagement is scoped, contracted, and evidence-linked. The terms below set the security, access, and claim posture buyers can rely on from the first conversation.
Security and support posture
Diligence materials cover subprocessors and our security posture, with an NDA available on request. The Trust Center states which controls are in place today and which are absent. Support terms, rate limits, and data-handling commitments are written into the engagement scope.
API access controls
Enterprise API access is provisioned under contract with defined rate limits, per-key usage metering, and key rotation that does not reset the quota.
Claim discipline
Every number travels with its evidence and its limits. A read that cannot be established is refused rather than estimated, and a published claim that turns out wrong is corrected in public rather than quietly edited.
Scoped first engagement
A focused starting scope: one data question, one delivery, one feedback loop, and a clear decision on whether the artifact saves analyst time.
Who this is for
Hedge funds and prop shops that want settlement data they can check rather than trust. The feed is chain-derived and the coverage receipt reproduces on an endpoint you pick, so the input can be verified before any model is built on it.
Venues that want a reproducible participant-flow review for their own public or permissioned data, with co-branded research only after methodology, data rights, and claim language are agreed.
Research desks at banks, trading firms, or universities that need a citable methodology for studies on forecasting, calibration, or incentive-regime effects on participant behavior. The published Manifold bundle is reproducible as it stands; the Polymarket reference cohort is not published, so ask before you scope a study that depends on it. API access and dated snapshots can be scoped into an enterprise engagement only where the underlying data rights support it. For venue-sourced material that question is open, so ask what is available before you scope around it rather than assuming a snapshot can be licensed to you.
Regulators and legal teams who need an evidence-linked review of public wallet behavior for specific case work, scoped and delivered under an enterprise engagement (signed PDF on Convexly Research letterhead, scoped review window, NDA available).
Start with the methodology, not the sales pitch
The V1-M paper is 19 pages. Read it first. Its data bundle was withheld on 2026-09-04 pending Manifold's written position on data rights, and the Polymarket cohort behind the V1 paper has never been published, so treat both papers as method-disclosed rather than reader-runnable. If the methodology passes your risk committee, the institutional deal is just pipes on top of it.
Ready to talk
Submit the short intake form. Convexly Research replies usually within 1-2 business days with a 30-minute call slot and any NDA you need to open deeper conversations.
Request scoping