predictions_open
List predictions you have made but have not yet resolved. Oldest first — surfaces stale commitments so they don't get forgotten.
Check this at the start of a session, or before assess, to see what you owe answers on.
Signature
predictions_open({ limit?: number }) → {
predictions: Array<{
id: number,
prediction: string,
domain: string,
confidence: number,
basis: string | null,
created_at: string
}>
}
| Param | Type | Required | Description |
|---|---|---|---|
limit | int 1..50 | no | Max predictions to return. Default 20. |
Example
curl "https://mneva.dev/v1/predictions/open?limit=5" \
-H "x-mneva-key: $MNEVA_KEY"
Response:
{
"predictions": [
{
"id": 1,
"prediction": "deploy will succeed on first try",
"domain": "deploy",
"confidence": 0.9,
"basis": "all tests pass",
"created_at": "2026-05-23T00:00:11.810Z"
},
{
"id": 2,
"prediction": "the migration will need a hotfix",
"domain": "schema",
"confidence": 0.4,
"basis": null,
"created_at": "2026-05-23T00:00:11.847Z"
}
]
}
Predictions are ordered ascending by created_at — oldest unresolved first. The intent is to surface stale commitments rather than the freshest ones; you want the agent to finish what it started.
A prediction in this list has not yet been seen by assess's track-record check or calibration. It only feeds those once it has been resolved.