Skip to article
/ docs

Search documentation

Popular starting points. Search all 37 articles.

  • Get startedProduct availability and preview limitationsUnderstand what works in the frontend and which product capabilities are not connected yet.
  • Get startedBuild your first RAG pipelineBuild and inspect your first seven-node Basic RAG graph and learn what validation means.
  • Build pipelinesBasic RAG and Hybrid Search templatesCompare Ragify's two starting graphs and decide which pattern to explore.
  • Node referenceUnderstand the node libraryBrowse the ten registered node types by role in the workflow.

↑ ↓ to navigate · Enter to open · Esc to close

Back to Ragify ↗
On this page

Documentation

Planned; not callable

API and deployment availability

Understand the future API direction without mistaking a mock endpoint for a live service.

Ragify is intended to provide pipeline-backed API endpoints so developers can connect configured RAG workflows to their own applications. That service is not yet connected to the reviewed frontend.

Available today #

You can design and validate a frontend graph. The API Access interface may show the shape of a future developer experience.

Not available today #

There is no operational pipeline deployment, backend execution service, persistent pipeline storage, or functional pipeline-scoped API key lifecycle. Do not use example API snippets as production integration instructions.

Planned API workflow #

A future deployment flow will need to store a validated pipeline, authorize its owner, configure providers and data dependencies, deploy an execution resource, issue scoped credentials, and serve requests with safe error handling and monitoring.

Next steps #

Read Planned chatbot integration flow for an architectural explanation rather than runnable instructions.