Returns the values of specified fields from a hash
in a single read. Non-existent fields return null.
Params
key field1 field2 ...
Returns
Array of values (null for missing
fields)
HMGET user:1 name email age
EXISTS
Check if keys exist
Returns the number of specified keys that exist.
Supports checking multiple keys at once.
Params
key1 key2 ...
Returns
Integer count of existing keys
EXISTS user:1:name user:1:email user:999
HEXISTS
Check if a hash field exists
Returns 1 if the hash contains the specified field,
0 otherwise.
Params
key field
Returns
1 if field exists, 0 otherwise
HEXISTS user:1 name
DATABASE.CREATE
Create a new encrypted database
Creates a new database with automatic numbering (up
to 1000). Each database is encrypted with
ChaCha20-Poly1305 using the provided key. Requires
server admin.
Params
encryption_keystring
Returns
Assigned database number (integer)
Auth
server admin
DATABASE.CREATE my-secret-key-123
DATABASE.STATUS
Get database metadata
Returns metadata for a specific database or all
databases: status, creation time, user count, public
read flag, and encryption key.
Params
db_number or
all
Returns
Array of metadata fields
Auth
server admin
DATABASE.STATUS 0
DATABASE.STATUS all
DATABASE.PUBLIC
Toggle public read access
Enable or disable unauthenticated read access to a
database. When on, any client can read (but not
write). Cannot be applied to DB0 (admin database).
Params
db_numberon|off
Toggle
on/off, true/false, 1/0, yes/no
Auth
server admin
DATABASE.PUBLIC 1 on
USER.CREATE
Create user with Ed25519 pubkey
Register a user by Ed25519 public key. They
authenticate via the CHALLENGE → TOKEN →
AUTH signature-based flow.
Three-step cryptographic authentication:
1.
CHALLENGE <pubkey> — server
returns random challenge 2.
TOKEN <pubkey>
<signed_challenge>
— server returns session token 3.
AUTH <token> — authenticate
with session token
Step 1
CHALLENGE <pubkey>
→ challenge string
Step 2
TOKEN <pubkey>
<signature>
→ session token
Step 3
AUTH <token> →
OK
Machine-readable OpenRPC spec available at
/api/openrpc
Load ontologies, explore concepts and relationships, and interact with the
graph database. Select a default ontology or load custom JSON.
Load Default Ontology
Load Custom JSON
Active Ontology
No ontology loaded
Graph Stats
No data
Controls
Ontology Browser
ID
Name
Description
Aliases
ID
Name
Description
Directional
Source
Edge
Target
Cardinality
Add Node
Add Edge
Query Graph
Log
Run performance benchmarks against a dedicated test database. A new database
is auto-created for the test. Choose between Standard (individual commands)
and Batched (MSET/MGET) mode to compare throughput.
No test database active. Click "Run
Write Test" to create one.
Step 1: Write Benchmark
0%
Preparing...
Step 2: Read Benchmark
0%
Preparing...
Results Summary
Metric
Value
Cleanup
Flush the test database and remove all test data.
Benchmark graph database operations: node creation, edge creation,
neighbor lookups, and traversal performance. A test ontology is loaded
automatically.