Get Started with Vemorak

This quickstart walks you through the fastest path from Console setup to offline verification. If you can copy and paste an API key, you can finish this in under ten minutes.

QuickstartOffline verificationAPI v1

On this page

1. Create a Console account 2. Create an API key 3. Open the Playground 4. Use the personal assistant 5. Explore Events and Batches 6. Download bundles 7. Get the Desktop Verifier 8. Verify offline Common settings What to do next

Start here

Console: Open

API docs: Read

Desktop Verifier: Download

You will need

A Console account
A tenant API key with test scopes
One event bundle to verify offline

If you get stuck

Try the API from the docs page: Try it panel

Support: Contact

1. Create a Console account

Create your account, then confirm you can access a tenant dashboard.

Permalink

Start by creating an account in the Vemorak Console. After signup, you should see an organisation, a default tenant, and an admin dashboard.

Signup: https://console.vemorak.com/signup
Dashboard: https://console.vemorak.com/dashboard

What you should see after login

An organisation created automatically
A default tenant available immediately
Admin dashboard access

2. Create an API key

Tenant scoped API keys authenticate actions across the API, Console, and Playground.

Permalink

Vemorak uses tenant scoped API keys. For testing, create a key with either admin.read or admin. If you want to ingest and delete events from your own scripts, include the core scopes too.

Console location

Console → API Keys

Recommended scopes for this quickstart

admin.read (minimum for Console features and inspection)
admin (full access, easiest for testing)
events.write (append events)
events.delete (create delete events and receipts)
proofs.read (fetch proofs and bundles)
receipts.read (fetch and verify deletion receipts)

Important

You will see the key secret once. Copy it and store it securely. If you plan to use the key inside a real application later, set a scope prefix such as app:billing:. For admin test keys, leaving it unrestricted is fine.

3. Open the Playground

The Playground writes to your real tenant ledger. Nothing here is simulated.

Permalink

Open the Playground from the Console, then paste your tenant API key when prompted. The Playground lets you write and delete events, inspect proofs, and observe how batching works.

Playground: https://console.vemorak.com/playground
API reference: /docs

Optional but useful

If you prefer, you can test your key immediately using the docs Try it panel. It calls /v1/whoami and /v1/ingest from the browser.

Open Try it panel

4. Use the Vemorak personal assistant

Assistant interactions produce real cryptographic events, just like manual ingest.

Permalink

Inside the Playground, the personal assistant can help you create memory events, ask questions about stored events, trigger deletions, and inspect receipts. Every interaction results in real events being recorded for your tenant.

A good first experiment

Ask the assistant to store a simple memory, then request a proof. After that, delete the memory and inspect the deletion receipt.

5. Explore Events, Proofs, and Batches in the Console

The Console is your audit surface for what the protocol recorded.

Permalink

Events

View all ingested events, see whether an event is batched or pending, and open event details and proofs.

Open Events

Batches

Inspect closed Merkle batches, view roots and signatures, and explore leaf counts.

Open Batches

Deletion receipts

View receipts, verify signatures, and download receipt bundles.

Open Deletion Receipts

6. Download a proof bundle or receipt bundle

Bundles are self contained, verifier friendly, and designed for offline verification.

Permalink

From the Console you can download:

Event bundles which contain the event, proof, and recomputation data
Deletion receipt bundles which contain the receipt, verification result, and the linked delete event bundle

Why bundles matter

Once you have a bundle, you do not need the Console, the API, or network access to validate it. You can hand the file to an auditor, a customer, or a security team.

API endpoints behind these downloads

HTTP

GET /v1/events/{event_id}/bundle
GET /v1/deletion-receipts/{receipt_id}/bundle

7. Download the Offline Desktop Verifier

The verifier is a standalone offline application with no network requirement.

Permalink

Download the Desktop Verifier for your platform. The verifier is designed to work offline. No API keys, no network, and no trust in the Console required.

Desktop Verifier downloads: https://vemorak.com/downloads

Platforms

Windows, macOS, and Linux.

8. Verify proofs offline

Load a bundle into the verifier and let it do the cryptography.

Permalink

Open the Desktop Verifier and load the downloaded bundle. The verifier will:

Recompute event hashes
Validate Merkle paths
Verify cryptographic signatures
Confirm integrity without contacting any server

The trust chain ends here

If verification succeeds, the bundle is cryptographically valid. You do not need to trust the Console, the API, or the network. Only the cryptography.

Verifier endpoints (optional)

If you ever want server side verification for troubleshooting, these exist:

HTTP

POST /v1/verify/bundle
POST /v1/verify/deletion-bundle

Common Console settings

Optional but useful habits once you move beyond a demo tenant.

Permalink

Default API key

You can mark one API key as the default for a tenant. This is the key used automatically by the Playground and admin features.

Manage API keys

Key rotation

Rotate keys regularly to reduce risk. Rotations and revocations are linked and auditable.

Audit logs

Track key creation, rotation, revocation, and access decisions for accountability.

Open audit logs

Multiple tenants

Use separate tenants for development, staging, production, or separate applications and teams.

What to do next

Once you have a successful offline verification, the next step is integration.

Permalink

You have done the important part. You created a tenant, generated cryptographic events, inspected proofs and batches, exported bundles, and verified offline.

Next steps

Read the full API reference: /docs
Use the interactive Try it panel: /docs#tryit
Explore SDKs: SDK docs
Grab the SDK repository: GitHub

Minimal cURL examples

bash

# WhoAmI
curl -s "https://api.vemorak.com/v1/whoami" \
  -H "Authorization: Bearer YOUR_TENANT_API_KEY"

# Ingest
curl -s "https://api.vemorak.com/v1/ingest" \
  -H "Authorization: Bearer YOUR_TENANT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "tenant_id":"vmp-tenant",
    "scope":"user:123",
    "op":"write",
    "fields":{},
    "meta":{}
  }'