curl --request POST \
--url https://api.memmachine.ai/v2/projects \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"project_id": "",
"description": "Test project for RAG pipeline"
}
'{
"org_id": "<string>",
"project_id": "<string>",
"config": {
"embedder": "bge-base-en",
"reranker": "bge-reranker-large"
},
"description": ""
}Create Project
Create a new project.
This endpoint creates a new project with the given identifier and
configuration. The project_id follows the rules: no slashes; only
letters, numbers, underscores, hyphens, colon, and Unicode characters.
Each project acts as an isolated memory namespace. All memories (episodes) inserted into a project belong exclusively to that project. Queries, listings, and any background operations such as memory summarization or knowledge extraction only access data within the same project. No cross-project memory access is allowed.
If a project with the same ID already exists, the request will fail with an error.
Returns the fully resolved project record, including configuration defaults applied by the system.
curl --request POST \
--url https://api.memmachine.ai/v2/projects \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"project_id": "",
"description": "Test project for RAG pipeline"
}
'{
"org_id": "<string>",
"project_id": "<string>",
"config": {
"embedder": "bge-base-en",
"reranker": "bge-reranker-large"
},
"description": ""
}Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Specification model for creating a new project.
The project ID must be unique for the authenticated user.
The identifier of the project. If empty, the user's default project is used.
^[\p{L}\p{N}_:-]*$A human-readable description of the project. Used for display purposes in UIs and dashboards. Optional; defaults to an empty string.
"Test project for RAG pipeline"
Response
Successful Response
Response model returned after project operations (e.g., creation, update, fetch).
Contains the resolved identifiers and configuration of the project as stored
in the system. Field formats follow the same validation rules as in
CreateProjectSpec.
The unique identifier of the organization this project belongs to.
Returned exactly as stored by the system.
The identifier of the project.
This value uniquely identifies the project within the organization.
Project configuration model.
This section defines which reranker and embedder models should be used for the project. If any field is left empty (""), the system automatically falls back to the globally configured defaults in the server configuration file.
Show child attributes
Show child attributes
A human-readable description of the project. Used for display purposes in UIs and dashboards. Optional; defaults to an empty string.