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 files API

Upload and manage JSONL files for batch processing.Each line in the file should be a JSON object with:- `custom_id` - your identifier for tracking the request- `method` - HTTP method (POST)- `url` - endpoint path (e.g., `/v1/chat/completions`)- `body` - the request payload[Learn more about the JSONL file format →](https://docs.doubleword.ai/batches/jsonl-files)

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

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

This API exposes 6 operations across 4 paths, and defines 8 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.

6 operations 4 paths 8 schemas 1 DELETE4 GET1 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 files 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 6

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

files 6

Upload and manage JSONL files for batch processing. Each line in the file should be a JSON object with: - customid - your identifier for tracking the request - method - HTTP metho…

GET
/files
List files
list_files 4 params → 200500
POST
/files
Upload file
upload_file body → 201400403413429500
GET
/files/{file_id}
Retrieve file
get_file 1 param → 200404500
DELETE
/files/{file_id}
Delete file
delete_file 1 param → 200404500
GET
/files/{file_id}/content
Retrieve file content
get_file_content 3 params → 200404500
GET
/files/{file_id}/cost-estimate
Get file cost estimate
get_file_cost_estimate 2 params → 200404500

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are FileResponse (7 properties), FileCostEstimate (6 properties), ModelCostBreakdown (5 properties), FileListResponse (5 properties). Each schema is shown below with its type and property counts.

FileListResponse
object
Response for file list
5 properties 3 required
ObjectType
string
Object type - always "file"
ModelCostBreakdown
object
Per-model cost breakdown
5 properties 5 required
FileResponse
object
File object response (OpenAI-compatible)
7 properties 6 required
FileDeleteResponse
object
Response for file deletion
3 properties 3 required
ListObject
string
Object type for lists - always "list"
Purpose
string
Purpose for file
FileCostEstimate
object
Response for file cost estimation
6 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

txt-files-api-openapi.yml Raw ↑

Other APIs .txt publishes across the network.

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

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