prediction-bridge-search

Use this skill when the user wants to find relevant prediction markets/events for:

• a short text query (topic, question, headline)
• a URL to an article
• an X (Twitter) status link (the backend resolves and extracts the tweet text)

Usage scenarios (when to use)

Use this skill when the user asks:

• “Find prediction markets for this topic/headline”
• “What markets match this tweet/X link?”
• “Search Polymarket/Kalshi for events about …”

This skill is best for:

• turning unstructured text (or an X URL) into ranked, actionable event links
• quickly surfacing the top 5–10 matches with a brief market snapshot

Not a good fit when the user wants:

• full market orderbooks or historical candles (use the market-data endpoints instead)
• deep-dive sentiment/timeline generation (use the event deep-dive endpoints instead)

This skill calls the existing Prediction Bridge backend endpoint:

• POST /api/v1/search/unified

It returns matched events (prediction market events) and optionally matched news.

Configuration

API base (defaults to production):

• PREDICTION_BRIDGE_API_URL

Defaults:

• Production: https://prediction-bridge.onrender.com/api/v1
• Local dev (if you run the backend locally): http://localhost:8000/api/v1

How to run

1. Build the query text

• If the user provides an X status link, pass the URL as text unchanged. The backend will resolve it.
• If the user provides plain text, pass it as-is.

2. Call unified search

Use exec with curl:

API_URL="${PREDICTION_BRIDGE_API_URL:-https://prediction-bridge.onrender.com/api/v1}"

curl -sS -X POST "$API_URL/search/unified" \
  -H "Content-Type: application/json" \
  -H "X-Request-ID: pb-$(date +%s)" \
  --data-binary @- <<'JSON'
{
  "text": "<USER_TEXT_OR_X_URL>",
  "limit": 10,
  "offset": 0,
  "include_inactive": false,
  "include_markets": true,
  "markets_per_event": 1,
  "include_translations": false
}
JSON

Notes:

• Use markets_per_event: 1 to keep payload small but still show the leading market.
• If the user explicitly asks for more markets per event, increase markets_per_event.

API response format (what you will receive)

POST /search/unified returns JSON with this shape (fields may be omitted or null depending on data availability):