Skip to content
Documentation

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.

PathBest forStart here
CHAMPREP VortexInstallable AI code editor for macOS, Windows, Linux with Eve built-inVortex IDE
Eve AI for VS CodePair-programming, code planning, and file edits in VS CodeEve AI for VS Code
CHAMPREP for ChromeBrowser side panel, page capture, and approval-based browser actions for EveCHAMPREP for Chrome
Desktop ClientCross-platform native application for macOS, Windows, LinuxDesktop client
API GatewayDirect HTTPS integrations and custom applicationsAPI Gateway overview
CHAMPREP CLI (eve / champrep)Interactive terminal work, scripts, and CI jobsCLI overview
MCP ServerConnect external assistants (Claude, Cursor) to CHAMPREPMCP server
WebhooksEvent-driven integrations that should not pollWebhooks
SDKsComing soon; sign-in requiredDeveloper downloads
SCIM 2.0Enterprise identity-provider provisioningSCIM provisioning
CHAMPREP RTCAudio/video communication inside your applicationRTC developer guides
Customer-managed deploymentIn development, not yet availableCustomer-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.

  1. Sign in to CHAMPREP and open API Keys.
  2. Create a key with only the scopes required by your integration.
  3. Store the key in a secret manager or operating-system keychain.
  4. Send a request to the production Gateway:
Terminal window
export CHAMPREP_TOKEN='replace-with-your-api-key'
curl --fail-with-body \
--header "Authorization: Bearer $CHAMPREP_TOKEN" \
https://api.champrep.com/v1/auth/whoami

The response identifies the active account and credential context. Continue with authentication and API keys before adding service scopes.

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.