Tool reference

Third-party tool setup reference

01 Installation reference

Install from official sources

Official installation commands and links for compatible third-party tools. WORLDNITE does not host downloads, and tool names do not imply partnership.

[ A ]From model makers6

[ B ]Open-source agents2

[ C ]Agent platforms3

02 Connection settings

Connect with three settings

Once your service is provisioned, prepare your assigned endpoint, API key, and model ID; this public site has no account backend.

Step one

Prepare connection settings

Confirm your assigned endpoint, API key, and permitted model IDs from your service plan.

1Base URLExample: https://api.example.com/v1 (replace with your assigned endpoint)
2API keyStore it in a local environment variable or a secret manager.
3Model IDThe exact model ID in your provisioned catalog.

Step two

Write the tool configuration

Enter the settings in the configuration file or environment variables, then make a test request.

03 Tool setup

Connect your development tools

Choose a tool for configuration examples. Confirm your provisioned endpoint, API key, and supported protocol first.

Third-party tool configuration reference.

BAC
WORLDNITE

AFrom model makersBOpen-source agentsCAgent platforms

01 / 11A // From model makers

DeepSeek Harness

DeepSeek

Where it runs
Web UI, desktop app
Models it uses
DeepSeek models built in. Other models and tools are added as plugins
How to connect
Configure a compatible endpoint, key, and model for your tool version. Confirm protocol and permissions before using plugins.
terminalExample

# Developer preview: starts the web UI
npx @deepseek-ai/dsh web
# Then open http://127.0.0.1:3080

02 / 11A // From model makers

Codex

OpenAI

Where it runs
Terminal, IDE, app
Models it uses
OpenAI models, or other providers you add in config.toml
How to connect
Add WORLDNITE as a provider in config.toml using your assigned API endpoint and key.
~/.codex/config.tomlExample

model = "<model-id>"
model_provider = "worldnite"
 
[model_providers.worldnite]
name = "WORLDNITE"
base_url = "https://api.example.com/v1"
env_key = "WORLDNITE_API_KEY"
wire_api = "responses"

03 / 11A // From model makers

Grok Build

xAI

Where it runs
Terminal
Models it uses
xAI's Grok models. Sign in with xAI or use XAI_API_KEY
How to connect
Before connecting WORLDNITE, confirm that your tool version supports a custom endpoint and the required protocol. xAI sign-in and WORLDNITE keys are separate credentials.
terminalExample

# Windows PowerShell: irm https://x.ai/cli/install.ps1 | iex
cd your-project
grok

04 / 11A // From model makers

Claude Code

Anthropic

Where it runs
Terminal, IDE, desktop, web
Models it uses
Anthropic models, or any service that uses the Anthropic API format
How to connect
Set ANTHROPIC_BASE_URL to your provisioned Anthropic-compatible endpoint.
~/.claude/settings.jsonExample

{
  "env": {
    "ANTHROPIC_BASE_URL": "https://api.example.com",
    "ANTHROPIC_AUTH_TOKEN": "<WORLDNITE_API_KEY>",
    "ANTHROPIC_MODEL": "<model-id>"
  }
}

05 / 11A // From model makers

Kimi Code

Moonshot AI

Where it runs
Terminal, desktop, IDE
Models it uses
Kimi models. Sign in to Kimi Code or use a Moonshot AI Open Platform API key
How to connect
For WORLDNITE access, confirm that your tool version supports the endpoint and protocol required by the selected model.
terminalExample

kimi
/login
# Choose Kimi Code sign-in or an Open Platform API key

06 / 11A // From model makers

Gemini CLI

Google

Where it runs
Terminal
Models it uses
Google Gemini models. Sign in with Google, a Gemini API key, or Vertex AI
How to connect
For WORLDNITE access, configure a compatible Gemini endpoint, key, and model. Google account sign-in is a separate access method.
terminalExample
export GEMINI_API_KEY="<WORLDNITE_API_KEY>"
export GOOGLE_GEMINI_BASE_URL="https://api.example.com"
export GEMINI_MODEL="<model-id>"
gemini

07 / 11B // Open-source agents

OpenCode

Open source

Where it runs
Terminal, desktop, IDE
Models it uses
Many providers, including any OpenAI-style service
How to connect
Add WORLDNITE as an OpenAI-style provider in opencode.jsonc. Keep the key in an environment variable.
opencode.jsoncExample

{
  "providers": {
    "worldnite": {
      "name": "WORLDNITE",
      "env": ["WORLDNITE_API_KEY"],
      "package": "@opencode/ai/providers/openai-compatible",
      "settings": { "baseURL": "https://api.example.com/v1" },
      "models": { "<model-id>": { "name": "<model name>" } }
    }
  }
}

08 / 11B // Open-source agents

pi

Open source

Where it runs
Terminal
Models it uses
Many providers and models. Switch with /model
How to connect
Select your configured WORLDNITE provider and a provisioned model ID in pi.
terminalExample

pi
/login   # sign in to a provider
/model   # pick an available model

09 / 11C // Agent platforms

Hermes Agent

Nous Research

Where it runs
Terminal
Models it uses
Many providers, including your own OpenAI-style service
How to connect
Run hermes model, choose Custom endpoint, and enter your API address, key, and model.
terminalExample

hermes model
# Choose "Custom endpoint", then enter:
#   API base URL   https://api.example.com/v1
#   API key        <WORLDNITE_API_KEY>
#   Model name     <model-id>

10 / 11C // Agent platforms

OpenClaw

Open source

Where it runs
Your machine, as a background service
Models it uses
Many providers, including your own
How to connect
Choose Custom provider during setup and enter your assigned endpoint and model ID.
terminalExample

openclaw onboard --install-daemon
# Choose "Custom provider", then enter
# https://api.example.com/v1 and <model-id>

11 / 11C // Agent platforms

AstrBot

Open source

Where it runs
Messaging apps, web dashboard
Models it uses
Many providers, added in the web dashboard
How to connect
In the AstrBot dashboard, add a provider with your assigned API endpoint, key, and model ID.
terminalExample

astrbot
# Open the web dashboard and add a model provider
# with the values from your console

04 Security

Security best practices

  • Use official sources

    Install tools only from their official website or repository.

  • Protect API keys

    Use environment variables or a secret manager. Do not hard-code keys or share them in group chats.

  • Separate keys by environment and team

    Use separate development, testing, and production keys to limit the impact of rotation or revocation.

  • Review generated changes

    Review and test generated code patches and configuration changes before merging or deploying.

Light · Limitless · Forward

Tool setup for partners