interlocute.ai beta
Create a node

Observability & Logging

Full visibility into every node interaction — requests, responses, tool calls, token usage, and costs. Built into the platform, not bolted on.

Try Interlocute Read the docs

What is AI observability?

Observability means having full visibility into what your AI nodes are doing: every request, every response, every tool call, every token consumed. Interlocute logs all of this automatically — there is nothing to configure and no third-party integration required.

Why it matters

AI systems are inherently opaque. Without observability, you cannot debug unexpected responses, track costs, or demonstrate compliance. Built-in logging makes your AI operations transparent and auditable from day one.

Token usage and cost tracking

Every node interaction includes detailed token accounting: input tokens, output tokens, and computation tokens. Costs are calculated and attributed to the specific node and API key, giving you granular visibility into what each use case costs.

Audit-ready logging

Every interaction is logged with timestamps, request/response content, tool invocations, and token counts. These logs are accessible through the dashboard and API, making it straightforward to investigate issues or satisfy compliance requirements.

Frequently Asked Questions

Observability & Logging

What does Interlocute log for each node interaction?
Every interaction is logged with the full request, response, any tool invocations, token counts (input, output, computation), latency, and the API key used. Logs are available through the dashboard and API.
Do I need to set up a logging pipeline?
No. Logging is built into the platform and enabled by default. Every node interaction is automatically logged with no configuration required. You can access logs through the dashboard or query them via the API.
How does Interlocute track token usage and costs?
Every request includes detailed token accounting broken down by input tokens, output tokens, and computation tokens. Costs are calculated per interaction and attributed to the specific node and API key for granular billing visibility.
Can I use observability data for debugging?
Yes. Logs include the full request and response content, tool call details, and any errors. This makes it straightforward to investigate unexpected behavior, trace issues to specific inputs, and understand why the LLM produced a particular response.
Is observability data available in real time?
Interaction logs are available shortly after each request completes. The dashboard provides a near-real-time view of node activity, and the API supports querying recent interactions for programmatic access.
How long are logs retained?
Log retention depends on your plan. All plans include a retention window sufficient for debugging and operational visibility. Contact us for extended retention requirements or compliance-driven archival needs.

Documentation

Observability Guide API Reference

Related Features

Commercial Control

Govern usage, enforce quotas, and maintain cost visibility across all your AI nodes. Built for teams that need accountability.

Guardrails & Governance

Control what your AI can do with granular policies — token quotas, refusal semantics, access restrictions, and execution boundaries.

Tool Use & Function Calling

Let your AI nodes call external tools and APIs. Pre-configured function calling with governed execution, built into the runtime.

Ready to build with Observability & Logging?

Deploy your node in seconds and start using Observability & Logging today.

Try Interlocute Read the docs