Developer Preview

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

API

Chameleon Eye API

A business intelligence API — not a raw model API. Connect your workflows, documents, reports, risk reviews, industry systems, and private intelligence outputs to Chameleon Eye AI through structured, scoped endpoints.

API Overview

What the Chameleon Eye API is designed for.

Business Intelligence

Submit business context, operational data, or document content and receive structured intelligence outputs — risk scores, report content, decision support, and next-best-action recommendations.

Industry System Integration

Connect your workflows to Chameleon Eye AI's industry-specific endpoints. Operational events can be piped in and out via API.

Event Webhooks

Subscribe to platform events and receive real-time notifications when reports are generated, risk reviews are created, or operational status changes occur.

Planned Endpoints

Endpoint structures planned for the Chameleon Eye API. These describe the Developer Preview — production access is not yet generally available.

Chameleon Eye API v1 — Developer Preview

GET/healthAPI health check.

GET/v1/me/usageUsage and quota check.

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.

Example Request

A sample POST /v1/risk/check request with approved business summary text.

POST /v1/risk/check
Authorization: Bearer <your-api-key>
Content-Type: application/json

{
  "workspace_id": "ws_example123",
  "content_type": "business_summary",
  "approved_text": "Q3 revenue declined 12% vs Q2. Team headcount reduced by 3. Two key enterprise contracts are pending renewal."
}

Authentication

API keys are scoped to specific permissions and follow a structured naming format.

Key format

che_live_************

Chameleon Eye API keys follow this format. Test keys use che_test_ prefix. Keys are scoped to specific permissions and can be revoked at any time. Real keys are never shown in documentation or exposed in frontend code.

Key types

·Live key — for production use, scoped to approved operations
·Test key — for development and integration testing
·Read-only key — for dashboards and monitoring integrations

Authentication Details Rate Limits

Webhook Events

Subscribe to platform events to trigger your own workflows.

report.generated

Fired when a report generation completes.

risk_review.created

Fired when a risk review is created.

device.activated

Fired when a desktop device is activated.

device.revoked

Fired when a desktop device is revoked.

API Safety Controls

Key management and access control status.

Scoped API keysImplemented

Read-only key typeImplemented

Test and live key separationImplemented

Key revocationImplemented

Audit logs for API accessPlanned

Rate limitsPlanned

Security and Access

How Chameleon Eye API protects requests and prevents unauthorised access.

+Chameleon Eye API is authenticated.

+Customer apps should call from server-side.

+API keys must not be embedded in clients.

+Short-lived tokens for approved desktop and mobile flows.

+Site connector keys are server-side only.

+Raw provider model IDs are not accepted from clients.

+Provider keys are never exposed to browser, desktop, or mobile clients.

+Rate limiting is planned — currently not enforced in developer preview.

Data Handling

How Chameleon Eye API handles customer data during processing.

+Private archives are not sent by default.

+Selected text requires approval before cloud processing.

+Usage metadata is recorded for billing, abuse prevention, and audit integrity.

+Raw private content is not logged by default.

Error Codes

HTTP status codes returned by Chameleon Eye API.

Code	Meaning
401	Unauthorized — missing or invalid key
403	Forbidden — insufficient permissions
409	consent_required — user approval needed before cloud processing
429	rate_limited — retry after specified seconds
500	internal_error — contact support if persistent

API Early Access

The Chameleon Eye API is in Developer Preview. The endpoint structures shown here describe the planned API. Production access is not yet generally available. Join the early access list to be notified when production API access opens.

Join API Early Access Authentication Rate Limits Trust Center