Skip to main content
SeeSaw is a social prediction platform: users take positions on prediction topics, publish opinions arguing for a side, and back the opinions they agree with. The SeeSaw Open API gives AI agents and third-party integrations a clean view of that world — plus the authenticated user’s own account, and optionally the ability to act on it. The same capability set is exposed on two faces, served by the same backend:

MCP server

https://api.seesaw.fun/mcp — 12 read tools (18 with a write key) over Streamable HTTP, ready for Claude Code, Cursor, VS Code, and any MCP client.

REST API

https://api.seesaw.fun/open/v1/* — the same capabilities as plain REST endpoints, documented by OpenAPI.

​
What you can do

Read — with any key:
  • Search and browse topics by keyword, ranking, or category.
  • Read a topic in full — options with current prices, resolution criteria and sources, status and trading deadline, the stake range it accepts and any live ruby boost.
  • Read the discussion — opinions with each author’s side attached.
  • See your own account — coin and gem balances, positions (open, settled, and sold in the app), opinions published and backed, watchlist, and the coin and ruby ledgers.
Write — only with a key created with the write scope:
  • Take a position on a topic — the number of coins the user chooses, within the topic’s stake range, on one option.
  • Publish an opinion on a topic — free, and no position needed; the opinion argues for the side you hold, or the side you pick.
  • Back an opinion you agree with.
Selling a position is only available in the SeeSaw app. See Rubies and positions. Every write is two steps: a preview that returns the summary to confirm and a short-lived token, then an execute call that accepts only that token. See Write actions and confirmation.

​
Design at a glance

  • One personal API key (sspat_…) in the Authorization: Bearer header — for both faces, no OAuth dance, no token exchange.
  • Two scope tiers chosen at creation: read, or read and write. Scopes are fixed for the life of the key.
  • snake_case fields, string decimals with 4 places (never floats), RFC 3339 UTC timestamps, opaque cursor pagination.
  • Every resource carries a human-visitable url.
  • Generous rate limits per key, with standard X-RateLimit-* headers; writes have their own tighter window.

​
Start here

Quickstart

Create a key, connect an agent, run your first query — in about five minutes.

MCP tools

All 18 tools, what they return, and when to use which.