Prediction feed
Daily BUY, HOLD, TAKE, and SKIP signals with horizon, confidence, price band, and anchor close. One object per asset, every market day.
Capwise API · Private developer preview
Build with the same signals Capwise uses.
One clean API for daily market predictions, calibrated price bands, and the outcome record behind every call.
BUY NOWHOLD TIGHTTAKE PROFITSKIP IT
Daily before the US openAdjusted-close bandsTrack record stays visible
6Forecast horizons
4Signal states
36Champion models
What developers get
Market calls as infrastructure, not screenshots.
The first developer program is meant for teams building investing, research, alerting, and portfolio workflows where users need a clear signal and a visible trust trail.
Model context
Versioned outputs, feature-spec hashes, quantile crossing flags, and plain-English rationale when available. No black box.
Outcome history
Resolved calls with realized price, band hit, direction hit, miss size, and rolling calibration metrics. Trust is visible.
Private API
A clean signal layer for apps, agents, and dashboards.
We are using the waitlist to decide which endpoints and rate limits matter first. The shape below is the intended private beta surface, not a public contract yet.
GET
/v1/predictions/latestLatest signal and price band for one symbol or a watchlist.
GET
/v1/markets/feedFiltered market feed by asset class, signal, horizon, or conviction.
GET
/v1/outcomesPrediction outcomes for audits, dashboards, and model trust views.
POST
/v1/webhooksSignal flip and daily digest events for apps that need push workflows.
example request
curl https://api.capwise.ai/v1/predictions/latest \
-H "Authorization: Bearer $CAPWISE_API_KEY" \
-G \
--data-urlencode "symbol=NVDA" \
--data-urlencode "horizon=24h"typescript sdk
import { Capwise } from "@capwise/sdk";
const capwise = new Capwise({
apiKey: process.env.CAPWISE_API_KEY,
});
const signal = await capwise.predictions.latest({
symbol: "AAPL",
horizon: "1w",
});
console.log(signal.verdict, signal.priceBand);SDK direction
Typed clients for teams that want to ship quickly.
The SDK should keep the boring parts small: auth headers, response typing, batching, webhook verification, and stable adapters for prediction and outcome objects.
- Typed TypeScript responses for predictions, outcomes, and ticker search.
- Batch helpers that keep watchlist calls fast without custom pagination glue.
- Webhook signature verification for signal flips and daily market digests.
Developer waitlist
Help decide what Capwise exposes first.
We are collecting interest before opening API keys. Tell us whether you care most about raw prediction access, SDK ergonomics, webhooks, or historical outcomes.
Private by defaultNo broker credentials, no order placement, no user trading actions.
Trust visibleModel version, horizon, price band, and outcome fields stay part of the payload.
Built for real productsConsumer apps, dashboards, agents, research tools, and alerting workflows.
Honest answers
The questions developers ask first.
Is this a brokerage or trading API?
No. Capwise is read-only research data. We deliver signals, price bands, and outcomes. We never touch accounts, balances, or order flow.
How fresh is the data?
Predictions update daily after the US market close, with crypto updating on its own UTC cycle. Outcomes resolve once each target horizon passes.
What assets are covered?
US stocks and ETFs, TSX names, and top crypto. New tickers can be requested through the same pipeline the consumer app uses.
Will there be rate limits?
Yes, but the waitlist is helping us decide the right tiers. Early developer partners will get enough headroom to build and test.
Come in early. Help shape the API.
The developer program starts with the same daily predictions the consumer product uses. Your feedback will decide which endpoints, SDKs, and webhooks ship first.