Retrieval, Vector and RAG

Where this market publishes its structure

• LlamaIndex llama-index-integrations (vector_stores, embeddings, postprocessor rerankers, readers) machine-readable, 118 SaaS data-source readers counted, never linked
• LangChain partner packages (libs/partners + langchain-ai langchain- repos) machine-readable, LLM-only partners are model-routing's, counted not linked
• Haystack / DSPy integration lists not machine-readable: not swept this pass
• Vector DB benchmark registries (ann-benchmarks, VectorDBBench) not machine-readable: benchmarks, not coverage

Own = declares at least one integration itself; covered = visible only because an aggregator, standards body, regulator or partner contract names it; distribution-only = listed only on cloud marketplaces it sells through, a channel reported beside, never counted as its own declared integrations; undeclared = nothing we can read, so no number; declares_compatibility = providers with a `compatible` shape vote, report only (kin, 2026-10-13): never counted as own, never in depth or position.

Taxonomy how this market maps onto apis.io

Derived 2026-10-15 from the 85 providers in this market we could resolve in the catalog. The percentage is the share of those providers carrying each one; it describes the market, not the tag or industry. Tag groups have no page of their own yet, so they are listed unlinked.

share of resolved cohort carrying it; tags >=0.20 & >=3 members (max 12, junk dropped), tag_groups >=0.20 (cooccurrence, non-cross-cutting; max 8), industries >=0.20 (max 6), areas >=0.10 (max 6; areas are keyword-matched and sparse), capabilities L1 >=0.20 (max 8); derive-market-taxonomy.py

Leaders by position (provisional)

Provisional: grouped by position, depth compared within a position only. Distribution (cloud marketplaces) and iPaaS bridges are counted beside position, never inside it. Unknown-builder listings are left out of position shares and counted here.

builds-on 3 · publishes apps on other platforms' stores

coverage 1 · reaches banks, carriers, systems or channels (an aggregator)

covered 81 · reached mainly through aggregators

Frontier timeline DRAFT · report only — not weighted

2026-10-15 anchor shape:

• Shape gravity: 4 providers declare compatibility with the shape in their own contracts.
• Mediation: frameworks and sources cover 85 providers; 23 are covered by every one (amazon-bedrock, azure-ai-foundry, chroma, cohere, datastax, elasticsearch, fireworks-ai, google-vertex-ai, hugging-face, milvus, mistral, mongodb, neo4j, nomic-ai, nvidia-nim, ollama, openai, pinecone, qdrant, redis, together-ai, upstage-ai, weaviate).