How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Terminal Use

Terminal Use Logs API

The Logs API from Terminal Use — 3 operation(s) for logs.

Documentation Provider Profile APIs.io OpenAPI GitHub

Terminal Use Logs API is one of 28 APIs that Terminal Use publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Logs. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 3 operations across 3 paths, and defines 20 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against a single base URL, https://api.terminaluse.com.

3 operations 3 paths 20 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.terminaluse.com
Resource Areas
1

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Logs 3
GET
/logs
List Agent Logs
logs_list 12 params → 200422
POST
/logs/otlp
Ingest Agent Logs (OTLP Format)
logs_ingest_otlp body → 200422
GET
/logs/stream
Stream Agent Logs
logs_stream 5 params → 200422

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are LogQueryEntry (13 properties), LogStreamLogEvent (12 properties), OTLPLogRecord (7 properties), OTLPAttributeValue (6 properties). Each schema is shown below with its type and property counts.

LogLevel
string
Log level for entries.
ValidationError
object
3 properties 3 required
OTLPScope
object
OTLP instrumentation scope.
2 properties
LogStreamConnectedEvent
object
Sent when SSE log stream connection is established. Indicates the client is now subscribed and will receive new logs. Only logs generated AFTER this event will…
2 properties 1 required
LogSource
string
Source of the log entry.
OTLPAttributeValue
object
OTLP attribute value supporting multiple types. Per OTLP JSON spec, intValue is transmitted as a string to avoid JSON number precision issues with int64 values…
6 properties
OTLPLogIngestionRequest
object
OTLP log data in JSON format.
1 property 1 required
LogQueryEntry
object
A log entry returned from queries.
13 properties 6 required
HTTPValidationError
object
1 property
LogStreamEvent
Union of all possible log stream SSE events. Use the 'type' field to discriminate between event types: - "connected": Stream connection established - "log": A…
OTLPScopeLogs
object
OTLP scope logs containing log records.
2 properties
OTLPResourceLogs
object
OTLP resource logs container.
2 properties
OTLPLogRecord
object
OTLP log record. The body field (message content) is limited to MAXMESSAGELENGTH (64KB). Messages exceeding this limit are truncated with a "[TRUNCATED]" indic…
7 properties
OTLPBodyValue
object
OTLP body value for log record messages. Unlike OTLPAttributeValue, this class does NOT have maxlength constraints on stringValue. This allows the OTLPLogRecor…
6 properties
LogStreamLogEvent
object
A log entry in the SSE stream. Wraps LogQueryEntry fields with a type discriminator for SDK parsing.
12 properties 6 required
LogListResponse
object
Response from logs list endpoint.
3 properties 3 required
OTLPLogIngestionResponse
object
Response from OTLP log ingestion endpoint.
2 properties 1 required
OTLPAttribute
object
OTLP key-value attribute.
2 properties 2 required
OTLPResource
object
OTLP resource with attributes.
1 property
LogStreamErrorEvent
object
Sent when an error occurs in the log stream. After this event, the stream may close or attempt recovery.
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

terminal-use-logs-api-openapi.yml Raw ↑

Other APIs Terminal Use publishes across the network.

Terminal Use Agent APIKeys API
AE Profile APIs.io
Terminal Use Agent Task Tracker API
AE Profile APIs.io
Terminal Use Agents API
AE Profile APIs.io
Terminal Use API Keys API
AE Profile APIs.io
Terminal Use Authentication API
AE Profile APIs.io
Terminal Use Branch Events API
AE Profile APIs.io
Terminal Use Branches API
AE Profile APIs.io
Terminal Use Builds API
AE Profile APIs.io
Terminal Use CLI Authentication API
AE Profile APIs.io
Terminal Use Environments API
AE Profile APIs.io
Terminal Use Events API
AE Profile APIs.io
Terminal Use Filesystems API
AE Profile APIs.io
#Logs
← Back to T APIs
API Details
ID
terminal-use:terminal-use-logs-api
Base URL
https://api.terminaluse.com
Docs
https://docs.terminaluse.com
Provider
Terminal Use
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=terminal-use-logs-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/terminal-use-logs-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Terminal Use Logs API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.