The Convexly REST API exposes current evidence surfaces for wallet ratings, Market Trust snapshots, and public track-record summaries. The Decisions API is a legacy surface inherited from an earlier product hypothesis and is in deprecation.
Edge Score API
Jump to reference. Compute the V3b composite from features or end-to-end from a Polymarket wallet address. Auth: Supabase JWT.
https://www.convexly.app/api/engine/edge-score
Market Trust API
Jump to reference. Public v0.1 market-quality cards with evidence counts, caveats, row hashes, links to full card payloads, plus a candidate preview endpoint for canary cards.
/api/market-trust · /api/market-trust/v0.2
Track Record Summary
Jump to reference. Public aggregate status for wallet ratings, Coherence Signals, Market Trust coverage, and caveat language.
https://www.convexly.app/api/track-record/summary
Decisions / Outcomes / Insights API
Legacy surface from the pre-pivot decision-tracking product. Sunsetting 2026-07-29. New integrations should use the Edge Score API. Existing callers will receive a 60-day deprecation notice before removal.
https://www.convexly.app/api/engine/public
https://www.convexly.app/api/engine. The old dedicated API subdomain is not published; do not use it in new integrations.Current · Edge Score API
Uses your Supabase access token (JWT) via the Authorization: Bearer <token> header. NOT the same auth as the legacy Decisions API below; the Edge Score routes do NOT accept X-API-Key. Sign in at convexly.app/login to obtain a session token (or use the Supabase client library with your project credentials). Plan-gated to Researcher and above.
curl -H "Authorization: Bearer <supabase_jwt>" \
https://www.convexly.app/api/engine/edge-score/from-wallet \
-H "Content-Type: application/json" \
-d '{"wallet": "0x..."}'Legacy · Decisions API (X-API-Key)
The decisions API at /api/v1/public/decisions uses X-API-Key header authentication. Generate keys from Settings → API Keys (Researcher tier or higher: Researcher $99/mo, Trader $499/mo, Pro grandfathered, Team $49/seat, or Enterprise custom). This API is in maintenance mode; new integrations should use the Edge Score API above.
curl -H "X-API-Key: cvx_your_api_key_here" \
https://www.convexly.app/api/engine/public/decisionsKeep your credentials secret. Both Supabase JWTs and X-API-Keys grant access to data scoped to your account. If a credential is compromised, rotate it immediately (sign out + back in for JWT; revoke + regenerate for X-API-Key).
The Edge Score API exposes the V3b composite (posture + conviction + discipline) to external callers. The full methodology is published at Edge Score Methodology V1. Two endpoints: compute from precomputed features, or compute end-to-end from a Polymarket wallet address.
The public Market Trust API exposes the same v0.1 daily card artifact used by /market-trust. It is intentionally caveated: pending pillars are listed as pending and unscored, not silently treated as clean evidence. Response-shape version is separate from methodology version:api_versiontracks the envelope; methodology_versiontracks the rating model.
The public track-record summary is a compact status endpoint for Convexly's evidence layer. It reports artifact coverage and caveats; it does not claim mature realized performance before resolved outcomes and matched controls support that wording.
Legacy: Decisions, Outcomes, Insights. The next three sections document the pre-pivot decision-tracking API. Authentication is via X-API-Key, not JWT. This surface is in deprecation and will be removed on 2026-07-29; existing callers receive a 60-day notice before that date. New integrations should use the Edge Score API above.
Key management endpoints use JWT authentication (your Supabase session), not API keys. These are used by the Settings page to manage keys.
Edge Score from a Polymarket wallet
curl -X POST https://www.convexly.app/api/engine/edge-score/from-wallet \
-H "Authorization: Bearer $SUPABASE_JWT" \
-H "Content-Type: application/json" \
-d '{
"wallet_address": "0x56687bf447db6ffa42ffe2204a05edaa20f55839"
}'Legacy: Decisions API
Create a decision
curl -X POST https://www.convexly.app/api/engine/public/decisions \
-H "X-API-Key: cvx_your_key" \
-H "Content-Type: application/json" \
-d '{
"title": "Example decision",
"probability": 0.65,
"best_case": 50000,
"expected_case": 20000,
"worst_case": -10000,
"category": "strategy"
}'List decisions
curl https://www.convexly.app/api/engine/public/decisions?limit=10 \
-H "X-API-Key: cvx_your_key"Record an outcome
curl -X POST https://www.convexly.app/api/engine/public/decisions/{id}/outcome \
-H "X-API-Key: cvx_your_key" \
-H "Content-Type: application/json" \
-d '{"result": "success", "notes": "Shipped on schedule"}'Need help? Manage API keys · Go to Dashboard
OpenAPI JSON will return after the dedicated API subdomain is configured; current working examples use the same-origin engine proxy above.