Moonshot AI · Schema
BatchObject
Artificial IntelligenceLLMInferenceLong ContextKimiFoundation Models
Properties
| Name | Type | Description |
|---|---|---|
| id | string | Unique identifier for the batch task |
| object | string | Object type, always batch |
| endpoint | string | Request endpoint |
| input_file_id | string | Input file ID |
| completion_window | string | Processing time window |
| status | string | Current status: validating, failed, in_progress, finalizing, completed, expired, cancelling, cancelled |
| output_file_id | stringnull | Output file ID for successful results |
| error_file_id | stringnull | Error file ID for failed results |
| created_at | integer | Creation timestamp (Unix) |
| in_progress_at | integernull | Execution start timestamp (Unix) |
| expires_at | integernull | Expiration timestamp (Unix) |
| finalizing_at | integernull | Result preparation start timestamp (Unix) |
| completed_at | integernull | Completion timestamp (Unix) |
| failed_at | integernull | Validation failure timestamp (Unix) |
| cancelling_at | integernull | Cancellation request timestamp (Unix) |
| cancelled_at | integernull | Cancellation completion timestamp (Unix) |
| request_counts | object | |
| metadata | objectnull | Custom metadata |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/moonshot-ai/main/json-schema/moonshot-ai-batch-object-schema.json",
"title": "BatchObject",
"x-generated": "2026-10-13",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/moonshot-ai-batch-api-openapi.yml#/components/schemas/BatchObject",
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Unique identifier for the batch task"
},
"object": {
"type": "string",
"description": "Object type, always batch"
},
"endpoint": {
"type": "string",
"description": "Request endpoint"
},
"input_file_id": {
"type": "string",
"description": "Input file ID"
},
"completion_window": {
"type": "string",
"description": "Processing time window"
},
"status": {
"type": "string",
"description": "Current status: validating, failed, in_progress, finalizing, completed, expired, cancelling, cancelled",
"enum": [
"validating",
"failed",
"in_progress",
"finalizing",
"completed",
"expired",
"cancelling",
"cancelled"
]
},
"output_file_id": {
"type": [
"string",
"null"
],
"description": "Output file ID for successful results"
},
"error_file_id": {
"type": [
"string",
"null"
],
"description": "Error file ID for failed results"
},
"created_at": {
"type": "integer",
"description": "Creation timestamp (Unix)"
},
"in_progress_at": {
"type": [
"integer",
"null"
],
"description": "Execution start timestamp (Unix)"
},
"expires_at": {
"type": [
"integer",
"null"
],
"description": "Expiration timestamp (Unix)"
},
"finalizing_at": {
"type": [
"integer",
"null"
],
"description": "Result preparation start timestamp (Unix)"
},
"completed_at": {
"type": [
"integer",
"null"
],
"description": "Completion timestamp (Unix)"
},
"failed_at": {
"type": [
"integer",
"null"
],
"description": "Validation failure timestamp (Unix)"
},
"cancelling_at": {
"type": [
"integer",
"null"
],
"description": "Cancellation request timestamp (Unix)"
},
"cancelled_at": {
"type": [
"integer",
"null"
],
"description": "Cancellation completion timestamp (Unix)"
},
"request_counts": {
"$ref": "#/$defs/BatchRequestCounts"
},
"metadata": {
"type": [
"object",
"null"
],
"description": "Custom metadata",
"additionalProperties": {
"type": "string"
}
}
},
"required": [
"id",
"object",
"endpoint",
"input_file_id",
"completion_window",
"status",
"created_at",
"request_counts"
],
"$defs": {
"BatchRequestCounts": {
"type": "object",
"properties": {
"completed": {
"type": "integer",
"description": "Number of completed requests"
},
"failed": {
"type": "integer",
"description": "Number of failed requests"
},
"total": {
"type": "integer",
"description": "Total number of requests"
}
},
"required": [
"completed",
"failed",
"total"
]
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/moonshot-ai-batch-object"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.