Convexly Enterprise / Data Room
Pilot diligence, with status labels attached.
This page collects the artifacts an institutional buyer needs before a pilot: API shape, public data samples, methodology receipts, audit-chain evidence, security posture, subprocessors, and commercial report scopes. It also says what is only a sample, what is available on request, and what is still planned.
Artifact health
8
Public live
1
Public sample
3
On request
2
Planned
Status is part of the artifact. A planned SOC 2 packet or pilot report is intentionally not rendered as available evidence.
API and data
API documentation
Current endpoint reference, authentication model, plan gates, and deprecated Decisions API separation.
Claim registry JSON
Machine-readable evidence registry for public claims and receipt state.
Market Trust public JSON
Stable public Market Trust snapshot metadata with evidence-status fields and score waterfall.
The v0.2 endpoint is a separate canary-preview contract. Enterprise feeds require contracted access and freshness SLAs.
Methodology and receipts
V1-M methodology paper
Cross-venue wallet-scoring methodology and Manifold incentive-regime analysis with public data bundle.
Pre-registration manifest
AsPredicted and internal-frozen methodology receipt index, including pending/broken receipt states where applicable.
Audit-chain verifier
SHA-256 evidence chain for research artifacts and Coherence Signal runs.
Security and legal
Security posture
Current hosting, access-control, data-protection, and vulnerability disclosure posture.
Subprocessor list
Vendors used for hosting, database, email, payments, analytics, and optional AI features.
DPA / MSA overview
Contract package for enterprise diligence, including data-processing and commercial terms.
Provided under sales process; not published as a self-serve legal template.
Data-rights appendix
Working packet that separates public venue data, user-authorized imports, partner-restricted data, and internal operational records.
Drafted for diligence; claims about Kalshi/entity coverage must stay scoped to partner or user-authorized data.
SOC 2 packet
SOC 2 readiness package and external audit report once available.
Security page currently labels SOC 2 Type 1/Type 2 as planned; do not imply certification before completion.
Commercial artifacts
Wallet Verification report
Signed wallet-level report for diligence, legal, or compliance review.
Market Quality Audit pilot spec
Planned venue-level audit covering coherence, capacity, slippage, and reproducibility.
Pilot scope and timing depend on validation; the public page is a spec, not a shipped sample report.
Pilot scope template
Design-partner pilot structure for one concrete market-quality or Researcher workflow question.
No SLA, support channel, or commercial commitment exists until written into the approved pilot scope.
The next enterprise gap is external assurance.
Convexly already has reproducible research, public claim registries, hash-chain evidence, and a clear subprocessor list. The remaining diligence work is outside-in: penetration-test summary, formal SOC 2 timeline, enterprise API keys, and contracted freshness/support terms for data products.