Proposal: an optional Kalshi–PredictIt arb Raptor (paid third-party feed, signal-only)

[mastertyrone]

Proposal: an optional Kalshi–PredictIt cross-venue arb Raptor

DRADIS trades Kalshi but has no PredictIt venue, so Kalshi–PredictIt price gaps on the same political contracts are invisible to it. They can't be traded from DRADIS, but they're a signal a Squadron operator might want to see next to the Kalshi book.

Offer: I'd contribute src/raptors/kalshi_predictit_arb.rs, an optional Raptor publishing an ArbSnapshot (pairs, executable count, best worst-case net after fees). It would be observe-only like the Tide, Sports and Tennis Raptors. It is signal-only: no trading calls, and not consumed by any Viper. It runs in demo mode by default, and with no key it publishes one snapshot from a bundled fictional sample with sample_data = true and connected = false, so it reads as neutral.

Disclosure: the feed is kalshi-predictit-arb, built and operated by Team Takatini, and I (mastertyrone) am affiliated with it, so this is vendor-authored. Plain numbers:

• The live feed costs $0.02 USDC per call, paid via x402 on Base.
• There is no free tier. Demo mode costs nothing, but it shows fictional sample data, not real gaps.
• The default live poll is hourly: 24 calls, $0.48/day, under a default $0.50/day cap and a $0.02 per-call cap.
• Payment requirements are checked before anything is signed.
• The gaps it reports are indicative until checked against live depth, fees and resolution.

Docs: https://mastertyrone.github.io/kalshi-predictit-arb/ · client: https://github.com/mastertyrone/kalshi-predictit-arb

Would you welcome a PR for this? If so, I'll follow the PR template: all five builds green, constants in the three profile templates, the key registered in the Setup panel and .env.example, no AI co-author trailers, and the CLA signed. If a paid, vendor-written Raptor isn't something you want in the tree, close this and there'll be no follow-up from me.

[mbordash]

Thanks for the disclosure. Naming the affiliation and giving real per-call pricing up front is more than most proposals do, and the offer to follow the PR template properly is appreciated.

I'm going to decline, and I've written down why so it isn't a judgment call: see the new "Third-party and vendor-backed Raptors" section in docs/CONTRIBUTING.md. Three things put this outside core rather than any issue with the work: there's no usable free tier, no Viper consumes the snapshot, and it asks the engine to hold a funded wallet and sign per-call payments, which I'm not willing to add to a process that already holds venue keys.

The demo-mode behavior is the one I'd flag even for an add-on. A Raptor whose unconfigured state publishes fictional numbers is the exact failure shape this codebase keeps getting bitten by. An absent ask published as $1.00 produced a nonsense mid, a stale line still read as current. sample_data = true doesn't protect the consumer that forgets to check it. With no key, publish a neutral snapshot and report disconnected.

If you build it against RAPTOR_SOURCES as an external add-on, it gets the same Setup panel experience: credential field, signup link, cadence, free-tier arithmetic without DRADIS carrying it.