Install Jentic One Beta

Connect the Leadboxer API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Leadboxer 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%2Fleadboxer.com%2Fleadboxer" | 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%2Fleadboxer.com%2Fleadboxer" | 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 Leadboxer API.

Retrieve the leads tracked on a site by dataset id, filtered by search text and criteria such as lead score and time window, as JSON or CSV

Drill into one lead's detail, then list its sessions and the page events within a session

Look up the organization, ISP, usage type, and geolocation behind an IP address with ipOrganization and ipCity fields

Look up company details for a domain or an email address, with optional firstName, lastName, and companyName hints

GET STARTED

Start building with Leadboxer API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Leadboxer API for, with concrete tasks.

★ Agent-driven lead follow-up through Jentic

An AI sales assistant can pull the recent high-scoring leads for a site, read each lead's sessions to see which pages they viewed, and then tag or assign the lead to a rep. Through Jentic the agent finds each LeadBoxer operation by intent, the x-api-key credential is injected at execution time, and a rule can allow reads and tagging while leaving user, dataset, and domain administration out of reach.

Call GET /v1/leads with site set to the dataset id, timeField 'eventEsTimestamp', and criteriaTimeFilter 'eventEsTimestamp|lessthan|6' for the last 7 days, then call PUT /v1/management/assign-leads with the top lead's leadId, the datasetId, and assignee set to the rep's numeric user id

Visitor-to-company identification

B2B teams want to know which organizations are behind anonymous website traffic. The LeadBoxer IP lookup returns fields such as ipOrganization, ipDomain, ipIsp, ipUsageType, ipCountryName, and ipCity for an address, and the domain and email lookups resolve company details for a known domain or contact, each charging credits against a dataset.

Call GET /v1/ip-lookup with ip '8.8.8.8' and report the returned ipOrganization, ipDomain, and ipCountryName

Lead segments and alerts

Sales teams often want an email when a target account returns, or a saved view of leads that meet a score threshold. LeadBoxer segments combine text, number, time, field, exit link, and lead score filters, and each segment can carry a notification type, recipient list, and schedule, so the right people hear about the right visitors.

Call POST /v1/segments with email 'owner@example.com' and a body containing name 'High intent', accountId, datasetId, type, and a leadscoreFilter for scores above 50

Session-level visitor activity

Understanding what a lead did on the site helps tailor outreach. LeadBoxer returns a lead's detail, the list of its sessions with a required limit, and the events inside a session, so an agent can summarise pages viewed and exit links before a rep makes contact.

Call GET /v1/leads/sessions with leadId, limit 10, and site, then call GET /v1/leads/events with the newest sessionId, limit 50, and site to list the pages viewed

Key Endpoints

42 endpoints — the leadboxer api retrieves the leads, sessions, and events that leadboxer tracks on your websites, where each tracked site is a dataset identified by a datasetid.

METHOD

PATH

DESCRIPTION

GET

/v1/leads

Retrieve leads for a site

GET

/v1/leads/{leadId}

Retrieve lead details

GET

/v1/leads/sessions

Retrieve a lead's sessions

GET

/v1/ip-lookup

Look up an IP address

GET

/v1/domain-lookup

Look up a domain

POST

/v1/segments

Create a segment

PUT

/v1/management/assign-leads

Assign leads

GET

/v1/leads

Retrieve leads for a site

GET

/v1/leads/{leadId}

Retrieve lead details

GET

/v1/leads/sessions

Retrieve a lead's sessions

GET

/v1/ip-lookup

Look up an IP address

GET

/v1/domain-lookup

Look up a domain

POST

/v1/segments

Create a segment

PUT

/v1/management/assign-leads

Assign leads

Why Jentic?

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

Setup

Wiring LeadBoxer by hand means carrying the x-api-key header, passing the right email and site parameters on each call, and building the criteria filters lead queries require. Through Jentic you install once, import LeadBoxer from the API Directory, store the key once, and your agent calls it.

Permission scoping

LeadBoxer puts some ids in the URL path (/v1/leads/{leadId}, /v1/segments/{segmentId}, /v1/datasets/{datasetId}/name), so a rule can pin those operations to one lead, segment, or dataset. Lead listing and lookups take the site id in the query string, so for those, rules bound which operations your agent may call. You choose the operations it may call, so destructive ones like removing a dataset or deleting a user are not included unless you add them.

Credential isolation

Your LeadBoxer 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 'retrieve website leads' or 'look up the company behind an IP', and Jentic returns the matching LeadBoxer operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Leadboxer API through Jentic.

Is there a LeadBoxer MCP server?

You don't need an MCP server to give your agent the LeadBoxer API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it. Operations are discovered on demand, so your agent's context carries no tool definitions it will not use.

What authentication does the LeadBoxer API use?

Per its OpenAPI spec, the LeadBoxer API authenticates with an API key in the x-api-key header. LeadBoxer says the API is for customers with a valid API license and key. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.

Can I find out which company is behind a website visitor's IP with the LeadBoxer API?

Yes. GET /v1/ip-lookup takes an ip and returns organization fields such as ipDomain and ipOrganization, geolocation fields such as ipCountryName and ipCity, and ISP details including ipUsageType. Pass datasetId to choose which dataset the lookup's credit is charged to.

What are the rate limits for the LeadBoxer API?

The OpenAPI spec does not specify rate limits. Lookups consume credits, which you can check with the credit usage summary operation; see https://docs.leadboxer.com/category/112-all for current limits.

How do I pull recent leads from LeadBoxer through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import the LeadBoxer API from the directory, and store your API key. Your agent then searches for 'retrieve website leads' and Jentic returns GET /v1/leads, which requires site, criteriaTimeFilter, and timeField. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Does the LeadBoxer API work on live data?

Yes. LeadBoxer warns that calls run against your production data, and recommends creating a separate LeadBoxer account if you want sandbox data for testing.

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

Yes. For a sales assistant, write a rule that allows GET /v1/leads, GET /v1/leads/sessions, and PUT /v1/management/lead-tags: the agent can read leads and their sessions and tag them, but cannot delete users, remove datasets, or change tracking domains, and every call it makes is logged.

Leadboxer API

AI ReadinessAI-Aware (B-)62/100

See full scorecard

Official vendor OpenAPI document · agent-readyAnalyticsWeb AnalyticsapiKey (x-api-key header)42 EndpointsREST

For Agents

Query tracked website leads, sessions, and events by dataset, look up company details from an IP, domain, or email, and manage segments, lead tags, and lead assignments in LeadBoxer.

Use for: I need to list the companies that visited our pricing page this week, Get the sessions and page events for this lead, Find out which organization owns IP address 8.8.8.8, Look up the company behind the domain acme.com

Not supported: Does not handle email sending, ad campaigns, deal pipelines, or installing the tracking pixel. Use for reading tracked website leads, sessions, and events, and IP, domain, or email lookups only.

The LeadBoxer API retrieves the leads, sessions, and events that LeadBoxer tracks on your websites, where each tracked site is a dataset identified by a datasetId. Lead queries take the site id with search text, criteria filters, and a time field, and return results as JSON or as a CSV export, while lead details, session lists, and per-session event lists drill into one visitor's activity. Alongside tracking data it looks up organization and geolocation details for an IP address, a domain, or an email address, and administers segments, lead tags and assignments, hidden leads, custom tracking domains, users, and credit usage.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

96%

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

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: A-Signals: 4

13%

Example Density

How richly the API is illustrated with examples.

98%

Example Validity

Percentage of examples that conform to their schemas.

74%

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

51%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

95%

OperationId Quality

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

25%

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: C-Signals: 1

50%

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: A-Signals: 1

76%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Leadboxer API to your agent

Capabilities

Start building with Leadboxer API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Leadboxer API

Jentic AI Readiness Score

Leadboxer 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