Connecting providers and tools
Understand mock execution, provider selection, credentials, search, and custom APIs.
Mock and real providers
Mock Runtime is the default model configuration and the only provider used in visitor demos. Mock output and simulated external tool calls support product evaluation without consuming a connected provider key.
Registered workspaces can configure OpenAI or Anthropic. Provider resolution checks workspace credentials, then platform configuration, and can fall back to Mock Runtime when no usable key is configured. Inspect the selected execution mode in the run before treating output as a live provider result.
Credential handling
Connect a provider through Settings → Integrations. Workspace credentials are encrypted at rest by the server, using the deployment's encryption configuration. The server reads them for execution; they are not returned as plaintext to the client.
Visitor demos cannot save or read integration credentials, including credentials imported into an older demo workspace. Use a registered workspace and an appropriately scoped provider key for a live evaluation.
Search and custom APIs
Web search supports configured search providers and a keyless search path. Page retrieval extracts readable content from public pages. Network tools apply URL and destination checks; the content they retrieve remains external, untrusted input.
A custom API defines its base URL, actions, parameter schema, and authentication method. Start with a narrow action and review its request shape against the destination's documentation. Treat writes as changes to a real system, and evaluate their approval behavior separately.
Provider acceptance
The application includes provider adapters, but a live provider acceptance run has not yet been completed. The next validation step is a short registered-workspace task with a supplied provider key, followed by a deterministic tool call and a separate approval scenario.
Acceptance should confirm the requested provider, actual output, usage, configured cost calculation, and tool telemetry without a mock fallback. A successful connection check alone does not establish the complete task flow.