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

HTTP endpoints

HTTP: connections

All 7 connections 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/connections

Read connections.

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

POST /v1/connections

Create connection.

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/connections/{id}

Delete connection.

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/connections/{id}

Patch connection.

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/connections/{id}/dependencies

Read connection dependencies.

Path parameters: id.

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

GET /v1/connections/{id}/models

Read connection models.

Path parameters: id.

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

POST /v1/connections/{id}/verify

Verify connection.

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.