Skip to main content
POST
/
api
/
v2
/
memories
/
semantic
/
set_id
/
get
Get Semantic Set Id
curl --request POST \
  --url http://localhost:8080/api/v2/memories/semantic/set_id/get \
  --header 'Content-Type: application/json' \
  --data '
{
  "metadata_tags": [
    "<string>"
  ],
  "org_id": "universal",
  "project_id": "universal",
  "is_org_level": false,
  "set_metadata": {}
}
'
{
  "set_id": "<string>"
}

Body

application/json

Specification model for getting a semantic set ID.

​
metadata_tags
string[]
required
Ordered list of metadata tag keys that define this set type. These tags
determine how set IDs are generated and grouped. For example,
["user_id", "session_id"] means sets are grouped by user and session.
​
org_id
string
default:universal
The unique identifier of the organization.

- Must not contain slashes (`/`).
- Must contain only letters, numbers, underscores, hyphens, colon, and Unicode
  characters (e.g., Chinese/Japanese/Korean). No slashes or other symbols
  are allowed.

This value determines the namespace the project belongs to.
Examples:

"MemVerge"

"AI_Labs"

​
project_id
string
default:universal
The identifier of the project.

- Must be unique within the organization.
- Must not contain slashes (`/`).
- Must contain only letters, numbers, underscores, hyphens, colon, and Unicode
  characters (e.g., Chinese/Japanese/Korean). No slashes or other symbols
  are allowed.

This ID is used in API paths and resource locations.
Examples:

"memmachine"

"research123"

"qa_pipeline"

​
is_org_level
boolean
default:false
Whether the set type is scoped at the organization level (True) or
project level (False). Org-level sets are shared across all projects
within the organization.
​
set_metadata
Set Metadata · object
Optional metadata key-value pairs used to filter or identify semantic sets.

Response

Successful Response

Response model for getting a semantic set ID.

​
set_id
string
required

Identifier of the semantic set.