Jensmostaert3 API of the Adshot Scraping Engine

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.