Direct Wines Account Lookup API

Name: Account Lookup API
Brand: Account Lookup API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentCompany Datanone1 Endpoints

Install Jentic One Beta

Connect the Account Lookup API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Account Lookup API, 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 Account Lookup API.

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

GET STARTED

Start building with Account Lookup API

Explore with Jentic

View OpenAPI Document

For Agents

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

Use for: I need to check for the existence of an existing user account by means of an email address, Find available data enrichment operations, Get the current status of Account Lookup API resources, List all records from Account Lookup API

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

Use Cases

Patterns agents use Account Lookup API for, with concrete tasks.

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

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.

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.

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

1 endpoints — this api provides services to query and validate user accounts.

METHOD

PATH

DESCRIPTION

POST

/api/account/email

Check for the existence of an existing user account by means of an email address

POST

/api/account/email

Check for the existence of an existing user account by means of an email address

Why Jentic?

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

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Account Lookup API through Jentic.

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.

Direct Wines Account Lookup API

Connect the Account Lookup API to your agent

Capabilities

Start building with Account Lookup API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs