Agenty API

Name: Agenty API API
Brand: Agenty API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi Cdbearer71 EndpointsREST

For Agents

Drive Agenty web scraping and automation: start jobs on existing agents, poll results, manage input lists and schedules, and rotate API keys.

Quickstart

Get started with Agenty API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"start an agenty scraping job and download the results"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Agenty API 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

GET STARTED

Start building with Agenty API API

Explore with Jentic

View OpenAPI Document

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 document for Agenty API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Agenty API 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

Why though Jentic?

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

Credential isolation

Agenty bearer tokens are stored in the Jentic vault and injected as the Authorization header at call time. Agents receive scoped execution results — the raw token never enters their context.

Intent-based discovery

Agents search by intent (e.g. 'start a scraping job' or 'download job results') and Jentic returns the matching Agenty operation with its input schema and required path parameters.

Time to first call

Direct Agenty integration: half a day to wire job start, polling, and result download. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Apify API

Larger scraping marketplace with site-specific Actors and dataset storage

Choose Apify when you need a maintained scraper for a major site (Google, Amazon, LinkedIn) rather than building the agent yourself.

Alternative

Scrapingdog

Single-endpoint web scraping with built-in proxy rotation

Choose Scrapingdog for one-off page fetches where you don't need persistent agents, schedules, or workflow chaining.

Complementary

ZenRows

Anti-bot proxy that complements Agenty when targets block direct requests

Configure ZenRows as the proxy layer for Agenty agents that scrape sites with strong anti-bot protection.

FAQs

Specific to using Agenty API 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 at https://app.jentic.com/sign-up.

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.