Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EasyDown 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.
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%2Feasydown.org%2Feasydown" | shStep 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%2Feasydown.org%2Feasydown" | 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.
What an agent can do with EasyDown API.
Parse a public media URL into the normalized EasyDown media format
Return full platform-specific data for a post alongside the normalized media
Extract media from TikTok, Douyin, Kuaishou, and Bilibili posts
Extract media from YouTube, Twitter/X, Instagram, and Threads posts
Extract media from Weibo, Xiaohongshu, and Toutiao posts
GET STARTED
Patterns agents use EasyDown API for, with concrete tasks.
★ AI Agent Media Resolution
Let an AI agent turn a social post link into usable media on demand: it passes a public URL to the generic parse operation and receives the normalized media the post contains. Through Jentic the agent discovers the parse operation by intent and calls it with the URL, so an agent that is handed a link can resolve its media without a developer wiring each platform's quirks by hand.
Parse a TikTok post URL with the generic parse operation and return the normalized media URLs to the agent
Cross-Platform Content Ingestion
Teams that collect posts from many networks want one shape of data regardless of source. The platform-specific parse operations return both the normalized media and the full platform payload for a given URL, so a pipeline can store the common fields and still keep the raw details. This covers short-video, image, and streaming platforms through a single API token.
Call the platform-specific parse operation for a YouTube URL to get both the normalized media and the full YouTube payload
Chinese Social Platform Support
Many media APIs stop at Western platforms, leaving Chinese networks unresolved. EasyDown parses Weibo, Bilibili, Xiaohongshu, Douyin, Kuaishou, and Toutiao URLs into the same normalized media format as everything else. An agent can process a mixed feed of global and Chinese posts without branching its logic per region.
Parse a Xiaohongshu note URL and a Douyin video URL, returning normalized media for each
13 endpoints — the easydown api parses public media urls from social platforms into a normalized media format or full platform-specific data.
METHOD
PATH
DESCRIPTION
/api/v1/parse
Parse media into the normalized EasyDown format
/api/v1/platforms/{platform}/parse
Parse media with normalized and full platform data
/api/v1/platforms/tiktok/parse
Parse TikTok media
/api/v1/platforms/youtube/parse
Parse YouTube media
/api/v1/platforms/instagram/parse
Parse Instagram media
/api/v1/platforms/twitter/parse
Parse Twitter / X media
/api/v1/platforms/bilibili/parse
Parse Bilibili media
/api/v1/platforms/weibo/parse
Parse Weibo media
/api/v1/parse
Parse media into the normalized EasyDown format
/api/v1/platforms/{platform}/parse
Parse media with normalized and full platform data
/api/v1/platforms/tiktok/parse
Parse TikTok media
/api/v1/platforms/youtube/parse
Parse YouTube media
/api/v1/platforms/instagram/parse
Parse Instagram media
/api/v1/platforms/twitter/parse
Parse Twitter / X media
/api/v1/platforms/bilibili/parse
Parse Bilibili media
/api/v1/platforms/weibo/parse
Parse Weibo media
What agents get from Jentic-routed access to this vendor.
Setup
Wiring EasyDown by hand means managing its bearer token and learning each platform's parse endpoint and the difference between normalized media and the full platform payload. Through Jentic you install once, import EasyDown from the API Directory, store the token once, and your agent calls it.
Permission scoping
EasyDown puts the platform in the URL path (/api/v1/platforms/{platform}/parse), so a rule can limit your agent to specific platforms such as YouTube or TikTok and the parse operations you pick. Every operation is a read-only parse, so there are no destructive operations to grant unless you add new ones later.
Credential isolation
Your EasyDown API token 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 'parse a TikTok video' or 'get media from a YouTube link', and Jentic returns the matching EasyDown operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using EasyDown API through Jentic.
What authentication does the EasyDown API use?
The EasyDown API authenticates with a bearer token per its OpenAPI spec, sent as an Authorization header carrying your EasyDown API token. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's context.
Can I parse a TikTok URL with the EasyDown API?
Yes. The TikTok parse operation takes a public TikTok post URL and returns normalized media along with the full platform payload, and the same pattern works for Douyin, YouTube, Twitter/X, Instagram, Threads, Xiaohongshu, Bilibili, Kuaishou, and Weibo. The generic parse operation returns normalized media for any supported URL.
What are the rate limits for the EasyDown API?
The OpenAPI spec does not specify rate limits; see https://easydown.org for current limits. Each parse call resolves a single URL, so processing many posts means one request per URL.
Is there an EasyDown MCP server?
You don't need an MCP server to give your agent the EasyDown API. Jentic connects it directly from the API Directory: import it, store your API token once, and your agent calls operations like parsing a TikTok or YouTube URL. Operations are discovered on demand, so no extra server's tool definitions sit in your agent's context.
Can I limit what my agent is allowed to do with the EasyDown API?
Yes. Because EasyDown addresses each platform through its own path, a rule can allow the agent to parse only specific platforms, such as YouTube and TikTok, and nothing else. Every operation is a read-only parse, so there are no destructive actions to grant, and each call the agent makes is logged.
How do I parse a media URL with the EasyDown API through Jentic?
Search Jentic for 'parse a social media URL into media' to find the parse operation, pass the public post URL, and read the normalized media back. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Parse a public social media URL into normalized media or full platform-specific data across TikTok, YouTube, Twitter/X, Instagram, and more. Covers 13 operations spanning 11 platforms.
Use for: Parse a TikTok video URL into downloadable media, Get the normalized media for a YouTube link, Extract images from an Instagram post, Resolve a Twitter/X post into its media
Not supported: Does not handle posting content, saving files to storage, or video transcoding. Use for parsing public media URLs into normalized media only.
The EasyDown API parses public media URLs from social platforms into a normalized media format or full platform-specific data. Agents pass a post URL to the generic parse operation to get normalized media, or call a platform-specific operation to also receive the raw platform payload. It covers TikTok, Douyin, Toutiao, YouTube, Twitter/X, Instagram, Threads, Xiaohongshu, Bilibili, Kuaishou, and Weibo. Authentication uses a bearer EasyDown API token.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>