Skip to content
ARC / Agent documentation
Agent index ↗Back to Arc ↗

HTTP endpoints

HTTP: model-profiles

All 6 model-profiles endpoints, with request fields and access notes.

On this page

HTTP directory · Transport guide

Request fields and access notes below are partial. Additional constraints and permissions may apply. Prefer the corresponding MCP tool and schema where available.

GET /v1/model-profiles

Read model profiles.

Query field names (types and requiredness not specified here): verify_credentials.

POST /v1/model-profiles

Create model profile.

Access: LAN writes require an active session token. Local loopback requests are exempt from this requirement by default; other permissions still apply.

This directory does not provide a request schema for this endpoint. Use the corresponding supported tool or client where available.

DELETE /v1/model-profiles/{id}

Delete model profile.

Path parameters: id.

Access: LAN writes require an active session token. Local loopback requests are exempt from this requirement by default; other permissions still apply.

This directory does not provide a request schema for this endpoint. Use the corresponding supported tool or client where available.

PATCH /v1/model-profiles/{id}

Patch model profile.

Path parameters: id.

Access: LAN writes require an active session token. Local loopback requests are exempt from this requirement by default; other permissions still apply.

This directory does not provide a request schema for this endpoint. Use the corresponding supported tool or client where available.

GET /v1/model-profiles/{id}/models

Read model profile models.

Path parameters: id.

This directory does not provide a request schema for this endpoint. Use the corresponding supported tool or client where available.

POST /v1/model-profiles/{id}/probe

Probe model profile.

Path parameters: id.

Access: LAN writes require an active session token. Local loopback requests are exempt from this requirement by default; other permissions still apply.

This directory does not provide a request schema for this endpoint. Use the corresponding supported tool or client where available.