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

Smithery namespaces API

The namespaces API from Smithery — 3 operation(s) for namespaces.

Smithery namespaces API is one of 9 APIs that Smithery publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 3 JSON Schema definitions.

Tagged areas include Namespaces. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a JSON-LD context, rate-limit docs, and 3 JSON Schemas.

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

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

5 operations 3 paths 7 schemas 1 DELETE1 GET1 POST2 PUT

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.smithery.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Smithery namespaces API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Smithery API key as Bearer token

Paths & Operations 5

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

namespaces 5
GET
/namespaces
Get user's namespaces or search namespaces
getNamespaces 7 params → 200401500
POST
/namespaces
Create a new namespace with generated name
postNamespaces → 201400401403
PUT
/namespaces/{name}
Create a new namespace
putNamespaces:name 1 param → 201400401403409
DELETE
/namespaces/{name}
Delete a namespace
deleteNamespaces:name 1 param → 200401403404409
PUT
/namespaces/{namespace}/servers/{server}deprecated
Create a server under a namespace (deprecated)
putNamespaces:namespaceServers:server 2 params body → 201400401403404

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are CreateServerResponse (5 properties), CreateNamespaceResponse (2 properties), NamespacesSearchResponse (2 properties), CreateServerRequest (2 properties). Each schema is shown below with its type and property counts.

CreateServerError
object
1 property 1 required
NamespacesError
object
1 property 1 required
CreateServerRequest
object
2 properties
NamespacesSearchResponse
object
2 properties 2 required
CreateNamespaceResponse
object
2 properties 2 required
NamespaceSearchResult
object
1 property 1 required
CreateServerResponse
object
5 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

smithery-namespaces-api-openapi.yml Raw ↑

Other APIs Smithery publishes across the network.

Smithery connect API
Smithery connect.mcp API
Smithery domains API
Smithery Health API
Smithery organizations API
Smithery servers API
Smithery skills API
Smithery tokens API
Where this information came from

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