The Playground is the fastest way to try something on nostackai without writing a client first. It's a real app-tier client — every call it makes is a genuine, authenticated request against your org, exactly like a real app would send.

What you can test

FeatureWhat it covers
Auth & AccountRegister, login, profile, change/forgot/reset password.
TenancyList, create, and join tenants; switch tenant from the top bar.
Entities (CRUD)Generic list, get, count, create, update, delete against any entity you've defined.
Public AccessThe no-login create + read flow for entities that opt into it.
Field UploadPresign → upload → save on a record → render, via the data CDN.
ContentFree-form file upload, list, share, publish, and delete.
Logic BlocksRun any custom API endpoint you've built.
AgentsInvoke an agent crew.
AI Chat (WebSocket)Run a Logic Block over the WebSocket gateway — ai_call tokens stream back live, exactly like a real chat UI would see them.
ConnectorsBrowse every connector your org can adopt, see what an org admin and tenant admin each need to configure, then test any action using only that action's own fields.

Setting it up — in this order

Each step below fixes a specific, otherwise-confusing failure if skipped — worth doing in order rather than guessing where a broken call is coming from.

1Sign into API Studio as your org's admin, and confirm your plan allows entities/logic blocks.
2In Org Settings → Allowed Domains, add the Playground's own origin. Skip this and every call fails with a browser-level CORS error (visible in DevTools) — not a clean API error message.
3Connect it: in the console app, go to My Account → Connection Details and click "Export for Playground" — this copies a ready-made connection (base URL, org code, client ID, API key) to your clipboard. Paste it into the Playground's own Connection card via Import, and every field fills in at once.
4Register a few test personas via Auth & Account → Register user — e.g. admin@…, member@…, viewer@…. Every new user starts on the default, read-only role.
5In the console's Tenant Management, assign each persona a real role/ACL. Registering a user alone grants nothing — see Roles, ACL & groups for why.
6Create the entities you want to test in API Studio, then exercise them from the Entities feature here.
7Optional: configure an AI provider before testing AI logic blocks, or a connector credential before testing that connector's actions.

Two different-looking failures, two different causes

A CORS error in DevTools means step 2 (Allowed Domains) is missing. A plain 403 "Forbidden" on login or register means your API key is wrong — don't chase the wrong one when troubleshooting.

Scenario packs — a guided shortcut

A handful of prebuilt demo scenarios (an e-commerce flow, a car-buying flow, an AI-chat-over-WebSocket flow) each ship a step-by-step playbook with real, pre-filled example payloads. Once a pack's prerequisite entities exist in API Studio, you can click through a realistic, working multi-step flow instead of constructing every request from scratch — a good starting point before building your own test scenario by hand.