Claude, GPT-5.5 and your own model, each with a separate identity.
Step 1 of 4: The first
Each model provider, with its own identity.
Your team connects each model provider with its own identity and credentials.
Integration and portability. It runs At your administrators’ request.
Every call goes out, and is recorded, under its own provider.
Support, engineering and finance each use the provider set up for them, and each call is on record under that provider’s identity.
Step 1 of 4: Support
A support reply goes to Claude, under Claude’s own identity.
Change one provider, and the others carry on.
Each provider has its own identity, so renewing, replacing or removing one leaves the others exactly as they were.
Step 1 of 4: Connected
January: three providers are connected, each with its own identity.
The model gets the request, never the credentials.
Your administrators connect each provider once. From then on, each call goes out under that provider’s identity, and the credentials stay out of the model’s reach.
Step 1 of 4: A call
An approved call sets off for Claude.
Runs model and tool calls under your rules.
Every model call and tool action runs once, after Duplex approves it, with credentials out of the model’s reach.
- A model call, approved first and run onceA model call runs once, after Duplex has approved it for that request.
- The same call, streamed as it is writtenAnswers appear as they are written, with the same rules applied.
- A tool action, exactly as approvedA tool action runs once, with exactly the arguments Duplex approved.
- Long tool runs, streamed and safe to cancelA long-running tool streams its progress and can be cancelled safely.
- Each model provider, with its own identityYour team connects each model provider with its own identity and credentials.
- Which model connections are healthyA failing model connection is spotted before it slows anyone down.
- Model connections, checked after every changeA model connection is checked before first use and after every change.
- Each tool, with its own permissions and riskEach tool is connected with its own identity, permissions and risk level.
- Which tools are connected and healthyA broken tool connection is visible before an agent depends on it.
- Tool connections, checked after every changeA tool connection is checked before first use and after every change.
See it on your own work.
From your own assistant to every agent your company runs, a pilot puts Duplex on your own work, with the measures agreed before it begins.