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

Terminal Use Namespaces API

The Namespaces API from Terminal Use — 5 operation(s) for namespaces.

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

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

8 operations 5 paths 8 schemas 1 DELETE4 GET1 PATCH2 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 8

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

Namespaces 8
GET
/namespaces
List Namespaces
namespaces_list 3 params → 200422
POST
/namespaces
Create Namespace
namespaces_create body → 201422
GET
/namespaces/slug-availability/{slug}
Check Slug Availability
namespaces_check_slug_availability 1 param → 200422
GET
/namespaces/slug/{slug}
Get Namespace by Slug
namespaces_retrieve_by_slug 1 param → 200422
DELETE
/namespaces/{namespace_id}
Delete Namespace
namespaces_delete 1 param → 200422
GET
/namespaces/{namespace_id}
Get Namespace
namespaces_retrieve 1 param → 200422
PATCH
/namespaces/{namespace_id}
Update Namespace
namespaces_update 1 param body → 200422
POST
/namespaces/{namespace_id}/retry-provisioning
Retry Namespace Provisioning
namespaces_retry_provisioning 2 params → 200422

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are Namespace (14 properties), ValidationError (3 properties), CreateNamespaceRequest (3 properties), SlugAvailabilityResponse (2 properties). Each schema is shown below with its type and property counts.

UpdateNamespaceRequest
object
Request model for updating a namespace. Infrastructure fields (k8snamespace, gcsbucket, gcpsaemail) are NOT exposed here — they are set exclusively by the prov…
1 property
Namespace
object
Response model for namespace.
14 properties 5 required
HTTPValidationError
object
1 property
CreateNamespaceRequest
object
Request model for creating a namespace.
3 properties 3 required
ValidationError
object
3 properties 3 required
SlugAvailabilityResponse
object
Response for slug availability check.
2 properties 2 required
NamespaceStatus
string
Status of namespace infrastructure provisioning.
DeleteResponse
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Terminal Use publishes across the network.

Terminal Use Agent APIKeys API
Terminal Use Agent Task Tracker API
Terminal Use Agents API
Terminal Use API Keys API
Terminal Use Authentication API
Terminal Use Branch Events API
Terminal Use Branches API
Terminal Use Builds API
Terminal Use CLI Authentication API
Terminal Use Environments API
Terminal Use Events API
Terminal Use Filesystems API
Where this information came from

This is an independent, third-party profile of Terminal Use Namespaces 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.