Custom model providers

Use an existing model gateway, a model server in your agent's environment, or Amazon Bedrock to supply model access. You save the route and credential as an AI connection, then select that connection on a compatible agent.

These connections are available without an experimental setting. They supply model access and do not add tool actions or a Permissions action catalog.

Choose the API format

The format must match the harness that runs your agent. Selecting a model from another provider does not change the harness.

ThinkingMach Runner uses the same compatibility rules for its Codex, OpenCode, and ACP Claude providers. Its Cursor and Grok profiles do not become compatible by selecting a custom endpoint.

Connect a gateway or local endpoint

1. Open Connectors and select Responses API, Messages API, Chat Completions API, or Local endpoint.
2. Enter Provider URL, using the base URL expected by that provider.
3. Review API format and Authentication.
4. Enter the credential when authentication is required.
5. Optionally add Model IDs (comma separated) using provider model IDs or gateway aliases.
6. Choose the connection's human audience and agent access, then select Connect.

The general model-provider setup also groups Custom gateway and Local endpoint under Advanced providers.

Remote gateway URLs require HTTPS. They cannot contain embedded credentials, query parameters, or a fragment. Local endpoints require localhost or a loopback address and may use HTTP, for example http://localhost:11434/v1.

A local address is relative to the agent's execution environment. If your agent runs in a sandbox, localhost means that sandbox, not your laptop or the ThinkingMach server. Make the model service available there before running the agent.

Connect Amazon Bedrock

Choose Amazon Bedrock, enter AWS region, select Bedrock API key authentication, and supply the key. You can add the Bedrock model IDs you want to use.

This connection supports a Bedrock API key and region. It does not accept a custom base URL or an AWS access-key pair. ThinkingMach projects the connection into the Claude harness using the Bedrock route.

Select the connection and model

Open the agent's Connection selector and choose the named compatible account. Custom routed connections require explicit selection; you cannot make one the responsible user's provider default.

When you create a new agent, the Connect a model step shows three tiles side by side: the provider's subscription, the provider's API key, and Advanced (tagged Custom Gateway). Choose Advanced to pick a saved compatible connection, or set up a new OpenRouter, Amazon Bedrock, Custom gateway, or Local endpoint connection without leaving agent setup. Then select Use connection.

A personal account can be selected explicitly, or a connection manager can share an account with the company. Every run still needs a responsible user who may use the credential, and the connection must be available to the agent. See How connector access works.

Use an exact model ID supplied by the endpoint. The IDs saved on the connection become model-picker choices; you can also enter an ID on the agent. ThinkingMach does not automatically fetch a model catalog from arbitrary gateways, local servers, or Bedrock. An OpenRouter connection without saved model IDs uses OpenRouter's public catalog and offers a refresh.

OpenCode uses paperclip/<model-id> for custom endpoints and openrouter/<model-id> for OpenRouter. The picker adds the harness prefix; Claude, Codex, and Hermes use the raw upstream ID.

Verify in the execution environment

Saving a custom connection is not proof that its endpoint, credential, or selected model works. Give the configured agent a short task and watch its run:

Reply with the single word: ready

This can consume provider usage. Check the account and model selected on the agent first. A local service that works in your browser may still be unreachable from the agent's environment.

Note: This is an example test, not a recorded live result.

Reconnect and troubleshoot

Reconnect replaces the credential while preserving the endpoint, API format, model list, and access. To change the route itself, create another connection and select it on the agent.

Related guides

• OpenRouter
• Check AI account usage
• Verify and troubleshoot
• ThinkingMach Runner