IntegrationsOpt-in

Every new feature works without the app

Each key belongs to a workspace and carries only the scopes you grant. The public routes cover the same features the app does (custom events, identity, evals, heartbeats, SLO events, metrics, secrets, MCP publishing), so a cron job, a GitHub Action or another platform can use e-volv without a browser session. Keys are shown once and stored hashed.

Opt in: most scopes need a per-workspace flag

• Post a custom event to start any workflow from any system
• Keys are shown once; only a SHA-256 hash is stored
• Least-privilege scopes per key, checked per route
• Prometheus text format for metrics scrapers
• Signed webhooks with an HMAC header for outbound alerts
• Scope by scope: events.custom, agents.identity, mcp.registry, vault.rotation, slo.tracking, monitoring.scheduled and alerts.rules each need their flag on

17API scopes

1. Git providersGitHub, GitLab, Bitbucket, and Azure DevOps adapters with PR, issue, branch, and CI support.
2. Ticket systemsJira, Linear, and ClickUp adapters for reading, creating, and updating tickets.
3. Ticket boardsConnect several boards per tracker and read them as a single kanban, filtered, searchable, and writable.
4. LLM modelsOpenAI, Anthropic, Azure OpenAI, AWS Bedrock, OpenRouter, and DeepInfra.
5. VaultAES-256-GCM encrypted workspace secrets, never returned in list endpoints.
6. MCP registryOpt-inVersioned, signed MCP server manifests that agents reference by name and semver range.