mem0ai/mem0

feat(ts-sdk): add Together embedding provider

Closed

#5,766 opened on Jun 23, 2026

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Python (6,343 forks)batch import
enhancementgood first issuehelp wantedsdk-typescriptsize:S

Repository metrics

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

Description

Summary

The Python SDK supports Together 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/together.py
Registered in (Python) mem0/utils/factory.py (EmbedderFactory)
Target file (TypeScript) mem0-ts/src/oss/src/embeddings/together.ts
Suggested implementation OpenAI-compatible /v1/embeddings — reuse OpenAIEmbedder with baseURL=https://api.together.xyz/v1.

Requirements

  • Implement TogetherEmbedder in mem0-ts/src/oss/src/embeddings/together.ts, extending Embedder (mem0-ts/src/oss/src/embeddings/base.ts) and mirroring the Python provider's behavior (embed / embedBatch).
  • Register the "together" 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/.
  • No new dependency — reuse the existing openai client with a custom baseURL.
  • Update docs under docs/ if this provider is user-facing.

Reference pattern

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

Notes

No new dependency. Match the default embedding model in the Python provider.

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

Contributor guide

Research direction
Implement TogetherEmbedder by extending the Embedder class, mirroring the Python provider. Reuse the OpenAI client with baseURL=https://api.together.xyz/v1. Register the provider in factory.ts, add types, and write a unit test.
Tech stack
typescript
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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