canonical: https://jentic.com/apis/greip.io/greip # Greip API Greip is a fraud prevention and data enrichment API that combines IP intelligence, identity scoring, and verification into a single endpoint surface. Agents can geolocate IPs, detect threats and proxies, look up ASNs and BIN numbers, validate IBANs, and score emails, phones, payments, and profanity in user content. The API exposes both a token-based bearer scheme and a query-string API key for lightweight client use. ## For AI agents Score risk on payments, emails, phones, and IPs, geolocate visitors, and validate financial identifiers like IBAN and BIN through one Greip endpoint surface. ## Scope Does not handle payment processing, KYC document capture, or chargeback management - use for IP intelligence, identity scoring, and identifier validation only. ## Capabilities - Geolocate an IP address to country, region, and city via /geoip - Detect proxy, VPN, Tor, and threat signals on an IP through `/lookup/ip/threats` - Run bulk IP lookups in a single request with `/lookup/ip/bulk` - Look up ASN ownership and BIN card metadata for fraud checks - Score the fraud risk of a payment with POST `/scoring/payment` - Validate an IBAN and score the deliverability of an email or phone number - Detect profanity in user-submitted text via `/scoring/profanity` ## Use cases ### Pre-Authorisation Fraud Scoring Score a payment before authorising it. Send the cardholder's IP, BIN, email, and phone to `/scoring/payment` and use the returned risk score to allow, challenge, or block the transaction. Greip combines IP threat data with identity scoring in a single call, reducing the integrations needed compared to stitching together separate IP, BIN, and email-validation vendors. Example prompt: Call POST `/scoring/payment` with the customer's IP, email, phone, and card BIN, then return 'approve', 'challenge', or 'decline' based on the risk score threshold. ### Visitor Geolocation and Threat Detection Geolocate a website visitor and detect whether they are using a proxy, VPN, or Tor exit. Use /geoip for country and city, then `/lookup/ip/threats` for the threat profile. Useful for content gating, geo-targeted experiences, and abuse prevention without shipping a heavy fraud-detection bundle to the browser. Example prompt: Call GET /geoip and GET `/lookup/ip/threats` for a visitor IP, then return the city, country, and a flag indicating whether the IP is a known proxy or threat. ### Email and Phone Quality Scoring Score the deliverability and risk of an email or phone before persisting it to a CRM. Greip's `/scoring/email` and `/scoring/phone` endpoints classify addresses as disposable, role-based, or risky and validate phone numbers without sending an SMS. This catches signup fraud and bad data at the form layer. Example prompt: Call GET `/scoring/email` and GET `/scoring/phone` for a new signup, and reject the registration if either score crosses the configured fraud threshold. ### AI Agent Risk Decisioning An AI ops assistant in a fintech checks Greip whenever a high-value action arrives - login from a new IP, payout request, account update. The agent uses Jentic to call the right Greip operation without hard-coding URLs and writes the resulting score back to the case file. Example prompt: Search Jentic for 'score a payment for fraud', load the POST `/scoring/payment` schema, execute with the transaction details, and attach the score to the open support case. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/geoip` | Geolocate an IP address | | GET | `/lookup/ip/threats` | Detect proxies, VPNs, and threats on an IP | | GET | `/lookup/ip/bulk` | Bulk IP lookup | | POST | `/scoring/payment` | Score a payment for fraud risk | | GET | `/scoring/email` | Score an email for deliverability and risk | | GET | `/scoring/phone` | Validate and score a phone number | | GET | `/lookup/iban` | Validate and parse an IBAN | | GET | `/lookup/bin` | Look up card BIN metadata | ## Key resources - **geoip** — Geolocate IP addresses with location and ASN data - **lookup** — Look up IP threats, ASN, BIN, IBAN, and country reference data - **scoring** — Score payments, emails, phones, and profanity for risk and quality - **account** — Manage Greip account user records ## Why Jentic - **Setup:** Wiring the Greip API by hand means choosing between its bearer token and query-string API key, picking the production or dev host, and mapping the geoip, lookup, and scoring endpoints yourself. Through Jentic you install once, import the Greip API from the API Directory, store the credential once, and your agent calls it. - **Permission scoping:** Greip carries its credential and its lookup targets in the request rather than in a resource path, so limit the agent to the operations it needs, such as looking up an IP or scoring an email. Every operation you allow is one you have chosen, and you leave out ones like deleting account users if the agent should not touch them. - **Credential handling:** Your Greip credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'geolocate an IP address' or 'score an email for fraud risk', and Jentic returns the matching Greip operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **ipstack** — IP geolocation specialist - choose when only IP-to-location is needed without payment or email scoring. - **Abstract API** — Bundles IP, email, phone, and IBAN validation across separate endpoints. - **MaxMind GeoIP2** — Long-established IP intelligence provider with deep ASN and threat data. - **Stripe API** — Payment processor - call Greip first to score the payment, then submit through Stripe if approved. ## FAQ ### What authentication does the Greip API use? Greip supports two schemes: an HTTP bearer token (Authorization: Bearer ) and a query-string API key (?key=). Through Jentic, the key is stored encrypted in your Jentic One instance and never enters the agent's context - the executor injects it at call time. ### Can I score a payment for fraud with the Greip API? Yes. POST `/scoring/payment` accepts the transaction details and returns a fraud risk score. Combine it with `/lookup/bin` and `/lookup/ip/threats` for a richer signal - Greip's scoring endpoint can fold those signals in directly when supplied. ### What are the rate limits for the Greip API? The OpenAPI spec does not declare explicit rate limits - Greip enforces them per plan on greip.io. Production agents should handle 429 responses with backoff. Through Jentic, retry policies can be configured at the workflow level. ### How do I geolocate an IP through Jentic? Search Jentic with 'geolocate an ip address', load the GET /geoip schema, and execute with the IP as the query parameter. Jentic returns the structured response so the agent can act on the country and city directly. ### Is the Greip API free? Greip offers a free tier and paid plans on greip.io with higher quotas and additional scoring features. The OpenAPI spec itself does not include pricing - check the Greip dashboard for current limits. ### Can Greip detect VPN and Tor exit nodes? Yes - GET `/lookup/ip/threats` returns flags for proxies, VPNs, and Tor exits along with the IP's threat reputation. Use it as a gate before granting access to high-trust actions. ### Can I limit what my agent is allowed to do with the Greip API? Yes. Because you self-host Jentic One, your own rules decide which Greip operations and credentials the agent may use, and Greip passes its credential and lookup targets in the request rather than in a resource path, so you scope by operation. You can allow just the calls the agent needs, such as GET /geoip, GET `/lookup/ip/threats`, GET `/scoring/email`, or POST `/scoring/payment`, while leaving out ones like deleting Greip account users. Every operation the agent can reach is one you have explicitly chosen.