Agenty API
Browse all Agenty APIsAgent-ready OpenAPI document · curated by JenticDeveloper ToolsCi Cdbearer71 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Drive Agenty web scraping and automation: start jobs on existing agents, poll results, manage input lists and schedules, and rotate API keys.
Use for: Start a scraping job on an existing Agenty agent and return the job id, Download the most recent job result as a CSV, List the agents I currently own with their last run status, Stop a running job that has been going for too long
Not supported: Does not author scraping logic, render HTML, manage proxies, or solve CAPTCHAs - use for executing and managing pre-built Agenty agents only.
Jentic publishes the only available OpenAPI specification for Agenty API, keeping it validated and agent-ready. Agenty is a web scraping and automation platform exposing 71 endpoints to manage agents, jobs, inputs, lists, schedules, workflows, users, connections, API keys, projects, and results. Operators build a scraping or automation agent in the Agenty UI, then use this API to start jobs, fetch results, and orchestrate runs from external systems. Bearer auth and a flat /v2 base URL make it straightforward to embed inside larger pipelines.
Install Jentic One Beta
Connect the Agenty API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Agenty 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.
1
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%2Fagenty.com%2Fagenty-api" | sh2
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%2Fagenty.com%2Fagenty-api" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Agenty API.
Start a scraping or automation job on an existing Agenty agent via POST /jobs/start
Download job results as CSV via GET /jobs/download for downstream loading
Fetch per-job result rows, logs, and output files for inspection or replay
Manage input lists used as the targets for batch scraping runs via /lists endpoints
Schedule recurring jobs and manage workflow chains via /scheduler and /workflows
Provision and revoke API keys for individual integrations via /api-keys
Use Cases
Patterns agents use Agenty API for, with concrete tasks.
★ Trigger Scrapes from External Systems
Kick off Agenty agents from CI pipelines, internal tools, or no-code platforms by calling POST /jobs/start with the agent id. The platform handles browser orchestration and result storage; the caller just retrieves results when the job finishes. Suitable for teams that built scrapers in Agenty's UI but need programmatic execution.
POST /jobs/start with agent_id=42, then poll GET /jobs/{job_id} until status is 'completed' and download the CSV
Result Pipeline Integration
Pull finished job results out of Agenty and into a data warehouse, S3 bucket, or database. The agent calls /jobs/{job_id}/result for JSON rows or /jobs/{job_id}/result/download for the full CSV, then loads downstream. Removes the need for users to log in to download files manually.
After a job completes, GET /jobs/{job_id}/result and write each row to a Postgres staging table
Input List Management
Keep the URL list that drives a batch scrape current by appending new targets and removing stale ones via the /lists endpoints. The agent can sync the list from a CRM, a sitemap, or a spreadsheet on a schedule. This makes Agenty agents data-driven without UI clicks.
POST /lists/{list_id}/rows with new URLs from the daily sitemap diff so the next scheduled run picks them up
Agent-Orchestrated Scraping
Let a Jentic-connected agent decide which Agenty agent to start, watch the job to completion, and act on results inside a longer plan. The agent searches Jentic for the start-job and result endpoints, loads their schemas, and chains them with conditional logic. This turns Agenty into a callable scraping primitive for autonomous workflows.
Given a list of competitor domains, start a price-monitoring agent against each, wait for completion, and summarise pricing changes
Key Endpoints
71 endpoints — jentic publishes the only available openapi specification for agenty api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/jobs/start
Start a new job on an Agenty agent
GET
/jobs/{job_id}
Get job details and status
GET
/jobs/{job_id}/result
Fetch parsed job results
GET
/jobs/download
Download jobs as CSV
GET
/agents
List agents
POST
/lists/{list_id}/rows
Append rows to an input list
POST
/jobs/start
Start a new job on an Agenty agent
GET
/jobs/{job_id}
Get job details and status
GET
/jobs/{job_id}/result
Fetch parsed job results
GET
/jobs/download
Download jobs as CSV
GET
/agents
List agents
POST
/lists/{list_id}/rows
Append rows to an input list
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Agenty API by hand means managing its bearer auth and coding your own polling across a large surface of job, agent, and list operations. Through Jentic you install once, import the Agenty API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Agenty puts the job id and list id in the URL path (/jobs/{job_id}/result, /lists/{list_id}/rows), so a rule can pin the agent to one job or list. You choose which operations it may call, such as starting a job or reading its result, so anything you leave out is not reachable.
Credential isolation
Your Agenty bearer token is stored once, encrypted, by your own Jentic One instance and injected as the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'start a scraping job' or 'download job results', and Jentic returns the matching Agenty operation with its input schema and required path parameters so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Agenty API through Jentic.
Why is there no official OpenAPI spec for Agenty API?
Agenty does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Agenty API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Agenty API use?
Agenty uses HTTP bearer token authentication. Pass the token in the Authorization header as 'Bearer <token>'. Through Jentic the token sits in the credential vault and is injected at execution; the raw value never enters agent context.
Can I start a scraping job and get results in one call with the Agenty API?
No - jobs are asynchronous. POST /jobs/start returns a job id immediately, and the agent polls GET /jobs/{job_id} until status is completed, then calls /jobs/{job_id}/result or /jobs/{job_id}/result/download for the parsed output.
What are the rate limits for the Agenty API?
Agenty rate-limits at the plan level on concurrent jobs and API call frequency rather than publishing a hard requests-per-second cap. Build retry-with-backoff for 429 responses and respect concurrent-job limits when starting many runs in parallel.
How do I trigger an Agenty scraping job through Jentic?
Run the Jentic search 'start an agenty job'. Jentic returns POST /jobs/start; load its schema, supply the agent_id (and any input override), and execute. The response includes the job_id you then poll for completion.
Does Agenty support scheduled runs via the API?
Yes. The /scheduler endpoints let you create, list, update, and delete schedules attached to an agent or workflow, so recurring scrapes can be configured programmatically without using the UI.
Can I limit what my agent is allowed to do with the Agenty API?
Yes. Because you self-host Jentic One, your own rules decide which Agenty operations the agent may call, so you can allow only starting a job (POST /jobs/start) and reading its result (GET /jobs/{job_id}/result) while leaving everything else unreachable. Agenty puts the job id and list id in the URL path, such as /jobs/{job_id}/result and /lists/{list_id}/rows, so a rule can pin the agent to a single job or input list. The bearer token stays with your instance and is injected at execution, never entering the agent's context.
GET STARTED