$870M+
Your users are the target — malicious-signature phishing has taken more than $870M from over 760,000 wallets since 2023, inside flows like yours.
Put SafeClick inside your flow.
Why partner with us.
You get a verdict, enforced — only an allowed transfer reaches the broadcast path. No risk model to build, no score to interpret.
One layer, built for what’s next — the same decision layer for human wallets today and autonomous systems next.
Building one of these?
Non-custodial wallets
That want a judgment call on each transfer — not just spend caps.
Crypto payment teams
That want a risk check in the path before a transfer executes.
Embedded wallets
That own a signing flow and would rather integrate a verdict than build risk infrastructure in-house.
30-Day Enterprise Evaluation
See what SafeClick finds in your real transaction flow.
Run SafeClick alongside one agreed live workflow for 30 days. SafeClick returns evidence-backed Allow, Hold, or Block shadow decisions while your existing controls remain authoritative.
Use the evaluation to measure coverage, review flagged activity, and decide where a SafeClick decision belongs in your production path.
Evaluate the decision layer against traffic you already understand.
Synthetic examples can show that an API responds. Your own workflow shows whether the verdict is useful.
During the evaluation, SafeClick observes an agreed transaction stream and produces a decision record with the evidence available at that moment. Your team can compare the result with its existing controls, investigations, and known outcomes.
Measure coverage
See how many transactions SafeClick evaluated, which workflows were represented, and where evidence was complete or unavailable.
Review risk
Separate activity that was flagged, investigated, customer-confirmed, or still unresolved. Each category keeps its evidence source and denominator.
Define the production path
Use the end-of-evaluation review to decide whether SafeClick should remain observational, move into a paid production integration, or require a scoped Pilot first.
One company. One workflow. Thirty days of evidence.
- One approved company and one agreed transaction workflow
- A limited decision allowance sized during application review
- An approved KYT configuration for the standard verdict pipeline
- Standard API onboarding and integration guidance
- Shadow decisions that do not alter the customer's execution path
- An end-of-evaluation report with coverage and outcome categories
- A technical and business review with the DetentLabs team
- No automatic conversion or billing at the end of the evaluation
From application to evidence in four steps.
1
Apply with a real workflow
Tell us what the transaction flow does, which controls it uses today, its expected volume, and the failure you most want to catch.
2
Confirm the evaluation configuration
We agree on the workflow, data fields, decision allowance, activation plan, and KYT provider configuration. Applicants may use an approved supported provider account or request SafeClick-provided coverage.
3
Activate shadow decisions
The 30-day period begins with the first completed authenticated shadow decision. The application lapses if activation does not occur within 30 days of credential issuance. SafeClick evaluates the approved flow while the customer's existing controls remain authoritative.
4
Review the results
At the end of the evaluation, both teams review coverage, flagged activity, confirmed outcomes, unresolved cases, provider availability, and the next appropriate deployment stage.
KYT is part of the standard verdict.
Every Enterprise Evaluation runs with an approved KYT configuration. Applicants may bring an existing supported provider account or request SafeClick-provided coverage.
Provider eligibility, credential handling, expected usage, and the final decision allowance are confirmed during application review.
Production traffic, observational decisions.
SafeClick can evaluate data from an agreed live workflow while the customer's existing transaction controls continue to decide what executes. Shadow decisions are produced for measurement and review.
Shadow decisions are measurements for your review. They are not a guarantee that any threat will be detected or any loss prevented, and they do not replace your existing controls.
When a customer is ready for its production execution path to depend on a SafeClick decision, that work moves into a Paid Pilot or Production engagement with an explicit integration and responsibility boundary.
Send the transaction context required for a verdict.
Evaluation inputs are limited to the approved transaction, address, chain, and supporting metadata needed for analysis.
Never send private keys, seed phrases, wallet sessions, cookies, or unrelated customer data. SafeClick is non-custodial and does not require key material to produce a verdict.
Raw Evaluation data is retained for the agreed review and dispute window, then deleted as described in your written evaluation agreement and the SafeClick Privacy Policy. Raw data is used for model training only with written opt-in. Confirmed indicators of malicious activity may be retained to improve detection across the SafeClick network, subject to your written evaluation agreement, the SafeClick Privacy Policy, and applicable law.
An evaluation report with denominators, not a threat-count headline.
The report records the traffic SafeClick was asked to evaluate and distinguishes:
- completed shadow decisions
- flagged activity
- investigated cases
- customer-confirmed malicious activity
- unresolved activity
- provider-unavailable or incomplete-evidence events
The report records the Customer-provided workflow total, submitted volume, completed volume, sampling method, and coverage percentage so each result can be interpreted against the workflow that produced it.
Choose the next responsibility level.
The Evaluation ends after 30 days or when its decision allowance is consumed, whichever comes first. The Evaluation key is then disabled. There is no automatic charge.
One manual allowance increase may be reviewed with the DetentLabs team; the 30-day term itself is not extended. Continued access, customer-specific implementation, production enforcement, service commitments, or dedicated support are scoped separately.
Paid Pilot
Work with DetentLabs on a bounded production integration or a customer-specific execution path.
Production
Run SafeClick under a subscription and usage agreement with the required operational and service commitments.
Enterprise
Agree custom volume, policy, retention, support, and service terms for a larger deployment.
Evaluation FAQ
When does the 30-day period begin?
The Activation Date is the timestamp of the first completed authenticated shadow decision, unless both parties agree to another date in writing. The application lapses if activation does not occur within 30 days of credential issuance.
What counts against the decision allowance?
Each completed ALLOW, HOLD, or BLOCK shadow decision consumes one unit of the allowance, including a completed decision with provider-unavailable or incomplete evidence. Authentication failures, malformed requests, internal retries, idempotent duplicates, and technical failures without a completed decision do not consume the allowance. Evidence gaps are reported separately and handled during the end-of-evaluation review.
Does the Evaluation change how our transactions execute?
Your existing controls remain authoritative throughout the Evaluation. SafeClick returns observational decisions for measurement and review.
Can we use our existing KYT provider?
Applicants may bring an approved supported provider account. Provider eligibility, delegated use, credential handling, chain coverage, and available capacity are confirmed during application review.
What if we need SafeClick-provided KYT coverage?
Request it in the application. DetentLabs will confirm availability and size the Evaluation allowance against the approved provider configuration.
What happens if a provider is temporarily unavailable?
SafeClick records the provider state and preserves fail-closed decision semantics. A completed decision still counts against the allowance. Provider-unavailable and incomplete-evidence events are reported separately and handled during the end-of-evaluation review.
What happens after 30 days?
The Evaluation allowance ends and the Evaluation key is disabled. There is no automatic conversion or billing. One manual allowance increase may be reviewed, but the 30-day term is not extended; continued use is otherwise scoped as a Paid Pilot, Production, or Enterprise engagement.
Can SafeClick enforce decisions in production?
Pre-broadcast enforcement is available through a Paid Pilot or Production engagement, where the execution path, support, and responsibility boundary are agreed explicitly.
We are building an AI-agent payment flow. Can we apply?
Tell us about the flow. Agent-payment and x402 integrations are reviewed separately based on the current product surface and the party that controls execution.
Bring us one transaction flow worth evaluating.
Tell us how value moves, what controls it today, and which failure would matter most. We will review the workflow, KYT configuration, data boundary, and evaluation allowance with you.
Bring us a real payment flow.
Prefer email? partner@detentlabs.ai