Use the API when you need Convexly evidence inside another workflow: Market Trust labels, wallet-quality diagnostics, track-record status, and caveats that can travel with an internal memo or product surface.
Market price
Read Market Trust cards and preview v0.2 fields with evidence counts, caveats, and row hashes.
Wallet
Use Edge Score routes for wallet diagnostics and feature-derived scoring.
Proof
Use track-record summaries to keep modeled signals separate from resolved outcomes.
Edge Score API
Jump to reference. Compute the Edge Score 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
Wallet Verdict API
Jump to reference. Four-state skill verdict (skilled / luck / insufficient / flagged) for one wallet or a tier-capped batch. Auth: X-API-Key.
https://www.convexly.app/api/engine/public/wallets
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. 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_address": "0x..."}'Current · Wallet Verdict API
Uses the X-API-Key header: single and batch four-state skill verdicts for a Polymarket wallet. See the Wallet Verdict reference for full paths, batch caps, and daily quotas. Same plan requirement as Edge Score above (Researcher tier or higher).
curl -H "X-API-Key: cvx_your_api_key_here" \
"https://www.convexly.app/api/engine/public/wallets/0x56687bf447db6ffa42ffe2204a05edaa20f55839/verdict"Keep 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).
GET /public/usage reports the calling key's wallet-read consumption for the current UTC day: plan, wallets used, cap, and remaining. It costs no quota, and the number it reports is read from the same counter that enforces the cap, so the two can never disagree.
curl -H "X-API-Key: cvx_your_api_key_here" \
"https://www.convexly.app/api/engine/public/usage"
# {"plan":"researcher","usage_date":"2026-08-14",
# "wallets_used":3,"wallets_cap":200,"wallets_remaining":197}The Edge Score API exposes the Edge Score 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.
The Wallet Verdict API returns the four-state skill-badge machine (skilled / luck / insufficient / flagged) for a Polymarket wallet, with the realized edge always paired to its BCa bootstrap 95% interval in the same object. This is a different surface from the Edge Score composite above: same kind of input (a wallet address), different math, different response shape. Authentication is X-API-Key, not JWT.
Your plan does not buy a number of reads; it buys a bounded set of distinct wallets that Convexly keeps current on a per-tier cadence. These three endpoints make that set fully self-service over the API (previously available only from the dashboard): add a wallet, list your set with each member's lifecycle and staleness, and remove one. Once a wallet is in your set, read its on-chain-reconciled full-history read with the sibling GET /wallets/{address}/reconciled-read endpoint documented below. Authentication is X-API-Key, same as Wallet Verdict 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"
}'Wallet skill verdict (X-API-Key)
curl https://www.convexly.app/api/engine/public/wallets/0x56687bf447db6ffa42ffe2204a05edaa20f55839/verdict \
-H "X-API-Key: cvx_your_key"Need help? Manage API keys · Go to Dashboard
Machine-readable spec: the X-API-Key surface (Wallet Verdict and the other key-authenticated public routes) publishes an OpenAPI 3 document at convexly.app/openapi.json, generated from the FastAPI schema and checked in CI against drift from the code.