For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dashboard
User GuideDeveloper GuidesAPI Reference
User GuideDeveloper GuidesAPI Reference
  • Getting Started
    • What is Runtype?
    • Creating your account
    • Platform Keys vs. BYOK
    • Understanding the Runtype UI
    • Quickstart: Social Media Post Generator
    • Quickstart: From Agent to Chat Widget
  • Dashboard
    • What is the Dashboard?
    • Daily Executions
  • Playground
    • What is the Playground?
  • Products & Surfaces
    • What are Products?
    • What are Surfaces?
    • Creating a Product
    • Setting up a Chat Surface
    • Setting up an API Surface
    • Setting up an MCP Surface
    • Setting up an A2A Surface
    • Setting up a Slack Surface
    • MCP authentication
    • Authenticating with product API keys
    • Embedding the chat widget (script tag)
    • Embedding the chat widget (React)
    • Surface orchestration modes
    • Product views
    • Adding Capabilities to a product
    • Connecting external agents
    • How A2A works
    • Connecting to Cursor / VS Code
    • Connecting to Claude Desktop
    • Scoping API keys to capabilities
    • Auto-generated OpenAPI spec
    • Calling your API endpoints
    • Client tokens and domain restrictions
    • AI-powered theme generation
    • Widget theming and customization
    • Product versioning and status
  • Flows
    • What are Flows?
    • Creating and Editing Flows
    • Flow step types overview
    • Agent and Flow Templates
    • Using prompt steps
    • Using transform-data steps
    • Using conditional steps
    • Using fetch-url and api-call steps
    • Using record steps (upsert/retrieve)
    • Flow variables and templates
    • Flow versioning and publishing
    • Running flows in batch
    • Handling batch failures
    • Debugging flows
  • Agents
    • What are Agents?
    • Creating and configuring Agents
    • Agent tools
  • Records
    • What are Records?
    • Creating and managing records
    • Using records in flows
    • Filtering and searching records
  • Tools
    • What are Tools?
    • Built-in Tools
    • Creating custom tools
    • Creating external tools
    • Runtime tools
  • Evals
    • What are Evals?
    • Running an Eval
    • Interpreting eval results
  • Schedules
    • What are Schedules?
    • Automating batch processing
  • Logs
    • What are Logs?
    • Working with Logs
  • Integrations
    • Connecting AI model providers
    • Slack integration
    • Google Workspace integration
    • GitHub integration
    • Linear integration
    • Weaviate (vector search)
    • Firecrawl (web scraping)
    • Exa (web search)
  • Settings
    • What's in Settings?
    • Available AI models
    • What are Organizations?
    • Managing AI models
    • Managing API keys
    • Billing and plans
    • Usage data
    • Team members and permissions
    • Appearance and preferences
    • Integrations (PostHog, Weaviate, Daytona)
  • Troubleshooting & FAQ
    • FAQ
    • Rate Limits and Usage
    • Managing Runtype with Claude
    • Flow execution failures
    • Common errors and solutions
    • Authentication issues
Dashboard
LogoLogo
On this page
  • What is Weaviate?
  • When to use Weaviate vs Records
  • Setting up Weaviate
  • Using Weaviate with the Semantic Search tool
  • RAG with Weaviate
  • Next steps
Integrations

Weaviate (vector search)

Was this page helpful?
Previous

Firecrawl (web scraping)

Next
Built with

Connect Weaviate as a vector provider for the Semantic Search built-in tool. Weaviate is not a standalone integration — it is a provider option within the Semantic Search tool available to Agents.

What is Weaviate?

Weaviate is a vector database for semantic search. Use it for RAG (Retrieval Augmented Generation) at scale with millions of documents.

When to use Weaviate vs Records

  • Use Runtype Records with platform vector search (pgvector): Up to 100k documents, simple setup
  • Use Weaviate: 100k+ documents, advanced filtering, production scale

Setting up Weaviate

  1. Create a Weaviate cluster at console.weaviate.cloud
  2. Get your cluster URL and API key
  3. Add your Weaviate credentials in Settings → Integrations

Using Weaviate with the Semantic Search tool

Weaviate is configured as a vector provider when adding the Semantic Search built-in tool to an Agent:

  1. Add the Semantic Search tool to your Agent
  2. Under Vector Provider, select Weaviate
  3. Enter your Collection Name (the Weaviate class to search)
  4. Optionally configure the similarity threshold and display name

The tool supports multiple instances, so you can add several Semantic Search tools pointing to different Weaviate collections in the same Agent.

RAG with Weaviate

Build retrieval-augmented generation by enabling the Semantic Search tool (with Weaviate provider) on an Agent. The Agent can autonomously query the Weaviate collection for relevant documents and use them as context for generating answers.

Next steps

  • What are Agents? to build Agents that use the Semantic Search tool