Skip to main content

Integrations

Siren is a thin, opinionated layer that sits on top of several battle‑tested protocols and services. This page is the high‑level map.

Kalshi + DFlow

DFlow is how Siren connects to Kalshi prediction markets. Used for:
  • Fetching live markets and probabilities
  • Getting quotes for YES/NO trades
  • Submitting orders & transactions
Keys & env:
  • DFLOW_API_KEY
  • DFLOW_METADATA_API_URL
  • DFLOW_QUOTE_API_URL
Docs: DFlow docs

Polymarket

Polymarket is Siren’s second live signal source. Used for:
  • Fetching active markets from the Gamma API
  • Reading order book snapshots from the CLOB
  • Detecting fast probability moves in parallel with Kalshi
  • Feeding the same Siren signal feed and token-matching flow
Env:
  • POLYMARKET_API_KEY
  • POLYMARKET_SECRET
  • POLYMARKET_PASSPHRASE
  • POLYMARKET_HOST

Bags (token launch + routing)

Bags powers meme token launches and fee routing. Used for:
  • Creating and configuring new tokens
  • Setting partner/fee share
  • Surfacing on‑chain token stats
Keys & env:
  • BAGS_API_KEY
  • BAGS_PARTNER_CONFIG_KEY
  • BAGS_REF_URL
Siren Bags token: Docs: Bags docs

Jupiter (swaps)

Jupiter is used for token swaps inside Siren. Used for:
  • Swapping SOL ↔ tokens
  • Routing through the best venues
Env:
  • JUPITER_API_KEY
Docs: Jupiter docs

Supabase (database + admin)

Supabase backs Siren’s basic data layer. Used for:
  • Waitlist (waitlist_signups)
  • Users (users table with wallet, auth user id, signup source, country)
  • Admin queries for investor‑ready dashboards
Env:
  • SUPABASE_URL
  • SUPABASE_SERVICE_ROLE_KEY
Docs: Supabase docs

Privy (auth + embedded wallets)

Privy is used for social auth + embedded wallets. Used for:
  • Social login via Google, GitHub, X
  • Creating embedded Solana wallets for execution
  • Creating embedded EVM wallets for Base / Ethereum / Polygon accounts
  • Managing sessions and wallet export flows
Env:
  • NEXT_PUBLIC_PRIVY_APP_ID
Docs: Privy docs

Resend (emails)

Resend sends welcome + access‑code emails to early users. Used for:
  • Access code emails when admins generate codes for waitlist signups
Env:
  • RESEND_API_KEY
  • SIREN_EMAIL_FROM
  • SIREN_APP_URL
Docs: Resend Node docs

Putting it together

At a high level:
  • Supabase stores waitlists and users.
  • Kalshi / DFlow power the current in-app prediction market trade flow.
  • Polymarket powers the second live signal source.
  • Bags creates tokens and routes fees.
  • Jupiter trades tokens.
  • Privy authenticates users and provisions embedded wallets.
  • Resend handles email.
Siren’s job is to stitch these together into a single event‑driven trading experience.