Beliefs endpoints

POST /v1/believe

Assert a belief. See believe.

curl -X POST https://mneva.dev/v1/believe \
  -H "x-mneva-key: $MNEVA_KEY" \
  -H "content-type: application/json" \
  -d '{"text":"<belief>","confidence":0.7}'

Response:

{ "id": 1, "text": "...", "confidence": 0.7 }

confidence is optional, default 0.7, clamped to [0.05, 0.95].

POST /v1/revise

Supersede a belief manually. See revise.

curl -X POST https://mneva.dev/v1/revise \
  -H "x-mneva-key: $MNEVA_KEY" \
  -H "content-type: application/json" \
  -d '{"belief_id":12,"new_text":"<corrected>","confidence":0.9}'

Response:

{ "revised_from": 12, "new_belief_id": 18, "text": "..." }

Errors: 404 belief X not found, belief X belongs to another project, belief X was already revised.

POST /v1/evidence

Record one supporting or refuting observation. See evidence and the SPRT concept.

curl -X POST https://mneva.dev/v1/evidence \
  -H "x-mneva-key: $MNEVA_KEY" \
  -H "content-type: application/json" \
  -d '{
    "belief_id": 1,
    "kind": "refuting",
    "strength": 0.85,
    "note": "<what was observed>"
  }'
FieldTypeRequiredDefault
belief_idintyes
kindsupporting | refutingyes
strengthnumber 0.1..0.9yes
notestringnonull

Response includes: evidence_id, belief_id, kind, strength, log_likelihood, new_log_ratio, new_confidence, confidence_delta, status (one of accumulating / promoted / demoted), and boundaries. See evidence for the full schema and a worked example.

GET /v1/evidence/:id

Read the audit trail for one belief. See evidence_for.

curl "https://mneva.dev/v1/evidence/1" -H "x-mneva-key: $MNEVA_KEY"

Response shape:

{
  "belief": { "id": 1, "text": "...", "confidence": 0.4, "sprt_log_ratio": -5.2, "evidence_count": 3, "sprt_status": "demoted", "last_evidence_at": "..." },
  "events": [
    { "id": 1, "kind": "refuting", "strength": 0.85, "log_likelihood": -1.7346, "note": "...", "created_at": "..." }
  ]
}

GET /v1/beliefs

List current (non-superseded) beliefs. See Beliefs.

Was this page helpful?