Open infrastructure

OpenChat treats connectors and agent templates as open, composable code — not black-box plugins. Anyone can publish; the library categorizes and surfaces them.

Connector shape

export const connector = {
  id: "connector-myapi",
  name: "My API",
  baseUrl: "https://api.example.com",
  auth: { type: "bearer", env: "MY_API_KEY" },
  endpoints: { … },
  open: true,
};

Examples: Replicate, Blotato, Anthropic, OpenRouter, OpenChat data lake — under lib/openchat/connectors/.

Agent template shape

export const template = {
  slug: "my-agent",
  kind: "agent",
  tools: ["search_catalog", "get_dataset_records"],
  pipeline: [ /* optional api-to-api steps */ ],
  requiredEnv: ["SOME_KEY"],
};

Register in catalog.ts with systemAddon so chat loads the right behavior. Or use /publish for community entries.

Trading bots

Upload Python/JS/Pine source + optional equity curve JSON at /trading. Public bots join the open library; chat agent trading-bot-scaffold reasons over history with market lake data.

API-to-API agents

Example chain for Instagram video: LLM script → Replicate prediction → Blotato schedule. Each hop is a connector; the agent template only orchestrates. Keys never belong to OpenChat unless the user connects them server-side later.

← Technical thesis
Open infrastructure — connectors & agents | OpenChat-1