Install Jentic One Beta

Connect the IntentWake API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the IntentWake 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fintentwake.com%2Fintentwake" | 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%2Fintentwake.com%2Fintentwake" | 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 IntentWake API.

Look up a batch of email identifiers across the activity, emaillogin, and intent services, with an Idempotency-Key header

Narrow intent matches to chosen category_ids, vertical_ids, or sub_category_ids from the intent taxonomy

Create a customer list, upload its initial entries, append new entries, and queue removals

Turn monitoring on or off for a list and set which services and intent categories it uses

GET STARTED

Start building with IntentWake API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use IntentWake API for, with concrete tasks.

★ Intent lookups from your agent through Jentic

An AI agent connected through Jentic checks a set of leads by sending their email identifiers to the batch lookup with the intent service enabled and a few category_ids picked from the intent taxonomy. It reuses an Idempotency-Key so a retried request is not billed twice, and reads usage afterwards to report the cost. The API key stays in your own Jentic One instance, not in the agent's context.

Call GET /api/v1/intent-taxonomy to pick category ids, then POST /api/v1/lookups/batch with identifiers ['ana@example.com', 'li@example.com'], services.intent.category_ids set to the chosen ids, and an Idempotency-Key header

Monitored lists with bounded spend

For a standing audience, create a list with its services and an idempotency_key, upload the initial entries, and enable monitoring. When result downloads appear, unlock one with max_cents as a hard ceiling on the debit, then fetch a short-lived URL for the artifact. Filtered downloads built from an unlocked result are free.

Call GET /api/v1/lists/{id}/downloads, then POST /api/v1/lists/{id}/downloads/{downloadId}/unlock with an idempotency_key and max_cents 5000, and fetch GET /api/v1/lists/{id}/downloads/{downloadId}/url

Keeping a list current

Lists change as people sign up or opt out. Start an append upload and complete it to queue intake of new entries, poll the append status, and queue entry removals for people who should no longer be matched. Both appends and removals are forward-only.

Call POST /api/v1/lists/{id}/entry-removals with entries ['old@example.com'] and an idempotency_key, then poll GET /api/v1/lists/{id}/entry-removals/{removalId} until it completes

Key Endpoints

26 endpoints — the intentwake api matches email identifiers against intentwake's activity, emaillogin, and intent services and returns the results, either in billed batch lookups or through managed customer lists.

METHOD

PATH

DESCRIPTION

POST

/api/v1/lookups/batch

Look up a batch of email identifiers

GET

/api/v1/intent-taxonomy

Get the intent taxonomy

POST

/api/v1/lists

Create a customer list

GET

/api/v1/lists/{id}

Get a list and its status

PATCH

/api/v1/lists/{id}/monitoring

Set monitoring for a list

POST

/api/v1/lists/{id}/downloads/{downloadId}/unlock

Unlock a match-result download

GET

/api/v1/wallet

Get the wallet balance

GET

/api/v1/usage

List lookup usage and charges

POST

/api/v1/lookups/batch

Look up a batch of email identifiers

GET

/api/v1/intent-taxonomy

Get the intent taxonomy

POST

/api/v1/lists

Create a customer list

GET

/api/v1/lists/{id}

Get a list and its status

PATCH

/api/v1/lists/{id}/monitoring

Set monitoring for a list

POST

/api/v1/lists/{id}/downloads/{downloadId}/unlock

Unlock a match-result download

GET

/api/v1/wallet

Get the wallet balance

GET

/api/v1/usage

List lookup usage and charges

Why Jentic?

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

Setup

Wiring IntentWake by hand means handling its bearer key, separate IP and key rate budgets with Retry-After, idempotency keys on billed calls, and multi-step upload and download flows. Through Jentic you install once, import IntentWake from the API Directory, store the key once, and your agent calls it.

Permission scoping

IntentWake puts the list id in the URL path (/api/v1/lists/{id}/...), so a rule can pin your agent to one list and the operations you pick. You choose the operations it may call, so billed or spending ones like batch lookups, download unlocks, and wallet funding requests are not included unless you add them.

Credential isolation

Your IntentWake API key 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 'look up intent signals for emails' or 'check list download status', and Jentic returns the matching IntentWake operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using IntentWake API through Jentic.

Is there an IntentWake MCP server?

You don't need an MCP server to give your agent IntentWake. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it. The agent finds the lookup, list, or wallet operation it needs on demand, which keeps unused tool definitions out of its context.

Can I limit what my agent is allowed to do with the IntentWake API?

Yes. For a reporting agent, write a rule that allows only GET /api/v1/lists/{id} and GET /api/v1/lists/{id}/downloads for one list id, plus GET /api/v1/usage. It can watch that list and report costs, but it cannot run billed lookups, unlock downloads, or request wallet funding, and every call it makes is logged.

What authentication does the IntentWake API use?

Per its OpenAPI spec, the IntentWake API uses HTTP bearer authentication on every operation: send your IntentWake API key in the `Authorization` header as `Bearer <key>`. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected when each call runs.

What are the rate limits for the IntentWake API?

Per the OpenAPI spec, fixed 60-second windows allow 60 requests per client IP per API service. Per API key, the budgets are 120 read requests, 60 non-billed mutation requests, and 30 requests to the billed batch lookup endpoint, and whichever IP or key budget runs out first applies. 429 responses include a Retry-After header.

How do I avoid being charged twice for an IntentWake lookup?

Send an Idempotency-Key header with POST /api/v1/lookups/batch, and an idempotency_key in the body of list creation, unlocks, removals, and funding requests. Reusing the same key on a retry lets IntentWake treat it as the same request.

How do I look up a batch of emails with the IntentWake API through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import IntentWake from the API Directory, and store your API key. Your agent searches for 'look up intent signals for email addresses', gets POST /api/v1/lookups/batch with its input schema, and calls it with identifiers and the services to match. To run it on your own infrastructure, install Jentic One from its GitHub repo.

IntentWake API

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentContact Enrichmentbearer26 EndpointsREST

For Agents

Run batch email lookups across IntentWake's activity, emaillogin, and intent services, manage monitored lists and their match-result downloads, and check wallet credit and usage.

Use for: Look up these 200 email addresses for intent signals, Get the list of intent categories I can filter on, Create a new monitored list from my CRM export, Append this week's new signups to the list

Not supported: Does not handle sending email, storing payment methods, or company firmographic enrichment. Use for email identifier lookups, monitored lists, and their match-result downloads only.

The IntentWake API matches email identifiers against IntentWake's activity, emaillogin, and intent services and returns the results, either in billed batch lookups or through managed customer lists. Lists accept an initial upload and forward-only appends or removals, can be monitored over time, and produce match-result downloads that are unlocked by debiting wallet credit with a max_cents ceiling. An intent taxonomy endpoint lists the categories you can select for the intent service, and wallet and usage endpoints report the credit balance, funding status, and per-service charges.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4

19%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

52%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

60%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the IntentWake API to your agent

Capabilities

Start building with IntentWake API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

IntentWake API

Jentic AI Readiness Score

IntentWake API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness