Reliability for contractors and vendors

The problem

Vendor performance lives in spreadsheets, inboxes and the memory of whoever managed the last contract. When they leave, the signal leaves with them.

Procurement decisions therefore get made on the most recent anecdote rather than on the record.

And when a number does exist, nobody can say what moved it, so nobody trusts it enough to act on.

The solution

• Report each engagement outcome as it completes, with an Idempotency-Key derived from your own purchase order. Retry logic can fire as often as it likes; the ledger records the event once.
• Stake level and transaction value are part of the event, so a delivered six-figure contract does not weigh the same as a small one.
• Ask the API what changed and why: the delta endpoint names the factor that moved most, and the same reason rides along on the webhook.
• Advisory risk signals flag concentration and velocity patterns for a human to look at. By design they never touch the score.

How it works

The API calls involved

• POST/api/v1/eventsReport one outcome. Idempotency-Key header makes the write exactly-once.
• POST/api/v1/events/batchUp to 100 events per call, partial success, per-item idempotency.
• GET/api/v1/users/{id}/score/deltaWhat changed since the previous computation, and which factor drove it.
• GET/api/v1/users/{id}/score/historyCursor-paginated score history.
• GET/api/v1/users/{id}/timelineUnified, cursor-paginated feed of events and score changes.
• POST/api/v1/users/{id}/score/projectWhat-if preview before you report. Writes nothing.
• GET/api/v1/users/{id}/riskAdvisory anti-gaming signals. Never affects the score.

$ curl -X POST https://api.credda.io/api/v1/events \
    -H "Authorization: Bearer $CREDDA_API_KEY" \
    -H "Idempotency-Key: po-2210-delivered" \
    -H "Content-Type: application/json" \
    -d '{"userId":"vendor_17","eventType":"CONTRACT_FULFILLED",
         "stakeLevel":"HIGH","isVerified":true,"transactionValue":12000}'

$ curl https://api.credda.io/api/v1/users/vendor_17/score/delta \
    -H "Authorization: Bearer $CREDDA_API_KEY"
{ "scoreDelta": 1.8, "direction": "up",
  "topDriver": { "factor": "OTR", "improved": true } }

Full request and response shapes are in the API reference.

Start building