--- name: bijection-context description: "Evaluate and integrate the Context component with Bijection." --- # Context Bijection component for calling the Context.dev API from Bijection functions. - Package: @bijectionhq/context - Category: AI & Agents - Status: Preview - License: MIT - Bijection source (repository access required): https://github.com/bijectionhq/context/tree/66af2f57cff6d1df606baf696c0813363231f774 - Upstream: https://github.com/context-dot-dev/convex-component/tree/49e396c1410fe0da5f8f1c77939f5b36af699d08 - Documentation: https://docs.bijection.com/components/using - Directory: https://bijection.com/components/context ## Get the source Bijection repository access is required. Request access at https://bijection.com/contact. ```sh git clone https://github.com/bijectionhq/context.git cd context git checkout 66af2f57cff6d1df606baf696c0813363231f774 ``` ## Before using this component Read the package README at the recorded revision for setup, dependencies, and API examples. Upstream documentation describes the original package and may differ from the Bijection adaptation. This is a source candidate for evaluation. Catalog inclusion does not establish npm availability or runtime qualification. Check compatibility with your SDK and deployment before adoption. External providers run their own compute. ## Integration workflow 1. Read the source README and package manifest at the recorded revision. 2. Confirm the required SDK, dependency availability, and runtime compatibility. 3. Follow the component's documented setup and configuration. Never invent an npm install command from a catalog package name. 4. Keep credentials in the project's existing secret store. 5. Follow the project's execution rules for verification and report what was actually checked. ## Original upstream skill The following guidance describes @context-dot-dev/convex. Its installation commands and APIs refer to the upstream package. Evaluate compatibility with the Bijection source separately. # Context.dev ## Instructions Use Context.dev to pull live web pages, brand data, logos, and search results into convex actions via the context.dev api without maintaining scrapers. This Convex component integrates directly with your backend. ### Installation ```bash npm install @context-dot-dev/convex ``` ### Capabilities - Retrieve structured brand data including logos, colors, fonts, and company info by domain, email, ticker, or ISIN from a single typed client - Scrape web pages and return clean Markdown or raw HTML directly inside Convex actions without managing external scraping infrastructure - Extract structured data from crawled pages using a JSON schema, enabling AI enrichment pipelines without leaving the Convex backend - Access 25+ typed helper methods covering scraping, crawling, brand lookup, competitor analysis, product extraction, and web search from one npm package ## Examples ### how to scrape web pages from Convex actions The Context.dev Convex component exposes scrapeMarkdown and scrapeHtml helper methods that can be called directly from Convex actions. Install @context-dot-dev/convex, configure your API key as a Convex environment variable, and call contextDev.scrapeMarkdown(ctx, { params: { url } }) to get clean Markdown back from any URL. ### how to get company brand data and logos in Convex The Context.dev component provides retrieveBrand, retrieveBrandByName, retrieveBrandByEmail, and retrieveBrandByTicker methods that return full brand payloads including logos, colors, and typography. Call these from a Convex action using the typed ContextDev client to enrich user or company records without building a scraper. ### how to extract structured data from websites in Convex The extract helper method crawls pages and extracts structured data based on a JSON schema you provide. This lets you run AI-powered data extraction pipelines entirely within Convex actions by calling contextDev.extract(ctx, { body: { schema, url } }). ### how to run web search from a Convex backend function The Context.dev Convex component includes a search method that queries the web with optional filters and can return results as Markdown. Call it from a Convex action to power RAG pipelines, research agents, or enrichment workflows without managing a separate search API integration. ## When NOT to use - When a simpler built-in solution exists for your specific use case - If you are not using Convex as your backend - When the functionality provided by Context.dev is not needed ## Troubleshooting **Does the Context.dev Convex component store scraped data in the Convex database?** No. The @context-dot-dev/convex component does not persist any data in Convex. It wraps the Context.dev REST API with typed helpers and isolated component actions. Caching behavior is controlled through API-level parameters such as maxAgeMs on individual requests, not through Convex storage. **How do I authenticate the Context.dev component with my API key?** Set your Context.dev API key as a Convex environment variable using npx convex env set CONTEXT_DEV_API_KEY your_api_key_here. Then wire the env variable through the component configuration in convex.config.ts using app.use(contextDev, { env: { CONTEXT_DEV_API_KEY: app.env.CONTEXT_DEV_API_KEY } }). **Can I call Context.dev component actions from Convex queries or mutations?** No. The Context.dev component methods must be called from Convex actions, not queries or mutations. This is because they make external HTTP requests to the Context.dev API, which is only permitted inside Convex actions per the Convex execution model. **What brand data fields does the Context.dev Convex component return?** The retrieveBrand method returns a full brand payload that includes logos, colors, typography, and design system details for a given domain. The retrieveSimplifiedBrand method returns a smaller subset of that payload. The styleguide and fonts methods can be used to extract specific design system details independently. **Does the Context.dev Convex component support looking up companies by stock ticker or ISIN?** Yes. The @context-dot-dev/convex package includes retrieveBrandByTicker and retrieveBrandByIsin helper methods for financial identifier lookups. There is also identifyBrandFromTransaction for matching a brand from transaction description text, and retrieveNaics and retrieveSic for industry classification. ## Resources - [npm package](https://www.npmjs.com/package/%40context-dot-dev%2Fconvex) - [GitHub repository](https://github.com/context-dot-dev/convex-component/) - [Live demo](https://drive.google.com/file/d/1_Ck4Pb2g6il3DPJ2hEDyf6elPy8Ke1t_/view?usp=sharing) - [Convex Components Directory](https://www.convex.dev/components/context-dot-dev/convex) - [Convex documentation](https://docs.convex.dev)