Praxos can parse any data source, from unstructured PDFs and API streams to conversational messages, to structured databases, and transform them into a single Knowledge Graph. Everything in this graph is semantically typed and its relationships are made explicit, turning data into a clean, queryable universe of understanding that AI can use without making mistakes.

Whether you need to query for the answer to a question or to extract data in a way that makes sense for the current use case, Praxos does it all, with no requerying needed. This enables AI apps to parse data end-to-end, and then act on it to deliver outputs across single-chain and multi-chain reasoning steps. Intermediate, final, and user-edited outputs can be added back to the knowledge graph, allowing Praxos to learn on the fly.

When we were building in insurance, we often ran into two major problems deploying AI:

First, LLMs would prove incapable of parsing documents such as property schedules and insurance policies. For reference, a property schedule may be a 50-page collection of Word, Excel, and PDF documents detailing construction, usage, and geographical information about a collection of physical properties. Recreating one object (a property) would mean combing through the files establish semantic, conceptual, spatial, and sometimes implicit linkages between the data.

The outcome: relationship information would be lost, left blank, or hallucinated.

Second, repeated calls to search, retrieve, and update information would sometimes lead to cascading errors. This became more frequent across complex tasks such as reading a document, fetching previous user information, performing a calculation, storing it, and then presenting it to the user.

We realized that for AI to deliver more useful and accurate responses that correctly use relationships in the document, these relationships need to be made explicit. Much of the contextual information is represented without the usage of words. In turn, this means that we cannot directly interact with them programmatically, and LLMs are forced to interpret them themselves, every single time. That’s when we started building Praxos.

We've set up a self-serve option with a free tier (up to a data cap) for hobbyists and early-adopters. For context (no pun intended), this should cover you for up to 200 document pages. You can register here: https://data.praxos.ai/sign-up.

Our first version is an SDK meant to cover you across all your data extraction, retrieval, and update needs.

Here's how it works:

Organizing information: Praxos sorts information into ontologies, which are structured schemas for storing data. These allow you to introduce predefined types, attributes, and relationships that guide how the knowledge graph is built and interpreted.

Processing input data: Praxos can handle any data source, ranging from PDFs to tabular data, JSONs, and dialog-like exchanges. Extraction is performed end-to-end. You don't need to OCR, chunk, or pre-process your inputs. Processing is as simple as passing in your file and selecting an ontology.

Retrieving information / memories: For each query, Praxos searches and retrieves related stored information by leveraging a combination of graph traversal techniques, vector similarity and key-value lookups. Search objects will return both the entities/their connections, as well as a sentence.

We’d love to hear what you think! Please feel free to dive in, and share any thoughts or suggestions with us over Discord (https://discord.gg/wVmrXD2dJA).

Your feedback will help shape where we take Praxos from here!