> ## Documentation Index
> Fetch the complete documentation index at: https://docs.minenet.pro/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Overview of Minenet Client API authentication, scope boundaries, and how this reference is generated.

The Minenet Client API v1 provides bearer-token access to team-scoped operations for deployments, servers, snapshots, files, and mod platform metadata.

For deployments, the normal workflow is:

1. create or update configuration,
2. push a configuration version,
3. apply the latest pushed version.

## Base path

```text theme={null}
/api/client/v1
```

## API scope and stability

This reference documents the public Client API surface.

Only endpoints under `/api/client/v1` are considered stable integration contracts for external automation.

Other app routes (for example `/api/compute-resources/*`, `/api/swiftbase/*`, `/api/teams/*`, `/api/system/*`) are internal product APIs and may change without compatibility guarantees.

## Authentication

All routes require a bearer token.

```bash theme={null}
Authorization: Bearer <token>
```

Supported token prefixes:

* `mnp_`: team API token
* `mna_`: team agent token

## Rate limiting

* Global: 100 requests per minute per token.
* Endpoint-specific limits: applied on selected mutating endpoints. Responses include `Retry-After` when limited.

## Reference source

This API reference is generated from OpenAPI using Mintlify's `openapi` integration in `docs.json`.

Source file:

```text theme={null}
api-reference/openapi.yaml
```