Skip to content

/connect

Grid in your coding workflow.

Prepare a tool configuration, then compare accepted changes, review effort and cost on a bounded set of coding tasks.

Connect is by invitation. Start with a pinned model; confirm tool compatibility and account terms for the pilot.

Setup candidates · documentation reviewed 2 October 2026

Configure the tool.
Verify the workflow.

Confirm invitation, the installed tool version and an account-enabled chat model before using the example. These publisher-based recipes are setup candidates; verify Grid compatibility during the pilot.

Selected setup

Cline / Provider settings

Cline settings

API Provider: OpenAI Compatible
Base URL: https://api.genai.forlex.cloud/v1
Model ID: replace-with-an-enabled-chat-model-id
API Key: enter your key in Cline, not on this page
Context, output and features: confirm for the enabled deployment
Cline setup and verification
  1. Open the provider settings and select OpenAI Compatible.

  2. Set the Grid base URL and replace the model placeholder with an exact ID enabled for your account.

  3. Enter your key in Cline’s supported credential setting. Confirm context, output and feature settings for that deployment.

  4. Verify streaming, required tool calls and the relevant tests on a bounded coding task.

Store keys in the tool’s supported credential mechanism or your local environment. The website prepares a configuration example; it does not connect to Grid or test your credentials.

Use an account-enabled model.

Replace the example model ID with the exact ID from your account. Public model names are comparison references. Keep the first pilot pinned; evaluate routing separately.

Access, keys and model discovery

The request carries your selected tool. Add its version, team, model access and adoption criterion in the inquiry.

Review data and deployment

A pilot with a clear adoption decision.

  1. 01 / Configure

    Confirm invitation, tool version, endpoint and enabled model. Start pinned; routing can be evaluated separately.

  2. 02 / Compare

    Use the same coding tasks and tests. Measure accepted changes, failed attempts, review time and total consumption.

  3. 03 / Decide

    Review quality, limits and cost per accepted change. Agree on account terms and team rollout before expanding use.

Use the evaluation checklist

Before team rollout

Review controls and account terms.

Routing stays opt-in. The resolved model and your account agreement determine rates. Review the operating details before expanding the pilot.

Optional routing and token rates

Smart Router is the same opt-in router used by the API. Keep an exact model ID pinned for work that must not move. Set the model to grid-auto to evaluate routing against the Grid catalog. The resolved model determines the token rate; any routing charge is specified in your account agreement.

Usage, limits and team rollout

Review the account default limit, per-user overrides and usage by day, user and model, in tokens. Finance can export CSV. Connect is quoted as part of the invitation. Agree on account terms, limits and the adoption decision before expanding team use.

Grid in your coding tool

Connect points your coding agent or IDE at Grid while you keep the tool you use. Grid serves, routes and fine-tunes models. Setup is reversible. Connect is by invitation; confirm compatibility with the installed tool version and enabled deployment during the pilot.

Put Grid to work in your coding workflow.

Prepare your setup

Request access

Grid is invite only while we scale.

Drafts stay in this browser visit. Refreshing the page clears them.

Talk to us

Tell us who you are and what you need to review.

Drafts stay in this browser visit. Refreshing the page clears them.

Each topic keeps its own requirements during this visit. Changing topic keeps your contact details.