Install Jentic One Beta

Connect the Ads Lighthouse API to your agent

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

Create monitoring projects and start on-demand checks of their keywords across markets and search engines

Read observations of the paid ads found for monitored keywords and the advertisers behind them

Rank competing advertisers by ad occurrences and inspect one advertiser's history, heatmap, and ad copy

Track affiliate IDs seen behind ads that use your brand and set their review status

GET STARTED

Start building with Ads Lighthouse API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Ads Lighthouse API for, with concrete tasks.

★ Agent-Run Ad Monitoring via Jentic

An AI agent can watch paid search for a brand and act on what appears instead of someone refreshing a dashboard. Through Jentic the agent starts an on-demand check of a project's keywords, waits for it to finish, then reads the observations and the advertisers found, flagging anything that uses the brand term.

Start an on-demand check for a project's keywords, poll it until it completes, then read the observations and list advertisers appearing on the brand terms

Competitor Paid-Search Intelligence

Teams track who competes for their keywords and how often. Ads Lighthouse ranks advertisers by ad occurrences, exposes one advertiser's appearance history and hourly-weekday heatmap, and lists its distinct ad copy over time, so an agent builds a picture of competitive pressure on a keyword set.

Read the ranked competitors for a project, then open one advertiser to read its appearance history, heatmap, and recent ad copy

Brand and Affiliate Compliance

Brands police affiliates that bid on brand terms. Ads Lighthouse surfaces affiliate IDs seen behind ads that use the brand, lets a reviewer set each one's compliance status, evaluates saved ads against policy rules, and opens cases with evidence, so non-compliant activity is tracked to resolution.

List a project's affiliate findings, set a non-compliant affiliate ID's review status, and read the policy cases opened against it

Key Endpoints

87 endpoints — the ads lighthouse api monitors paid-search advertising for a brand and reports what it finds as account-scoped data.

METHOD

PATH

DESCRIPTION

GET

/projects

Projects in the account

POST

/projects

Create a project and start its first checks

GET

/projects/{project_id}/observations

Saved checks with the paid ads they found

POST

/projects/{project_id}/checks

Start an on-demand check of a project's keywords

GET

/projects/{project_id}/competitors

Other advertisers ranked by ad occurrences

GET

/alert-rules

Alert rules configured in the account

GET

/account

Plan, monthly allowances, usage and rate limit

GET

/projects

Projects in the account

POST

/projects

Create a project and start its first checks

GET

/projects/{project_id}/observations

Saved checks with the paid ads they found

POST

/projects/{project_id}/checks

Start an on-demand check of a project's keywords

GET

/projects/{project_id}/competitors

Other advertisers ranked by ad occurrences

GET

/alert-rules

Alert rules configured in the account

GET

/account

Plan, monthly allowances, usage and rate limit

Why Jentic?

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

Setup

Wiring Ads Lighthouse by hand means learning its bearer key with the als_ prefix, staying within its request-rate limit, and polling on-demand checks until they finish before reading observations. Through Jentic you install once, import Ads Lighthouse from the API Directory, store the key once, and your agent runs checks and reads results.

Permission scoping

Ads Lighthouse puts the project id in the URL path (/projects/{project_id}), so a rule can pin your agent to one project and the operations you choose, such as starting checks and reading observations. You decide which operations it may call, so deleting projects or removing keywords stays out unless you add it.

Credential isolation

Your Ads Lighthouse 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 'monitor paid ads on my brand keywords' or 'find competitors bidding on my terms', and Jentic returns the matching Ads Lighthouse operation with its input schema so the agent calls the right endpoint directly.

FAQs

Specific to using Ads Lighthouse API through Jentic.

What authentication does the Ads Lighthouse API use?

The Ads Lighthouse API authenticates with an API key sent as a bearer token in an Authorization: Bearer header, per its OpenAPI spec, and the REST API is available on Scale plans and above. The same credential carries your plan's monthly allowances, which you can read from the account endpoint. Through Jentic the key is stored encrypted on your own instance and injected at call time.

Is there an Ads Lighthouse MCP server?

Yes, the same JSON operations are offered as MCP tools. You can also connect Ads Lighthouse directly through Jentic: your agent gets the full 87-endpoint surface without loading another server's tool definitions into its context, your key is injected at call time by your self-hosted instance instead of living in a config file, and your rules decide which operations the agent may call.

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

Yes. Because the project id travels in the URL path, you can write a rule that allows only starting checks and reading observations on one project, so the agent monitors that project and nothing else. Deleting projects, removing keywords, or changing team roles stays out of the rule unless you add it, and every call is logged.

Can I find competitors bidding on my keywords with the Ads Lighthouse API?

Yes. The competitors endpoint ranks advertisers by how often their ads appear for a project's keywords, and you can open one advertiser to read its appearance history, an hourly-weekday heatmap, and its distinct ad copy over time. Observations also link each paid ad back to the keyword and search it appeared on.

What are the rate limits for the Ads Lighthouse API?

The Ads Lighthouse spec states that each credential may make 120 requests per minute. Paid checks and redirect traces also draw on your plan's monthly allowances rather than that per-request limit, and the account endpoint reports current usage and remaining allowance. Check the Ads Lighthouse guide at https://adslighthouse.com/api for plan details.

How do I run an ad check with the Ads Lighthouse API through Jentic?

Search the Jentic API Directory for an intent like 'monitor paid ads on my brand keywords', import Ads Lighthouse, and store your key once. Your agent then starts an on-demand check for a project and reads the observations through Jentic. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Ads Lighthouse API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyMarketingSeo Sembearer87 EndpointsREST

For Agents

Run paid-search monitoring checks, read observations of ads and advertisers, rank competitors, track affiliate compliance, and configure alerts. Authenticates with a bearer API key.

Use for: I need to start a check of a project's monitored keywords, Find which advertisers are bidding on my brand terms, List the paid ads observed for a keyword this week, Set up an alert when a competitor appears on my keyword

Not supported: Does not handle creating or buying ads, bid management, or organic SEO rank tracking. Use for monitoring paid-search ads, competitors, and affiliate compliance only.

The Ads Lighthouse API monitors paid-search advertising for a brand and reports what it finds as account-scoped data. Monitoring projects run scheduled and on-demand checks of keywords across markets, search engines, and devices, recording observations of the paid ads displayed and the advertisers behind them. From there it ranks competing advertisers by ad occurrences, tracks one advertiser's history, heatmap, and ad copy over time, and surfaces affiliate IDs seen behind ads that use your brand. Alert rules fire by email, Slack, or webhook, PDF reports and CSV-style exports are available as endpoints, and the account endpoint reports plan allowances and 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

94%

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

43%

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.

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

88%

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

72%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Ads Lighthouse API to your agent

Capabilities

Start building with Ads Lighthouse API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Ads Lighthouse API

Jentic AI Readiness Score

Ads Lighthouse 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