Monaco Editor
The query editor is built on Monaco — the same engine behind VS Code — with a GraphQL language worker that provides:- Syntax highlighting for GraphQL operations, fields, arguments, and directives
- Schema-driven autocomplete — press
Ctrl+Spaceto see available fields, arguments, and types based on the live schema - Real-time error detection — red underlines and error markers for invalid field names, missing arguments, or type mismatches
- Bracket matching and auto-closing for braces, parentheses, and strings
- Multi-cursor editing for batch changes
Editor Panels
The editor area is divided into three tabs at the bottom. Switch between them to configure different parts of your request.Query Panel
The main editing area where you write GraphQL queries. This is where Monaco’s autocomplete, highlighting, and error detection are active.Variables Panel
Use the Variables panel to pass JSON variables to parameterized queries. This keeps your queries reusable — change variable values without editing the query text.- Query
- Variables
Headers Panel
Configure HTTP headers sent with every request. The Headers panel is shown by default with theX-API-KEY header pre-configured.
The
Content-Type: application/json header is automatically included — you do not need to set it manually.Toolbar
The toolbar sits at the top of the editor and provides quick-access actions:Executing Queries
To execute a query:- Write or load a query into the editor
- Set your
X-API-KEYin the Headers panel - Click the Execute button (▶) in the toolbar, or press Ctrl/Cmd+Enter
Results Panel
The results panel displays the JSON response from the GraphQL endpoint with:- Syntax highlighting for JSON keys, strings, numbers, and booleans
- Collapsible nodes for navigating deeply nested responses
- Copy response support via right-click context menu
data object matching your query structure, plus an extensions.credits object showing billing information.
Status Bar
The status bar at the bottom of the IDE provides real-time feedback on query execution:Credit Units (CU) reflect the computational cost of your query. Queries scanning more data or returning larger result sets consume more CU. See Billing & Credits for details.

