Schemas

GET /v1/schemas/{name} returns the full JSON Schema of one of five large request types. On the MCP and CoPilot tool surface, arguments of these types carry only a placeholder whose description ends in describe_schema('AgentConfig') (or another name): fetch the document, then write the object. The OpenAPI document, both SDKs and server-side validation always use the full types, so SDK users rarely need this endpoint.

curl https://api.talqing.com/v1/schemas/AgentConfig \
  -H "Authorization: Bearer $TALQING_API_KEY"

const { name, json_schema } = await talqing.schemas.get({ name: "AgentConfig" });

document = talqing.schemas.get("AgentConfig")

The response is {"name": "AgentConfig", "json_schema": {...}}. Any other name is a 422. Documents compose: AgentTeam refers to AgentConfig and AgentOverride instead of inlining them, so a document you fetch may itself point at another.

The five deferred types

Name	Describes	Accepted as
`AgentConfig`	A whole agent definition	`config` on `POST /v1/agents`; `agent` on `POST /v1/calls/outbound`, `POST /v1/calls/token`, `POST /v1/chats`, `POST /v1/calls/batches` and on a team member
`AgentOverride`	`AgentConfig` with every field optional	`config` on `PATCH /v1/agents/{agent_id}`; `agent_override` on the same four requests and on a team member
`AgentTeam`	Several agents on one call, handing off to each other	`agent_team` on the same four requests
`TaskConfig`	An agent task: inputs, output, model stack	`config` on `POST /v1/tasks` and, every field optional, `PATCH /v1/tasks/{task_id}`
`ToolOperations`	A tool’s operation tree	`operations` on `POST /v1/tools`, `PATCH /v1/tools/{tool_id}`, and an inline tool inside an agent config

What the fields mean is documented on the agent config, per-call configuration, agent teams on a call, task inputs and output and the operation tree.

Function arguments

GET /v1/schemas/functions/{name} returns {name, description, json_schema} for one MCP function: its full docstring and argument schema. On the MCP surface every function except describe_schema and describe_function defers its arguments here, so call describe_function before the first use of a function. SDK: talqing.schemas.functions.get(...).

Using the API

Endpoints

The five deferred types

Function arguments

​The five deferred types

​Function arguments

The five deferred types

Function arguments