Authentication
Use server-side credentials issued to an approved application. Keep secrets out of browser code, public repositories, logs, and client-visible responses.
API Docs
Integrate Chameleon with clear boundaries.
A public guide to the integration contract: how applications authenticate, scope business context, request intelligence, receive structured output, and handle approvals.
Integration model
Authenticate. Scope. Investigate. Review. Act.
Each request belongs to an approved application and workspace. The request identifies the task and permitted context. Chameleon returns structured intelligence and an action proposal only where the workflow supports it.
The API is in managed development. Approved developers receive the current endpoint reference, schemas, credentials, and change notices inside their developer workspace.
Conceptual requestJSON
{
"workspace": "approved-workspace",
"task": "investigate",
"question": "Where is margin leaking?",
"context": ["business_dna", "approved_files"],
"output": "executive_report",
"action_policy": "approval_required"
}Core guidance
The rules every integration should understand.
Context scoping
Reference only the workspace, memory classes, files, and tools the current user and task are allowed to use.
Request lifecycle
Create the task, monitor its state where asynchronous work is required, retrieve the result, and preserve the request identifier.
Structured output
Expect explicit findings, evidence references, missing facts, assumptions, risks, recommendations, and action proposals when requested.
Limits and retries
Respect application limits, back off after temporary failures, avoid duplicate submissions, and keep idempotency where the current contract requires it.
Errors and traceability
Store request identifiers, handle permission and validation errors distinctly, and never expose internal secrets when logging failures.
Production discipline
Treat intelligence workflows like critical application workflows.
Pin the contract
Use the approved version and review change notices before adopting a newer contract.
Protect credentials
Rotate compromised keys and keep credentials isolated by application and environment.
Review high-impact results
Require qualified review for legal, financial, medical, regulatory, or other consequential decisions.
Approve before action
Keep sensitive execution behind clear user or workspace approval boundaries.
Ready to integrate?
Request managed access to receive the current endpoint reference and implementation requirements.