--- title: "MCP guide: go live" description: Who switches a connection on, what inactive means, what changes at go-live, the exact buttons to click, and how to pause a live connection. --- # Go live Going live means switching a vendor connection on. Only a person can do it, in the OneHazel app. This page shows every click. ::: tip What you need before you start - A connection your agent created. It shows as **Inactive** on the **Connections** page. - Every module it needs shown as **Conformant** on the **Integrate with AI** tab. - The values the vendor gave you, for example an API key, a secret and a site code. - A OneHazel login for your team. ::: ## What "inactive" means An inactive connection exists and can hold the vendor's keys, but OneHazel refuses the vendor's traffic for it. No player can play through it and no money moves. Your agent can only ever create a connection in this state. ## Why a person clicks Go live Going live lets a vendor move real money in your casino. No tool, API or agent can do it. The most your agent can do is create the connection inactive and tell your team it is ready. Before it stops, your agent replaces any key that was shown in a chat. Word for word: > If a callback key or signing secret was ever printed, logged or committed, call connect_rotate_secret with {"module":"<that module>","what":"both"} before you stop; write to a 0600 file inside your workspace, never print. The previous values stay accepted for 1 hour, so update the adapter from save_as within that hour. When it reaches this point, your agent asks you to open the connection and switch it on. Word for word: > Please open \[connection path\] in the OneHazel app, check the connection and its vendor credentials, and click Go live. Going live is the **Go live** button on the connection page, as the steps below show. ## Step 1. Open the connection Open **Connect casino**, then the **Integrate with AI** tab. Under **Ready for go-live review**, click the connection. Or open **Connections** and click it there. Your agent may also give you its path, such as `/operator/connections/conn_1a2b3c4d5e6f`: open `https://app.onehazel.com` followed by that path. ::: info What you should see The connection page, with a status of **Inactive** at the top and a box headed "Your AI agent asked to take this connection live". The box names the connector, lists the credential fields already set (names only, never the values), shows each module the connector needs with its conformance state, and has one **Go live** button. ::: ## Step 2. Enter the vendor's values, if they are not set yet If the box lists every credential field, skip to step 3. Otherwise click the **Credentials** tab and type each value the vendor gave you into its field. A field you leave blank keeps what is already saved. For PatePlay, fill **API Key**, **API Secret** and **Site Code**. **Default Player Country** is optional. Leave the two fields that say "only if your casino is not connected through the OneHazel contract" empty. Click **Save & test connection** to save them. The values are saved first, then tested. ::: info What you should see A test result under the fields, with a button beside it: - Green: the test passed. The button says **Go live**. - Amber: "Couldn't auto-verify -- credentials saved", with a line saying the connector has no public auth-check endpoint. The button says **Go live anyway**. Vendors that only call OneHazel, PatePlay among them, always show this: there is nothing to send their keys to before the first game. It is not a failure. - Red: the vendor's reason. The button also says **Go live anyway**, but do not click it; fix the values first. The button beside the result switches the connection on. You can click it, or go back to the box at the top of the page for step 3, which shows the same result in its own words. ::: ## Step 3. Click Go live Click **Go live** in the box. It tests the saved values with the vendor first, and only switches the connection on when the test passes. ::: info What you should see One of three results: - Passed: the status at the top changes to **Active**. The box is replaced by a card titled "Live since" with the date and time. That card shows only for a connection your agent asked to take live. - Amber: "This connector has no public check; OneHazel verifies it from the first wallet call. If the values are correct, click Go live anyway." Vendors that only call OneHazel, PatePlay among them, show this, because there is nothing to send their keys to before the first game. If the values are correct, click **Go live anyway**. - Red: "The credential test failed:", then the vendor's reason, then "Fix the values on the Credentials tab, then click Go live again." Check each value with the vendor before you go on. ::: Never click **Go live anyway** after a red result. Fix the values on the **Credentials** tab first, then click **Go live** again. Once the status is **Active**, tell your agent: it calls `connect_status` and the journey says it is complete. The same **Go live** button is on the **Credentials** tab, next to **Save & test connection**. A connection your agent did not create has no box at the top, and its buttons have other names. While no field is edited, it shows **Reactivate Connection**, which tests the saved values and switches the connection on when the test passes. After **Save & test connection** it shows **Activate Connection** for a test that passed, and **Activate Anyway** for one that did not. ## What changes at go-live - The vendor's calls are accepted for this connection. Before, they were refused. - On `app.onehazel.com` those calls reach your wallet marked `live`, which means real players and real money. Conformance and simulated rounds always used `test`. - Your agent's work for this vendor is done. To change a live connection's keys later, use the **Credentials** tab. ## How to pause, or roll back On the connection page, click **Pause** at the top right, on the same line as the connection's name. It shows only while the connection is **Active**. ::: info What you should see The status changes to **Inactive** and the **Pause** button goes away. Within about 30 seconds the vendor's calls are refused again. ::: Pausing deletes nothing. The keys, the conformance history and the vendor's settings stay as they were. A round that is already being played can fail while the connection is inactive, so pause at a quiet time when you can. To switch it back on, open the connection, click the **Credentials** tab and click **Go live**. It tests the saved values again first. Do not use **Delete** to pause. Delete moves the connection to **Trash**. ## After go live: what to watch - **The first live bets.** Open the vendor's game as a real player and check your own records: each round shows a bet, and a win when it paid, against that player's balance. The balance the game shows matches your records. If it does not, pause the connection and look up the code in [Troubleshooting](/connect/mcp/troubleshooting). - **Deliveries.** If the vendor sends you events through `webhook.receive`, ask your agent to call `connect_deliveries`. It lists the last 50 deliveries, with secrets hidden. A delivery that keeps failing means the address in your casino that accepts events is refusing it. - **Pause and roll back.** Pausing is the rollback, as the section above shows. Nothing is deleted, and switching back on tests the saved values again. - **The key rotation window.** If a OneHazel callback key or signing secret is ever shown in a chat, a log or a file in your code, ask your agent to replace it with `connect_rotate_secret`. The old values keep working for one hour only. Put the new values on your adapter's host and restart the adapter within that hour. ::: info What you should see A day of live rounds that matches your own records, and no delivery that keeps failing. ::: ## See also - [The journey](/connect/mcp/journey): every step before this page, and the questions your agent asks. - [Troubleshooting](/connect/mcp/troubleshooting): every code a connect tool returns, and what to do. - [Start here](/connect/start-here): the whole path from a new account to a game live on your casino.