Install Jentic One Beta

Connect the HuntAPI API Reference to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the HuntAPI API Reference, 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.

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%2Fhuntapi.com%2Fhuntapi" | sh

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%2Fhuntapi.com%2Fhuntapi" | 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 HuntAPI API Reference API.

Read a media URL's title, duration, thumbnail, channel, and view counts without downloading the file

Download a video at a chosen video_quality (best, 1080p, 720p, 480p, or 360p) as mp4, webm, or mkv

Extract only the audio track of a video, or only the silent video, with download_type

Download audio as mp3, m4a, or wav at best, 320kbps, 256kbps, or 128kbps quality

GET STARTED

Start building with HuntAPI API Reference API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use HuntAPI API Reference API for, with concrete tasks.

★ Agent media lookup through Jentic

An AI agent handed a video link needs to know what it is before doing anything else. Through Jentic the agent searches for 'get metadata for a video URL', receives the HuntAPI Media Metadata operation with its input schema, and calls GET /v1/media/metadata with the URL as query. It reads the title, duration, channel, thumbnail, and view counts without downloading the file.

Call GET /v1/media/metadata with query 'https://www.youtube.com/watch?v=dQw4w9WgXcQ' and report the title, duration, and channel

Audio extraction for transcription

A team transcribing interviews or talks needs the audio track only. GET /v1/audio/download takes the media URL as query, an audio_format of mp3, m4a, or wav, and an audio_quality, and returns a job id. Polling GET /v1/jobs/{id} until the status is CompletedJob gives the file to pass to a speech-to-text service.

Call GET /v1/audio/download with query set to the talk URL, audio_format 'mp3', and audio_quality '128kbps', then poll GET /v1/jobs/{id} until status is CompletedJob and return the result

Video archiving with webhooks

A content team archives its own published videos across platforms. GET /v1/video/download takes video_quality, video_format, and download_type, and with webhook_url set the result is posted to that URL with up to three attempts. webhook_authorization adds an Authorization header so the receiving endpoint can check the request.

Call GET /v1/video/download with query set to the video URL, video_quality '1080p', video_format 'mp4', and webhook_url 'https://example.com/hooks/huntapi'

Key Endpoints

8 endpoints — the huntapi api downloads video and audio from media urls on platforms such as youtube, instagram, tiktok, vimeo, x, facebook, twitch, and reddit, and reads their metadata without downloading the file.

METHOD

PATH

DESCRIPTION

GET

/v1/media/metadata

Read metadata for a media URL

GET

/v1/video/download

Start a video download job

GET

/v1/audio/download

Start an audio download job

GET

/v1/jobs/{id}

Poll a download job

GET

/v1/usage

Usage and credit balance

GET

/v1/media/metadata

Read metadata for a media URL

GET

/v1/video/download

Start a video download job

GET

/v1/audio/download

Start an audio download job

GET

/v1/jobs/{id}

Poll a download job

GET

/v1/usage

Usage and credit balance

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring HuntAPI by hand means sending the x-api-key header, starting a download job, and polling the jobs endpoint or running a webhook receiver for the result. Through Jentic you install once, import HuntAPI from the API Directory, store the key once, and your agent calls it.

Permission scoping

HuntAPI puts each tool in its own URL path (/v1/media/metadata, /v1/video/download, /v1/audio/download), while the media URL travels as a query parameter. Rules bound which operations your agent may call, not which media links it uses, so you choose whether downloads are included at all.

Credential isolation

Your HuntAPI key 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 'get metadata for a video URL' or 'download audio from a video', and Jentic returns the matching HuntAPI operation with its input schema so the agent sets the right quality and format fields without browsing the reference docs.

FAQs

Specific to using HuntAPI API Reference API through Jentic.

What authentication does the HuntAPI API use?

The HuntAPI API authenticates with an API key in the `x-api-key` request header, declared as the ApiKeyAuth scheme in its OpenAPI spec. The separate webhook_authorization parameter is not for HuntAPI itself: it sets the Authorization header HuntAPI sends to your webhook. Through Jentic the HuntAPI key is held by your own Jentic One instance and attached at call time.

Which platforms does the HuntAPI API support?

The spec lists YouTube, Instagram, TikTok, Vimeo, X, Facebook, Twitch, and Reddit as examples of supported media URLs. It notes that private, deleted, and age-restricted content may fail to download, so check GET /v1/media/metadata first if you are unsure.

How do HuntAPI downloads return the file?

Downloads are asynchronous. GET /v1/video/download and GET /v1/audio/download return a job id; poll GET /v1/jobs/{id} until the status is CompletedJob, Error, NotFound, or BadRequest, using progress (0 to 100) meanwhile. Alternatively pass webhook_url and the result is posted to your endpoint.

What are the rate limits for the HuntAPI API?

The OpenAPI spec does not specify rate limits; it describes credit costs and a GET /v1/usage endpoint for your balance. Check the HuntAPI documentation at https://huntapi.com for current limits.

How do I download a video's audio through Jentic?

Search Jentic for 'download audio from a video URL', load the GET /v1/audio/download operation, and execute it with query set to the URL and audio_format 'mp3'. Then poll GET /v1/jobs/{id} with the returned job id. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a HuntAPI MCP server?

You don't need an MCP server to give your agent HuntAPI. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the metadata, download, and job operations on demand without extra tool definitions in its context.

Can I limit what my agent is allowed to do with the HuntAPI API?

Yes. For an agent that should only identify media, write a rule that allows GET /v1/media/metadata alone. It can then read titles, durations, and channels for links it is given, but it cannot start video or audio downloads, and every call it makes is logged.

HuntAPI API Reference

AI ReadinessFoundational (C)55/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaVideo ProcessingapiKey8 EndpointsREST

For Agents

Download video or audio from YouTube, TikTok, Instagram, Vimeo, and other media URLs as asynchronous jobs, or read a video's title, duration, channel, and view counts without downloading it.

Use for: Get the title and duration of this YouTube video, Download the audio of a podcast episode URL as mp3, I want a 720p mp4 of a Vimeo video, Check the progress of my download job

Not supported: Does not host, edit, or transcribe media. Use for reading media metadata and downloading video or audio from URLs only.

The HuntAPI API downloads video and audio from media URLs on platforms such as YouTube, Instagram, TikTok, Vimeo, X, Facebook, Twitch, and Reddit, and reads their metadata without downloading the file. Video downloads choose a quality from 360p to 1080p or best, a format of mp4, webm, or mkv, and whether to keep the audio, the video, or both. Audio downloads output mp3, m4a, or wav at a chosen bitrate. Downloads run as asynchronous jobs that are polled for progress and result, or delivered to a webhook URL with an optional Authorization header.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

89%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

18%

Example Density

How richly the API is illustrated with examples.

88%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

42%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

75%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

16%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: CSignals: 1

56%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the HuntAPI API Reference to your agent

Capabilities

Start building with HuntAPI API Reference API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

HuntAPI API Reference

Jentic AI Readiness Score

HuntAPI API Reference

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness