What We Verify
This process applies to Poker-Eye product pages, platform pages, setup guides, screenshots, FAQs, and other public claims about the application. It does not turn a commercial product page into an independent review of a third-party product.
The goal is traceability: a reader-facing statement must be supported by current documentation, visible product behavior, recorded product use or a confirmed answer from the product team. The page states the relevant limit when the available evidence is narrower than the claim.
Evidence Sources
We identify the source before drawing a conclusion. Documentation supports documented requirements; a demo supports only what is visible in that recording; product confirmation covers the specific fact answered.
Product Documentation
We use the current setup guide, version information and confirmed product notes to define the expected workflow and supported environment.
Recorded Product Use
We review full demo sessions and individual hands, not isolated promotional frames. The current evidence set includes 17 product-team videos.
Real Interface Captures
Screenshots must show the actual Poker-Eye overlay and table state. Player details are blurred before publication.
Product Confirmation
The product team confirms facts that cannot be established from the interface alone, such as current formats, Fuel rules and support access.
Test Environment
Each check records the Poker-Eye version, Android version, phone or emulator configuration, poker room, game format, date, and source of access. Compatible Android phones use Android 9 or later; verified LDPlayer configurations include 9.2.7.0 with Android 12 and 9.5.27 with Android 9. Product confirmation also covers MuMuPlayer for Mac on Apple Silicon Mac.
Published LDPlayer 9 minimums are identified as emulator-vendor requirements rather than Poker-Eye performance measurements. MuMuPlayer for Mac runs on an Apple Silicon Mac; it does not add iPhone or iOS support. A result from one room, format, or emulator is not extended to another environment without separate evidence.
Verification Workflow
- Confirm the current build, installation requirements and Agent Code flow.
- Record the device or emulator, room, format and source of access.
- Open the supported poker room and join the table manually.
- Verify the live inputs and the action cue shown over the room interface.
- Check guidance mode and automatic mode as two modes of the same Poker-Eye application.
- Verify ready, connection, balance or state, and unsupported-game indicators where evidence is available.
- Record the result with a screenshot, video timestamp or product confirmation while protecting player data.
- Reconcile the page copy, compatibility list, FAQ, links and structured data with the verified result.
Verify Guidance and Automatic Modes
Poker AI and Poker Bot are not tested as separate applications. Poker AI describes the shared decision engine and guidance mode; Poker Bot describes the optional automatic mode in the same Poker-Eye application.
- Live ContextCurrent hand, cards, position, table state, and available opponent signals.
- Action CueVisible Raise, Bet, Call, Check, or Fold text over the room interface.
- Guidance ModeYou see the cue and click the room control manually.
- Automatic ModePoker-Eye uses the same decision engine and clicks the corresponding supported action.
- User ControlThe mode can be changed, paused, or stopped from the on-table control.
- Multiple TablesEvidence must show a separate Poker-Eye account and status indicator for each active table; the practical number depends on the computer and emulator setup.
Compatibility and Status Checks
Room and format claims are checked separately. Current confirmed room support covers AAPoker, RedDragon, WePoker, PPPoker, WPT Global, HHPoker, XPoker, PokerWorld, and DePuZhiXing. Published room-format combinations appear on the product pages.
The table indicator is verified by both icon and meaning: green for ready, gray signal bars for a connection issue, orange for a balance or operating-state warning, and a red cross for an unsupported game type. The indicator belongs to the active table window.
Claims and Limitations
We separate directly observed behavior, product-team confirmation, and information still awaiting clarification. A screenshot is evidence only for what it visibly shows. A product statement is not presented as an Editorial Team test result without supporting method and conditions.
Poker-Eye does not guarantee profit, win rate, account safety, or permitted use in every room or jurisdiction. Current room rules and local requirements take priority. Fuel rates depend on the room and game type and are checked through the official Support bot.
Fuel and Support
Fuel is used per hand or round. Consumption depends on the room and game type, so the current rate is checked in the official Poker-Eye Support bot before use.
The Support bot contains the knowledge base and provides access to a live operator 24/7. Technical specialists and analysts are available through Support when needed.
Limitations, Updates and Corrections
A new application build, compatibility change, revised room rule, Fuel change, support change, new product evidence or material error can trigger another check. The team re-verifies the affected claim and connected page elements rather than changing one sentence in isolation.
Material factual errors are handled under the Editorial Policy. Update dates change after material verification work, and a correction note is added when the change affects a decision-relevant fact.
Questions About Product Verification
To question a Poker-Eye product claim or provide newer evidence, use Contacts and include the page URL, disputed passage, product version, room or format and strongest available source. Learn more about responsibility on the Editorial Team page and about publishing standards in the Editorial Policy.
Include the page URL, product version and strongest available evidence.