Polymarket CLOB API Keys: What NOVA Needs and What It Never Asks For
A practical guide to the Polymarket CLOB credential boundary NOVA uses before guarded BTC signal automation.
Polymarket automation starts with a credential boundary. If that boundary is loose, every other control becomes weaker.
NOVA uses Polymarket CLOB API credentials for execution setup. It does not need a wallet seed phrase. It does not need a raw private key. It does not need unrestricted wallet access. That line matters because CLOB credentials are made for trading requests, while seed phrases and private keys control the wallet itself.
The difference operators should care about
The CLOB is Polymarket's central limit order book. CLOB credentials let software make authenticated trading requests when the account is configured for that use. They are not the same thing as giving away the wallet's root control.
For NOVA, the credential handoff is only one part of setup. The system still needs payment verification, risk settings, and a no-submit check before any live automation is considered. A valid credential does not mean a live order should happen.
What NOVA asks for
NOVA asks for the information needed to check and use the Polymarket CLOB path for the approved setup. The exact fields can change as Polymarket updates its API, but the principle does not change: use the narrowest trading credential that supports the task.
The setup flow should confirm:
The account is the account the operator intends to use.
The API credential can be checked without placing an order.
The configured risk cap matches the operator's approved amount.
The first run can stay in no-submit mode until the operator is ready.
What NOVA never asks for
Do not paste a seed phrase into a setup form. Do not send a private key in chat. Do not give a tool broader wallet control than it needs.
If a trading tool asks for the keys that control the whole wallet, pause. That may be normal for a self-custody script you write and run yourself, but it is not the boundary NOVA uses for managed setup.
Why this matters for BTC 15-minute windows
Short market windows create pressure. Pressure is where sloppy credential handling happens. A trader sees a window forming, wants automation live fast, and skips the boring checks.
NOVA is built to slow that part down. The setup can move quickly after the facts are clear, but credentials, payment, and risk caps still need to pass before live mode.
The operator takeaway
Treat API credentials as a scoped tool, not a trust shortcut. NOVA's job is to help create a guarded path from signal to execution. The credential boundary is where that path starts.