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

The Filesystems API from Terminal Use — 9 operation(s) for filesystems.

Documentation Provider Profile APIs.io OpenAPI GitHub

Terminal Use Filesystems 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 Filesystem. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 10 operations across 9 paths, and defines 14 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.

10 operations 9 paths 14 schemas 5 GET4 POST1 PUT

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 10

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

Filesystems 10
GET
/filesystems
List Filesystems
filesystems_list 1 param → 200422
POST
/filesystems
Create Filesystem
filesystems_create body → 201422
GET
/filesystems/{filesystem_id}
Get Filesystem
filesystems_retrieve 1 param → 200422
POST
/filesystems/{filesystem_id}/download-url
Get Download URL
filesystems_get_download_url 1 param body → 200422
GET
/filesystems/{filesystem_id}/file-download
Download File
filesystems_download_file 2 params → 200422
PUT
/filesystems/{filesystem_id}/file-upload
Upload File
filesystems_upload_file 8 params body → 200201400404409412422428
GET
/filesystems/{filesystem_id}/files
List Files
filesystems_list_files 7 params → 200422
GET
/filesystems/{filesystem_id}/files/{file_path}
Get File
filesystems_get_file 3 params → 200422
POST
/filesystems/{filesystem_id}/sync-complete
Complete Sync Operation
filesystems_sync_complete 1 param body → 200422
POST
/filesystems/{filesystem_id}/upload-url
Get Upload URL
filesystems_get_upload_url 1 param body → 200422

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are FilesystemResponse (11 properties), FilesystemFileResponse (10 properties), FilesystemFile (9 properties), SingleFileUploadResponse (7 properties). Each schema is shown below with its type and property counts.

FilesystemStatus
string
Filesystem lifecycle status states.
FileUploadWriteMode
string
Single-file upload write semantics.
HTTPValidationError
object
1 property
PresignedUrlRequest
object
Request model for presigned URL generation.
1 property
SyncCompleteResponse
object
Response model for sync-complete operation.
4 properties 4 required
FilesystemCreate
object
Request model for creating a filesystem. Filesystems inherit permissions from their parent project.
2 properties 1 required
FilesystemFile
object
File metadata - used for both input (sync-complete) and as base for response.
9 properties 2 required
ValidationError
object
3 properties 3 required
ListFilesResponse
object
Response model for listing files in a filesystem.
4 properties 3 required
PresignedUrlResponse
object
Response model for presigned URL operations.
5 properties 4 required
SingleFileUploadResponse
object
Response model for single-file upload operations.
7 properties 7 required
SyncCompleteRequest
object
Request model for completing a sync operation.
6 properties 3 required
FilesystemFileResponse
object
File metadata response - adds server-side fields.
10 properties 3 required
FilesystemResponse
object
Response model for filesystem operations.
11 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

terminal-use-filesystems-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 Groups API
AE Profile APIs.io
#Filesystem
← Back to T APIs
API Details
ID
terminal-use:terminal-use-filesystems-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-filesystems-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/terminal-use-filesystems-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 Filesystems 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.