# Greip integrations: IP data, scoring and payments

> Greip is a fraud prevention API that scores IP addresses, emails, phone numbers and payments, and provides IP geolocation, BIN and IBAN lookups.

**Canonical page:** https://tray.ai/connectors/greip-integrations/
**Categories:** Security and compliance
**Connects through:** HTTP Connector

## Overview

Greip is a fraud prevention API that scores IP addresses, emails, phone numbers and payments, and provides IP geolocation, BIN and IBAN lookups. Tray.ai connects to Greip through the HTTP Connector, so your workflows can call the Greip API alongside the rest of your stack.

## Use cases

### IP data

Read ip data in Greip from any Tray.ai workflow. The Greip API covers calls such as look up an IP and look up IPs in bulk.

- Look up an IP
- Look up IPs in bulk
- Get IP geolocation

### Scoring

Manage scoring in Greip from any Tray.ai workflow. The Greip API covers calls such as score an IP address and score an email.

- Score an IP address
- Score an email
- Score a phone number

### Payments

Read and manage payments in Greip from any Tray.ai workflow. The Greip API covers calls such as score a payment and look up a BIN.

- Score a payment
- Look up a BIN
- Validate an IBAN

### Reference data

Read reference data in Greip from any Tray.ai workflow. The Greip API covers calls such as look up a country and look up a domain.

- Look up a country
- Look up a domain

## Challenges Tray.ai solves

### Keeping Greip credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Greip credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Greip API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Greip API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Greip?

Yes. Tray.ai connects to Greip through the HTTP Connector, which calls the Greip API directly. Any call the Greip API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Greip?

The Greip API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Greip connector?

Greip runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Greip connector from the Greip API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/