SDKs & Postman Integration
Programmatically access the Aevum Encyclopedia knowledge graph. Our official SDKs and ready-to-import Postman collection streamline API integration with type safety, automatic retries, and built-in authentication.
https://api.aevumencyclopedia.dev/v2All endpoints require Bearer token authentication and return JSON responses.
SDK Installation
Install the official client for your preferred language. SDKs handle serialization, pagination, and error mapping automatically.
# Install via pip
pip install aevum-encyclopedia
# Initialize client
from aevum import AevumClient
client = AevumClient(api_key="ae_live_your_key_here")
results = client.search.query("quantum entanglement", depth=3)
for article in results:
print(article.title, article.summary[:80])
Postman Collection
Aevum Encyclopedia API v2
Complete request examples, environment variables, and pre-request scripts.
Environment Variables Required:
- AEVUM_API_KEY secret
- AEVUM_BASE_URL https://api.aevumencyclopedia.dev/v2
- ORGANIZATION_ID optional
Example Postman Request: Semantic Search
POST {{AEVUM_BASE_URL}}/search/semantic
Authorization: Bearer {{AEVUM_API_KEY}}
Content-Type: application/json
{
"query": "impact of CRISPR on agricultural biodiversity",
"filters": {
"language": "en",
"discipline": ["biology", "environment"],
"min_confidence": 0.85
},
"limit": 10,
"include_graph": true
}
Authentication
All requests must include a valid Bearer token in the Authorization header. Tokens are scoped to your project and can be rotated from the developer dashboard.
curl -X GET "https://api.aevumencyclopedia.dev/v2/articles/crud/78291" \
-H "Authorization: Bearer ae_live_sk_8x92m..." \
-H "Accept: application/json"
ae_live_* keys in client-side code. Use ae_test_* keys for development and restrict domains in the dashboard.Rate Limits & Usage
| Plan | Requests / min | Concurrent | Batch Size | Graph Depth |
|---|---|---|---|---|
| Free | 60 | 2 | 50 | 2 hops |
| Pro | 1,200 | 10 | 500 | 5 hops |
| Enterprise | Custom | Unlimited | 2,000 | Unlimited |
Rate limit headers are returned with every response: X-RateLimit-Remaining, X-RateLimit-Reset, and X-Request-ID.
Error Handling
Errors follow standard HTTP status codes with a consistent JSON payload:
{
"error": {
"code": "VALIDATION_ERROR",
"message": "Invalid filter: discipline must be one of [physics, biology, history...]",
"request_id": "req_9x82mf3k",
"docs_url": "https://dev.aevumencyclopedia.dev/errors/validation"
}
}
Common Status Codes
| Code | Meaning | Recovery |
|---|---|---|
| 401 | Unauthorized | Check API key scope & expiration |
| 429 | Rate Limited | Implement exponential backoff |
| 400 | Bad Request | Validate JSON schema against docs |
| 503 | Service Unavailable | Retry after Retry-After header |
Need Help?
Visit the Developer Community, check the Interactive Playground, or contact devs@aevumencyclopedia.dev.