1. Create your API key
Open the SeeSaw app, go to the MCP section of the sidebar, and create a key. You choose its permissions there:- Read only — browse topics and read your own account. Start here.
- Read and write — additionally lets the agent take positions, publish opinions and back opinions, spending your coins.
Scopes are fixed when the key is created; there is no upgrade path. To move from
read to read+write, create a new key. See Authentication.
2. Connect
For Claude Code, one command:3. First query
Ask your agent something like:What prediction topics are live on SeeSaw right now, and what are the odds?A typical run calls
list_topics (or search_topics) and reads the prices off
the result:
implied_price values are strings ("0.4988" = 49.88%) and sum to 1 across
a topic’s options. close_time is the trading deadline — the one to count down
to. stake_rules is the range of coins the topic accepts per order, and
ruby_boost shows a live boost on what a correct call pays (or null). Every
topic carries a url your agent can hand back to humans.
Prefer curl? The same capability over REST:
4. Your first write (optional)
With a read+write key, ask for something that costs coins:Put 300 coins on Yes on that Fed topic.Your agent should call
preview_order first with amount_coins: 300, show you
what it returns — the stake, your balance before and after, the price, and what
a correct call pays in rubies — and only call place_order after you say yes.
Compatible clients also raise their own permission prompt on that second call.
If you don’t say how much, the agent should ask you rather than pick an amount
itself.
If an agent tries to place an order without showing you a summary first, it
can’t: place_order accepts nothing but the token preview_order mints.
Next steps
Tools overview
All 18 tools and when to use which.
Write actions
The preview → confirm → execute flow in detail.
Rate limits
Per-key quotas and how to handle 429s.
Authentication
Scopes, key lifecycle, security, and revocation.