Rank #5 of 5 in Payment Fraud Prevention
Access
Try itExperimental
See what an agent can do with Sift before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; commands tagged live-capable can re-run against the real endpoint from our edge, right now (▶ run live — the exact same request, live and recorded lines always labeled); sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$curl -s -X POST https://api.sift.com/v205/events -H 'Content-Type: application/json' -d '{}' # keyless → status 51 "Invalid API Key"recorded session — replayed, not liveVerified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Agentic commerce — stories about agentic commerce in this arenaAgentic commerceevidence →
Stories about agentic commerce in this arena
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Chargeback disputes — stories about chargeback disputes in this arenaChargeback disputesevidence →
Stories about chargeback disputes in this arena
Fraud agent access — stories about fraud agent access in this arenaFraud agent accessevidence →
Stories about fraud agent access in this arena
Fraud surfaces — stories about fraud surfaces in this arenaFraud surfacesevidence →
Stories about fraud surfaces in this arena
Model transparency — stories about model transparency in this arenaModel transparencyevidence →
Stories about model transparency in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Residency compliance — stories about residency compliance in this arenaResidency complianceevidence →
Stories about residency compliance in this arena
Review queues — stories about review queues in this arenaReview queuesevidence →
Stories about review queues in this arena
Risk scoring — stories about risk scoring in this arenaRisk scoringevidence →
Stories about risk scoring in this arena
Rules engine — stories about rules engine in this arenaRules engineevidence →
Stories about rules engine in this arena
Story verdicts — every judged story with its evidenceStory verdicts
Follow the green: where the map greys out is where Sift stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agentic commerce — stories about agentic commerce in this arenaAgentic commerce
Stories about agentic commerce in this arena
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
~6/10
unlocks → Webhooks · Official SDKs · MCP server · Machine-readable spec · Versioning policy · API sandbox · Official CLI · Full data export · The product distinguishes malicious bots from legitimate AI buying agents, so agent-driven purchases aren't blanket-blocked as fraud · Pass verified agent identity — agentic-payment protocols, signed agent tokens, delegated spending scopes — into the risk decision as a first-class signal · An agent can read my fraud posture and manage rules and lists programmatically — propose a velocity rule, update a blocklist — with human approval gates · An agent can work the review queue — pull flagged cases with their context, summarize the evidence, and recommend a decision for a human to confirm · The product ships its own AI assistant — natural-language queries over my fraud data, drafted rules, investigation summaries — built into the console
Subscribe to events via webhooks
—–
Build against official SDKs
—–
Issue scoped/least-privilege API credentials for an agent
n/an/a
Connect an agent via an official MCP server
—0/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—–
Test against a sandbox environment without touching production data
—–
Explore an interactive API reference with runnable examples
—–
Docs for agents
Point an agent at llms.txt or agent-oriented docs
—–
Agentic features
Delegate tasks to a built-in AI assistant inside the product
—–
Operate the product with natural-language commands
—–
Plug MCP servers into this product so it can use their tools
n/an/a
Get AI-generated insights and suggestions from my data inside the product
—0/10
Set up automations that run autonomously in the background
~4/10
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Chargeback disputes — stories about chargeback disputes in this arenaChargeback disputes
Stories about chargeback disputes in this arena
Shift fraud liability to the vendor — a chargeback guarantee that reimburses approved-then-disputed orders, with clear coverage terms
—–
See the numbers that matter — dispute rate, false-positive rate, approval-rate lift, review workload — and export them for the board
—–
Chargeback responses are automated — evidence compiled from order, delivery, and session data and submitted to the issuer without manual copy-paste
—–
Fraud agent access — stories about fraud agent access in this arenaFraud agent access
Stories about fraud agent access in this arena
An agent can read my fraud posture and manage rules and lists programmatically — propose a velocity rule, update a blocklist — with human approval gates
—0/10
An agent can work the review queue — pull flagged cases with their context, summarize the evidence, and recommend a decision for a human to confirm
—0/10
The product ships its own AI assistant — natural-language queries over my fraud data, drafted rules, investigation summaries — built into the console
—0/10
Fraud surfaces — stories about fraud surfaces in this arenaFraud surfaces
Stories about fraud surfaces in this arena
Protection extends beyond checkout — account takeover, fake account creation, promo and policy abuse are scored and managed in the same system
✓8/10
There are maintained integrations for my commerce stack — Shopify, Salesforce Commerce, BigCommerce, and the major PSPs — not just a raw API
—0/10
Use the product across whatever payment stack I run — multiple PSPs, gateways, and platforms — rather than being locked to one processor's rails
~5/10
Model transparency — stories about model transparency in this arenaModel transparency
Stories about model transparency in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Residency compliance — stories about residency compliance in this arenaResidency compliance
Stories about residency compliance in this arena
Control where fraud data lives and how long it's kept — regional residency options and retention controls that survive a privacy review
—0/10
European traffic is routed intelligently through SCA — 3DS triggered when required or risky, exemptions requested when safe — to protect both compliance and conversion
—–
Review queues — stories about review queues in this arenaReview queues
Stories about review queues in this arena
Flagged transactions land in a review queue that shows the full context — customer history, signals, similar cases — so I can decide quickly and consistently
~5/10
My review decisions and confirmed fraud outcomes feed back into the model and rules, so the system learns from every case we work
~6/10
Review work is a team workflow — assignment, escalation, SLAs, and a decision audit trail that shows who approved what and why
~5/10
Risk scoring — stories about risk scoring in this arenaRisk scoring
Stories about risk scoring in this arena
Feed the model my own signals — device fingerprints, behavioral data, custom metadata — so scoring reflects my business, not just network defaults
✓8/10
Scoring benefits from a cross-merchant network — a card or identity seen across thousands of other businesses informs the risk decision on mine
—–
Map score ranges to actions — allow, review, block, step-up 3DS — and tune thresholds to my own risk appetite instead of a fixed cutoff
~7/10
Get a machine-learning risk score for a transaction in real time — synchronously, before authorization completes — through a documented API
~6/10
Rules engine — stories about rules engine in this arenaRules engine
Stories about rules engine in this arena
Backtest a rule against my historical traffic before deploying it, seeing exactly what it would have blocked, flagged, and cost
—0/10
Maintain allow and block lists — emails, cards, devices, IPs — and velocity limits, managed through the dashboard and programmatically
!3/10
Author custom rules that combine model scores, velocity counters, list matches, and transaction attributes into allow, block, or review decisions
!5/10
Sorted by importance (agentic first) (high → low) · 54/54 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 6/10 | Xcommunity | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | untested | none yet | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | untested | none yet | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | none | untested | none yet | |
Get a machine-learning risk score for a transaction in real time — synchronously, before authorization completes — through a documented API C Scoring api | developer | Risk scoring — stories about risk scoring in this arenaRisk scoring | 3 | partial | 6/10 | Xcommunity | |
Author custom rules that combine model scores, velocity counters, list matches, and transaction attributes into allow, block, or review decisions C Rule authoring | risk analyst | Rules engine — stories about rules engine in this arenaRules engine | 3 | disputed | 5/10 | Dcontradicted | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | disputed | 5/10 | Dcontradicted | |
Flagged transactions land in a review queue that shows the full context — customer history, signals, similar cases — so I can decide quickly and consistently C Case review | risk analyst | Review queues — stories about review queues in this arenaReview queues | 3 | partial | 5/10 | Xcommunity | |
Use the product across whatever payment stack I run — multiple PSPs, gateways, and platforms — rather than being locked to one processor's rails C Psp coverage | developer | Fraud surfaces — stories about fraud surfaces in this arenaFraud surfaces | 3 | partial | 5/10 | Cclaimed | |
An agent can read my fraud posture and manage rules and lists programmatically — propose a velocity rule, update a blocklist — with human approval gates C Agent operations | ai-native user | Fraud agent access — stories about fraud agent access in this arenaFraud agent access | 3 | none | 0/10 | ||
Every score comes with its top risk factors — why this transaction looks risky — not just an opaque number C Explainability | risk analyst | Model transparency — stories about model transparency in this arenaModel transparency | 3 | none | 0/10 | ||
Chargeback responses are automated — evidence compiled from order, delivery, and session data and submitted to the issuer without manual copy-paste C Representment | ops user | Chargeback disputes — stories about chargeback disputes in this arenaChargeback disputes | 3 | none | untested | none yet | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | n/a | untested | none yet | |
Feed the model my own signals — device fingerprints, behavioral data, custom metadata — so scoring reflects my business, not just network defaults C Custom signals | developer | Risk scoring — stories about risk scoring in this arenaRisk scoring | 2 | full | 8/10 | Cclaimed | |
Protection extends beyond checkout — account takeover, fake account creation, promo and policy abuse are scored and managed in the same system C Abuse coverage | risk analyst | Fraud surfaces — stories about fraud surfaces in this arenaFraud surfaces | 2 | full | 8/10 | Cclaimed | |
Map score ranges to actions — allow, review, block, step-up 3DS — and tune thresholds to my own risk appetite instead of a fixed cutoff C Score actions | ops user | Risk scoring — stories about risk scoring in this arenaRisk scoring | 2 | partial | 7/10 | Xcommunity | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 6/10 | Cclaimed | |
My review decisions and confirmed fraud outcomes feed back into the model and rules, so the system learns from every case we work C Feedback loop | risk analyst | Review queues — stories about review queues in this arenaReview queues | 2 | partial | 6/10 | Xcommunity | |
Review work is a team workflow — assignment, escalation, SLAs, and a decision audit trail that shows who approved what and why C Team workflows | ops user | Review queues — stories about review queues in this arenaReview queues | 2 | partial | 5/10 | Xcommunity | |
Maintain allow and block lists — emails, cards, devices, IPs — and velocity limits, managed through the dashboard and programmatically C Lists | ops user | Rules engine — stories about rules engine in this arenaRules engine | 2 | disputed | 3/10 | Dcontradicted | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 3/10 | Cclaimed | |
An agent can work the review queue — pull flagged cases with their context, summarize the evidence, and recommend a decision for a human to confirm C Agent triage | ai-native user | Fraud agent access — stories about fraud agent access in this arenaFraud agent access | 2 | none | 0/10 | ||
Backtest a rule against my historical traffic before deploying it, seeing exactly what it would have blocked, flagged, and cost C Backtesting | risk analyst | Rules engine — stories about rules engine in this arenaRules engine | 2 | none | 0/10 | ||
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Control where fraud data lives and how long it's kept — regional residency options and retention controls that survive a privacy review C Residency | ops user | Residency compliance — stories about residency compliance in this arenaResidency compliance | 2 | none | 0/10 | ||
The product ships its own AI assistant — natural-language queries over my fraud data, drafted rules, investigation summaries — built into the console C Builtin ai | risk analyst | Fraud agent access — stories about fraud agent access in this arenaFraud agent access | 2 | none | 0/10 | ||
There are maintained integrations for my commerce stack — Shopify, Salesforce Commerce, BigCommerce, and the major PSPs — not just a raw API C Integrations | ops user | Fraud surfaces — stories about fraud surfaces in this arenaFraud surfaces | 2 | none | 0/10 | ||
European traffic is routed intelligently through SCA — 3DS triggered when required or risky, exemptions requested when safe — to protect both compliance and conversion C Sca | developer | Residency compliance — stories about residency compliance in this arenaResidency compliance | 2 | none | untested | none yet | |
Measure the model itself — precision and recall on my traffic, shadow-mode trials of new models or rules before they take over decisions C Model evaluation | finance lead | Model transparency — stories about model transparency in this arenaModel transparency | 2 | none | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | n/a | untested | none yet | |
Pass verified agent identity — agentic-payment protocols, signed agent tokens, delegated spending scopes — into the risk decision as a first-class signal C Agent identity | developer | Agentic commerce — stories about agentic commerce in this arenaAgentic commerce | 2 | none | untested | none yet | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | n/a | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | n/a | untested | none yet | |
Scoring benefits from a cross-merchant network — a card or identity seen across thousands of other businesses informs the risk decision on mine C Network effects | founder | Risk scoring — stories about risk scoring in this arenaRisk scoring | 2 | none | untested | none yet | |
See the numbers that matter — dispute rate, false-positive rate, approval-rate lift, review workload — and export them for the board C Outcome reporting | finance lead | Chargeback disputes — stories about chargeback disputes in this arenaChargeback disputes | 2 | none | untested | none yet | |
Shift fraud liability to the vendor — a chargeback guarantee that reimburses approved-then-disputed orders, with clear coverage terms C Guarantee | finance lead | Chargeback disputes — stories about chargeback disputes in this arenaChargeback disputes | 2 | none | untested | none yet | |
The product distinguishes malicious bots from legitimate AI buying agents, so agent-driven purchases aren't blanket-blocked as fraud C Agent detection | ai-native user | Agentic commerce — stories about agentic commerce in this arenaAgentic commerce | 2 | none | untested | none yet | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | n/a | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 42 stories with headroom
What would move Sift’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productDelegate tasks to a built-in AI assistant inside the product
nonemoves Built-in AIimpact 45
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Agenticness — how well agents can access and operate the productConnect an agent via an official MCP server
nonemoves agent-readyimpact 45
Missing: any mention of MCP, agent integration protocol, or official MCP server endpoint.
Fraud agent access — stories about fraud agent access in this arenaAn agent can read my fraud posture and manage rules and lists programmatically — propose a velocity rule, update a blocklist — with human approval gates
nonemoves PA Scoreimpact 30
Missing: any mention of AI agent integration, agentic rule-proposal workflow, or human-approval gate mechanism tied to programmatic rule/list changes.
Chargeback disputes — stories about chargeback disputes in this arenaChargeback responses are automated — evidence compiled from order, delivery, and session data and submitted to the issuer without manual copy-paste
nonemoves PA Scoreimpact 30
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
Missing: any documented data export/download capability, open-format export (CSV/JSON dumps), or account data portability tooling.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
Missing: any documentation of an opt-out mechanism, training-data exclusion policy, or user-facing privacy control preventing model training use.
Model transparency — stories about model transparency in this arenaEvery score comes with its top risk factors — why this transaction looks risky — not just an opaque number
nonemoves PA Scoreimpact 30
Missing: any documentation of explainability/reason-code output, feature-importance breakdowns, or examples of a score being paired with human-readable risk drivers.
Agenticness — how well agents can access and operate the productPoint an agent at llms.txt or agent-oriented docs
nonemoves agent-readyimpact 30
Missing: llms.txt file, agent-readable docs format, any mention of AI-agent-targeted documentation.
Showing the top 8 of 42 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map4 surfaces · 16 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
docs16 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Set up automations that run autonomously in the background
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Protection extends beyond checkout — account takeover, fake account creation, promo and policy abuse are scored and managed in the same system
- Use the product across whatever payment stack I run — multiple PSPs, gateways, and platforms — rather than being locked to one processor's rails
- Do everything through the API that I can do in the UI
- Flagged transactions land in a review queue that shows the full context — customer history, signals, similar cases — so I can decide quickly and consistently
- My review decisions and confirmed fraud outcomes feed back into the model and rules, so the system learns from every case we work
- Review work is a team workflow — assignment, escalation, SLAs, and a decision audit trail that shows who approved what and why
- Feed the model my own signals — device fingerprints, behavioral data, custom metadata — so scoring reflects my business, not just network defaults
- Map score ranges to actions — allow, review, block, step-up 3DS — and tune thresholds to my own risk appetite instead of a fixed cutoff
- Get a machine-learning risk score for a transaction in real time — synchronously, before authorization completes — through a documented API
- Maintain allow and block lists — emails, cards, devices, IPs — and velocity limits, managed through the dashboard and programmatically
- Author custom rules that combine model scores, velocity counters, list matches, and transaction attributes into allow, block, or review decisions
Tutorials docs15 stories
- Run the product headlessly / in CI for automation
- Drive the product through a documented public API
- Set up automations that run autonomously in the background
- Perform bulk operations across many items at once
- Define rules that trigger actions automatically on events
- Protection extends beyond checkout — account takeover, fake account creation, promo and policy abuse are scored and managed in the same system
- Use the product across whatever payment stack I run — multiple PSPs, gateways, and platforms — rather than being locked to one processor's rails
- Do everything through the API that I can do in the UI
- My review decisions and confirmed fraud outcomes feed back into the model and rules, so the system learns from every case we work
- Review work is a team workflow — assignment, escalation, SLAs, and a decision audit trail that shows who approved what and why
- Feed the model my own signals — device fingerprints, behavioral data, custom metadata — so scoring reflects my business, not just network defaults
- Map score ranges to actions — allow, review, block, step-up 3DS — and tune thresholds to my own risk appetite instead of a fixed cutoff
- Get a machine-learning risk score for a transaction in real time — synchronously, before authorization completes — through a documented API
- Maintain allow and block lists — emails, cards, devices, IPs — and velocity limits, managed through the dashboard and programmatically
- Author custom rules that combine model scores, velocity counters, list matches, and transaction attributes into allow, block, or review decisions
Hacker News9 stories
- Drive the product through a documented public API
- Define rules that trigger actions automatically on events
- Flagged transactions land in a review queue that shows the full context — customer history, signals, similar cases — so I can decide quickly and consistently
- My review decisions and confirmed fraud outcomes feed back into the model and rules, so the system learns from every case we work
- Review work is a team workflow — assignment, escalation, SLAs, and a decision audit trail that shows who approved what and why
- Map score ranges to actions — allow, review, block, step-up 3DS — and tune thresholds to my own risk appetite instead of a fixed cutoff
- Get a machine-learning risk score for a transaction in real time — synchronously, before authorization completes — through a documented API
- Maintain allow and block lists — emails, cards, devices, IPs — and velocity limits, managed through the dashboard and programmatically
- Author custom rules that combine model scores, velocity counters, list matches, and transaction attributes into allow, block, or review decisions
Solutions docs2 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$curl -s -X POST https://api.sift.com/v205/events -H 'Content-Type: application/json' -d '{}' # keyless → status 51 "Invalid API Key"reproduced$ curl -s -X POST https://api.sift.com/v205/events -H 'Content-Type: application/json' -d '{}' # [redacted]less → status 51 "Invalid API [redacted]"
{"status":51,"error_message":"Invalid API [redacted]. Please check your credentials and try again.","time":1789428793,"request":"{}"}
$curl -sL https://sift.com/llms.txt | head -3reproduced$ curl -sL https://sift.com/llms.txt | head -3 # Sift **Fraud Prevention Platform for Digital Business**
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
5 of 10 testable claims verified · 3 contradicted → integrity 0/100
14 distinct capability claims found in Sift’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
5
Verified
2
Unverified
3
Contradicted
6
Undersold
Verified (6)
“Integrates via REST APIs, a JS snippet, and iOS/Android SDKs”
Drive the product through a documented public APIpartialproof ↗
“Send user lifecycle event data (signups, orders, posts) to Sift via the Events REST API”
Drive the product through a documented public APIpartialproof ↗
“Send business decision actions (approve, block, cancel) back to Sift via the Decisions API”
My review decisions and confirmed fraud outcomes feed back into the model and rules, so the system learns from every case we workpartialproof ↗
“Produces a 0-100 risk score where higher means riskier”
Get a machine-learning risk score for a transaction in real time — synchronously, before authorization completes — through a documented APIpartialproof ↗
“Configure custom Decisions (e.g. Ban Account, Cancel Order) tied to real backend business actions”
Map score ranges to actions — allow, review, block, step-up 3DS — and tune thresholds to my own risk appetite instead of a fixed cutoffpartialproof ↗
“Offers Review Queues alongside Workflows for managing flagged cases”
Flagged transactions land in a review queue that shows the full context — customer history, signals, similar cases — so I can decide quickly and consistentlypartialproof ↗
Unverified (4)
“Add abuse-specific risk scores to target multiple distinct fraud types at once”
Protection extends beyond checkout — account takeover, fake account creation, promo and policy abuse are scored and managed in the same systemfullproof ↗
“Define custom events and fields to capture user actions not covered by built-in events”
Feed the model my own signals — device fingerprints, behavioral data, custom metadata — so scoring reflects my business, not just network defaultsfullproof ↗
“Blocks unauthorized access attempts (account takeover) in real time”
Protection extends beyond checkout — account takeover, fake account creation, promo and policy abuse are scored and managed in the same systemfullproof ↗
“Stops fraudulent account signups at creation time”
Protection extends beyond checkout — account takeover, fake account creation, promo and policy abuse are scored and managed in the same systemfullproof ↗
Contradicted (3)
“Integrates via REST APIs, a JS snippet, and iOS/Android SDKs”
“Workflows let you build custom rule-based real-time decisioning on key events”
Define rules that trigger actions automatically on eventsdisputedproof ↗
“Improves order approval rates while reducing declines on legitimate orders”
See the numbers that matter — dispute rate, false-positive rate, approval-rate lift, review workload — and export them for the boardnone
Undersold (6)
Run the product headlessly / in CI for automationpartialproof ↗
Set up automations that run autonomously in the backgroundpartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Use the product across whatever payment stack I run — multiple PSPs, gateways, and platforms — rather than being locked to one processor's railspartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Review work is a team workflow — assignment, escalation, SLAs, and a decision audit trail that shows who approved what and whypartialproof ↗
Claims outside our story set (2)
Real capability claims found in Sift’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Backfill months of historical data to jump-start and improve model accuracy”
source ↗“Provides a session_id field to track anonymous users across the JS snippet and Events API”
source ↗
Business model
Quote-only enterprise pricing sold on event volume — no public pricing page, sales contact only; a score-only model: Sift offers no chargeback liability-shift guarantee.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
