Register / API Access

Request access and get an EigenVertex API key

Self-serve auth and billing are not wired yet, so this page acts as the clean public entry point for API onboarding. It explains the real product surface as it exists today: `WikiLLM`, `Retrieval`, and the `Graph-LLM` path.

What access unlocks

  • Workspace creation in `wiki_llm` or `retrieval` mode
  • Native ingestion, search, SSE and structured intelligence routes
  • OpenAI-compatible `chat/completions` and `responses`
  • WikiLLM maintenance flows: `index.md`, `log.md`, `lint`, and `maintain`
  • Reference console plus future production integrations

Request access

Share the essentials

Email fallback Review integration surfaces

Preview

What your request will contain

Hello EigenVertex team,

I would like to request access to EigenVertex.
Name: Not provided yet
Email: Not provided yet
Company: Not provided yet
Integration path: native_api

Use case:
Not provided yet

WikiLLM

Best when you want durable memory that gets smarter over time

Use this path when the workspace should accumulate and maintain knowledge as a persistent wiki instead of rediscovering it from raw evidence on every question.

Retrieval

Best when evidence recall and exploration come first

Use this path for vector, lexical and graph-backed search patterns when you want the corpus to stay retrieval-first instead of wiki-first.

API shape

Native first, OpenAI-compatible when it helps

The native API exposes the full product surface. The OpenAI-compatible facade is there when an existing app already expects `models`, `chat/completions`, or `responses`.