Skip to main content
Back to Docs
🤖Bot Builder

Strategy Marketplace & Library

Publish your bots or fork community strategies

The Strategy Marketplace turns Predite into a two-way bot ecosystem. Instead of building every automated strategy from scratch, you can fork a configuration that someone else has already tuned, publish your own bot for the community to use, and study an official, Predite-maintained library of templates with live backtested stats. This page covers all of it: the community Marketplace (/dashboard/marketplace), the official Strategy Library (/dashboard/strategies-library), how publishing and forking actually work under the hood, the likes/forks reputation system, and the plan gating you need to know before you click anything.

Two Surfaces, One Goal

Predite ships two distinct strategy hubs, and it's worth understanding the difference up front because they look similar but behave differently.

  • Strategy Marketplace (/dashboard/marketplace) is community-driven. Every entry here was published by another Predite user from one of their own bots. Publishing always records the source bot, and the performance shown is computed from that bot's real trades — cards carry a ✓ Verified by Predite block rather than numbers the author typed in. Quality still varies; that is what likes and forks are for.
  • Strategy Library (/dashboard/strategies-library) is the official catalog maintained by Predite. It contains a curated set of battle-tested templates (EV Follower, ARB Hunter, Whale Copier, Mean Reversion, News Reactor) with expected performance figures and a live 30-day backtest you can run on demand against real market history.

Both surfaces require the Pro plan ($59/mo) or higher just to browse. Forking a strategy into a working bot requires the Bot plan ($99/mo), because a fork creates a real, executable bot in your account — and bots are a Bot-tier feature. More on that below.

The Community Marketplace

Browsing and sorting

Open Dashboard → Tools → Strategy Marketplace — it is a card on the Tools hub, not a sidebar entry. You'll see a grid of published strategies, each shown as a card with:

  • The strategy name and a short description written by the author.
  • A template badge (e.g. ev_follower, arb_hunter) showing which engine the strategy is built on, plus up to three tags.
  • Verified performance computed from the source bot's real trades: number of trades, win rate, and P&L over a stated period. Win rate is color-coded — teal at 55%+, amber below.
  • A reputation footer: likes (❤) and forks (⑂).

Use the two sort tabs at the top:

  1. 🔥 Popular — ranks by total likes. This is the default and the best starting point.
  2. 🆕 Recent — ranks by publish date, newest first. Good for spotting fresh ideas before they accumulate likes.

Sorting is all the grid offers: Popular or Recent. There is no tag or template filter in the interface — the API accepts ?tag= and ?template=, but nothing on the page exposes them, so narrowing to "only arbitrage strategies" means reading the template badges yourself.

Reading reported stats critically

The trades / win rate / P&L numbers on a community card are self-reported by the author at publish time. Treat them as a starting hypothesis, not proof. A strategy showing "62% win rate, +$1,400 over 30d" might be real, cherry-picked, or measured during an unusually favorable market window. Two habits protect you:

  • Cross-check with the official Library. If a community strategy is built on the ev_follower template, open the Library entry for EV Follower and run its 30-day backtest to see how that engine behaves on current data.
  • Backtest after forking. Once you fork (Bot plan), the bot lands in your account where you can run it through the Backtesting engine yourself, then validate it in Paper Trading before risking capital.

Likes and forks: the reputation layer

Reputation on the Marketplace is intentionally simple and trader-honest:

  • Likes signal "this is worth a look." They drive the Popular ranking.
  • Forks are the stronger signal — they mean people actually copied the strategy into their own account and ran it. A high fork count is harder to fake than likes and usually the better quality indicator.

When you publish, these counters become your public track record. A strategy that accumulates forks is the closest thing Predite has to a community endorsement.

Forking a Strategy

Forking is the core action of the Marketplace. A fork creates a brand-new, independent bot in your own account with the same configuration as the source strategy — it is *not* a live link. The original author can later change or delete their published strategy and your forked bot is completely unaffected.

Requirements

  • Bot plan, active subscription. The fork endpoint checks your plan server-side and returns a clear "Bot plan required to fork strategies" message if you're on Starter or Pro. Browsing is Pro; forking is Bot.

How to fork — step by step

  1. On the Marketplace, find a strategy you want and click the ⑂ Fork button on its card.
  2. Predite creates a new bot in your account named `<Strategy Name> (fork)`.
  3. The bot is created paused by default. This is deliberate — nothing trades until you explicitly review and start it.
  4. The bot's platform defaults to Polymarket. You can switch it to Kalshi (or adjust anything else) afterward in the bot editor.
  5. The source strategy's fork counter increments, and you'll see a success toast pointing you to Dashboard → Bots to edit the new bot.

What gets copied — and what doesn't

What carries over:

  • The template (which engine the bot runs).
  • The full config — thresholds like minimum edge, maximum position size, stop-loss percentage, copy percentage, and any other template-specific parameters.

What does not carry over:

  • The author's trade history, capital, or live P&L. You start clean.
  • The author's wallet or platform connection. The bot runs against *your* connected account.
  • Any link back to the original. Edits you make are yours alone; the author never sees them.

After forking: the safe path to live

Because a fork starts paused, you control the entire ramp-up:

  1. Open the bot in Dashboard → Bots and review every parameter. A config that suited the author's bankroll may be too aggressive (or too timid) for yours — pay special attention to max_size_usd.
  2. Run a backtest to see how the strategy performed on recent history. See Backtesting.
  3. Switch the bot to paper mode and let it run on virtual capital for a meaningful sample — aim for 30+ closed trades. See Paper Trading.
  4. Only then enable live execution, which itself requires the Bot plan and a connected wallet. See Live Trading and Connecting Your Wallet.

Publishing Your Own Strategy

Sharing a bot you've built is how you earn reputation — and help the community. Publishing happens from the Bots page, not the Marketplace.

How to publish — step by step

  1. Go to Dashboard → Bots and find the bot you want to share.
  2. Click the 🏪 Publicar / Publish button on that bot's card. A publish modal opens.
  3. Fill in the public-facing details. These are separate from your private bot: - Name — defaults to your bot's name, but you can give the public version a clearer title. - Description — explain what the strategy does, when it works best, and known risks. This is the single biggest factor in whether people fork you. - Tags — up to 10, for discoverability (e.g. arbitrage, low-variance, news).
  4. Submit. Predite creates a Marketplace entry via the strategies API with visibility = published, so it appears in the public Marketplace immediately.

What publishing shares — and what it protects

Publishing copies only the strategy's template and configuration. It deliberately does not expose:

  • Your bot's live trades, current positions, or running P&L.
  • Your wallet address, API keys, or platform credentials.
  • Your original bot, which stays private and keeps running exactly as before.

In other words, a published strategy is a recipe, not a window into your account. People who fork it get the recipe and cook with their own ingredients.

Visibility options

Strategies support three visibility states:

  • Published — listed publicly in the Marketplace and forkable by anyone on the Bot plan.
  • Unlisted — hidden from the public grid. Be aware that this is not "shareable by link": the fork endpoint only resolves published strategies or your own, so anyone else following a direct link to an unlisted strategy gets a 404. Treat unlisted as private-with-a-URL, not as a sharing mode.
  • Draft — saved but invisible to others.

Changing a strategy's name, description, tags or visibility after publishing — or deleting it — is not possible from the interface yet. The PATCH and DELETE endpoints exist, but no screen calls them: the app only publishes, likes and forks. If you need a published strategy changed, publish a corrected version. (When editing does arrive, it will not affect bots others have already forked — a fork is a copy, not a link.)

Publishing tips

  • Write an honest description. State the conditions where the strategy struggles (e.g. "loses during breaking-news spikes"). Honest cons build trust and ironically earn *more* forks than hype.
  • Tag accurately. Mistagged strategies get ignored because they surface for the wrong searches.
  • Set a sane `max_size_usd` before publishing. Forkers inherit your sizing as a starting point; a reckless default reflects badly on you and can hurt the people who trust your strategy.

The Official Strategy Library

The Strategy Library (/dashboard/strategies-library, Pro plan) is Predite's curated catalog. Unlike community entries, these are maintained by Predite and come with structured documentation and a live backtest.

What each entry includes

Every Library strategy is an expandable card showing:

  • Category (Signal, Arbitrage, Copy, Quant, News) and a risk level (low / medium / high, color-coded).
  • Expected win rate and expected Sharpe ratio — a single figure each, prefixed with ~ (e.g. ~58% and ~1.4). These are fixed reference values per strategy, not ranges and not recomputed per run.
  • A detailed description of the mechanism, plus explicit Pros, Cons, and a Best For profile so you can match a strategy to your own style and bankroll.
  • The default config the strategy ships with (e.g. EV Follower: min_edge_pp: 15, max_size_usd: 200, stop_loss_pct: 25).

The five current entries are EV Follower (signal-driven auto-buys on edge), ARB Hunter (cross-platform Polymarket↔Kalshi arbitrage), Whale Copier (mirrors verified top wallets), Mean Reversion (fades unexplained extreme moves), and News Reactor (trades breaking headlines via AI Market Match).

Running a live 30-day backtest

The Library's standout feature is Preview Backtest 30d:

  1. Expand any strategy card.
  2. Click Preview Backtest 30d. Predite runs the strategy's config through the backtest engine against the last 30 days of real market history.
  3. You get back trades, win rate, P&L, and max drawdown for that window.

This is the honest counterpart to the community Marketplace's self-reported numbers: the same engine, the same recent data, every time. Note that expected win rate and Sharpe are 2-year estimates — the live 30-day backtest reflects only the current regime and will swing with volatility. Read both together.

From Library to bot

Click Use this strategy → on any Library entry to jump to the bot builder with that template pre-selected (/dashboard/bots?template=<id>). From there it's the same safe ramp: configure, backtest, paper trade, then go live. The Library is the recommended on-ramp for new bot builders because the configs are sane defaults and the backtest gives you immediate, trustworthy feedback. For a deeper look at each engine's parameters, see Bot Strategies.

Plan Gating Summary

  • Browse Marketplace or Library: Pro ($59/mo) or Bot ($99/mo).
  • Publish a strategy: any plan that can build bots — in practice the Bot plan, since publishing is done from a bot you own.
  • Fork a strategy into a working bot: Bot plan, active subscription. Enforced server-side.
  • Run forked bots live: Bot plan plus a connected wallet and live trading enabled.

Gotchas Worth Knowing

  • A fork is a snapshot, not a subscription. It will not auto-update when the author improves their strategy. Re-fork if you want the latest version.
  • Reported community stats are unverified. Always validate with your own backtest and paper trading.
  • Forked bots start paused on Polymarket. Nothing trades until you start them, and you may need to switch the platform to Kalshi.
  • Inherited sizing can be wrong for you. Re-check max_size_usd against your bankroll and your Kelly Calculator output before going live.
  • Editing or deleting your published strategy never touches bots others have already forked — those are independent copies.

Related Docs