Use FraudLabs Pro from Claude
Add the FraudLabs Pro connection to a Space that runs Claude, then use it from every channel in that Space.

Create a FraudLabs Pro connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the FraudLabs Pro connection to a Space that runs Claude, then use it from every channel in that Space.
Add the FraudLabs Pro connection to a Space that runs Codex, then use it from every channel in that Space.
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
FraudLabs Pro screens ecommerce orders for fraud risk and helps merchants limit chargebacks across payment methods. With FraudLabs Pro connected to type.com, an ops Space can ask Claude to screen a new order, pull back a past screening result, confirm an SMS verification code, or log feedback that improves future scoring.
Connect FraudLabs Pro once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Run a new order through fraud screening so the team can decide whether to fulfill, hold, or cancel it.
Screen this order from a new customer paying with a different billing and shipping address using FraudLabs Pro.
Retrieve a previous order's fraud result to review during a chargeback dispute or customer service call.
Get the FraudLabs Pro result for order ID 88213 from last week's chargeback.
Submit feedback on a reviewed order so the fraud model learns from real outcomes over time.
Submit FraudLabs Pro feedback marking order 88213 as approved after our manual review.
Provisions a new sub-account under a reseller key, for teams managing FraudLabs Pro on behalf of customers.
Submits feedback on a screened order, marking it approved, rejected, or blacklisted to train future scoring.
Assesses an order's fraud risk before fulfillment.
Retrieves a previously screened transaction's result on a paid plan.
Checks whether an SMS one-time password was entered correctly after a verification request.
FraudLabs Pro provides fraud-prevention APIs for screening ecommerce orders, retrieving fraud results, submitting order feedback, and checking user/payment risk. Official SDKs are available across PHP, Java, Python, Ruby, .NET, Node.js, Rust, Go, Kotlin, and Scala, with API-key based screening requests.
Yes. Once FraudLabs Pro is connected to a type.com Space, Claude can screen new orders, pull past results, check SMS verification, and submit feedback from a thread.
FraudLabs Pro uses an API key, added once by an admin when the connection is created, who then decides which Spaces can use it.
Yes. A type.com automation can check a queue of new orders on a recurring schedule and flag any that score as high risk in a channel.
Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
Connect IBM X-Force Exchange to Claude in type.com to pull threat collections and check IP or URL reputation from a thread.
Connect Identitycheck to Claude in type.com to check API health, list KYC configurations, and manage endpoints from a thread.
Connect Ip2Proxy to Claude in type.com to check whether an IP is a VPN, proxy, or Tor exit node in a shared thread.
Ip2WhoisConnect Ip2Whois to Claude in type.com to pull domain registration records and hosted-domain data from a shared thread.