Abstractapi Abstract APIs

Name: Abstract APIs
Brand: Abstract APIs
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentContact EnrichmentapiKey3 Endpoints

Install Jentic One Beta

Connect the Abstract APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Abstract APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

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

Capabilities

What an agent can do with Abstract APIs.

Validate an email address with deliverability, MX, and disposable-domain checks via /v1

Verify a phone number's format, country, and carrier via /v1/phone

Retrieve live currency exchange rates for a base currency via /v1/exchange

GET STARTED

Start building with Abstract APIs

Explore with Jentic

View OpenAPI Document

For Agents

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.

Use for: I want to validate a user's email address before sending a welcome message, Check whether an email is from a disposable provider, Verify that a phone number is reachable and in E.164 format, Get the current USD to EUR exchange rate

Not supported: Does not handle email sending, SMS delivery, or live currency conversion of funds - use for validating contact data and reading FX rates only.

Jentic publishes the only available OpenAPI specification for Abstract APIs, keeping it validated and agent-ready. Abstract APIs is a collection of focused REST APIs from Abstract that covers email validation, phone validation, and currency exchange rates, each addressed by its own subdomain (emailvalidation.abstractapi.com, phonevalidation.abstractapi.com, exchange-rates.abstractapi.com). Every endpoint is keyed by a single api_key query parameter, returns JSON, and is intended for lightweight enrichment and verification work inside larger workflows. The bundle is useful when an agent needs quick checks on user-supplied contact data or live FX figures without integrating a heavier specialist provider.

Use Cases

Patterns agents use Abstract APIs for, with concrete tasks.

★ Signup form email validation

Before allowing a new account, call the email validation endpoint to confirm the address has valid syntax, an MX record, and is not a disposable mailbox. This blocks the most common low-quality signups and keeps marketing lists clean. Integration is a single GET to /v1 with the email and api_key query parameters.

Call GET /v1 with email=user@example.com and return whether deliverability is DELIVERABLE and is_disposable_email is false

Phone number verification for onboarding

Use the phone validation endpoint to confirm a user-supplied phone number is correctly formatted, identify its country and carrier, and decide whether to send an SMS verification code. Useful for fraud reduction in fintech and marketplace onboarding.

Call GET /v1/phone with phone=+14155552671 and return country.code, carrier, and is_valid

Multi-currency invoicing

Pull current exchange rates from the exchange-rates endpoint to display invoice totals in the customer's local currency or to reconcile cross-border revenue. Daily refresh is sufficient for most accounting workflows.

Call GET /v1/exchange with base=USD and target=EUR,GBP,JPY and return the exchange_rates object

AI agent contact enrichment

An agent collecting leads or processing form submissions calls the email and phone validation endpoints inline to score and clean each record before passing it to a CRM. Through Jentic the agent loads the schemas on demand and never sees the raw API key.

For each lead in the input batch, call /v1 to validate the email and /v1/phone to validate the phone, then mark the lead as clean only if both return is_valid_format=true

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for abstract apis, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v1

Validate an email address

GET

/v1/phone

Validate a phone number

GET

/v1/exchange

Get live currency exchange rates

GET

/v1

Validate an email address

GET

/v1/phone

Validate a phone number

GET

/v1/exchange

Get live currency exchange rates

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Abstract api_key is stored once, encrypted, by your own Jentic One instance and injected as the api_key query parameter at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'validate an email address' or 'get exchange rates', 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.

Time to first call

FAQs

Specific to using Abstract APIs through Jentic.

Why is there no official OpenAPI spec for Abstract APIs?

Abstract API does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Abstract APIs via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Abstract APIs use?

Each endpoint takes the API key as a required api_key query parameter. There is no header-based auth and no OAuth. Through Jentic the api_key is held in the vault and injected at execution time, so the agent never sees the raw secret.

Can I validate an email address with the Abstract APIs?

Yes. Call GET /v1 on emailvalidation.abstractapi.com with email and api_key query parameters. The response includes deliverability, is_valid_format, is_disposable_email, is_role_email, and MX record presence.

What are the rate limits for the Abstract APIs?

Limits depend on the plan attached to your Abstract account, and each subdomain (email, phone, exchange) has its own quota. The free tier is typically 100 requests per month per API; paid tiers raise this and add concurrency. The spec does not encode these limits, so check your Abstract dashboard for the live numbers.

How do I look up exchange rates with the Abstract APIs through Jentic?

Search Jentic for 'get currency exchange rates', load the operation that maps to GET /v1/exchange on exchange-rates.abstractapi.com, then execute with base and target parameters. Install with pip install jentic and use the async pattern: await client.search, load, then execute.

Is the Abstract API free?

Abstract offers a free tier on each API (commonly 100 requests/month) and paid tiers for higher volume. Free-tier responses are identical in shape to paid-tier responses, so you can prototype on free and scale without code changes.

Can I limit what my agent is allowed to do with the Abstract APIs?

Yes. Because you run Jentic One yourself, your own rules decide which Abstract operations the agent can call, so you can allow only email validation (GET /v1) while withholding phone validation (GET /v1/phone) and exchange rates (GET /v1/exchange). These endpoints take the api_key and their inputs as query parameters with no resource id in the URL, so scoping is done at the operation level rather than by record. Grant just the operations a given agent needs, and anything you do not add, such as phone lookups, stays out of its reach.