This quick guide demonstrates how to build and evaluate an AI application for intent classification using the Orq platform. Before you begin, make sure you have an Orq account. If you don’t have one, sign up first. Additionally, we’ve prepared a Google Colab file that you can copy and run immediately, simplifying the setup process. Just replace the API key, and you’re ready to go! After completing this tutorial, visit the Orq documentation for more advanced topics Note: Orq also includes a fully hosted knowledge base powered by Pinecone. This is a great option if you want to enable retrieval without managing infrastructure. This guide is for users who prefer to connect their own Pinecone project or another third party vector database. Why External Vector Databases Matter Connecting your own vector database gives you full control over data ingestion, embedding logic, and scaling. This can be especially useful when:Documentation Index
Fetch the complete documentation index at: https://docs.orq.ai/llms.txt
Use this file to discover all available pages before exploring further.
- You are working with sensitive or proprietary datasets that need to stay within your infrastructure
- You are using custom embeddings not generated within Orq’s built-in knowledge base
- You are integrating with other data pipelines where the vector database is a shared component
- You are building multi-source retrieval systems that combine local and remote sources
Get an API key
You need an API key to make calls to your Pinecone project. Use the widget below to generate a key. If you don’t have a Pinecone account, the widget will sign you up for the free Starter plan.Python
Bash
chunk_text key because of the field_map we specified when creating the index above.
Other fields which are not mapped in the field mapping, like category, will become metadata on the upserted records.
Famous historical structures and monuments.
Again, because your index is integrated with an embedding model, you provide the query as text and Pinecone converts the text to a dense vector automatically.
- Filtering by metadata: When records contain additional metadata, you can limit the search to records matching a filter expression.
- Hybrid search: You can add lexical search to capture precise keyword matches (e.g., product SKUs, email addresses, domain-specific terms) in addition to semantic matches.
- Chunking strategies: You can chunk your content in different ways to get better results. Consider factors like the length of the content, the complexity of queries, and how results will be used in your application.

- Use RAGAS inside Orq to evaluate the quality of retrieved chunks before they reach the model. This helps you understand if the retrieval step is actually helping the model generate better answers.
- Connect other vector databases such as Qdrant or Weaviate using the same interface
- Experiment with prompt variations and test their impact using Orq’s built-in evaluation tooling
- Version, deploy, and monitor your pipelines using Orq’s production features