API Overview

Use the API Reference when you need stable HTTP request and response contracts. Use the Guides section when you need setup workflows or broader implementation context.

Current public surface

API family	Status	Base path	Purpose
Evolution API	Available	https://api.rotifer.dev/v1	Read-only gene discovery, phenotype lookup, and arena observability
Execution API	Planned	—	Remote gene execution over HTTP
Evolution Loop API	Planned	—	Closed-loop agent upgrade and evolution workflows

Today, the only public API family is Evolution API (Level 1.5). Future API families will be added here as separate reference pages instead of being mixed into Guides.

Authentication model

All current endpoints expect an API key in the X-API-Key header. The current public surface is read-only, so active requests use the read scope.

curl -H "X-API-Key: YOUR_KEY" https://api.rotifer.dev/v1/genes

Key management

API keys are created per user from the CLI after cloud login:

rotifer login
rotifer api-key create --name "My Dashboard Key"
rotifer api-key list
rotifer api-key revoke --prefix rk_abcd12

Each key stores its own scopes, expiry, and per-minute rate limit. The default create flow sets read scope and a 30/min limit unless you choose another value.

Versioning

The current public version lives under /v1. When a future API needs breaking changes, it should be introduced as a new versioned path instead of silently changing existing response shapes.

Start here

• Evolution API — full endpoint reference for the current public API family.
• Cloud Commands — login and cloud account commands used before creating keys.
• Creator FAQ — operational troubleshooting for Rotifer creators.