Create a request
Define the specific credential or threshold condition that your application needs to verify.
CrediFi's integration model is designed around explicit consent, signed credentials, verification status, revocation, and Solana-native on-chain infrastructure and public-key based wallet analysis.
Public API keys are not issued from this marketing site. Integration access is provisioned directly so security, permitted use, and data handling can be reviewed first.
Define the specific credential or threshold condition that your application needs to verify.
The user reviews the requested fields and authorizes a time-limited verification scope.
Your service validates the signed result, status, expiry, issuer, and revocation state.
{
"request_id": "cf_req_01J...",
"subject": "passport_7f2...",
"checks": {
"identity_verified": true,
"income_over_3000": true,
"income_history_months": 12
},
"credential_status": "valid",
"expires_at": "2026-09-06T18:00:00Z"
}
Illustrative schema only. It is not a public production endpoint or a promise that these exact fields are available.
The website calls a same-origin, read-only endpoint. It accepts a public Solana wallet address and returns the current CrediFi on-chain score, confidence, evidence metrics, and component breakdown.
GET /api/wallet-score?address=YOUR_SOLANA_WALLET
{
"ok": true,
"network": "Solana",
"cluster": "mainnet-beta",
"score": 742,
"band": "Very Good",
"confidence": 88,
"methodologyVersion": "2.0",
"metrics": { "walletAgeDays": 410, "activeMonths12": 9 },
"components": []
}
The web endpoint is intended for interactive CrediFi use. High-volume or commercial API access should use separately provisioned infrastructure and rate controls.
The live scoring runtime uses Solana mainnet JSON-RPC for public-key validation, balances, confirmed signatures, transaction details, and SPL token accounts. Production deployments should configure a dedicated SOLANA_RPC_URL.