Quickstart

Prerequisites

• An Interlocute account — sign up free
• An API key (see Auth & Keys)
• A node — create one from the dashboard

1. Send a message (cURL)

Replace my-node with your node's alias from the dashboard.

curl -X POST https://my-node.interlocute.ai/chat \
  -H "Authorization: Bearer $INTERLOCUTE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "Hello! What can you help me with?"
  }'

2. Read the response

You'll receive a JSON response containing the node's reply and usage data:

{
  "threadId": "thr_abc123",
  "message": {
    "role": "assistant",
    "content": "Hello! I'm your Interlocute node. I can help you with..."
  },
  "usage": {
    "inputTokens": 12,
    "outputTokens": 34,
    "computationTokens": 2
  }
}

3. Continue the conversation

Pass the threadId from the response to maintain conversation state:

curl -X POST https://my-node.interlocute.ai/chat \
  -H "Authorization: Bearer $INTERLOCUTE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "Tell me more about that.",
    "threadId": "thr_abc123"
  }'

Same thing in C#

using var http = new HttpClient();
http.DefaultRequestHeaders.Authorization =
    new System.Net.Http.Headers.AuthenticationHeaderValue(
        "Bearer", Environment.GetEnvironmentVariable("INTERLOCUTE_API_KEY"));

var response = await http.PostAsJsonAsync(
    "https://my-node.interlocute.ai/chat",
    new { content = "Hello from C#!" });

var result = await response.Content.ReadAsStringAsync();
Console.WriteLine(result);

Same thing in JavaScript

const response = await fetch(
  "https://my-node.interlocute.ai/chat",
  {
    method: "POST",
    headers: {
      "Authorization": `Bearer ${process.env.INTERLOCUTE_API_KEY}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({ content: "Hello from JS!" }),
  }
);

const data = await response.json();
console.log(data);

What just happened

• You invoked an addressable node at its stable subdomain — https://my-node.interlocute.ai
• The request hit /chat — the node's interactive conversation surface
• The request was authenticated via your API key and checked against the node's policies
• A thread was created (or continued) to track conversation state
• The response was logged with full token accounting and cost attribution
• Policies were evaluated — if the node had quotas or refusal rules, they would have been enforced

Common issues

Next steps

• Auth & Keys — secure setup, key rotation, and scoping
• Chat & Chit — the /chat and /chit surfaces