YAP Sentinel
FrançaisRequest a demo
Controlled pilot — YAP Sentinel

Eight agents. One accountable workflow.

Specialized analysis without autonomous authority.

Each agent has a narrow mission, a defined output, evidence requirements, and explicit prohibited actions. The pilot is designed to help people decide—not to decide for them.

Human approval required

Supervised case pipeline

minimum-fact intake → specialist analysis → evidence synthesis → human decision → approved external action → sanitized improvement note

Pilot agent directory

One case, handed off with context intact.

Specialists receive only the information needed for their task. Every output identifies evidence, confidence, limitations, and the next required human approval.

A01Controlled pilot — YAP Sentinel

Teller intake

Teller Intake Orchestrator

Guide one calm question at a time, collect the minimum necessary facts, and route the case to the right specialists.

  • Clarify asset, amount, payment method, and destination
  • Ask who supplied the wallet and why the transfer is happening
  • Surface coaching, secrecy, urgency, and payment-story signals
Boundary

Recommends the next teller step; it never refuses or freezes a transaction by itself.

Pilot limitation

Pilot design only. Live case routing, schema enforcement, and Trading Tool integration still require implementation and verification.

A02Controlled pilot — YAP Sentinel

Scam patterns

Scam Pattern & Behavioral Risk

Connect the customer’s story and transaction pattern to known crypto-enabled scam scenarios without blaming or diagnosing the customer.

  • Identify fake profits, withdrawal taxes, and verification fees
  • Recognize romance, investment, job/task, impersonation, and recovery patterns
  • Explain which observed facts support each risk indicator
Boundary

Never uses protected traits, makes a diagnosis, or labels the customer or another person a criminal.

Pilot limitation

Pattern coverage is defined for synthetic pilot evaluation; no measured production detection performance is claimed.

A03Controlled pilot — YAP Sentinel

Entity research

Person / Entity Research

Conduct lawful, purpose-limited research on identifiers supplied by the customer or directly relevant to the case.

  • Research names, handles, domains, companies, emails, and phone numbers
  • Classify findings from confirmed through insufficient evidence
  • Preserve contradictory findings and source references
Boundary

Uses lawfully obtained public sources only—no doxxing, leaked data, login bypasses, or contact with suspected scammers.

Pilot limitation

No live research sources or entity-resolution integrations are implemented as part of this marketing site.

A04Controlled pilot — YAP Sentinel

On-chain analysis

On-Chain Analysis

Explain defensive wallet and transaction indicators across direct, one-hop, and two-hop exposure.

  • Review transaction IDs, flows, clusters, and counterparties
  • Surface exchange, bridge, mixer, sanctions, and consolidation indicators
  • Preserve explorer links, vendor labels, timestamps, and graph references
Boundary

Wallet labels are indicators, not proof; the agent never supplies laundering guidance, assigns identity from an address, or promises recovery.

Pilot limitation

No blockchain-analytics integration is live. Hop analysis and third-party labels depend on separately approved tools and data.

A05Controlled pilot — YAP Sentinel

Phishing review

Phishing & Infrastructure Reporting

Analyze suspicious infrastructure safely and prepare an evidence-rich abuse report for approved human submission.

  • Record exact and redirected URLs, domains, DNS, certificates, and hosting
  • Capture synthetic screenshot references, impersonated brands, and wallet indicators
  • Track whether personal information has been redacted
Boundary

Suspicious links are never opened on teller workstations, and no report is submitted automatically.

Pilot limitation

Sandbox and reporting-portal integrations are interface placeholders until they are implemented, security-reviewed, and approved.

A06Controlled pilot — YAP Sentinel

Evidence packaging

Compliance & Law-Enforcement Packager

Turn case facts and specialist findings into a chronological, reviewable escalation package.

  • Separate observed facts from inference
  • Highlight missing fields and contradictory evidence
  • Draft internal escalation and suspicious-activity narratives
Boundary

Prepares drafts only; qualified humans decide, approve, and file.

Pilot limitation

Jurisdiction-specific templates, legal interpretations, and filing connections require separate implementation and qualified review.

A07Controlled pilot — YAP Sentinel

Victim support

Victim Support & Psychological Safety

Help staff speak calmly and without shame to customers who may be caught in a long-running scam.

  • Encourage a pause before further payments
  • Help preserve evidence and avoid recovery scams
  • Escalate immediate self-harm danger to emergency support and a supervisor
Boundary

Does not provide therapy, diagnose, shame, argue, promise recovery, or suggest confronting the suspected scammer.

Pilot limitation

Support scripts assist staff; they are not clinical care, crisis services, or a substitute for emergency procedures.

A08Controlled pilot — YAP Sentinel

Safe improvement

Continuous Improvement / Codex Refiner

Turn sanitized frontline feedback into testable changes for human review.

  • Draft issues, prompt differences, test cases, and documentation
  • Require regression coverage for behavioral changes
  • Keep an explicit change history and reviewer decision
Boundary

Never trains on raw customer data, removes approval gates, adds protected-trait signals, or deploys automatically.

Pilot limitation

The improvement workflow is an architecture proposal; it does not train, change prompts, or deploy code autonomously.

Scenarios the pilot is designed to surface

The story around the transfer matters.

01Pig-butchering02Romance or investment scams03Job and task scams04Impersonation05Fake withdrawal taxes or fees06Wallet-verification payments07Recovery scams08Coaching and secrecy09Artificial urgency10Fake displayed profits

Research boundary

Investigate the signal. Do not pursue the person.

01

Research is limited to lawfully obtained public sources.

02

Suspicious links are analyzed in an isolated environment—not on a teller workstation.

03

Agents never contact suspects, use leaked data, or bypass access controls.

04

A name, wallet label, or cluster is never treated as identity proof on its own.

Initial integration boundary

Interfaces first. External actions later—and only with approval.

  • Blockchain analytics vendorInterface only
  • Public block explorerInterface only
  • URL sandboxInterface only
  • Domain intelligenceInterface only
  • KYC / sanctions providerInterface only
  • Case managementInterface only
  • Reporting portalsInterface only

Built for the counter. Designed for review.

See where Sentinel fits in your operation.

Request a demo