Introduction
Recommend continuously computes the live state of the objects you follow: a calibrated 0–100 score, a verdict, trajectory, the top driver, and the recommended move. The same state your team reads in the Platform is what your agents fetch here.
The base URL for all requests is https://api.recommend.co.
Quickstart
Three steps to your first live-state query.
# create a key in the dashboard, then: export RECOMMEND_API_KEY=rcmd_live_...
curl https://api.recommend.co/v1/objects/demand:facial-spf/state \ -H "Authorization: Bearer $RECOMMEND_API_KEY"
{
"mcpServers": {
"recommend": {
"url": "https://mcp.recommend.co",
"apiKey": "rcmd_..."
}
}
}Authentication
Authenticate every request with a Bearer API key from your dashboard. Keep keys server-side — they grant access to your workspace.
Authorization: Bearer rcmd_...
Objects
An object is the thing you follow — a market or category (managed universe objects, no setup), or something we maintain for you (a custom object like an account or release). Each object is addressed by an id, e.g. demand:facial-spf.
State
Every object resolves to one contract — the exact shape returned by the API and over MCP:
{
"object": "demand:facial-spf",
"state": 73,
"verdict": "watch",
"trajectory": [58, 63, 69, 73],
"driver": "rising search volume + repeat-purchase intent",
"move": "Brief 2 creators before the UV peak",
"settles_on": "purchase window + 14 days",
"calibration": "held 7 of last 10"
}Querying
Read an object’s state with a single GET, or call the same data as a native tool from an agent over MCP. There’s no drift between the two — one object, one state, two consumers.
curl https://api.recommend.co/v1/objects/demand:facial-spf/state \ -H "Authorization: Bearer $RECOMMEND_API_KEY"