This is the plain-language version of how the system captures, prices, grades, and reports picks. It is deliberately specific — the whole product is that our numbers mean exactly one thing, and you can see what that thing is. Where a convention disagrees with a capper's self-reported record, that disagreement is the point, not a bug.
Capture, pricing, grading, reporting — each step is written down so you can see what a figure counts and what it doesn’t. Where a convention disagrees with a self-reported record, that disagreement is the point.
The bot watches your picks channel passively. There is no /pick command — cappers write in plain English, exactly as they always have. When a pick appears, the system does five things in order, and none of them can be undone later:
A record only means something if the thing being recorded can't choose what gets recorded. Because the bot sees every pick the moment it's posted — not the ones someone later decides to log — there is no survivorship editing at the source.
A single "the odds were X" hides most of what matters. So every pick carries three prices, kept separate on purpose:
P_stated — the price the capper claimed.P_att0 — the best price actually attainable at the moment of posting, across monitored US-licensed books.P_real — the price a follower actually got, when a tail is recorded.Every price is converted from American to decimal the moment it's captured and stored with the probability it implies, so every comparison we make is on a fair-odds basis — the book's built-in margin taken out — rather than on raw American odds. If a pick is posted without odds, we fill in the fair-odds consensus across books at post and mark it odds_imputed — never a best-case number. If the stated price wasn't actually gettable at post, the pick is flagged stale_line: that flag is an honesty signal we show on purpose, not something we quietly clean up.
Every book builds in a margin — the vig. Comparing raw prices across books compares their margins as much as their opinions. Taking the margin out first lets us compare the real probability each price implies — the only fair way to say whether an edge was actually there.
Grades are not binary. A pick can land in any of six states, and every one of them is counted on the record — nothing is silently dropped:
Grading follows fixed rules and runs from official game data, cross-checked against a second source when one is configured. When two sources disagree, or when a case is inherently ambiguous, the pick is routed — loudly — to a review queue rather than auto-graded. That "unsafe set" includes things like a player who didn't play a prop, a postponed or suspended event, and a stat line still inside its correction window.
GradeRevision and a public correction-log entry — we never overwrite the original grade in place.Parlays are graded leg by leg. Each leg of a multi-leg pick is settled on its own from official game data. A void or push leg drops out and the combined odds are recomputed over the surviving legs; any losing leg settles the whole parlay as a LOSS; a leg that routes to review holds the parlay in PENDING_REVIEW until it clears; if every leg voids, the parlay is a PUSH. A parlay is settled only once every leg’s event is final — and every leg stays visible on the record.
Every graded pick stores the exact grading_rules_version it was settled under, so the rule set that produced any number is always recoverable.
We publish two ROI records side by side, always — and we lead with the one that can't be gamed:
ROI is profit divided by total risked, pooled — never an average of per-pick percentages. Win% is W / (W + L) with pushes excluded from the denominator, and we always show the full W-L-P plus the count of voids and ungraded picks. Units and rates only — you will never see a dollar-winnings figure on any surface we publish, because that is exactly the opacity marketing we exist to replace.
Detecting a real edge from raw ROI at typical prices can take thousands of picks; closing-line value converges in dozens to a few hundred. So ROI is a reporting metric and closing-line value is the ranking metric. No surface we build sorts cappers on raw ROI or win-rate — those make good screenshots and bad evidence.
Slippage is the distance between the number a capper posts and the number a follower can actually get. We measure it directly: capture the pick the second it posts, snapshot every monitored US book, then re-snapshot at 30 seconds, 2, 5 and 15 minutes. Posted price minus what's still gettable — compared on a fair-odds basis, with the book's margin taken out — is the slippage, and the baseline is always the best price attainable at post, never a best-case screenshot price.
Aggregated across a capper's picks, this produces the official-vs-realized gap: a record can look excellent at posted prices while the attainable record — what a follower could realistically get — is meaningfully worse. We ship how much of a capper's activity a figure covers alongside every aggregate, count one-sided markets without adjusting their margin, and label every figure with how many picks it's built on, the dates it covers, and the version of how we track. We publish our own error rate too.
Until a pilot community opts a period into public sharing, any slippage figure on this site is an illustrative preview on demo data from our own test server, clearly labeled as such. We would rather show a thin, honest launch than launder a made-up number as a finding.
Tailability is a single score for how followable a capper actually is — not an opaque "AI score." It's a plain weighted blend of pieces that each come straight from the locked record, and every piece is shown on its own, always. The main input is follower closing-line value; the rest capture whether the posted price was actually available, how the line held up as money came in, and how long the window to bet it stayed open.
Weights are frozen on first publication. Any change means a new methodology version, a changelog, operator sign-off, and a 30-day period where both versions are published side by side.
We say independently tracked — and we mean tracked, not rubber-stamped. A badge is something someone can sell you; "independently tracked, append-only, timestamped at post, graded by a system that can't be paid to look away" is a sentence you can check. We keep the language of formal attestation in reserve for a future book-synced execution tier that does not exist yet, and we won't borrow its credibility early.
We are a measurement layer, not a tout. We win by showing our work — including our own error rate and the losing weeks — not by showing you a screenshot and asking for trust.
RC Verified means a community’s betting record is independently tracked by Ranked Cappers: every pick is timestamped when it is posted, graded against game data, and written to an append-only ledger that no one — not the community, not Ranked Cappers — can edit or delete. The community’s owner has opted in to publishing this record. RC Verified is a statement that the record is independently tracked and owner-published — it is not an endorsement, rating, ranking, or prediction of future results, and it does not assert the record is good or profitable.
Only communities whose owners have published a record appear in the directory. A community that isn’t listed simply has no owner-published record on file — that is the only thing its absence means. We never label any community, and we publish only true facts measured from our own tracked data plus our verification status.
← Back to home Browse the directory → Get your Discord tracked →
No sportsbook money, no affiliate links, no “bet here” buttons on any surface, ever. The evidence outlives the vendor, and named records are published only with a community’s written consent.