Developer Preview

The Chameleon Eye API structures shown here describe the planned API. Production access is not yet generally available.

Join API Early Access
Developers

Build with Chameleon Eye AI

Authenticated API for embedding structured private intelligence into approved products and business systems.

Quick Start

Get up and running with Chameleon Eye API in four steps.

1

Request API access

Submit a request via /contact. API access is approved for business and partner use cases.

2

Receive credentials

You will receive scoped API credentials after approval. Keys follow the che_live_ format.

3

Make your first request

POST to /api/v1/risk/check with your workspace_id and approved_text payload.

4

Handle the response

Parse the structured intelligence response containing risk_level, answer, and mode fields.

Authentication Example

A sample authenticated POST request to the risk analysis endpoint.

Request

curl -X POST https://chameleoneye.ai/api/v1/risk/check \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "workspace_id": "ws_demo123",
    "content_type": "business_summary",
    "approved_text": "Q3 revenue declined 12% vs Q2. Two enterprise contracts pending renewal."
  }'

Response

{
  "task_type": "risk_review",
  "risk_level": "medium",
  "answer": "Three operational signals identified...",
  "mode": "deep_strategy",
  "created_at": "2026-07-15T10:00:00Z"
}

Planned Core Endpoints

Endpoint structures planned for the Chameleon Eye API v1.

Base URL: https://chameleoneye.ai/api — Developer Preview
GET/healthAPI health and status check
GET/v1/me/usageUsage counters and quota
POST/v1/risk/checkBusiness risk analysis
POST/v1/decision/memoDecision memo generation
POST/v1/report/structuredStructured intelligence report
POST/v1/desktop/activateDesktop Connector device activation
POST/v1/desktop/refresh-tokenToken refresh
POST/v1/desktop/revoke-deviceRevoke device access

Error Codes

Standard error codes returned by Chameleon Eye API.

CodeHTTP StatusMeaning
unauthorized401Missing or invalid API key
forbidden403Insufficient plan permissions
consent_required409User approval needed before cloud processing
privacy_route_unavailable423Required ZDR route unavailable
rate_limited429Request rate limit exceeded — retry after N seconds
internal_error500Server error — contact support if persistent

Data Handling

How the Chameleon Eye API handles submitted content.

+

Chameleon Eye API never accepts raw full archive uploads, local file dumps, or automated full document library transfers. Only approved payloads are processed. In Offline Local Mode, no third-party AI API is contacted.

Key Security Notes

Practices required for all API integrations.

+Keep API keys server-side only — never embed in browser, mobile, or desktop bundles
+Use short-lived tokens for desktop/mobile flows via Device Activation
+Rotate keys immediately on any suspected exposure
+All API requests require HTTPS

Documentation

Explore the full Chameleon Eye developer documentation.