Developer tools
CHAMPREP developer tools provide supported interfaces for automating workflows and building applications. General workspace automation uses the API Gateway. RTC provides a separate, documented project-key API for real-time communication.
Choose an integration path
Section titled “Choose an integration path”| Path | Best for | Start here |
|---|---|---|
| CHAMPREP Vortex | Installable AI code editor for macOS, Windows, Linux with Eve built-in | Vortex IDE |
| Eve AI for VS Code | Pair-programming, code planning, and file edits in VS Code | Eve AI for VS Code |
| CHAMPREP for Chrome | Browser side panel, page capture, and approval-based browser actions for Eve | CHAMPREP for Chrome |
| Desktop Client | Cross-platform native application for macOS, Windows, Linux | Desktop client |
| API Gateway | Direct HTTPS integrations and custom applications | API Gateway overview |
CHAMPREP CLI (eve / champrep) | Interactive terminal work, scripts, and CI jobs | CLI overview |
| MCP Server | Connect external assistants (Claude, Cursor) to CHAMPREP | MCP server |
| Webhooks | Event-driven integrations that should not poll | Webhooks |
| SDKs | Coming soon; sign-in required | Developer downloads |
| SCIM 2.0 | Enterprise identity-provider provisioning | SCIM provisioning |
| CHAMPREP RTC | Audio/video communication inside your application | RTC developer guides |
| Customer-managed deployment | In development, not yet available | Customer-managed deployment |
Networked CLI commands and general platform requests use the Gateway. RTC integrations instead use the RTC server API and RTC-specific project keys. Avoid undocumented browser-facing or backend-private routes; those are not public integration contracts.
Quick start
Section titled “Quick start”- Sign in to CHAMPREP and open API Keys.
- Create a key with only the scopes required by your integration.
- Store the key in a secret manager or operating-system keychain.
- Send a request to the production Gateway:
export CHAMPREP_TOKEN='replace-with-your-api-key'
curl --fail-with-body \ --header "Authorization: Bearer $CHAMPREP_TOKEN" \ https://api.champrep.com/v1/auth/whoamiThe response identifies the active account and credential context. Continue with authentication and API keys before adding service scopes.
Platform controls still apply
Section titled “Platform controls still apply”A valid key does not bypass the product controls that apply in CHAMPREP. A request can proceed only when all of the following are true:
- API Gateway access is enabled for the active plan and profile.
- The destination service is available to the active plan and organization.
- The key contains the scope required by the method and resource.
- The live per-minute, daily, and service-specific usage controls allow it.
- The active role is authorized to perform the operation in the destination service.
This is why an API key should be treated as an additional interface to the same account, not as a way around account, plan, role, or organization policy.
Reference map
Section titled “Reference map”- CHAMPREP Vortex
- Eve AI for VS Code
- CHAMPREP for Chrome
- CHAMPREP Desktop Client
- API Gateway overview
- Authentication and API keys
- Service endpoint reference
- Errors, limits, and retries
- Webhooks
- SCIM 2.0 provisioning
- MCP server (connect AI assistants)
- Install the CLI (
eve/champrep) - CLI authentication
- CLI command reference
- CLI troubleshooting
- AI agent in terminal (Eve)
- CHAMPREP Code & Runner Farm
- Self-hosted code runner
- Customer-managed deployment (in development)