Docs · Connector reference

Moonshot AI (Kimi) connector reference

Operations, inputs, troubleshooting, and questions for the Moonshot AI (Kimi) connection. Policy decides each change before the credential is resolved, and the action record carries the result.

Set up and verify the Moonshot AI (Kimi) connection

Choose one task and its account, and match the reads and actions on the overview page to it before granting provider permissions.
Prepare the connection settings from the overview page, connect the provider in Deixic, and choose which tools your agent can use.
Try a small task with a known result, and compare the returned identity and resource with what the account owner expects.
Configure approval for sensitive changes, review the destination and inputs, and check the result in the provider before expanding the workflow.

Information your agent can use

Resource	Record identity	Start with	Page coverage
Model catalog	`id`	Top level	None configured
Files	`id`	Top level	None configured
File details	`id`	Files	None configured
Batches	`id`	Top level	None configured
Batch details	`id`	Batches	None configured

Record identity: Match on these fields before joining or deduplicating results; where none is specified, check the returned record first.
Start with: Resolve the parent identifier first.
None configured: No page continuation is configured for this resource. Check the response and any provider limits before treating it as a complete inventory.

Supported operations

Review the inputs before granting an action to an agent. Required inputs must be supplied, optional inputs narrow the request, and provider permissions apply in addition to Deixic policy.

Read: Retrieves information; check the returned scope and identifiers before use.
Action: Can change provider state; review the target and inputs, then retain the result to avoid repeating completed work.

Operation	Effect	Approval	Provider permissions	Inputs
Chat Completions	Read	By policy	models.invoke	6
Batches Create	Action	Approval required	batch_jobs.write	4
Batches Cancel	Action	Approval required	batch_jobs.write	1
Files Delete	Action	Approval required	files.write	1
Batches Get	Read	By policy	batch_jobs.read	1

Inputs by operation

Chat Completions Read

Inputs for Moonshot Chat Completions
Input	Requirement	Accepted value
`max_tokens`	Optional	integerMinimum: 1Maximum: 32768
`messages`	Required	arrayMinimum items: 1Maximum items: 128
`model`	Required	string
`stream`	Optional	value
`temperature`	Optional	numberMinimum: 0Maximum: 2
`top_p`	Optional	numberMaximum: 1

Batches Create Action · approval required

Inputs for Moonshot Batches Create
Input	Requirement	Accepted value
`completion_window`	Required	string
`endpoint`	Required	string; one of: /v1/chat/completions
`input_file_id`	Required	string
`metadata`	Optional	object

Batches Cancel Action · approval required

Inputs for Moonshot Batches Cancel
Input	Requirement	Accepted value
`batch_id`	Required	string

Files Delete Action · approval required

Inputs for Moonshot Files Delete
Input	Requirement	Accepted value
`file_id`	Required	string

Batches Get Read

Inputs for Moonshot Batches Get
Input	Requirement	Accepted value
`batch_id`	Required	string

When the Moonshot AI (Kimi) task does not produce the expected result

Connected, but the expected data is missing

Check the identity behind the bearer token connection and its access to the specific resource; a successful connection does not establish access to every object.

Resolve parent resources first: Files, Batches. A matching display name is not enough for a child lookup.

The answer covers only part of the data

Check the resource’s page coverage, query filters, and result limit, and have the agent state the account and time window it inspected, so a partial response yields a scoped answer.

The agent keeps doing the same work

Inspect the action history for repeated targets and inputs, keep the successful result’s identifiers with the task, and refresh a lookup only when the information changed.

A change is waiting or failed

Check whether the call awaits approval, was rejected by policy, lacks an input, or failed at the provider, and after a timeout inspect the destination before repeating a write.

See how an action proceeds and how to review an approval.

Questions about the Moonshot AI (Kimi) connector

Can I use my existing agent with Moonshot AI (Kimi)?

Yes: connect your agent to Deixic through MCP, choose which connected tools it can use, and Deixic checks calls routed through its gateway; Dex is available if your team also wants an agent.

Can an agent change data in Moonshot AI (Kimi)?

This connector supports 2 actions, listed on its overview page. Configure a connection and choose the tools and provider permissions your task needs; an available action is not permission for every agent to run it, and Deixic policy and any required approval still apply to calls through the gateway.

What do I need to connect Moonshot AI (Kimi)?

Prepare API key; the connection uses Bearer token, and the connected identity’s provider permissions determine which resources it can access.

Does connecting Moonshot AI (Kimi) keep every answer up to date?

No: an earlier answer is still an earlier answer, so for a decision that depends on current state, have the agent refresh the source and retain the lookup time, and save stable instructions separately from facts that can change.

Moonshot AI (Kimi) connector overview Docs All connectors