Embeddr Find Similar To Artifact ID

Find Similar To Artifact is the "show me more like this one" node. You hand it an artifact ID - something already in your Embeddr library - and it goes and finds the other artifacts that look like it. Where its sibling Find Similar Artifacts takes an image that might not be in your library, this one takes an ID and lets your library's own index do the work with zero image upload.

It's the natural follow-up to any search. Text search round up a set of candidates → find the best one → then fan out from that ID to grab everything in its visual neighborhood. Or take the artifact_ids output from Load Artifacts and chain: load a batch, pick one, find its siblings, keep the ones you actually want.

Inputs and mechanism

• artifact_id - the source artifact's ID, in the pack's custom EMBEDDR_ARTIFACT_ID type. This is the one you set, and it's happy to take a value straight off another Embeddr node's ID output. If you pass it a list somehow, it uses the first one.
• limit - results, 1–50, default 5.
• model_name - the embedding model to search with, default "lotus". Same knob as the image-search node: match it to whatever embedding model your Embeddr server is actually configured with, or you'll get a fruitless search.

Under the hood it POSTs the ID, limit, and model name to /api/v1/plugins/embeddr-comfyui/find_similar_to_id on your server, gets back candidate IDs, then fetches each candidate's image content through the plugin route and decodes it into a tensor. Round-trip through your Embeddr backend either way.

Outputs

• images - the similar images as an IMAGE list, ready to pipe into an img2img chain, an IP-Adapter, or a preview.
• artifact_ids - the matching IDs in the same order. These are your lineage hooks: feed one into Upload as a parent_ids value and the "inspired by" relationship is recorded.

No matches (or a bad model name) gives you an empty 64×64 image and an ID of "-1" rather than an error - an all-black output is your "nothing found" signal, so check model_name and the backend before assuming your library is empty.

Install

Standard pack: embeddr serve running first, pack installed via ComfyUI Manager or a release extracted into custom_nodes, ComfyUI restarted. Declared dependency is requests only. And the usual reassuring property: the search and the image fetch all hit your own localhost server - nothing about this node leaves your machine.