Documentation / Developer Tool

OcaltQL Console

Write and run OcaltQL in the browser with live output. No install, no project, no local runtime to drift.

Open Console

Overview

The OcaltQL Console is a browser-based editor for writing, testing and running OcaltQL scripts. It is the fastest way to experiment with the language and to see exactly what a script produces — rendered or raw.

There is no setup, no local install and no separate environment to configure. Open the page and start writing. The console presents the same execution engine that every other part of the platform uses.

What it is

A surface, not a second runtime. Scripts are submitted directly to the OcaltQL runtime over HTTPS. What you see is what https://ql.ocalt.com/api would return, with an editor and a result pane around it.

Free accounts carry the entire language. The first lesson is not gated behind a plan. Query spend still counts; the verbs do not.

What it does

  • A live editor with immediate execution.
  • Output as rendered results or as raw data.
  • The same credentials and namespace as the rest of the account.
  • A place to iterate until a script is worth saving into storage, a CRON, a subdomain, or Grimoire.

How it works

You type a script. The console posts it. The runtime parses, executes, and returns the body. Errors come back as the runtime reports them, including !!FAILED!! markers, not as a framework stack trace from the editor.

Rendered view is for HTML, images, maps and other content types the runtime actually produced. Raw view is the bytes. Switch when the pretty version is hiding a header or a status you need to see.

Getting started

  1. Open console.ocalt.com and run EMIT "hello". That is the whole setup step.
  2. Take an API key from accounts.ocalt.com when you want the same script from curl or from your own code.
  3. Read the reference at ql.ocalt.com. Every verb with its slots and a worked example.
  4. When a script is done, put it in a file, on a subdomain, in a CRON, or behind OMNI. The console does not have to remain the home of it.
First chained script
EMIT "Hello World"
AFTER CALCULATE 1 + 1 SET ?result
AFTER EMIT ?result
The same script, from curl
curl https://ql.ocalt.com/api \
  -d identity=you@example.com \
  -d password=YOUR_API_KEY \
  --data-urlencode 'q=EMIT "hello"'

Who it is for

Anyone learning OcaltQL, debugging a script, or prototyping something before moving it into a permanent workflow. Teachers: the console works on a Chromebook. There is no toolchain to install in a lab image.

OcaltQL language docsThe full tutorial and verb reference.OcaltQL (this site)A shorter orientation.QueryAdminConsole plus every other panel.OcaltQL ClientLocal files, real execution.

FAQ

Does the console save my scripts?

Treat it as a scratch surface. If you want a script to exist tomorrow, write it to /root or put it on a subdomain as an .oql file. QueryAdmin's file panel and Ocaltio both edit those files in place.

Why did I get 429?

The daily query allowance is spent. Credits draw after the daily amount. See Pricing.