Contact

Let’s talk about the corpus, the product and the integration path

This page is intentionally simple for now. The public site will be refined later, but we already want a clear place to route product conversations, API access requests and integration discussions.

Product conversations

Discuss the right workspace and retrieval model

If you are thinking about RAG quality, multimodal ingestion, traceability, or reference-app UX, start here. We can shape the right product surface around your corpus and application.

Integration

Plan the API path before wiring everything

EigenVertex can be consumed through the native API or through an OpenAI-compatible layer. The right path depends on how much of the advanced product surface your application needs.

Access

Request console or API onboarding

For now, access is still coordinated deliberately. That is a good thing: it lets us align the product setup, the corpus model and the integration expectations before scaling self-serve flows.

Current channels

Best next actions

  • Use the console if you already have access
  • Request API access if you want to integrate EigenVertex into an application
  • Share your corpus shape, source types and expected product behavior

Practical note

The public contact workflow will evolve

We are keeping this page lightweight while the platform and console mature. The important part right now is that the product, the docs and the integration story stay coherent.

Access path

Request API access or return to the console

The next concrete step for most teams is either requesting an API key or continuing inside the reference console.

Open Console Request API key