Risk and location

IP risk, geo-fencing, geocoding and watchlist screening.

Score an IP address for fraud with proxy, VPN and Tor flags, check that it resolves inside the country and state you expect, and turn a latitude and longitude into an address. Screen a person or a business against AML, CFT, sanctions, PEP, defaulter and enforcement watchlists.

APIs
4 you can call, 6 more on request
Consent
Bound to every read
Audit
Every call in a hash-chained log

APIs in Risk and location

Every API shares the same key, error format and audit log. Each one is switched on for your account separately.

  • IP quality check

    Fraud score, proxy, VPN and Tor flags, ISP and location for an IPv4 or IPv6 address.

    POST /v1/risk/ipReference
  • IP geo-fencing

    Whether an IP resolves inside the expected country (ISO code) and optional state, with its location.

    POST /v1/risk/geo-fenceReference
  • Reverse geocode

    Address, city, state and pincode for a latitude and longitude.

    POST /v1/geo/reverse-geocodeReference
  • Negative due diligence

    Screens an individual or entity against AML, CFT, non-compliance and lending watchlists: sanctions, PEP, defaulter and enforcement lists.

    POST /v1/risk/negative-due-diligenceReference

Available on request

We set these checks up for your account. Subscribe to the one you need and we will have it ready for you.

What teams use it for

Use cases for each Risk and location check. See how they combine with other products on the use cases page.

  • Fraud score, proxy, VPN and Tor flags, network and location for an IP address.

    • Flag sign-ups and logins from VPNs, proxies and Tor.
    • Add a fraud score to sign-up and payment decisions.
    • Spot bots and multiple accounts abusing offers and referrals.
  • Whether an IP address is inside the expected country and state.

    • Make sure customers sign up from India, or from the states you serve.
    • Block a service in regions where you cannot operate.
  • Address, city, state and pincode for a latitude and longitude.

    • Turn a device location into an address during onboarding or field visits.
    • Confirm a field agent or delivery partner is where they say they are.
    • Tag inspections, claims and visits with a readable address.
  • Screens a person or business against sanctions, PEP, defaulter and enforcement lists.

    • Screen customers as anti-money-laundering rules require.
    • Check directors, promoters and vendors before onboarding.
    • Re-screen existing customers on a regular schedule.
  • Combines several identity checks into one trust score.

    • Decide to approve, review or reject a customer from one score.
    • Auto-approve low-risk customers and cut manual review.
  • Searches court records for cases against a person.

    • Check borrowers, directors and senior hires for court cases.
    • Due diligence on business partners and vendors.
  • Checks a person against known fraud and defaulter lists.

    • Stop known fraudsters and defaulters at onboarding.
    • Screen customers before extending credit.
  • Checks that the network a customer connects from fits the rest of their identity.

    • Flag sign-ups whose network does not fit the stated location.
    • Spot account takeovers from unusual networks.
  • Checks a latitude and longitude against the address a customer gave.

    • Confirm from the device location that a customer is at the address they gave.
    • Verify doorstep onboarding and field visits.
  • The distance between two addresses.

    • Check that home and work addresses are a sensible distance apart.
    • Assign the nearest branch or field agent.

How you get Risk and location

From a new account to a live call in four steps.

  1. Create your account

    Sign up with your work email and create an app and its key. No API is active on a new account.

  2. Pay and subscribe

    Add money to your wallet, then subscribe to this API in Dashboard → API access. We switch it on for your account after your payment.

  3. Make your first call

    Once the API is activated, send the sample request to /v1/risk/negative-due-diligence with your key and read back the JSON.

  4. Go live

    Use a live key in production. Every call is checked against the APIs activated for you, drawn from your prepaid wallet, and recorded in a hash-chained audit trail.

Call negative due diligence

The main call for this product. Use your own key once this API is switched on for your account.

POST /v1/risk/negative-due-diligence
curl -X POST https://grappi.ai/v1/risk/negative-due-diligence \
-H "Authorization: Bearer $GRAPPI_API_KEY" \
-H "content-type: application/json" \
-d '{"name":"Acme Traders","type":"entity"}'

Developer ready

Docs, MCP, and a prompt that does the work

Every product ships with an integration guide, an MCP server for AI agents, and a ready-to-paste prompt, so your first Risk and location call takes minutes, not days.

Integration guide

The quickstart covers keys, auth, idempotency, the error envelope, and paise money units. The catalog documents every Risk and location endpoint with a live sample you can run from the playground.

MCP server for AI agents

grappi-mcp exposes the API as agent tools over the same gateway, so every tool call keeps auth, consent, metering, and audit. Drop this into your MCP client config.

mcp.json
{
  "mcpServers": {
    "grappi": {
      "command": "npx",
      "args": ["grappi-mcp"],
      "env": {
        "GRAPPI_API_BASE": "https://grappi.ai",
        "GRAPPI_API_KEY": "your-api-key"
      }
    }
  }
}

Prompt-ready integration

Paste this into your coding assistant or agent. It carries the real contract rules, so the generated client matches the gateway on the first try.

integrate-risk-location.prompt
Integrate the Grappi Risk and location API into my app.

Endpoints:
- POST /v1/risk/ip (IP quality check)
- POST /v1/risk/geo-fence (IP geo-fencing)
- POST /v1/geo/reverse-geocode (Reverse geocode)
- POST /v1/risk/negative-due-diligence (Negative due diligence)

Contract rules: send the key as a Bearer token in the Authorization header, treat all money as integer paise (100 paise is one rupee), send an Idempotency-Key on every POST, and branch on the error envelope error.code (handle 402 insufficient_balance, 403 api_not_activated, 403 consent_required, 422 validation_failed, 429 rate_limited, 503 api_unavailable).

Write a small typed client for these endpoints plus one worked call, with validation and error handling, in my project's language.

Questions

How do I start?

Create an account and add money to your wallet. Then subscribe to this API in your dashboard and we switch it on for your account.

What comes with every API?

Auth, idempotency, consent and metering hooks, a unified error envelope, and a hash-chained audit trail, identical across every API on the platform.

What do I need to go live?

Subscribe to the API in your dashboard and we switch it on for your account after your payment. The request and reply format is the same in test and in production.

Is this compliant for regulated use?

Reads are consent-bound and DPDP and RBI-AA aligned. Every call lands in a hash-chained audit trail, and every API is switched on for your account individually.