For Agents
Upload a video, clip it into vertical Shorts, publish clips to connected social destinations, and pull measured performance receipts. Authenticated with a bearer API key; API access needs the Pro or Scale plan.
Use for: Upload a video to turn into Shorts, Clip the best moments from my video, Publish a finished clip to YouTube and TikTok, Check the status of a clip job
Not supported: Does not handle long-form video hosting, ad buying, or timeline editing. Use for clipping videos into Shorts, publishing them, and measuring performance only.
The Everpop API turns a user's own videos into published vertical Shorts for YouTube, Instagram, Facebook, and TikTok. It takes a direct upload, finalizes it into a clippable video, clips the best moments, and publishes finished clips to named connected destinations. It then returns measured 48h and 7d performance receipts per clip and supports paid-clipping campaigns with a measured payout proof. API access requires the Pro or Scale plan.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Everpop 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%2Feverpop.app%2Feverpop" | 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%2Feverpop.app%2Feverpop" | 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 Everpop API.
Upload a source video with a presigned direct upload and finalize it into a clippable video
Clip the best moments from a video into vertical Shorts
Publish a finished clip to connected YouTube, Instagram, Facebook, and TikTok destinations
Poll clip jobs for their status and the produced Shorts
Pull measured 48h and 7d performance receipts for published clips
Create paid-clipping campaigns and read their measured payout proof
Patterns agents use Everpop API for, with concrete tasks.
★ Automated Shorts Production
A creator turns long videos into a steady stream of Shorts. The Everpop API requests a presigned upload for the source file, finalizes it into a clippable video, clips the best moments into vertical Shorts, and publishes the finished clips to the creator's connected YouTube, Instagram, Facebook, and TikTok destinations.
Request a presigned upload, finalize the uploaded video, clip it into Shorts, then publish a finished clip to the chosen destinations
Shorts Performance Tracking
A team measures how published Shorts actually perform. The Everpop API returns per-clip receipts with real 48h and 7d numbers, lists the posts created from each clip, and for paid-clipping campaigns provides a measured payout proof with per-clip totals, so reporting is based on measured views rather than estimates.
List receipts for recently published clips and pull the campaign proof to report measured 48h and 7d views
AI Agent Short-Form Pipeline via Jentic
An AI agent runs a short-form content pipeline through Jentic without holding the Everpop key itself. It searches by intent, receives the matching operation and its input schema, and runs upload, clip, and publish with the credential injected at run time, so a video becomes published Shorts end to end.
Search Jentic for 'clip a video into Shorts', load the clip operation schema, run it, and publish the result with Jentic-managed credentials
18 endpoints — the everpop api turns a user's own videos into published vertical shorts for youtube, instagram, facebook, and tiktok.
METHOD
PATH
DESCRIPTION
/api/v1/videos/upload
Request a presigned direct upload slot
/api/v1/videos/complete
Finalize the upload into a clippable video
/api/v1/clip
Clip the best moments into Shorts
/api/v1/jobs/{id}
Poll a clip job for status and output
/api/v1/publish
Publish a clip to named destinations
/api/v1/receipts
Read measured performance per clip
/api/v1/campaigns
Create a paid-clipping campaign
/api/v1/videos/upload
Request a presigned direct upload slot
/api/v1/videos/complete
Finalize the upload into a clippable video
/api/v1/clip
Clip the best moments into Shorts
/api/v1/jobs/{id}
Poll a clip job for status and output
/api/v1/publish
Publish a clip to named destinations
/api/v1/receipts
Read measured performance per clip
/api/v1/campaigns
Create a paid-clipping campaign
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>What agents get from Jentic-routed access to this vendor.
Setup
Wiring Everpop by hand means managing its epk_ bearer key, running the two-step presigned upload, and polling clip jobs for completion yourself. Through Jentic you install once, import Everpop from the API Directory, store the key once, and your agent calls it.
Permission scoping
Limit the agent to the operations it needs, such as uploading, clipping, and reading jobs, so publishing and paid-campaign creation are not included unless you add them. Everpop puts job and campaign ids in the URL path, so those read operations can be scoped by path as well.
Credential isolation
Your Everpop 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 'clip a video into Shorts' or 'publish a clip', and Jentic returns the matching Everpop 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 Everpop API through Jentic.
What authentication does the Everpop API use?
The Everpop API authenticates with a bearer token, an epk_ API key, in the Authorization header per its OpenAPI spec, and API access requires the Pro or Scale plan. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent.
Can I publish Shorts to YouTube and TikTok with the Everpop API?
Yes. After a clip is produced, the publish operation sends it to the destinations connected to the account, which can include YouTube, Instagram, Facebook, and TikTok. The list-destinations operation shows exactly which connected targets your API key can publish to before you publish.
What are the rate limits for the Everpop API?
The OpenAPI spec does not specify numeric rate limits for the Everpop API, but usage is bounded by your plan: accounts without an active Pro or Scale subscription receive an HTTP 402 response. The usage operation reports videos used and remaining for the month so an agent can pace its work.
How do I clip a video into Shorts with the Everpop API through Jentic?
Search Jentic for 'clip a video into Shorts' and it returns the Everpop clip operation with its input schema. Load the schema, reference the finalized video, and the key is injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the Everpop API?
Yes. Write a rule that allows only uploading, clipping, and reading jobs, so the agent can produce Shorts but cannot publish or create paid campaigns until you allow it. You choose which operations it may call, and every request runs through your own instance where it is logged.
Is there an Everpop API MCP server?
Yes, Everpop offers an MCP connector on its Pro and Scale plans. You can also connect Everpop directly through Jentic: your agent gets the full 18-endpoint surface without loading another server's tool definitions into its context, your key is injected at call time by your self-hosted instance instead of living in a config file, and your rules decide which operations the agent may call.
GET STARTED