What is out of scope for Abstract's APIs?

They validate and enrich data but do not act on it. There is no email or SMS delivery, no conversion of actual funds, and no physical-address geocoding, routing, or places search. Use them to validate contact data, read FX rates, and resolve IPs to location and risk flags only.

Are the Abstract APIs free to use?

Each service offers a free tier, commonly around 100 requests per month for the contact-data APIs and 20,000 lookups per month at one request per second for IP geolocation, with paid tiers raising quota and concurrency. Free-tier and paid-tier responses share the same shape, so you can prototype on free and scale without code changes.

Abstract APIs for AI Agents

Data EnrichmentContact EnrichmentGeocodingJentic-Generated SpecsAPI keyAgent Ready

www.abstractapi.com·Developer portal → www.abstractapi.com

Abstract API Catalog

3 APIs across 2 product groups. All share one credential.

Maps Geolocation2

Abstract IP Geolocation APIResolve an IP address to country, region, city, timezone, currency, security flags, and ISP via a single Abstract endpoint authenticated by an api_key query parameter.~1 endpoint IP geolocation APIResolve any IPv4 or IPv6 address to country, region, city, timezone, currency, and language using a single Abstract endpoint authenticated by an api_key query parameter.~1 endpoint

Data Enrichment1

Abstract APIsValidate emails and phone numbers and fetch live currency exchange rates through a small set of Abstract REST endpoints, all keyed by a single api_key query parameter.~3 endpoints

Which Abstract API should I use?

I want to...	Use	Why
Validate emails or phone numbers, or read live FX rates	Abstract APIs	This bundle covers email validation, phone validation, and currency exchange rates; it is the only entry here that handles contact-data checks and FX.
Resolve an IP to location plus VPN, proxy, and Tor risk flags	Abstract IP Geolocation API	This IP geolocation entry returns a security object with is_vpn, is_proxy, is_tor, and is_hosting alongside country, city, timezone, currency, and ISP, so use it when fraud signals matter.
Resolve an IP to country, city, timezone, currency, and language	IP geolocation API	This IP geolocation entry returns location, timezone, currency, and language for IPv4 and IPv6 without the security flags, so use it for personalization and localization lookups.

Install Jentic One Beta

Connect the Abstract APIs to your agent

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Abstract by hand means tracking a separate subdomain for each service and appending the api_key query parameter on every call. Through Jentic you install Jentic One once, add the Abstract APIs you need from the Jentic directory, store each api_key once, and your agent calls them.

Permission scoping

Every Abstract endpoint takes the api_key and its inputs as query parameters with no resource id in the URL, so your own rules scope the agent at the operation level. You can allow only email validation while withholding phone validation, FX rates, or IP lookups, and anything you do not add stays out of reach.

Credential isolation

Each Abstract api_key is stored encrypted by your own Jentic One instance and injected as the api_key query parameter at execution time. Keys never enter the agent's prompt, logs, or context, and separate keys per service can be scoped independently.

FAQs

Specific to using Abstract APIs through Jentic.

What can I do with Abstract's APIs through Jentic?

You can validate email addresses and phone numbers, fetch live currency exchange rates, and resolve IPv4 or IPv6 addresses to country, region, city, timezone, currency, language, ISP, and security flags. These are lightweight enrichment and verification calls meant to run inline inside a larger workflow rather than as a standalone platform.

Do all the Abstract APIs share one API key?

They share the same api_key query-parameter model, but each Abstract product runs on its own subdomain and has its own quota and billing. Under one Abstract account you may hold a separate api_key per service, so check your dashboard for the key and limits tied to each API.

Which Abstract entry should I use for IP geolocation?

Both IP geolocation entries resolve an IP to country, city, timezone, currency, and language. Use the entry that also returns the security object with VPN, proxy, and Tor flags when you need fraud signals, and use the simpler location-and-locale entry when you only need personalization or localization data.

Are these APIs a good fit for AI agents?

Yes. Each service is a small set of GET endpoints with a single api_key parameter and a compact, stable JSON response, which is easy for an agent to call and parse. Through Jentic the agent loads the operation schema on demand and calls the right subdomain without reading the reference docs.

BOOK A DEMO

Start Connecting APIs to Your AI Agents

Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.

Book a Demo

For Agents

APIs3 in catalogue

Endpoints5 indexed

AuthAPI key — 1 credential for all 3 APIs

ProvenanceJentic-generated specs

An agent can validate user-supplied emails and phone numbers, fetch live currency exchange rates, and resolve any IPv4 or IPv6 address to country, region, city, timezone, currency, language, ISP, and security flags. Every call uses the same api_key query parameter and returns a small, stable JSON payload suited to inline enrichment.

Abstract packages contact and location data checks as single-endpoint REST APIs rather than a monolithic platform, so an agent can call just the check it needs. Each service uses the same api_key query-parameter auth and a small JSON response, which makes it a light drop-in for onboarding, fraud, and personalization flows where a heavier database install is unnecessary.

Use for: Inline validation of user-supplied emails and phone numbers, reading daily currency exchange rates, and resolving IPv4 or IPv6 addresses to location, timezone, currency, language, ISP, and risk flags

Not supported: email or SMS delivery, currency conversion of funds, physical address geocoding, routing or directions, places search, real-time streaming

Credentials: One Abstract api_key model covers every service, but each product (email validation, phone validation, exchange rates, IP geolocation) is billed and quota-limited separately on its own subdomain, so you may hold a distinct api_key per service under a single Abstract account.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fabstractapi.com" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fabstractapi.com" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 AI Agents Can Do with Abstract

Each workflow spans multiple Abstract APIs. Jentic routes each operation to the right API automatically.

Clean and locate a new signup

When a user signs up, validate the email address and phone number, then resolve the signup IP to a country to compare against the user-supplied billing country. Combining the contact check with the IP location gives a single clean-and-locate pass before an account is created.

Example prompt:

Validate the email and phone with the abstract-apis endpoints, resolve the signup IP with ip-geolocation, and flag the signup when the email is disposable, the phone is invalid, or the IP country does not match the billing country

APIs used

Abstract APIs + Abstract IP Geolocation API

Localize pricing with correct currency

Resolve a visitor IP to its country and currency, then read the matching live exchange rate to display prices in the visitor's local currency. Pairing IP geolocation with FX rates converts a raw visitor request into a localized price without a heavier localization stack.

Example prompt:

Call the geolocation endpoint with the visitor IP to get currency.currency_code, then call the abstract-apis exchange endpoint with base=USD and that target currency and return the converted price

APIs used

IP geolocation API + Abstract APIs

Enrich CRM records with contact and location context

For each inbound lead, validate the email and phone, then resolve the lead's IP to country, city, and ISP so the CRM record carries both contact quality and geographic context. The two enrichment passes produce one scored, located record for downstream routing.

Example prompt:

For each lead, validate the email and phone with abstract-apis and resolve the IP with geolocation, then write is_valid_format, country, city, and isp onto the CRM record

APIs used

Abstract APIs + IP geolocation API

Abstract APIs for AI Agents

Abstract API Catalog

Maps Geolocation2

Data Enrichment1

Which Abstract API should I use?

Connect the Abstract APIs to your agent

Why Jentic?

FAQs

Start Connecting APIs to Your AI Agents

What AI Agents Can Do with Abstract

If you need a different Data Enrichment vendor