DASHBOARD //

API Reference

The Cencera Trust Protocol API delivers computable trust for any blockchain entity. All responses are structured Trust Manifold objects — composite score, signals, trajectory, and computation metadata.

Base URL

https://api.cencera.xyz/v1

All endpoints below are relative to this base URL. In development you can call http://localhost:3000/v1, which is internally rewritten to the Next.js route handlers under /api.

Authentication & Access Tiers

All API requests require an API key passed in the Authorization header. Three access tiers are available.

Authorization: Bearer YOUR_API_KEY
TierAuthData AvailableRate Limit
PublicNoneComposite score + lifecycle state only100 req/hr per IP
StandardAPI keyFull Trust Manifold, trajectory, category-level triggersPer-contract SLA
EnterpriseAPI key + contractSignal-level detail, batch screening, webhooks, custom SLAsCustom

Core Endpoints

GET/trustp99 latency < 200ms

Entity Trust Query — returns a full Trust Manifold for any blockchain address + chain combination.

GET /v1/trust?address=0xADDRESS&chain=56

address: EVM address or ENS name
chain: chain ID (56 = BNB Chain, 1 = Ethereum, 137 = Polygon, etc.)
fresh: optional boolean — force fresh scoring run (slower, higher cost)
{
  "composite_score": 82,
  "confidence_level": "High",
  "lifecycle_state": "Active",
  "score_trajectory": [79, 80, 81, 81, 82],
  "score_manifest": { /* signal groups, weights, lookback period */ },
  "contribution_breakdown": { /* per-signal-group % contribution */ },
  "triggered_indicators": ["no_adverse_signals"],
  "model_version": "v2.1.0",
  "computed_at": "2026-03-14T17:38:00Z"
}
GET/transaction-riskp99 latency < 100ms

Pre-transaction risk context for all parties involved. Returns Trust Manifolds for sender, receiver, and contract.

GET /v1/transaction-risk?from=0xFROM&to=0xTO&chain=56
POST/batchp99 latency < 2s · up to 500 entities

Batch Screening — screen up to 500 entities per request. Standard and Enterprise tiers only.

POST /v1/batch
Content-Type: application/json

{
  "chain": "56",
  "addresses": ["0xADDR1", "0xADDR2", /* ... up to 500 */]
}
GET/history

Historical Reputation Query — score trajectory over a user-specified time range.

GET /v1/history?address=0xADDRESS&chain=56&from=2026-01-01&to=2026-03-14
POST/webhooksEnterprise

Score Webhook Registration — proactive push on score or lifecycle state changes. Enterprise tier only.

POST /v1/webhooks
Content-Type: application/json

{
  "address": "0xADDRESS",
  "chain": "56",
  "callback_url": "https://your-server.com/webhook",
  "trigger_on": ["score_change", "lifecycle_change"]
}
POST/loss-report

Loss Report Submission — user-reported losses. Transaction hash verification required. Elevates the associated entity's review priority.

POST /v1/loss-report
Content-Type: application/json

{
  "tx_hash": "0xTRANSACTION_HASH",
  "chain": "56",
  "loss_amount_usd": 5000
}

Cross-Chain Architecture

  • •Scores are chain-scoped by default — Ethereum score is independent from BNB Chain score.
  • •Cross-chain linkages established via cryptographic evidence of address ownership.
  • •Negative signals propagate more strongly across chain links than positive signals — attackers cannot reset reputation by switching chains.
  • •Bridge provenance tracking: funds bridged from low-trust sources carry risk context onto the destination chain.