API Overview
The Archeus API provides programmatic access to the platform core capabilities. Through the API, you can create and manage threads, submit tasks, monitor execution, and retrieve results. This enables the integration of Archeus SI — the autonomous Superintelligence — into your own applications, workflows, and systems.
The API follows REST conventions with JSON request and response formats. Authentication uses API keys that can be generated from the Archeus dashboard. Rate limits ensure fair usage and platform stability, with higher limits available for enterprise customers.
API endpoints are organized by function. Thread management endpoints handle conversation creation and history. Task submission endpoints accept natural language instructions and return execution results. Monitoring endpoints provide real-time execution status and progress updates.
Authentication and Setup
API access is authenticated using API keys. Generate a key from the Archeus dashboard under Settings > API Keys. Keys can be scoped to specific capabilities — read-only access for monitoring, full access for task execution, or custom scopes for specific integrations.
Include the API key in the Authorization header of every request: `Authorization: Bearer your-api-key`. Keys should be stored securely and never committed to source code. Use environment variables or secret management systems to protect key material.
Rate limits are applied per API key. The free tier provides sufficient capacity for development and testing. Production workloads can request higher limits through the enterprise tier. Rate limit headers in API responses provide current usage and remaining capacity.
Making Your First Request
Start by creating a thread — a conversation context that maintains state across requests. Use the create thread endpoint to initialize a new thread, then submit tasks to that thread using the task submission endpoint.
Task submission accepts a natural language instruction and optional parameters. The instruction describes what you want Archeus to do — research a topic, analyze data, generate code, or automate a workflow. Parameters control execution options like model selection, skill preferences, and output format.
Results are returned synchronously for quick tasks or asynchronously for longer operations. Async results include a status endpoint that you can poll for completion, or you can configure webhooks to receive notifications when tasks complete.
Error Handling and Best Practices
The API uses standard HTTP status codes to indicate success and failure. 2xx codes indicate success, 4xx codes indicate client errors (invalid request, authentication failure, rate limit exceeded), and 5xx codes indicate server errors. Error responses include descriptive messages to help diagnose issues.
Implement retry logic with exponential backoff for transient failures. Rate limit responses include a Retry-After header that specifies when to retry. Server errors are typically brief and resolve quickly with a single retry.
For production integrations, implement idempotency — the ability to safely retry requests without causing duplicate operations. Use unique request identifiers to prevent duplicate task execution. This ensures reliability even when network issues cause request retries.