interlocute.ai beta
+Node

API Overview

The Interlocute API is a means to invoke nodes. Start from goals, not endpoints.

Philosophy

The Interlocute API is not the product — it is the interface to the product. Start from what you want your node to do, then find the endpoint that does it. The API surface is intentionally small: most interactions use a single endpoint.

For the full OpenAPI specification, see the API reference. This page covers the concepts that make the reference useful.

Node addressing

Every node is addressable by its alias. The base URL for any node is: 

https://YOUR-NODE-ALIAS.interlocute.ai

Replace YOUR-NODE-ALIAS with the alias you chose when creating your node (visible on the dashboard). All endpoints are relative to this base.

Routes

Every API endpoint supports three equivalent routing patterns. All accept the same request bodies and return the same responses. The docs use the alias (subdomain) form throughout — but all three work interchangeably.

Pattern Example When to use
Alias (subdomain) https://my-node.interlocute.ai/chat Default. Shortest URL, human-readable. Used throughout these docs.
Path-based (node ID) https://api.interlocute.ai/nodes/{nodeId}/chat When you have the raw node GUID and don't know the alias.
Path-based (alias) https://api.interlocute.ai/nodes/my-node/chat When subdomain routing isn't available in your environment.
The alias subdomain pattern is recommended for all new integrations. The path-based patterns exist for environments where custom subdomains are restricted (e.g., corporate proxies).

Concept mapping

node alias

The stable subdomain for your node. Found on the dashboard. Forms the base URL: https://YOUR-NODE-ALIAS.interlocute.ai.

threadId

Identifies a conversation. Omit to start a new thread; include to continue an existing one. Returned in every response.

content

The user's message text. Required in /chat requests.

usage

Token accounting returned with every response: input tokens, output tokens, computation tokens.

Primary endpoints

POST /chat

Send a message to the node. Supports buffered JSON and SSE streaming via Accept header. See Chat API Reference.

GET /chit

Deterministic node information sheet for discovery and governance. See Chit API Reference.

GET /chit/identity

Node identity and capabilities — primary v1 starting point for /chit. See Chit API Reference.

POST /inform

Feed knowledge into the node — text, documents, images. Async processing with polling. See Inform API Reference.

POST /media/audio/transcribe

Audio-to-text transcription. Capability-gated — requires media.audio.transcribe. See Audio Transcribe API.

Error model

Error responses follow a consistent structure:

{
  "error": {
    "code": "quota_exceeded",
    "message": "Token quota for this key has been reached.",
    "status": 429
  }
}
401

Missing or invalid API key

403

Key lacks required scope

400

Malformed request body

422

Policy refusal — the node declined the request

429

Quota exceeded or rate limited

Next steps

TriggersChat API Reference