Install Jentic One Beta

Connect the API of the Adshot Scraping Engine to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API of the Adshot Scraping Engine, 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%2Fswaggerhub.jensmostaert3%2Fapi-of-the-adshot-scraping-engine" | 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%2Fswaggerhub.jensmostaert3%2Fapi-of-the-adshot-scraping-engine" | 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 API of the Adshot Scraping Engine API.

Create a new Channel Job.

List / search all Channel scrape jobs.

Retrieve details of a specific Channel Job.

Update a Channel Job.

Delete a specific Channel Job.

GET STARTED

Start building with API of the Adshot Scraping Engine API

Explore with Jentic One

View OpenAPI Document

Automated Operations on Channels Management

Automate operations on channels operations by combining multiple API of the Adshot Scraping Engine endpoints. Agents can list / search all channel scrape jobs. and then retrieve details of a specific channel job. in a single workflow.

Call GET /v1/channels/jobs to list / search all channel scrape jobs., then verify the result

AI Agent Integration via Jentic

AI agents discover and call API of the Adshot Scraping Engine 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 'create a new channel job.', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

14 endpoints — this is the api definition for the adshot scraping engine service.

METHOD

PATH

DESCRIPTION

POST

/v1/channels/jobs

Create a new Channel Job.

GET

/v1/channels/jobs

List / search all Channel scrape jobs.

GET

/v1/channels/jobs/{id}

Retrieve details of a specific Channel Job.

PATCH

/v1/channels/jobs/{id}

Update a Channel Job.

DELETE

/v1/channels/jobs/{id}

Delete a specific Channel Job.

GET

/v1/channels/scrapes

List / search all Channel scrapes.

GET

/v1/channels/scrapes/{id}

Retrieve details of a specific Channel Scrape.

POST

/v1/media/jobs

Create a new Media Job.

POST

/v1/channels/jobs

Create a new Channel Job.

GET

/v1/channels/jobs

List / search all Channel scrape jobs.

GET

/v1/channels/jobs/{id}

Retrieve details of a specific Channel Job.

PATCH

/v1/channels/jobs/{id}

Update a Channel Job.

DELETE

/v1/channels/jobs/{id}

Delete a specific Channel Job.

GET

/v1/channels/scrapes

List / search all Channel scrapes.

GET

/v1/channels/scrapes/{id}

Retrieve details of a specific Channel Scrape.

POST

/v1/media/jobs

Create a new Media Job.

Why Jentic?

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

Setup

Wiring the Adshot Scraping Engine by hand means reading its spec, building calls across its channel jobs, scrapes, and media jobs endpoints, and handling request formatting and retries yourself. Through Jentic you install once, import the Adshot Scraping Engine from the API Directory, store any required connection detail once, and your agent calls it.

Permission scoping

The Scraping Engine puts the job and scrape ids in the URL path (/v1/channels/jobs/{id}, /v1/channels/scrapes/{id}), so a rule can pin your agent to reading one channel job or scrape. You choose the operations it may call, so the PATCH update and DELETE on a job are not included unless you add them.

Credential isolation

Any connection detail the Adshot Scraping Engine needs 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 'create a new channel scraping job', and Jentic returns the matching Adshot Scraping Engine operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using API of the Adshot Scraping Engine API through Jentic.

What authentication does the API of the Adshot Scraping Engine use?

The API of the Adshot Scraping Engine 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 create a new channel job. with the API of the Adshot Scraping Engine ?

Yes. Use the POST /v1/channels/jobs endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the API of the Adshot Scraping Engine ?

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 create a new channel job. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new channel job.'. Jentic returns the matching API of the Adshot Scraping Engine operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the API of the Adshot Scraping Engine have?

The API of the Adshot Scraping Engine exposes 14 endpoints covering operations on channels, operations on media operations.

Can I limit what my agent is allowed to do with the Adshot Scraping Engine API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Adshot Scraping Engine operations and connection details the agent may use. Because the API carries each job and scrape id in the URL path (/v1/channels/jobs/{id} and /v1/channels/scrapes/{id}), you can pin the agent to reading a single channel job or scrape. You choose the operations it may call, so the PATCH update and DELETE on a job stay out of reach unless you explicitly grant them.

Jensmostaert3 API of the Adshot Scraping Engine

Browse all Swaggerhub Jensmostaert3 APIs

AI ReadinessAI-Ready (A-)75/100

See full scorecard

Community OpenAPI document · agent-readyMaps GeolocationMappingnone14 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically create a new channel job., list / search all channel scrape jobs.. Covers 14 operations.

Use for: I need to a new channel job., I want to / search all channel scrape jobs., Search for details of a specific channel job., Find all a channel job.

Not supported: Does not handle payments, communications, or crm - use for maps and geolocation only.

This is the API definition for the Adshot Scraping Engine service. This API should only be made available internally for use by Adshot Core. There is no dependency in the other direction. Meaning that the Scraping Engine API should not fetch data from Adshot Core or store foreign keys to entities stored in Adshot Core, thereby avoiding coupling between these services as much as possible. Mappings . The API exposes 14 endpoints.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

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

60%

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

37%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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: C-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.

64%

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.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the API of the Adshot Scraping Engine to your agent

Capabilities

Start building with API of the Adshot Scraping Engine API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Jensmostaert3 API of the Adshot Scraping Engine

Jentic AI Readiness Score

API of the Adshot Scraping Engine

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