> ## Documentation index
> Fetch the complete documentation index at: https://docs.predictefy.com/llms.txt
> Use it to discover every available page before exploring further.

# Venue credentials

> Which venues need their own API credential, exactly what each one issues, and whether it reaches Predictefy or stays in your process.

You need one Predictefy API key to read data across every venue. Trading is different: the venue
owns the account, the funds, and the credential, so you get that credential from the venue itself.

**Fourteen of the sixteen served venues trade through the hosted API.** Four of those need no
venue credential at all — a wallet signature is the whole story. Arming is per deployment, so
`GET /v1/exec/venues` is the live answer for any given environment.

This page answers three questions in one place — does this venue need a credential, what exactly does
it issue, and does that credential reach Predictefy or stay in your process. For the full
walkthrough of any single venue, follow its guide; each one carries a "Step zero" section covering
account creation, funding, and eligibility.

## Two credential paths

Both are real, and which one a venue offers is a property of that venue, not a limitation of the API.

**Hosted lane.** You call `/v1/exec/{venue}/orders/…` and Predictefy performs the venue call. Where
the venue needs a credential, you send it on that request. Predictefy uses it in memory for that one
call and never stores or logs it. Predictefy never holds your funds — the venue custodies them.

**Client-side lane.** The credential never leaves your process. The venue SDK signs locally and talks
to the venue directly. Two venues offer only this path, by custody design.

Read [Trading & execution](/guides/trading/) for the full contract, including the required scopes and
the spend caps that bound every hosted submit. If you have not chosen a venue yet, start with
[Choose your first venue](/guides/trading/getting-started/).

## No venue credential — your wallet is the whole auth story

These venues issue no API credential to fetch. You sign with a key that stays yours, so there is no
API key screen to visit — though Pascal still requires an eligible venue account first.

| Venue                                                | What authenticates you                                                          | Where to start                                       |
| ---------------------------------------------------- | ------------------------------------------------------------------------------- | ---------------------------------------------------- |
| [Hyperliquid](/guides/trading/hyperliquid/)          | An EVM master wallet, or an agent you approve with it, signs the L1 action.      | [app.hyperliquid.xyz](https://app.hyperliquid.xyz)           |
| [Limitless](/guides/trading/limitless/)              | A Base EOA signs the order. Predictefy holds the partner HMAC credential itself. | [limitless.exchange](https://limitless.exchange)     |
| [Rain](/guides/trading/rain/)                        | An Arbitrum EOA signs and broadcasts the returned transaction.                   | [www.rain.one](https://www.rain.one)                  |
| [Pascal](/guides/trading/pascal/)                    | Your registered wallet key, or a revocable delegated trading key — no relay credential. Needs an eligible Pascal account and custody wallet first. | [pascal.trade](https://pascal.trade)              |

Never paste a seed phrase or private key into Predictefy. It never asks for one, and no hosted lane
needs it.

## Venue credential required

Create these in your own account at the venue, then supply them as each guide describes. Store them
outside source control — several are shown once and never again.

| Venue                                                    | What the venue issues                                                                                              | Where to create it                                   |
| -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------- |
| [Kalshi](/guides/trading/kalshi/)                        | An API key ID and its matching RSA private key. Record your subaccount if you use one — it must be a non-negative integer. | [kalshi.com](https://kalshi.com)                    |
| [Gemini](/guides/trading/gemini/)                        | A Trader API key and secret. See the settings note below — three account options must be right or auth fails.       | [exchange.gemini.com](https://exchange.gemini.com)                    |
| [XO](/guides/trading/xo/)                                | A CLOB API key, secret, and passphrase. Your EVM wallet must own an XO smart account for the default model.         | [xo.market](https://xo.market)                       |
| [Polymarket](/guides/trading/polymarket/)                | A CLOB key, secret, and passphrase. The direct SDK path can derive these locally instead.                           | [polymarket.com](https://polymarket.com)             |
| [Polymarket US](/guides/trading/polymarket-us/)          | A UUID key ID and a base64 Ed25519 API secret. This is request auth, not a Solana wallet key.                       | [polymarket.us](https://polymarket.us)              |
| [Myriad](/guides/trading/myriad/)                        | A wallet-bound API key and secret, tied to the connected EOA. Bare credentials are not supported.                   | [myriad.markets](https://myriad.markets)             |
| [Novig](/guides/trading/novig/)                          | An account access token you own. Confirm personal API credential access before depositing.                          | [novig.us](https://novig.us)                        |
| [Opinion](/guides/trading/opinion/)                      | A user API key, needed for hosted cancel and status. Hosted build and submit use Predictefy's builder key.          | [app.opinion.trade](https://app.opinion.trade)               |
| [Predict.fun](/guides/trading/predict-fun/)              | A session bearer for the hosted lane. On the direct SDK path the venue API key and wallet key stay in your process. | [predict.fun](https://predict.fun)                   |
| [PredictStreet](/guides/trading/predictstreet/)          | An API key, plus a vault that already exists for your account. **Build and submit only — this lane has no hosted cancel.** | [adipredictstreet.com](https://adipredictstreet.com) |

### Gemini needs three account settings, not just a key

A Gemini Trader key authenticates only when the account is configured for it: **time-based nonce
enabled, heartbeat disabled, and trusted-IP mode set to Unrestricted**. A key created without these
looks correct and still fails. Set them yourself — Predictefy never changes venue account settings or
accepts terms on your behalf. Master API keys must also supply an `account`.

## Venue-direct only — your credentials never reach Predictefy

One venue integrates client-side by design. This is a custody property rather than a gap: the
signing key and the venue credential stay in your process and go only to the venue, and Predictefy
never sees either.

| Venue                                          | How you trade it                                                                                                          |
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| [SX Bet](/guides/trading/sxbet/)               | `client.accounts.sxbet`, live since 2026-07-27. Your key signs each order locally; a venue API key covers V3 cancellation.  |

SX Bet does not appear in `GET /v1/exec/venues`, and `/v1/exec/sxbet/…` answers
`404 VENUE_NOT_SUPPORTED` by design. Its guide documents the client-side integration in full.

## Smarkets is not served

[Smarkets](/guides/trading/smarkets/) is a **dark venue** as of 2026-09-02: implemented, but excluded
from hosted routes, router fan-outs, and the served venue count until a commercial API agreement is
in place. `/api/smarkets/…`, account, and funding routes return 404. The venue-direct SDK client
stays in the package for customers holding their own Smarkets API approval, but it is not a supported
product lane.

## PRED is unavailable

[PRED](/guides/trading/pred/) has been darked since 2026-08-13: the venue refuses Predictefy
platform-key submissions for caller-owned Safes. This is the venue's own model, not a missing
integration. Do not fund it for hosted submit while it stays darked.

## A note on where these screens live

Each link above is the venue's onboarding entry point, taken from the execution service's own
requirements table (`packages/execution/src/venue-requirements.ts`), so it stays tied to what the
lane actually expects. The specific screen that issues a credential belongs to the venue and can
move without notice, so sign in there and look for API keys, API settings, or developer settings.

Before you deposit anywhere, check that venue's guide for eligibility: several venues restrict access
by jurisdiction, and one is geo-gated at the network level.

## Check what is actually armed

Arming is per deployment and can change. `GET /v1/exec/venues` reports the live state, and it is the
answer that matters — not this page, and not the venue's own marketing.