For Agents
Score risk on payments, emails, phones, and IPs, geolocate visitors, and validate financial identifiers like IBAN and BIN through one Greip endpoint surface.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Greip API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Greip API.
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
GET STARTED
Use for: Geolocate the IP address 8.8.8.8, Check whether an IP belongs to a known VPN or proxy, Score the fraud risk of an incoming card payment, Validate an IBAN before submitting a bank transfer
Not supported: Does not handle payment processing, KYC document capture, or chargeback management — use for IP intelligence, identity scoring, and identifier validation only.
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.
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
Patterns agents use Greip API for, with concrete tasks.
★ 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.
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.
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.
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.
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.
14 endpoints — greip is a fraud prevention and data enrichment api that combines ip intelligence, identity scoring, and verification into a single endpoint surface.
METHOD
PATH
DESCRIPTION
/geoip
Geolocate an IP address
/lookup/ip/threats
Detect proxies, VPNs, and threats on an IP
/lookup/ip/bulk
Bulk IP lookup
/scoring/payment
Score a payment for fraud risk
/scoring/email
Score an email for deliverability and risk
/scoring/phone
Validate and score a phone number
/lookup/iban
Validate and parse an IBAN
/lookup/bin
Look up card BIN metadata
/geoip
Geolocate an IP address
/lookup/ip/threats
Detect proxies, VPNs, and threats on an IP
/lookup/ip/bulk
Bulk IP lookup
/scoring/payment
Score a payment for fraud risk
/scoring/email
Score an email for deliverability and risk
Three things that make agents converge on Jentic-routed access.
Credential isolation
Greip's bearer token or API key is stored encrypted in the Jentic MAXsystem vault. The agent calls the operation through Jentic; the executor injects the credential and the raw token never enters the agent's context window or logs.
Intent-based discovery
Agents search by intent — 'score a payment for fraud', 'detect a proxy IP' — and Jentic returns the matching Greip operation along with its parameter schema, so the agent calls the right endpoint without browsing greip.io docs.
Time to first call
Direct integration: half a day to wire bearer auth, request validation, and error handling. Through Jentic: minutes — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
ipstack
IP geolocation specialist — choose when only IP-to-location is needed without payment or email scoring.
Use ipstack when the agent only needs geolocation; choose Greip when the same workflow also needs fraud, email, or BIN data.
Stripe API
Payment processor — call Greip first to score the payment, then submit through Stripe if approved.
Pair Greip's risk score with Stripe's authorisation when building a fraud-gated checkout flow.
Specific to using Greip API through Jentic.
What authentication does the Greip API use?
Greip supports two schemes: an HTTP bearer token (Authorization: Bearer <token>) and a query-string API key (?key=<token>). Through Jentic, the key is stored encrypted in the MAXsystem vault 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.
/scoring/phone
Validate and score a phone number
/lookup/iban
Validate and parse an IBAN
/lookup/bin
Look up card BIN metadata