POST /v1/local-models

Local models. Permissions, parameters, responses and examples.

Private service protocols are unsupported for external integration. Their schemas describe source declarations; they are not public service endpoints.

Local models

Local models through POST /v1/local-models. The parameters and declared response shapes below come from this exact source snapshot.

Internal protocol; unsupported for external integration. This page makes no request to a local installation.

Authority

Private service protocol. No public or third-party integration authority.

Inspect the authority source · Authentication guide

Parameters and headers

No explicit path, query or header parameters are declared here. The authority boundary still applies.

Request body

No typed JSON body is declared by this handler. That does not rule out source-level request parsing; inspect the pinned implementation, especially for internal connector protocols.

Responses

Status	Meaning and declared shape
`200`	Successful Response application/json · object `{ "additionalProperties": true, "title": "Response Local Models V1 Local Models Post", "type": "object" }`
`413`	Reduce the authorized capture to the documented size and file limits. See source-linked error catalog.
`422`	Correct the field or semantic validation error. Input values are omitted from control validation errors. See source-linked error catalog.

An empty or broad schema preserves the source contract. It is not a promise of an empty response.

Source-linked errors

Literal HTTP errors in this handler and same-file helper call graph, plus control middleware. Dynamic and cross-module failures may add other errors; source links are authoritative.

5 source error observations

Status	Source detail	Recovery
413 ↗	`connector request exceeds the bounded size`	Reduce the authorized capture to the documented size and file limits.
413 ↗	`connector request exceeds the bounded size`	Reduce the authorized capture to the documented size and file limits.
413 ↗	`invalid request length`	Reduce the authorized capture to the documented size and file limits.
422 ↗	`request fields do not match the connector contract`	Correct the field or semantic validation error. Input values are omitted from control validation errors.
422 ↗	`request must be one strict UTF-8 JSON object`	Correct the field or semantic validation error. Input values are omitted from control validation errors.

Read the recovery guide

Synthetic examples

These examples validate declared JSON shapes and formats. They contain no real installation data and do not prove runtime admission, cross-field validation, authority or successful work.

Response 200 JSON

{}