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

Memories Serve API

The Serve API from Memories — 30 operation(s) for serve.

Memories Serve API is one of 3 APIs that Memories publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Serve. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 30 operations across 30 paths, and defines 35 schemas. It is described by OpenAPI 3.1.0, at version v1.

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

30 operations 30 paths 35 schemas 7 GET23 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v1
Base URL
https://api.memories.ai
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Memories Serve API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (ApiKeyAuth). By default, every request must be authenticated.

Paths & Operations 30

Across 30 paths, the API surfaces 30 operations — 7 GET, 23 POST. Each is listed below with its method, path, parameters, and response codes.

Serve 30
POST
/serve/api/v1/memories/add
Add Memory
add_memory body → 200
GET
/serve/api/v1/get_audio_transcription
Get Audio Transcription
get_audio_transcription 1 param → 200
POST
/serve/api/v1/delete_videos
Delete Videos
delete_videos body → 200
POST
/serve/api/v1/download
Download Video
download_video body → 200
GET
/serve/api/v1/get_video_ids_by_task_id
Get Task Status
get_task_status 1 param → 200
POST
/serve/api/v1/memories
List Memories
list_memories body → 200
GET
/serve/api/v1/get_metadata
Get Video Metadata
get_video_metadata 1 param → 200
POST
/serve/api/v1/list_videos
List Videos
list_videos body → 200
POST
/serve/api/v1/chat_personal_stream
Chat with Personal Media Entities
chat_personal_stream body → 200
POST
/serve/api/v1/search_clips_by_image
Search Clips by Image
search_clips_by_image body → 200
GET
/serve/api/v1/search_audio_transcripts
Search from Audio
search_audio_transcripts 3 params → 200
POST
/serve/api/v1/memories/search
Search Memories
search_memories body → 200
POST
/serve/api/v1/search
Search from Private Library
search_private_library body → 200
POST
/serve/api/v1/search_public
Search from Public Video Sources
search_public_library body → 200
POST
/serve/api/v1/search_public_similar_images
Search Public Videos by Image
search_public_similar_images body → 200
POST
/serve/api/v1/upload_img
Upload Image from File
upload_image_from_file body → 200
POST
/serve/api/v1/scraper
Upload Video from Platform Creator URL
upload_video_from_creator_url body → 200
POST
/serve/api/v1/upload
Upload Video from File
upload_video_from_file body → 200
POST
/serve/api/v1/scraper_tag
Upload Video from Hashtag
upload_video_from_hashtag body → 200
POST
/serve/api/v1/scraper_url
Upload Video from Platform URL
upload_video_from_platform_url body → 200
POST
/serve/api/v1/upload_url
Upload Video from URL
upload_video_from_url body → 200
POST
/serve/api/v1/chat
Video Chat
video_chat body → 200
POST
/serve/api/v1/marketer_chat
Video Marketer
video_marketer body → 200
GET
/serve/api/v1/get_video_caption
Get Video Caption
get_video_caption 1 param → 200
GET
/serve/api/v1/folders
List Folders
list_folders → 200
POST
/serve/api/v1/folders/create
Create Folder
create_folder body → 200
POST
/serve/api/v1/folders/rename
Rename Folder
rename_folder body → 200
POST
/serve/api/v1/folders/delete
Delete Folder
delete_folder body → 200
GET
/serve/api/v1/folders/videos
List Videos in Folder
list_folder_videos 3 params → 200
POST
/serve/api/v1/folders/move
Move Videos to Folder
move_videos_to_folder body → 200

Schemas 35

The contract defines 35 schemas that model the data the API accepts and returns. The most detailed are ListVideosRequest (12 properties), SearchPrivateRequest (11 properties), UploadVideoFromUrlRequest (10 properties), UploadVideoRequest (10 properties). Each schema is shown below with its type and property counts.

UploadVideoFromCreatorRequest
object
4 properties 1 required
UploadImageResponse
object
5 properties
FolderItem
object
2 properties
UploadVideoFromHashtagRequest
object
4 properties 1 required
FlexibleFilter
object
Flexible filter object used by memories list and search endpoints.
MemoryEntryInput
object
2 properties 2 required
VideoMarketerRequest
object
3 properties 1 required
SearchAudioTranscriptsResponse
object
5 properties
SearchClipsByImageRequest
object
3 properties 3 required
DeleteVideosRequest
array
Raw JSON array of video IDs to delete.
FolderListResponse
object
3 properties
SearchPublicResponse
object
5 properties
SearchMemoriesRequest
object
4 properties 1 required
DownloadVideoRequest
object
1 property 1 required
VideoChatRequest
object
3 properties 2 required
UploadVideoResponse
object
5 properties
ListVideosRequest
object
12 properties
PersonalMediaChatRequest
object
2 properties 1 required
SearchPrivateRequest
object
11 properties 1 required
SearchPrivateResponse
object
Response shape depends on searchtype. For BYCLIP / BYVIDEO / BYAUDIO data is an array of video-search items (carries videobucket/videoblob and, for BYCLIP, key…
5 properties
SearchSimilarImagesResponse
object
5 properties
ListMemoriesRequest
object
3 properties
UploadVideoFromPlatformUrlRequest
object
5 properties 1 required
GetMetadataResponse
object
5 properties
UploadVideoFromUrlRequest
object
10 properties 1 required
FolderItemResponse
object
3 properties
AddMemoryRequest
object
5 properties 1 required
GenericJsonResponse
object
5 properties
SearchClipsByImageResponse
object
5 properties
ListVideosResponse
object
5 properties
SearchSimilarImagesRequest
object
3 properties 1 required
UploadImageRequest
object
6 properties 1 required
ScraperTaskResponse
object
5 properties
UploadVideoRequest
object
10 properties 1 required
SearchPublicRequest
object
5 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

memories-serve-api-openapi.yml Raw ↑

Other APIs Memories publishes across the network.

Memories Stream Understanding API
Memories Understand API
Where this information came from

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