Model Reference

Shaped offers a rich library of model policies that power retrieval, scoring, and ranking within your recommendation and search systems. These policies range from classic collaborative filtering techniques and rule-based heuristics to state-of-the-art deep learning architectures. Explore the available policies below to understand their capabilities and how to configure them for optimal performance.

Plan Availability

Shaped offers models across different plan tiers:

• Free Plan: Includes foundational models like ALS, ELSA, Item2Vec, and Rising Popularity
• Standard Plan: Includes all Free Plan models plus advanced models like SASRec, Two-Tower, BERT4Rec, GBDT, and more

Individual model cards below indicate their plan availability.

Model types in Shaped

Shaped systems typically use a combination of:

• HuggingFace embedding models (zero-shot): Pre-trained encoders used to generate embeddings without training on your interaction data. These are commonly used for vector search retrieval (semantic text search, similarity, content filtering) and as feature inputs to downstream trained models.
• Trained embedding models: Models trained or fine-tuned on your data to learn user and item representations (e.g., matrix factorization, two-tower retrieval, sequential models). These are often used for candidate retrieval, similarity, and as features for scoring.
• Scoring models: Point-wise models used in the scoring stage to produce a relevance score for a (user, item) pair, typically using rich feature sets.

Trained embedding and scoring models are trained on the data in your engine and retrained continuously based on your configured training schedule.

Embedding models

Embedding models are trained to represent items and users in vector space.

For pre-trained, zero-shot embedding generation, see HuggingFace embedding models.

🧩 ALS

Matrix Factorization (Alternating Least Squares) for implicit feedback collaborative filtering.

🧩 SVD (retired)

Retired: no longer accepted via the V2 API. Matrix Factorization (Singular Value Decomposition inspired) for collaborative filtering, often including biases.

💡 ELSA

Scalable Linear Shallow Autoencoder for implicit feedback recommendations using factorized structure.

✨ EASE

Embarrassingly Shallow Autoencoder with a simple closed-form solution for item collaborative filtering.

🗼 Two-Tower

Scalable deep learning model with separate user and item networks for efficient candidate retrieval.

🐝 beeFormer

Fine-tunes sentence Transformers on interaction data, bridging semantic and behavioral signals.

🔄 Item2Vec

Learns item embeddings based on co-occurrence within interaction sequences (Word2Vec adaptation).

➡️ SASRec

Self-Attentive Sequential Recommendation model using Transformers for next-item prediction.

↔️ BERT4Rec (retired)

Retired: no longer accepted via the V2 API. Bidirectional Transformer (BERT) for sequential recommendation via masked item prediction.

✅ GSASRec (retired)

Retired: no longer accepted via the V2 API. Improved SASRec (Generalized Self-Attentive) reducing overconfidence in sequential models.

🧪 HSTU (Coming soon)

Cutting-edge sequential transducer architecture our engineers are actively building.

🧪 Semantic IDs (Coming soon)

Content-derived discrete item identifiers to improve long-tail and cold-start generalization.

HuggingFace embedding models (zero-shot)

HuggingFace models are used for generating embeddings in a zero-shot way. They can be used for:

• Vector search retrieval: Semantic search, similarity lookup, and content filtering using the embedding vector index.
• Downstream features: As feature inputs to trained embedding models (e.g., two-tower, beeFormer) and scoring models (e.g., GBDT, Wide and Deep).

In v2, HuggingFace embeddings are configured in your engine index.embeddings via the hugging_face encoder. See Use a pre-trained model.

If you prefer embeddings trained on your data, you can also encode with trained models and use them in the same retrieval and scoring flows.

📝 Sentence Transformers

Text embedding models used for semantic search, similarity, and as features for downstream models.

🖼️ CLIP, OpenCLIP, SigLIP

Multimodal encoders used for image and cross-modal retrieval, and image features in ranking.

🏷️ Jina, Nomic, Marqo

Common providers for text and multimodal embedding models on HuggingFace.

🧠 E5, BGE, GTE families

Popular embedding model families, typically published as compatible Sentence Transformers.

You will typically use these embeddings in two places:

• Index configuration: Create one or more embeddings in index.embeddings. See engine-recipes and Feature types.
• Queries: Retrieve with vector search (text_search(mode='vector', ...)) or similarity (similarity(embedding_ref=..., ...)). See Vector search retriever and ShapedQL: text_search().

Common gotchas:

• Modality matters: Text encoders should be used with text fields, and CLIP-style encoders can be used with image URL fields. See Create embeddings for text and image features.
• Private models: If the model is private, you will need a HuggingFace token at train time. See Invalid Huggingface model.

Supported HuggingFace model collections

Shaped supports HuggingFace embedding models from:

• Sentence Transformers: Any compatible model from the HuggingFace Sentence Transformers collection.
• CLIP: Any compatible model from the HuggingFace CLIP collection.

Common providers and architectures

In addition to the collections above, users commonly use models from providers and families like:

• Jina AI: Text and multimodal embedding models published on HuggingFace (e.g., jinaai/jina-clip-v2).
• Nomic AI: Text embedding models published on HuggingFace (e.g., nomic-ai/*).
• Marqo: Domain-tuned multimodal retrieval/embedding models published on HuggingFace (e.g., Marqo-published CLIP-style models).
• Other common embedding families: E5, BGE, and GTE models, when published as compatible Sentence Transformers or CLIP-style encoders.
• Other common multimodal architectures: OpenCLIP and SigLIP variants, when published as compatible CLIP-style encoders.

Commonly used models

These are common examples used in our v2 docs:

• sentence-transformers/all-MiniLM-L6-v2
• sentence-transformers/modernbert
• Alibaba-NLP/gte-modernbert-base
• openai/clip-vit-base-patch32

Scoring models

Scoring models are used to rank items by relevance or other predicted business metrics (e.g., engagement, predicted click-through-rate, conversion).

Zero-shot scoring and reranking

For text-heavy search use cases, Shaped also supports zero-shot rerankers and rank fusion methods that work well on a small candidate set.

These are score-stage expressions, so they can be used for both search and recommendations anywhere score(expression='...') is supported.

🔎 ColBERTv2

Late-interaction text reranker for high-quality retrieval and reranking.

🧾 Cross-encoders

Zero-shot text reranking by scoring each (query, item) pair.

🔀 Reciprocal rank fusion (RRF)

Robustly fuse lexical and vector ranked lists using ranks.

⚖️ Linear interpolation

Blend retrieval scores and model outputs with explicit weights.

🌳 GBDT

Gradient Boosted Decision Trees, effective for classification and ranking tasks.

➕ Wide & Deep (retired)

Retired: no longer accepted via the V2 API. Combines a wide linear model (memorization) and a deep neural network (generalization) for scoring.

🔗 DeepFM

Combines Factorization Machines (FM) and Deep Neural Networks (DNN) for interaction modeling.

#️⃣ Ngram

Simple sequential model predicting based on fixed-length interaction counts (n-grams).

📈 Rising Popularity

Trending policy ranking items by recent increase in engagement (momentum).