Providers and models.

Nodes and Penny need access to the provider behind the operation you choose. Studio supports managed access on Kaitoi credits, eligible personal provider keys, and supported local services. Availability depends on your account and the installation's enabled providers.

#Match the setting to the access route

Managed access uses Account → Providers and available Kaitoi credits. Eligible personal credentials use Variables and the provider account behind the key. Local services use Integrations and require a working service, model and connection. Check the chosen model on General Penny, Lab Penny or the workflow node itself; changing one surface does not reconfigure all the others. Catalog entries, supported prices, capabilities and balances remain separate requirements.

The selected route connects one operation to a managed balance, an eligible personal credential or a configured local service. The three independent General Penny, Lab Penny and workflow-node selectors remain below that route.

#Choose how to pay and connect

Access	What you supply
Managed provider	Your Kaitoi account and sufficient available credits
Personal provider key	A key for your provider account, with the required account capability
Local service	The service, models, hardware, and a working Studio connection

Managed access is configured in Settings → Account → Providers. Eligible personal secrets use Settings → Variables. Settings → Integrations contains OpenRouter model choices and supported local-service settings. Avoid putting keys into prompts, public node source, or shared graph parameters.

#Configure OpenRouter choices

Open OpenRouter in Integrations to choose the models Graph Penny should offer. The model picker includes a configuration link back to these settings. Where an administrator has configured defaults, Reset to defaults removes your saved list after confirmation so you use that default selection again.

A model that exists at a provider is not necessarily enabled for your account or priced for Kaitoi-managed usage. Use the current picker and node library rather than relying on an old model name from an example.

#Keep different connections distinct

Signing in with Google or GitHub establishes your Kaitoi identity. Connecting Google Drive or another service grants access to that service. A provider API key supplies model access. These are separate connections and permissions.

#Troubleshoot access

Read the required key or provider named by a failing node. Check that the appropriate configuration is enabled and that you have the needed capability and available balance. If an operation has no supported managed price, repeated retries cannot create that price; use a supported operation or your own key where permitted.

For a local node, confirm the service is running and reachable before changing the graph. See Local models and services.

#Find the setting for the connection you mean

Managed: Settings → Account → Providers controls supported managed access. Personal key: Settings → Variables manages eligible secrets. Local/model choices: Integrations configures OpenRouter choices and supported local services. General Penny, Lab Penny and workflow model settings are distinct. No provider, key or model selection is changed here.

#Checks and next steps

Use the control that corresponds to the kind of access:

Need	Where to check
Enable or disable managed access	Settings → Account → Providers
Configure an eligible personal secret	Settings → Variables
Choose offered OpenRouter assistant models	Settings → Integrations → OpenRouter
Connect supported local services	Settings → Integrations → the service

Check the model on the surface that will use it. General Penny, Lab Penny, and a model configured inside a workflow step are different choices. An OpenRouter list change does not reconfigure every existing model node.

When access fails, identify the node's required provider and whether it is using managed access or a personal credential. A valid key, enabled managed provider, catalog entry, available price, and sufficient balance are distinct requirements. Do not keep retrying an unavailable operation as a way to enable it.