Contributor & API Documentation

Everything you need to contribute to Aevum Encyclopedia, access our knowledge graph, and integrate verified content into your applications.

Platform Overview

Aevum Encyclopedia provides a dual-access model: a curated contributor portal for verified authors and a REST/GraphQL API for developers. All content undergoes multi-stage verification before publishing.

ℹ️

Note for New Contributors

Access requires a verified academic or institutional email. Community contributors can request review access after 50 successful edits.

Quickstart Guide

1. Generate an API Key

Visit your dashboard to create a project and generate a secret key. Keep this key secure and never expose it in client-side code.

bash

curl -X POST https://api.aevum.org/v2/auth \
  -H "Content-Type: application/json" \
  -d '{"provider": "github", "code": "your_oauth_code"}'

2. Fetch an Article

Use the `/articles/{slug}` endpoint to retrieve structured markdown with metadata.

javascript

const response = await fetch('https://api.aevum.org/v2/articles/quantum-computing', {
  headers: { 'Authorization': 'Bearer AE_live_8x92j...' }
});
const data = await response.json();
console.log(data.metadata.verification_score); // 0.994

Content Writing Guidelines

All entries must adhere to the VERITAS framework:

Verifiable: Every claim requires at least one primary or peer-reviewed source.
Extensible: Structure entries to allow future updates without breaking references.
Referenced: Use standardized citation formats (APA, Chicago, or DOI links).
Inclusive: Present multiple scholarly perspectives where consensus varies.
Temporal: Tag content with publication dates and version hashes.
Anchored: Cross-link related concepts using our knowledge graph ontology.
Structured: Follow the standardized YAML frontmatter template.

API Endpoints

Base URL: https://api.aevum.org/v2

Method	Endpoint	Description
`GET`	`/articles/{slug}`	Retrieve full article with citations and metadata
`GET`	`/search`	Semantic search across verified corpus
`POST`	`/contributions`	Submit draft for editorial review
`GET`	`/graph/{concept}`	Fetch related nodes and edges in knowledge graph

Rate Limits & Quotas

Aevum uses a tiered rate limiting system based on your subscription plan:

Plan	Requests/min	Concurrent	Export Limit
Free	60	2	100 docs/mo
Pro	1,200	10	Unlimited
Enterprise	Custom	Dedicated	Full corpus sync

⚠️

Rate Limit Headers

Always monitor X-RateLimit-Remaining and implement exponential backoff on 429 Too Many Requests responses.

Error Handling

The API uses conventional HTTP status codes. Error payloads include a machine-readable code and human-readable message.

json

{
  "error": {
    "status": 403,
    "code": "INSUFFICIENT_VERIFICATION",
    "message": "Article requires Level 2 editorial clearance. Contact support for access.",
    "request_id": "req_88x29a"
  }
}

Frequently Asked Questions

How long does editorial review take?

Standard submissions are reviewed within 48–72 hours. Urgent corrections or breaking science topics are prioritized and typically cleared within 12 hours.

Can I self-host the Aevum corpus?

Yes. Enterprise customers receive Docker-compatible database snapshots and full schema definitions. Open-source mirrors are available under CC BY-NC 4.0.

How are conflicting sources resolved?

Our AI triage system flags discrepancies. Human reviewers apply the Preponderance of Peer-Reviewed Evidence standard, with minority views documented in dedicated "Alternative Perspectives" sections.