API Reference
HTTP endpoints backed by the same analysis engine that powers the Cencera dashboard.
Base URL
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
During the MVP the API is tied to your connected wallet and credit balance. Requests should include both an API key header and your wallet address as a user query parameter.
API keys are created from the Cencera dashboard under Dashboard → API Keys. The user parameter must be the EVM address that owns the credits used for deductions.
Wallet and contract analysis
/analyzeRun the full chain analysis pipeline for a wallet, contract address, or ENS name.
GET /v1/analyze?q=vitalik.eth&chain=1&user=0xYOURWALLET
q: search query (address, ENS, token symbol)
chain: optional chain id (default 1 for Ethereum)
user: required wallet address for credit deduction{
"address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
"type": "wallet",
"trust_score": 94,
"risk_level": "low",
"risk_flags": ["airdrop_hunter"],
"summary": "High reputation wallet with long history and diversified activity.",
"market_data": { ... },
"report": { ... },
"validation": { ... },
"social_detail": { ... }
}Sentiment and AI assistant
/x-sentimentFetch social sentiment for an entity across X and other sources.
GET /v1/x-sentiment?q=PEPE&chain=1/trust-agentAsk an AI agent to run multi-chain checks and return an aggregated explanation.
GET /v1/trust-agent?q=Is+this+wallet+safe+to+interact+with%3F&chains=1,137,42161Simulation and reports
/simulateDry-run a transaction to estimate gas usage and see high level state changes.
POST /v1/simulate
Content-Type: application/json
{
"chainId": "1",
"action": "native_transfer",
"from": "0xFROM...",
"to": "0xTO...",
"value": "0.05"
}/ca-report/pdfGenerate a one-page PDF summary of an address analysis suitable for sharing.
GET /v1/ca-report/pdf?q=0xADDRESS&chain=1