Overview
The Aevum Encyclopedia API provides programmatic access to our verified knowledge base. All responses follow a consistent JSON structure, optimized for caching, pagination, and semantic querying.
🚀 Quick Start
Generate an API key from your developer dashboard, attach it to the Authorization header, and start querying. All endpoints support both JSON and Markdown output formats.
Base URL & Response Format
Base URL: https://api.aevumencyclopedia.com/v1
Content-Type: application/json
Accept: application/json
JSON Schema Definition
Every article response follows this strict schema. Additional metadata and knowledge graph edges are included for advanced linking.
{
"type": "object",
"properties": {
"article_id": { "type": "string", "format": "uuid" },
"title": { "type": "string" },
"summary": { "type": "string", "maxLength": 256 },
"content": {
"type": "object",
"properties": {
"html": { "type": "string" },
"markdown": { "type": "string" },
"word_count": { "type": "integer" }
}
},
"metadata": {
"type": "object",
"properties": {
"created_at": { "type": "string", "format": "date-time" },
"updated_at": { "type": "string", "format": "date-time" },
"language": { "type": "string", "pattern": "^[a-z]{2}$" },
"verification_score": { "type": "number", "minimum": 0, "maximum": 1 },
"tags": { "type": "array", "items": { "type": "string" } }
}
},
"knowledge_graph": {
"type": "array",
"items": {
"type": "object",
"properties": {
"entity": { "type": "string" },
"relation": { "type": "string" },
"confidence": { "type": "number" },
"target_id": { "type": "string", "format": "uuid" }
}
}
}
},
"required": ["article_id", "title", "content", "metadata"]
}
Core Endpoints
All routes are relative to the base URL. Pagination uses cursor-based navigation for consistent performance.
| Method | Path | Description |
|---|---|---|
| GET | /articles/{id} | Retrieve a specific article by UUID |
| GET | /search | Semantic & keyword search with filters |
| GET | /graph/edges | Fetch knowledge graph connections |
| POST | /translate | Translate article content to target language |
| PUT | /contributions | Submit draft for expert review |
Authentication
Aevum uses standard bearer token authentication. Include your API key in the request header:
Authorization: Bearer sk_aevum_live_xxxxxxxxxxxxxxxxxxxx
⚠️ Security Note
Never expose your API keys in client-side code or public repositories. Use environment variables and rotate keys quarterly.
Rate Limits & Tiers
Requests are throttled per API key to ensure platform stability. Limits reset at the start of each UTC hour.
| Tier | Requests / Hour | Graph Queries | Translation |
|---|---|---|---|
| Free | 100 | 10 | 5 |
| Pro | 5,000 | 500 | 100 |
| Enterprise | Custom | Unlimited | Unlimited |
Example Request
Query the semantic search endpoint to find articles about quantum computing with high verification scores.
# POST /search curl -X POST https://api.aevumencyclopedia.com/v1/search \
const response = await fetch('https://api.aevumencyclopedia.com/v1/search', { method: 'POST', headers: { 'Authorization': `Bearer ${API_KEY}`, 'Content-Type': 'application/json' }, body: JSON.stringify({ query: 'quantum computing', filters: { min_verification: 0.85 }, limit: 5, expand: ['knowledge_graph', 'metadata'] }) }); const data = await response.json(); console.log(data.articles);
Error Handling
The API uses standard HTTP status codes. All errors return a structured JSON object:
{
"error": {
"code": "RESOURCE_NOT_FOUND",
"message": "Article with ID 'x' does not exist or is restricted.",
"details": {
"request_id": "req_8f3a2b1c",
"timestamp": "2025-03-15T10:22:41Z"
}
}
}