API Keys
Generate and manage API keys to authenticate requests to the Credify verification engine. Keep your keys secure — do not expose them in client-side code.
Active API Keys
| Name | Key | Created | Usage | Actions |
|---|
Test the Trust Layer Protocol verification engine in real-time. Select an API key, enter a claim, and observe the full verification pipeline.
Verification Request
Request Details (cURL)
curl -X POST https://api.credify.dev/v1/verify \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"claim": "..."}'
Response Output
Real-time stream of all verification requests made across your active API keys. Each entry includes the claim, classification, score, and latency.
Verification Logs
| Timestamp | Claim Snippet | Classification | Score | Latency |
|---|
Analyze verification volume, accuracy distribution, and performance metrics across your infrastructure.
Requests (30d)
Error Rate
Avg Latency
Usage by API Key
| Key Name | Total Requests | Last Used |
|---|
Credify Verification API
The Credify API allows you to programmatically verify claims against an enterprise-grade consensus network of trusted sources.
Authentication
Authenticate your account by including your secret API key in the authorization header of your requests.
Authorization: Bearer sk_live_...
Your secret API keys carry many privileges. Do not share them publicly or commit them to version control.
Errors
Credify uses conventional HTTP response codes to indicate the success or failure of an API request.
| 200 | OK — Request succeeded. Verification result returned. |
| 400 | Bad Request — The request was malformed. Check the claim parameter. |
| 401 | Unauthorized — Invalid or missing API key in the Authorization header. |
| 429 | Too Many Requests — Rate limit exceeded. Free: 100/min, Pro: 1,000/min. |
| 500 | Internal Server Error — Something went wrong on our end. Retry with exponential backoff. |
Verify a Claim
Analyzes a text string and returns a probabilistic truth score alongside source citations.
HTTP Request
POST https://api.credify.dev/v1/verify
Parameters
| claim required string |
The text statement to be analyzed. Max length 2000 characters. |
| strict_mode optional boolean |
If true, returns "Uncertain" if fewer than 3 high-authority sources are found. Default: false. |
Response Objects
A successful verification returns a JSON object containing the analysis results.
| id string | Unique identifier for the verification (e.g. veri_9a8b7c6d). |
| score float | Credibility score between 0.00 (false) and 1.00 (verified). |
| status string | Classification label: Verified, Likely True, Uncertain, Likely False, or False. |
| confidence float | Model confidence in the analysis between 0 and 1. |
| sources array | Array of source objects with name, stance, and url fields. |
| reasoning string | Human-readable explanation of the verification result. |
Example Response
{
"id": "veri_9a8b7c6d5e4f3g2h1",
"object": "verification",
"claim": "India banned EV vehicles in 2025",
"score": 0.21,
"status": "Likely False",
"confidence": 0.94,
"sources": [
{
"name": "Reuters",
"stance": "contradicts",
"url": "https://reuters.com/..."
}
],
"reasoning": "Multiple trusted sources contradict the claim."
}