> For the complete documentation index, see [llms.txt](https://docs.qubixquantum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qubixquantum.com/understand/introduction.md).

# Introduction

#### What is Qubix

Qubix lets you use a real quantum computer through a simple chat interface. No code, no setup and nothing to install.

Quantum computers are some of the most advanced computing systems in the world, but using them has traditionally required specialized knowledge, technical setup, and quantum programming experience. For most people, that creates a wall between the idea of quantum computing and actually being able to use it.

Qubix removes that wall.

You describe what you want in plain language, and Qubix helps turn that request into a quantum workflow that can run on supported quantum hardware.

Here is the basic flow:

1. You ask for something in normal language, such as flipping a coin, generating randomness, or selecting a random winner.
2. Qubix interprets your request and turns it into quantum instructions.
3. The job is submitted to supported IBM Quantum hardware.
4. You receive the result, along with proof that the run was executed on real quantum hardware.

The goal is simple: make quantum computing accessible, understandable and verifiable.

#### Provable, Not Claimed

This is the core idea behind Qubix.

Many products use the word “quantum,” but very few make it easy for users to verify that real quantum hardware was actually involved. In many cases, the experience is powered by classical simulation, ordinary computation, or abstract claims that the user cannot inspect.

Qubix is built around proof.

Every completed hardware run should give you clear execution details, including:

* The code or circuit submitted for execution
* The hardware backend used
* The job ID
* The raw result returned from the quantum hardware
* Timing and execution metadata
* Relevant backend details, such as calibration or device information when available

Think of it like a receipt.

Anyone can claim that something happened. A receipt gives you evidence. Qubix is designed to give you that evidence for every real hardware run.

#### Why We're Different

Qubix is different for three main reasons.

1. It uses real quantum hardware

Qubix is not only a quantum themed interface or a classical simulator. When a job is submitted to supported quantum hardware, the run includes verifiable hardware execution details.

That means users can see where the job ran, what was submitted, and what result came back.

2. It removes the technical barrier

Instead of writing quantum code manually, you can describe your request in plain language. Qubix handles the translation layer and helps make the result understandable.

Quantum computing becomes something you can actually interact with, not just read about.

3. It is honest about what quantum can and cannot do

Quantum computing is powerful, but it is still early. Real hardware has limits. Not every problem is suitable for quantum execution, and not every quantum run creates an advantage over classical computing.Qubix is built to be transparent about that.

If something runs on real hardware, we show the proof. If something is simulated, experimental, limited, or not yet supported, we say so clearly. That honesty matters because the entire product is built around trust, verification, and access.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.qubixquantum.com/understand/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.