agenthub · knowledge.embed
Attach an embedding vector to every chunk. This is the step that costs model money in the ingestion chain.
Why the node earns its place
Chunks arrive without vectors and leave with them. The vector width is the adapter's business — the node never asserts one — so the same graph runs against different embedding backends unchanged.
How it works at run time
concurrency requests at a time.What you wire
Configuration
| Key | Type | Default & options | What it does |
|---|---|---|---|
| concurrency | number | default 4 | Concurrent embedding requests per batch. |
What usually goes wrong
Watch for this
Failures drop chunks rather than failing the run — partial success beats total failure for an indexer, but it means a quiet gap in your knowledge base. Compare the chunk count in and out before treating an index as complete.
Behaviour & provenance