Skip to main content
The Worlds architecture separates management operations from graph data operations:

Authentication

Platform API requests use platform tokens with the wzp_ prefix:
Platform tokens manage resources. World auth tokens use the wzw_ prefix and are intended for data-plane access to specific worlds.

Base URL

For local development of the Platform API server, use the Wrangler dev URL for your Worker.

Resources

The Platform API covers these management resources: worlds-api mints each immutable world ID as w_<ULID>. The Platform API stores it as world_id, and both APIs expose the unchanged value as id. Create requests define a display name but no caller-selected ID or slug field. Use world.id as the worldId path parameter.

Data-plane boundary

The Platform API does not execute SPARQL, search triples, import RDF, or export RDF. Those operations belong to the Worlds Data API (data.wazoo.dev), its generated client @worlds/client, or the embedded @worlds/sdk. The Data API runs inside a Cloudflare Worker. Graph data lives in a shared Cloudflare D1 database, partitioned by world. Each world gets a cached WorldsSdk instance backed by:
  • D1QuadStore — RDF triple storage with D1-backed hexastore indexes.
  • CloudflareSearchIndex — FTS5 keyword search projected into D1.
  • WazooSparqlEngine — the sparql-engine evaluator, wired to a D1RdfjsStore that streams quads from D1 on each query (no in-memory hydration).
SPARQL and search requests run against this per-world SDK instance inside the Worker isolate. See Query for details on the query path.