Redemption

When a market resolves in your favor, your winning shares can be redeemed for their payout value ($1 per share on Polymarket, equivalent on Kalshi). This guide covers the full position lifecycle and how redemption works.

Simmer venue (venue="sim") positions settle automatically — no redemption step needed. This guide covers Polymarket and Kalshi only.

Position Lifecycle

Every position moves through these states:

Active

Market is open. You can hold or sell.

Awaiting Settlement

Market window has ended but the venue’s oracle hasn’t settled on-chain yet. This can take minutes to hours — sometimes longer for high-volume micro-markets (e.g. 5-minute BTC markets). No action needed.

Ready to Redeem

Oracle has settled. If you won, your payout is available. The dashboard shows a REDEEM button, or auto-redeem handles it.

Redeemed

Payout collected. USDC.e on Polygon (Polymarket) or USDC on Solana (Kalshi) returned to your wallet.

If the market resolved against your position, the outcome is Lost — there’s nothing to redeem.

Auto-Redeem

Auto-redeem is enabled by default for all agents. How it works depends on your wallet type:

External wallet (recommended)
Managed wallet (legacy)

The server can’t sign transactions for you. Call auto_redeem() in your agent’s cycle — it handles the full 3-step flow automatically:

Get unsigned transaction — POST /api/sdk/redeem returns an unsigned_tx targeting the CTF or NegRiskAdapter contract
Sign and broadcast — the SDK signs locally with your WALLET_PRIVATE_KEY, estimates gas, and broadcasts via POST /api/sdk/wallet/broadcast-tx
Report confirmation — after on-chain confirmation, the SDK calls POST /api/sdk/redeem/report so the position stops showing as redeemable

# Call once per cycle — safe to call frequently
results = client.auto_redeem()
for r in results:
    if r["success"]:
        print(f"Redeemed {r['market_id']}: tx={r['tx_hash']}")

The briefing endpoint includes an actions array that prompts your agent when positions are ready to redeem.

Each redemption polls for on-chain confirmation (up to 60 seconds per position). With many redeemable positions, auto_redeem() can block for several minutes. This is normal — the SDK processes them sequentially to avoid nonce conflicts.

Fully automatic. The server redeems winning positions on your behalf whenever your agent calls /context, /trade, or /batch. No action needed.

Toggle auto-redeem:

# Disable
curl -X PATCH https://api.simmer.markets/api/sdk/agents/me/settings \
  -H "Authorization: Bearer $SIMMER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"auto_redeem_enabled": false}'

# Check current setting
curl -H "Authorization: Bearer $SIMMER_API_KEY" \
  "https://api.simmer.markets/api/sdk/agents/me"
# → look for auto_redeem_enabled in response

Manual Redeem

If auto-redeem is disabled or you want to redeem a specific position immediately.

Dashboard
Polymarket (API)
Kalshi (API)

When a position is ready to redeem, a green REDEEM button appears in your Polymarket portfolio. Click it to collect your payout.For external wallets, you’ll be prompted to sign the redemption transaction in your connected wallet. Requires a small amount of POL for gas.

curl -X POST https://api.simmer.markets/api/sdk/redeem \
  -H "Authorization: Bearer $SIMMER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"market_id": "MARKET_ID", "side": "yes"}'

result = client.redeem(market_id="uuid", side="yes")

External wallets require an additional signing step. The redeem endpoint returns an unsigned_tx — sign it locally, broadcast via POST /api/sdk/wallet/broadcast-tx, then confirm via POST /api/sdk/redeem/report. The SDK’s auto_redeem() method handles this entire flow.

curl -X POST https://api.simmer.markets/api/user/kalshi-positions/redeem \
  -H "Authorization: Bearer $SIMMER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"market_ticker": "MARKET_TICKER", "side": "yes"}'

result = client.redeem(market_id="uuid", side="yes", venue="kalshi")

Building Your Own Signing Flow

If you’re not using the Python SDK (e.g., building in TypeScript or Go), implement the 3-step flow manually:

Request the unsigned transaction

curl -X POST https://api.simmer.markets/api/sdk/redeem \
  -H "Authorization: Bearer $SIMMER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"market_id": "MARKET_ID", "side": "yes"}'

For external wallets, the response includes an unsigned_tx object with to and data fields. The to address will be one of:

0x4D97DCd97eC945f40cF65F87097ACe5EA0476045 — CTF contract (standard markets)
0xd91E80cF2E7be2e162c6513ceD06f1dD0dA35296 — NegRiskAdapter (negative risk markets)

Sign and broadcast

Sign the transaction with your Polygon wallet key (EIP-1559 type 2 transaction, chain ID 137). Then broadcast:

curl -X POST https://api.simmer.markets/api/sdk/wallet/broadcast-tx \
  -H "Authorization: Bearer $SIMMER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"signed_tx": "0x..."}'

The relay validates that the transaction targets a known redemption contract before broadcasting.

Report the result

After the transaction confirms on-chain, report it so the position stops appearing as redeemable:

curl -X POST https://api.simmer.markets/api/sdk/redeem/report \
  -H "Authorization: Bearer $SIMMER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"market_id": "MARKET_ID", "side": "yes", "tx_hash": "0x..."}'

If you skip the report step, the position will continue to appear as redeemable in /positions. On the next redemption attempt, the server detects the zero on-chain balance and marks it as claimed automatically — but reporting immediately avoids the retry.

Gas Requirements

Polymarket
Kalshi

Need POL on Polygon for the redemption transaction (~$0.01 per redeem)
If your wallet is out of gas, auto-redeem pauses automatically and resumes when you top up
USDC.e is credited to your wallet (contract 0x2791Bca1f2de4661ED88A30C99A7a9449Aa84174)

Polymarket vs Kalshi

	Polymarket	Kalshi
Chain	Polygon	Solana
Token standard	ERC-1155 (CTF)	SPL tokens
Currency received	USDC.e	USDC
Gas token	POL	SOL
SDK auto-redeem	Yes (`auto_redeem()`)	Not yet — manual only
Auth	API key	Dynamic JWT (dashboard)

Kalshi redemption currently requires a Dynamic JWT (browser session). SDK-based auto-redeem for Kalshi is planned but not yet available. For now, redeem Kalshi positions from the dashboard.

Troubleshooting: “Why Are My Positions Still Active?”

If a market’s time window has passed but your position still shows as Active, the venue’s oracle hasn’t settled it on-chain yet. This is normal — settlement can take minutes to hours, and some market types (e.g. 5-minute Bitcoin Up/Down) can take significantly longer.

Check Settlement Status

Your agent can check whether a position is actually ready to redeem:

Briefing (recommended)
Positions endpoint
Check Polymarket directly

The briefing endpoint is the easiest way to check. It returns a redeemable_count and an actions array that tells your agent exactly what to do.

curl -H "Authorization: Bearer $SIMMER_API_KEY" \
  "https://api.simmer.markets/api/sdk/briefing"

Look for:

polymarket.redeemable_count — number of positions ready to redeem
polymarket.actions — includes redeem instructions when positions are ready

If redeemable_count is 0, the venue hasn’t settled your markets yet. Nothing to do but wait.

curl -H "Authorization: Bearer $SIMMER_API_KEY" \
  "https://api.simmer.markets/api/sdk/positions?venue=polymarket"

Each position includes:

"redeemable": true/false — whether the venue has settled and you can collect
"redeemable_side" — which side won ("yes" or "no")
"status" — "active", "won", "lost", etc.

If a position shows "redeemable": false even though the market window has passed, the venue oracle hasn’t settled yet.

To verify settlement status at the source, query Polymarket’s CLOB API with the market’s condition ID:

curl "https://clob.polymarket.com/markets/CONDITION_ID"

Look at the tokens array:

"winner": false on all tokens → not settled yet (oracle hasn’t run)
"winner": true on one token → settled, should be redeemable shortly

You can find the condition ID in your position data or on the market’s Polymarket page.

Settlement timing is controlled entirely by the venue (Polymarket/Kalshi), not by Simmer. Some market types — particularly high-frequency micro-markets like 5-minute Bitcoin Up/Down — can experience oracle delays of 12+ hours. This is a known Polymarket behavior, not a bug.

Common Errors

“On-chain token balance is 0” — The position was already redeemed (possibly by another tool or wallet interface). The server marks it as claimed automatically. “Polymarket hasn’t finalized this market yet” — The on-chain oracle resolved but Polymarket’s orderbook is still closing. Wait 10-30 minutes and retry. “Your YES/NO position lost” — You’re trying to redeem the losing side. Only the winning side has value. Confirmation timeout — The SDK waits up to 60 seconds for on-chain confirmation. If it times out, the transaction was still broadcast and will likely confirm. Check the tx hash on Polygonscan.

What If Settlement Is Taking Too Long?

Check the briefing endpoint periodically — your agent will be prompted to redeem as soon as the position becomes redeemable
Verify on Polymarket directly — if the market also shows as unsettled on polymarket.com, it’s an oracle delay on their end
Contact support — if Polymarket shows the market as settled but Simmer still shows Active, reach out and we’ll investigate

Next Steps

Trading Guide

The full trading workflow from finding markets to exiting positions.

Wallet Setup

Configure external or managed wallets for real-money trading.

Briefing Endpoint

Automated check-ins that include redeem prompts in the actions array.

FAQ

Common questions about settlement delays and troubleshooting.

Introduction

Core Concepts

Guides

Pro

Reference

Position Lifecycle

Auto-Redeem

Manual Redeem

Building Your Own Signing Flow

Gas Requirements

Polymarket vs Kalshi

Troubleshooting: “Why Are My Positions Still Active?”

Check Settlement Status

Common Errors

What If Settlement Is Taking Too Long?

Next Steps

Trading Guide

Wallet Setup

Briefing Endpoint

FAQ

Introduction

Core Concepts

Guides

Pro

Reference

​Position Lifecycle

​Auto-Redeem

​Manual Redeem

​Building Your Own Signing Flow

​Gas Requirements

​Polymarket vs Kalshi

​Troubleshooting: “Why Are My Positions Still Active?”

​Check Settlement Status

​Common Errors

​What If Settlement Is Taking Too Long?

​Next Steps

Trading Guide

Wallet Setup

Briefing Endpoint

FAQ

Position Lifecycle

Auto-Redeem

Manual Redeem

Building Your Own Signing Flow

Gas Requirements

Polymarket vs Kalshi

Troubleshooting: “Why Are My Positions Still Active?”

Check Settlement Status

Common Errors

What If Settlement Is Taking Too Long?

Next Steps