canonical: https://jentic.com/apis/abstractapi.com

# Abstract APIs

Abstract provides a set of focused REST APIs for lightweight data validation and enrichment. The endpoints in the Jentic directory cover email validation, phone validation, live currency exchange rates, and IP geolocation, each addressed by its own subdomain and keyed by a single api_key query parameter that returns JSON. They are built for inline checks inside larger workflows, such as validating a signup, resolving a visitor IP to a country and currency, or pulling a daily FX rate, without integrating a heavier specialist provider.

## For AI agents

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.

## Scope

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

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| Abstract APIs | data-enrichment | 3 | Validate 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. |
| Abstract IP Geolocation API | maps-geolocation | 1 | Resolve 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. |
| IP geolocation API | maps-geolocation | 1 | Resolve 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. |

## Which API to use

| Need | API | 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 | ip-geolocation | 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 | geolocation | 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. |

## Cross-API use cases

### 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

### 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

### 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

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** Agents search the Jentic directory by intent, such as 'validate an email address', 'get exchange rates', or 'find country from ip', and Jentic returns the matching Abstract operation with its input schema so the agent calls the right subdomain and endpoint without browsing the reference docs.

## Related vendors

- **MaxMind** — GeoIP2 web service and downloadable databases; an alternative when you need offline IP lookups or industry-standard accuracy for fraud scoring.
- **ipstack** — Single-endpoint IP geolocation with bundled security and currency modules; a direct alternative to Abstract's IP lookup.
- **ZeroBounce** — Email validation specialist with richer per-address scoring than Abstract's email endpoint when deliverability is the sole concern.
- **Hunter** — Email finder and verifier for B2B lead generation; complements Abstract's inline format and deliverability checks.

## FAQ

### 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.

### 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.