CompatibleModelPorts

SUPPORT · interface · Type contract

Adapter ports the App may override without replacing the provider.

Import

TypeScript

import type { CompatibleModelPorts } from '@jangts/agent-core/support';

JavaScript

/** @typedef {import('@jangts/agent-core/support').CompatibleModelPorts} CompatibleModelPorts */

Other public entry points:@jangts/agent-core, @jangts/agent-core/types, @jangts/agent-core/structs, @jangts/agent-core/support, @jangts/agent-core/support/model.

Definition

interface CompatibleModelPorts

Field structure

Field	Type	Required	Description
request	((input: RequestInfo | URL, init?: RequestInit) => Promise<Response>) | undefined	Optional	Fetch implementation; defaults to the global fetch.
error	((failure: ModelProviderFailure) => Error) | undefined	Optional	Builds the thrown error for a classified failure.
ensureJsonInstruction	boolean | undefined	Optional	Prefix a JSON instruction when the prompt does not already mention JSON.
allowEmptyJson	boolean | undefined	Optional	Accept an empty JSON response instead of reporting MODEL_INCOMPLETE.
completionPolicy	CompletionPolicy | undefined	Optional	Decide whether a finished stream satisfies the request; defaults to the legacy rules.
observer	ProviderObserver | undefined	Optional	Optional Support observations, collected by the caller independently of Core diagnostics.

Examples

• Compatible Provider and custom Providers: Support owns the common Chat Completions HTTP/SSE lifecycle; an App can substitute its own ChatProvider.

Connect a common protocol with real server-side configuration

Beginner · Node.js

Running this example requires connection configuration for an available model service.

TypeScript

import { ModelRunner, Support } from '@jangts/agent-core';
const provider = new Support.CompatibleModelProvider({ config: {
  baseUrl: process.env.MODEL_BASE_URL!, apiKey: process.env.MODEL_API_KEY!, model: process.env.MODEL_NAME!,
} });
const runner = new ModelRunner({ provider });
console.log((await runner.invoke('你好')).value);

JavaScript

import { ModelRunner, Support } from '@jangts/agent-core';
const provider = new Support.CompatibleModelProvider({ config: {
        baseUrl: process.env.MODEL_BASE_URL, apiKey: process.env.MODEL_API_KEY, model: process.env.MODEL_NAME,
    } });
const runner = new ModelRunner({ provider });
console.log((await runner.invoke('你好')).value);

Declared fields and wire mapping for a direct tool thread

Configuration · Node.js

This only demonstrates message conversion, with no network request or tool execution. Raw tool_calls, tool_call_id, and host-attached data are not forwarded.

TypeScript

import { Support } from '@jangts/agent-core';
const messages: Support.ProviderMessage[] = [
  { role: 'user', content: '查询资料' },
  { role: 'assistant', content: '', toolCalls: [
    { id: 'call-1', name: 'lookup', arguments: '{"query":"资料"}' },
  ] },
  { role: 'tool', content: '{"found":true}', toolCallId: 'call-1' },
];
console.log(Support.chatCompletionMessages(messages));

JavaScript

import { Support } from '@jangts/agent-core';
const messages = [
    { role: 'user', content: '查询资料' },
    { role: 'assistant', content: '', toolCalls: [
            { id: 'call-1', name: 'lookup', arguments: '{"query":"资料"}' },
        ] },
    { role: 'tool', content: '{"found":true}', toolCallId: 'call-1' },
];
console.log(Support.chatCompletionMessages(messages));

Related policy source

• HTTP failure mapping and controlled request fields

Related definitions

• CompletionPolicy
• ModelProviderFailure
• ProviderObserver