Agenty API

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

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi Cdbearer21 EndpointsREST

For Agents

Run pre-built Agenty agents to extract structured web data, capture screenshots, or generate LLM-ready markdown; manage lists, schedules, and workflows.

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"

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

Capabilities

What an agent can do with Agenty API API.

Start a job on an existing Agenty agent and retrieve the result via /jobs and /jobs/{id}/result

Convert URLs into LLM-ready markdown by running an Agenty agent configured for that output

Maintain reusable URL lists that drive batch scrapes via /lists and /lists/{id}/rows

Schedule recurring runs of agents and workflows via /scheduler

GET STARTED

Start building with Agenty API API

Explore with Jentic

View OpenAPI Document

Use for: Start a job on an existing Agenty agent and return the job id, Get the parsed results of a finished scraping job, List the agents available on my Agenty account, 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 pre-built Agenty agents and workflows 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. This is the curated 21-endpoint cut of the Agenty platform covering the core surface most integrations need: agents, jobs, lists, scheduler, workflows, users, connections, API keys, dashboard, and projects. The platform itself does the web data extraction — capture screenshots, track redirects, and convert URLs into LLM-ready markdown — while this API drives execution and reads results.

Use Cases

Patterns agents use Agenty API API for, with concrete tasks.

★ Programmatic Web Scraping

Run scrapers built in the Agenty UI from external systems by calling POST /jobs to start a job and then GET /jobs/{id}/result for parsed output. Agenty handles browser orchestration, retries, and storage. Suited to teams who prefer a visual scraper builder but need programmatic execution.

POST /jobs with agent_id=42 and input list_id=11, poll until completed, then fetch the results

URL-to-Markdown for LLM Pipelines

Use an Agenty agent configured to output Markdown to convert a list of URLs into LLM-ready text for retrieval or summarisation. The agent handles JavaScript rendering and content extraction; the calling code only manages the input list and result download. Useful for building a custom RAG corpus from public web pages.

Update list 7 with 50 new URLs, start the markdown-conversion agent, and upload the resulting markdown chunks to a vector store

Scheduled Monitoring

Configure /scheduler entries to run an agent or workflow at fixed times so price changes, availability, or content updates are captured automatically. The agent reads back the latest job result on each schedule tick. Suitable for competitive monitoring or stock trackers.

Create a daily scheduler entry at 06:00 UTC for workflow 9 and email the result diff to a Slack channel

Agent-Driven Web Research

Let a Jentic-connected agent select an Agenty agent, kick off a job, and reason over the results inside a longer plan. The agent searches Jentic for the start-job operation, loads its schema, and chains it with /jobs/{id}/result. This makes Agenty a callable scraping primitive for autonomous research.

Given a question, choose the appropriate Agenty agent, start a job with the relevant URLs, and summarise the results

Key Endpoints

21 endpoints — jentic publishes the only available openapi specification for agenty api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/jobs

Start a new job

GET

/jobs/{job_id}

Get job status

GET

/jobs/{job_id}/result

Fetch job results

GET

/agents

List agents

POST

/lists/{list_id}/rows

Append rows to an input list

POST

/jobs

Start a new job

GET

/jobs/{job_id}

Get job status

GET

/jobs/{job_id}/result

Fetch job results

GET

/agents

List agents

POST

/lists/{list_id}/rows

Append rows to an input list

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 execution. The raw token never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g. 'start a scraping job' or 'convert URL to markdown') and Jentic returns the matching Agenty operation with its input schema and tag-grouped resource.

Time to first call

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

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Apify API

Scraping marketplace with maintained Actors for major sites and dataset storage

Choose Apify when you need a maintained scraper for a major site rather than building one in Agenty's UI.

Alternative

Bannerbear API

Image and screenshot generation API focused on templated visuals

Choose Bannerbear when the workflow needs templated marketing visuals rather than free-form web data extraction.

Complementary

ZenRows

Proxy and anti-bot bypass for hard-to-scrape targets

Use ZenRows in front of Agenty for sites that block direct requests, then let Agenty handle the structured extraction.

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 is held in the credential vault and injected at execution time.

Can I convert a URL to LLM-ready markdown with the Agenty API?

Yes, via an Agenty agent configured for markdown output. POST /jobs with that agent_id and a single-URL input; the resulting job result contains the markdown payload. The Agenty platform handles JavaScript rendering and content extraction.

What are the rate limits for the Agenty API?

Limits are tied to your plan's concurrent-job and API-call quotas rather than a single requests-per-second cap. Watch for 429 responses, retry with backoff, and respect the concurrent-job ceiling when fanning out runs.

How do I run an Agenty agent through Jentic?

Use the Jentic search 'start an agenty job'. Jentic returns POST /jobs; load its schema, supply the agent_id and any input list_id, and execute. The response contains the job_id which you poll via GET /jobs/{job_id}.

Does Agenty support workflow chaining via the API?

Yes. The /workflows endpoints let you create and execute chains of agents with sequential and conditional steps, so multi-stage scrapes can be defined and triggered from this API.