Docs

The sandbox is the quickest way to see how Raptor MCP feels in a real AI client without first connecting your own Qlik tenant.

It is intentionally short-lived and limited. Use it to explore the workflow, test starter prompts, and decide whether the gateway model fits your team.

• Use sample, public, or non-sensitive data only.
• Expect a time-bound evaluation slot, not an always-on environment.
• Use the starter prompts to test Qlik exploration, script assistance, and safe delivery patterns.
• Do not connect production tenants, customer databases, confidential documents, or regulated data to the sandbox.

When you start a slot, the portal gives you the temporary connection details you need for the session. When the slot ends, those details should no longer be used.

For extra protection, sandbox access is limited to the public IP address you choose when the slot starts. Use the network your browser and AI client will actually use during the session.

• Use the detected public IP when your browser and AI client are on the same network.
• Enter a different public IP only when your client uses a different approved network route.
• Changing VPN, office network, hotspot, or NAT route during a slot can block access.
• When the slot expires, stop using the temporary details and start another slot if more evaluation time is available.

The sandbox is designed for AI clients that support Raptor MCP connections. Starter prompts are provided for common tools where available, and other clients may need their own configuration format.

• Paste temporary details only into the client or secure configuration store needed for the active slot.
• Treat temporary tokens as secrets while they are active.
• If a client reports that the session is gone, reconnect and start a fresh session before retrying.
• Longer requests may still depend on the client tool's own timeout and reconnect behaviour.