iframe.polyembed.io inside your articles.
On every page load
1
Your page loads the iframe
Your article template renders the PolyEmbed iframe with the article’s title and keywords in the URL.
2
PolyEmbed authorizes the request
The widget reads the page’s origin from the browser’s
Referer header and checks that the widget is active, your publisher account is active, and the page is on your verified domain or one of its subdomains. If any check fails, the widget collapses.3
PolyEmbed searches Polymarket
The title and each comma-separated keyword become search queries against Polymarket’s public market data. Only active, open markets are considered.
4
Markets are scored
Each candidate gets a score built mostly from relevance to your title and keywords, with smaller weight for liquidity, volume, how soon the market resolves and category. Markets with effectively decided odds, or that aren’t accepting orders, are ranked lower. See Market matching.
5
The widget shows the best match, or collapses
If the top market clears the relevance threshold, the widget shows its question, odds and trade controls, and tells your page how tall to be. If nothing clears the threshold, the widget tells your page to hide the frame, so your layout never shows an empty box.
When a reader trades
1
Region check
The widget asks Polymarket whether trading is available in the reader’s region. If it’s blocked, or the check can’t complete, the reader sees odds only.
2
Sign in
The reader connects a browser wallet, or continues with email. The reader always owns the signer; PolyEmbed never holds their keys.
3
Deposit wallet
Polymarket’s SDK derives the reader’s Polymarket deposit wallet and deploys it through Polymarket’s gasless relayer.
4
Fund and trade
The reader funds the deposit wallet with pUSD through a bridge address, enables trading once, and places market orders. Orders go to Polymarket’s order book with PolyEmbed’s registered builder code.