> For the complete documentation index, see [llms.txt](https://docs.ai.neevcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ai.neevcloud.com/api-reference/tenant.md).

# Tenant API

The Tenant API is the identity and account-management layer of the NeevAI platform. It handles everything that happens before you provision GPUs or call a model: authenticating users, organizing them into organizations and projects, managing team membership, and issuing the API keys that authorize every other NeevAI service.

The `access_token` returned by **`POST /api/v1/auth/login`** is the credential used across the entire platform — the same token authenticates the Tenant, AI Runtime (GPU Instance), and Dedicated Model Deployment APIs.

## What you can do

* **Authentication & sessions** — sign up, log in, log out, refresh access tokens, and run the full password-reset flow (`forgot-password` / `reset-password`).
* **Account verification** — verify email and phone, add a phone number, and resend verification codes.
* **User profile** — fetch the current user (`/users/me`), change the password, and delete the account.
* **Organizations** — list the organizations you belong to, read and update organization details, and manage organization members (add / list / remove).
* **Projects** — create and list projects within an organization, read and update a project, and manage per-project membership.
* **API keys** — create, list, and revoke the project-scoped API keys that authorize storage, runtime, and inference calls.
* **Referrals** — view an organization's referral records.

Use the interactive reference below to inspect request and response schemas and try each endpoint directly.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ai.neevcloud.com/api-reference/tenant.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.