canonical: https://jentic.com/apis/swaggerhub.direct-wines/account-lookup-api

# Direct Wines Account Lookup API

This API provides services to query and validate user accounts. The API exposes 1 endpoints.

## For AI agents

Programmatically check for the existence of an existing user account by means of an email address. Covers 1 operations.

## Scope

Does not handle payments, communications, or crm - use for data enrichment only.

## Capabilities

- Check for the existence of an existing user account by means of an email address
- Manage data enrichment data programmatically
- Integrate Account Lookup API into automated workflows
- Query and filter Account Lookup API records by parameters
- Monitor Account Lookup API operational status and events

## Use cases

### Data Enrichment Operations

Use the Account Lookup API to perform data enrichment operations programmatically. The API provides 1 endpoints covering core functionality including check for the existence of an existing user account by means of an email address.

Example prompt: Call POST /api/account/email to check for the existence of an existing user account by means of an email address

### Data Retrieval and Monitoring

Query Account Lookup API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Account Lookup API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Account Lookup API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'check for the existence of an existing user account by means of an email address', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /api/account/email | Check for the existence of an existing user account by means of an email address |

## Key resources

- **developers** — Operations available to regular developers.

## Why Jentic

- **Setup:** Wiring the Account Lookup API by hand means reading its OpenAPI definition, targeting the right server, and hand-coding the lookup call and its retries yourself. Through Jentic you install once, import the Account Lookup API from the API Directory, store any credential it needs once, and your agent calls it.
- **Permission scoping:** This API exposes a single account-email lookup that takes its target in the request body, so limit the agent to the operations it needs, such as checking whether an account exists for an email. You choose the operations it may call, so nothing beyond that lookup runs unless you add it.
- **Credential handling:** Any credential this API requires is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'check whether an account exists for an email address', and Jentic returns the matching Account Lookup API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Clearbit** — Alternative data enrichment API
- **Fullcontact** — Alternative data enrichment API
- **Hunter** — Complementary data enrichment API

## FAQ

### What authentication does the Account Lookup API use?

The Account Lookup API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I check for the existence of an existing user account by means of an email address with the Account Lookup API?

Yes. Use the POST /api/account/email endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Account Lookup API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I check for the existence of an existing user account by means of an email address through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'check for the existence of an existing user account by means of an email address'. Jentic returns the matching Account Lookup API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Account Lookup API have?

The Account Lookup API exposes 1 endpoints covering developers operations.

### Can I limit what my agent is allowed to do with the Account Lookup API?

Yes. Jentic One runs self-hosted, so your own rules decide which operations and credentials the agent may use. The Account Lookup API exposes only a single account-email lookup (POST /api/account/email) that takes its target email in the request body, and you choose whether the agent may call it. Nothing beyond that lookup runs unless you explicitly grant it.