Chameleon for AI agents

Chameleon builds in-app product experiences like tours and tooltips, and tracks how users engage with them, without needing a release from engineering. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

MarketingAPI keyMCP + RESTchameleon.io
AUDIT LOG · CHAMELEONPOLICY: acme-support
09:41:07 · claude · u_8f2read
chameleon.list_changes
List Changes✓ allowed · 212ms
09:41:08 · claude · u_8f2read
chameleon.track_event
Track Event✓ allowed · 164ms
09:41:09 · claude · u_8f2write
chameleon.upsert_customer_record
Upsert Customer Record✓ approved · approved by user
EVERY CHAMELEON CALL, ON THE RECORD
01 · USE CASES

What agents do in Chameleon.

01

Look up a customer's record

Look up a customer record to see what in-app experiences they've already seen.

02

Check an experience's analytics

Pull analytics for a specific in-app experience before deciding to keep or retire it.

03

Track a product event

Track a custom event for a user, such as completing an onboarding step.

02 · ACTIONS

14 Chameleon actions, graded by risk.

Every Chameleon action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

13

Look things up. Allowed by default.

  • chameleon.get_delivery
    Get Delivery
  • chameleon.list_changes
    List Changes
  • chameleon.get_experience
    Get Experience
  • chameleon.list_deliveries
    List Deliveries
  • chameleon.list_experiences
    List Experiences
  • chameleon.get_account_identity
    Get Account Identity
  • chameleon.list_targeting_metadata
    List Targeting Metadata
  • chameleon.search_customer_records
    Search Customer Records
  • chameleon.list_experience_analytics
    List Experience Analytics
  • chameleon.list_domains_or_environments
    List Domains or Environments
  • chameleon.track_event
    Track Event
  • chameleon.count_customer_records
    Count Customer Records
  • chameleon.lookup_customer_record
    Lookup Customer Record

write

1

Create and change things. Allow, or ask the user first.

  • chameleon.upsert_customer_record
    Upsert Customer Record

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · HOW IT WORKS

Chameleon in three steps.

  1. 01Your users connect ChameleonThey add their Chameleon api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “upsert Customer Record” can wait for the user to approve.
  3. 03Any agent can actYour agent calls Chameleon through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('chameleon', {
  read: 'allow',
  write: 'ask',        // upsert_customer_record
  destructive: 'deny',  
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Chameleon connects.

Users add their Chameleon api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Chameleon connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Chameleon from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Chameleon and Arc0, answered.

Q01

Can I use Chameleon with Claude, ChatGPT or Cursor?

Yes. Connect Chameleon to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Chameleon actions you allow.

Q02

How do users connect Chameleon?

Users add their Chameleon api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Chameleon actions can my agent take?

14 in total: 13 read, 1 write and 0 destructive, such as “upsert Customer Record”. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in Chameleon?

Yes. Allow read actions and deny writes in the Chameleon policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call Chameleon too?

Yes. The same Chameleon connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Chameleon into your agent.

Your users connect Chameleon once, under your brand. Your agent gets 14 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan