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

.txt chat API

Create model responses for chat conversations.Supports:- **Multi-turn dialogue** with conversation history- **System prompts** to control model behavior- **Tool calling** for function execution and structured outputs- **Streaming** for real-time token delivery- **Sampling parameters** like temperature, top_p, and frequency penalties

.txt chat API is one of 6 APIs that .txt publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 1 operation across 1 path, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.dottxt.ai/v1.

1 operations 1 paths 12 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.dottxt.ai/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

.txt chat API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (API Key) (BearerAuth).

  • BearerAuth — API key authentication. Include your key in the Authorization header: Authorization: Bearer YOURAPIKEY API keys can be created and managed in the dashboard.

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

chat 1

Create model responses for chat conversations. Supports: - Multi-turn dialogue with conversation history - System prompts to control model behavior - Tool calling for function exe…

POST
/chat/completions
Create chat completion
chat_completions body → 200400401402403404429500

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are ChatCompletionRequest (15 properties), ChatCompletionResponse (7 properties), ChatMessage (5 properties), OpenAIError (4 properties). Each schema is shown below with its type and property counts.

ChatCompletionRequest
object
Request body for chat completions.
15 properties 2 required
JsonPatchOperation
object
An RFC 6902 JSON Patch operation, emitted one per line (NDJSON) or per SSE event when stream: "patch" is set on /chat/completions. The first record seeds the d…
3 properties 3 required
ChatCompletionResponse
object
Response from chat completions.
7 properties 5 required
Usage
object
Token usage statistics.
3 properties 3 required
FunctionDefinition
object
Definition of a function that can be called by the model.
3 properties 1 required
ChatMessage
object
A message in a chat conversation.
5 properties 1 required
ChatChoice
object
A chat completion choice.
3 properties 2 required
OpenAIError
object
OpenAI-compatible error details.
4 properties 2 required
ToolCall
object
A tool call made by the model.
3 properties 3 required
Tool
object
A tool that the model may call.
2 properties 2 required
OpenAIErrorResponse
object
OpenAI-compatible error response.
1 property 1 required
FunctionCall
object
A function call within a tool call.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

txt-chat-api-openapi.yml Raw ↑

Other APIs .txt publishes across the network.

.txt batches API
.txt embeddings API
.txt files API
.txt models API
.txt responses-api API
Where this information came from

This is an independent, third-party profile of .txt chat 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.