Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

Jentic OneSelf-hosted, open-source control plane between your agents and any APIAPI DirectoryBrowse 10,000+ APIs ready for AI agent integrationAPI ScorecardAssess your APIs for AI-readiness with automated scoringAgentic SandboxSafely simulate AI agents with your production APIsJenticSign in to the Jentic web app

CAPABILITIES

IntegrationConnect AI agents to your existing systemsWorkflowsDiscover and capture successful agent workflowsGovernanceDefine, observe, and enforce AI policies

TOOLS

Arazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually
Pricing
Developers

GET STARTED

DocumentationGuides and API referenceQuickstartGet up and running in minutes

COMMUNITY

GitHubOpen source projects and examples
Resources
BlogLatest articles and insightsPress & MediaBrand assets and press contactOpen StandardsBuilt on open specs. Never locked in.NewsletterAPIs, AI agents, mixed with architecture and strategy.
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Install Jentic OneBook a Demo
How Jentic WorksJentic OneAPI DirectoryAPI ScorecardAgentic SandboxJenticIntegrationWorkflowsGovernanceArazzo UIArazzo Editor
Pricing
DocumentationQuickstartGitHub
BlogPress & MediaOpen StandardsNewsletter
About UsCareersContact
Request a demoInstall Jentic One
Jentic
For Enterprises
  • Product Overview
  • Agentic Sandbox
  • Book a Demo
For Developers
  • Jentic One
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
ISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic. All rights reserved.
APIs / Maps Geolocation / Swaggerhub Jensmostaert3 / API of the Adshot Scraping Engine
API of the Adshot Scraping Engine logo

Jensmostaert3 API of the Adshot Scraping Engine

Browse all Swaggerhub Jensmostaert3 APIs
★ Only Publicly Available OpenAPI DocumentMaps GeolocationMappingnone14 EndpointsREST

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 GithubView OpenAPI Document

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.

1

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
2

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

Use Cases

Patterns agents use API of the Adshot Scraping Engine API for, with concrete tasks.

★ Maps and Geolocation Operations

Use the API of the Adshot Scraping Engine to perform maps geolocation operations programmatically. The API provides 14 endpoints covering core functionality including create a new channel job., list / search all channel scrape jobs., retrieve details of a specific channel job..

Call POST /v1/channels/jobs to create a new channel job.

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?

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

Credential management

Credential isolation

API of the Adshot Scraping Engine none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Intent-based discovery

Agents search by intent (e.g., 'create a new channel job.') and Jentic returns the matching API of the Adshot Scraping Engine operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Time to first call

Direct API of the Adshot Scraping Engine integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Here

→

Alternative maps geolocation API

Choose Here when you need a different approach to maps geolocation operations

Alternative

Tomtom

→

Alternative maps geolocation API

Choose Tomtom when you need a different approach to maps geolocation operations

Complementary

Googleapis

→

Complementary maps geolocation API

Choose Googleapis when you need a complementary approach to maps geolocation operations

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.

GET STARTED

Start building with API of the Adshot Scraping Engine API

Explore with Jentic
View OpenAPI Document