mem0ai/mem0

feat(ts-sdk): add Vertex AI embedding provider

Closed

#5,768 opened on Jun 23, 2026

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Python (6,343 forks)batch import
enhancementhelp wantedsdk-typescriptsize:M

Repository metrics

Stars
 (55,741 stars)
PR merge metrics
 (Avg merge 6d 11h) (208 merged PRs in 30d)

Description

Summary

The Python SDK supports Vertex AI as an embedding provider, but the TypeScript OSS SDK (mem0ai/oss) does not. Add it to bring the TS SDK to parity.
Python reference mem0/embeddings/vertexai.py
Registered in (Python) mem0/utils/factory.py (EmbedderFactory)
Target file (TypeScript) mem0-ts/src/oss/src/embeddings/vertexai.ts
Suggested implementation Use @google-cloud/aiplatform (PredictionServiceClient) text-embedding models.

Requirements

  • Implement VertexAIEmbedder in mem0-ts/src/oss/src/embeddings/vertexai.ts, extending Embedder (mem0-ts/src/oss/src/embeddings/base.ts) and mirroring the Python provider's behavior (embed / embedBatch).
  • Register the "vertexai" provider in mem0-ts/src/oss/src/utils/factory.ts (EmbedderFactory).
  • Add config typing in mem0-ts/src/oss/src/types/.
  • Add a unit test under mem0-ts/src/oss/src/tests/.
  • Add @google-cloud/aiplatform to mem0-ts/package.json (optional/peer dependency, lazy-imported like other providers).
  • Update docs under docs/ if this provider is user-facing.

Reference pattern

Mirror an existing TS provider: embeddings/openai.ts.

Notes

GCP auth (ADC / service account). Mirror mem0/embeddings/vertexai.py.

Part of the TypeScript ↔ Python SDK provider-parity effort. One provider per issue (atomic).

Contributor guide

Research direction
Study the Python Vertex AI embedding provider and the TypeScript OpenAI provider, then implement VertexAIEmbedder following the same pattern.
Tech stack
typescriptnodejs
Domain
backendai
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
TypeScriptGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80