Skip to main content
Worlds is Wazoo’s context engine. It stores facts as knowledge graphs, exposes search and SPARQL query paths, and provides APIs that let agents retrieve and update verifiable context. Worlds lets models use tool calls to retrieve facts from a graph rather than infer them from model weights. Worlds is designed for curated memory. Store durable facts in a world and discard the rest, instead of keeping every message.

What Worlds provides

  • Graph storage: RDF triples and named graphs for durable facts.
  • Hybrid search: Keyword and vector retrieval over graph literals.
  • SPARQL queries: Declarative graph traversal and reasoning.
  • API and CLI surfaces: Programmatic and terminal workflows for creating, importing, exporting, searching, and querying worlds.
  • Edge-ready adapters: LibSQL/Turso backends for durable deployments.

Repositories

Quickstart

Start with the hosted API when you want managed storage, or use the embedded @worlds/client when you want in-memory graph memory during development. Hosted Worlds has two surfaces:
  • The Wazoo Platform API (@wazoo/client) manages platform resources such as user-owned Worlds and tokens.
  • The Worlds Data API, hosted at worlds-api.wazoo.dev, handles graph data through import, export, search, and SPARQL operations.

Prerequisites

  1. Get access to the hosted Wazoo private beta.
  2. Generate a platform token (wzp_) from the Console tokens page.
  3. Save it as WAZOO_PLATFORM_TOKEN.

Create a world

Mint a world token

Data-plane requests use a wzw_ token scoped to a single world. Save the returned secret immediately; it is shown only once:
Save it as WORLDS_TOKEN.

Import, search, and query

To provision hosted resources programmatically, use the Platform TypeScript SDK.

Embedded client

For in-memory graph memory during development, wire the core adapters into a Client from @worlds/client:
index.ts
Durable embedded backends are published as separate packages, including @worlds/libsql (LibSQL/Turso) and @worlds/postgres.

Next steps