VideoCoreAssistant connector

The VideoCore API

The same real-data YouTube lookups as the VideoCore assistant connector, as plain HTTPS and JSON, for your own code, a spreadsheet or a no-code tool. Read-only: nothing here changes a channel or a video. Free on every plan, with a daily allowance.

Make an API key   OpenAPI file

Start

  1. Sign in to VideoCore and connect your YouTube channel (the API, like the rest of VideoCore, is for people with a channel).
  2. Settings, API keys, Generate. Copy the key now: it is shown once.
  3. Call an endpoint with the key in a header:
curl -X POST https://videocore.uk/api/v1/diagnose_video \
  -H "Authorization: Bearer vcapi_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"video_url":"https://www.youtube.com/watch?v=VIDEO_ID"}'

Send the key in the header (Authorization: Bearer or X-API-Key), never in the address: addresses end up in logs. Keep it secret; revoke it in Settings if it leaks. You can have up to 5 keys.

Endpoints

RequestWhat it does
GET /api/v1/Name, version and the tool names.
GET /api/v1/toolsEvery endpoint with its arguments.
GET /api/v1/usageLookups used and left today.
GET /api/v1/openapi.jsonThe OpenAPI 3.1 file (no key needed).
POST /api/v1/diagnose_videoDiagnose a video. Diagnose why a specific YouTube video is or isn't getting views. Returns YouTube's counts (views, likes, comments) plus figures VideoCore calculates from them (view velocity, engagement, performance vs the channel's OWN recent median, a verdict), and an AI teardown of the thumbnail, title and hook with specific fixes. Use when a creator asks why a video under/over-performed.
Arguments: video_url (needed) – A YouTube video URL or 11-char video id.
POST /api/v1/channel_auditAudit a channel. Audit any YouTube channel from its public YouTube numbers: subscribers and total views (from YouTube), plus upload cadence, recent median views, best and worst recent videos, and consistency (calculated by VideoCore). Use for competitive intelligence or auditing your own channel.
Arguments: channel (needed) – Channel URL, @handle, channel id, or name.
POST /api/v1/find_outliersFind breakout videos on a channel. Find a channel's outlier videos — the ones that massively over- or under-performed versus that channel's own recent median. Reveals what topics/formats are actually working right now. Use to find breakout patterns to replicate, and for asks like "the five biggest channels on my topic and which of their videos beat their usual numbers" (call it once per channel).
Arguments: channel (needed) – Channel URL, @handle, channel id, or name.
POST /api/v1/find_nicheRate a niche. Rate a YouTube niche/topic: demand, competition, a rough RPM estimate and trend, with an overall viability label (all calculated by VideoCore, not YouTube metrics) and the top-performing videos. Use to evaluate whether a niche is worth entering.
Arguments: keyword (needed) – A niche or topic, e.g. "budget van builds".
POST /api/v1/trending_in_nicheWhat is trending in a niche. Surface videos gaining serious momentum in a niche. Default: recent uploads (last ~45 days) ranked by view velocity (views per day), to spot formats and topics before they peak. With window "24h": what broke in the niche in the last 24 hours, grouped into stories, each with how many videos and channels are already out on it, when the first went up and the fastest views per hour, plus the creator channel promise when one is saved, so you can say which angle is still open and fits.
Arguments: niche (needed) – A niche or topic keyword.; region – Optional 2-letter region code, e.g. US, GB.; window – Optional. "24h" for the last 24 hours grouped into stories; default "45d".
POST /api/v1/keyword_ideasTitle ideas for a topic. Generate title/keyword angles for a seed topic, grounded in the title patterns of the real top-performing videos for that topic. Returns the recurring patterns + the real videos they came from.
Arguments: seed (needed) – A seed topic or keyword.
POST /api/v1/compare_channelsCompare channels. Compare 2-4 YouTube channels side by side: subscribers (from YouTube), recent median views, upload cadence, consistency and recent best video (calculated by VideoCore). Use to benchmark your channel against competitors.
Arguments: channels (needed) – Two to four channels (URLs, @handles, ids or names), comma-separated.
POST /api/v1/video_ideasNext video ideas. Generate specific next-video ideas for a niche, grounded in what is actually overperforming right now (real top performers + recent momentum). Returns concrete concepts with a title, angle and why it should work.
Arguments: niche (needed) – The niche/topic to generate video ideas for.
POST /api/v1/check_titleCheck a title. Run VideoCore's measured checks on a YouTube title (the same checks as the public Title Checker): whether it names a person or a situation and not only a topic, whether the words on the thumbnail repeat the title (when the creator gives them), and, for a published video, whether its first thirty seconds deliver the title's key words. Each check is pass, flag or not checked; curiosity, clarity, length and emotional pull are listed as not checked because no code measures them. Never a score. Use before a creator publishes, or to compare title options.
Arguments: title (needed) – The title to check.; thumbnail_words – Optional: the words on the thumbnail, exactly as they appear.; video_url – Optional: the published video this title is for, so its opening can be checked against the title.
POST /api/v1/my_seasonsMy channel's seasons. The creator's own connected channel only. part "months" (default): each calendar month's views a day against the channel's own months around it, by year, and which months repeat as above or below usual in every year measured (needs a year of history; says so when there is not enough). part "titles": the channel's own uploads with a year or a seasonal phrase in the title (Christmas, summer, a month name) against its untagged uploads, by publish month; give "title" to see the channel's own videos with the same markers. Its own history, not a general rule, and not a forecast. Use when a creator asks when to publish, about seasonal topics, or whether to put a year in a title.
Arguments: part – months (default) or titles.; title – Optional, with part "titles": a planned title, matched to the channel's own videos with the same year or seasonal markers.
POST /api/v1/my_retentionWhere viewers left my video. The creator's own connected channel only, long videos (three minutes or more). For one video (newest by default): the share of people who started it still watching at 0:30, a quarter, halfway, three quarters and near the end, beside the channel's own usual at the same points; the steepest drop in the opening; the three steepest drops after it; and up to three places where more people were watching than a moment before (they rewound to it or skipped ahead to it; the curve cannot say which). When VideoCore holds the captions, each drop and rise carries what was being said there. From YouTube Analytics curves VideoCore already stores; no lookup is used. Use when a creator asks why people stop watching, or for edit notes for the next cut. Write notes from these times and words only; the reason people left is the creator's judgement.
Arguments: video – Optional: the video's link or id, or words from its title. Leave out for the newest long video with a curve.
POST /api/v1/my_projectsMy VideoCore projects. List the videos (projects) in the key holder's own VideoCore workspace, newest first, with whether each has a script.
Arguments: none

POST takes a JSON body; GET with the arguments in the query string also works. Every answer carries open_in_videocore, a link to the full view with thumbnails.

Limits

Errors

Always JSON: {"error": {"code": "...", "message": "..."}}.

StatuscodeMeaning
400bad_requestA needed argument is missing, or the body is not a JSON object.
401missing_key, invalid_keyNo key, or a key that is wrong or revoked.
403channel_required, plan_requiredConnect a YouTube channel first; or the plan does not include the API.
404unknown_toolNo such endpoint.
422lookup_failedThe lookup could not finish (for example, the video was not found). Not counted against your lookups.
429rate_limited, daily_limitToo many calls a minute, or today’s lookups are used.
500tool_errorA fault on our side. Not counted. Try again in a minute.
503busyThe shared YouTube allowance for today is used.

What the numbers are

Views, likes, comments and subscribers come from YouTube. Medians, ratios, rates and verdicts are calculated by VideoCore from them, and each answer says which is which (source_note). The API gives you the verdict word and labels, not a made-up 0 to 100 score.

Also

Prefer an assistant? Connect VideoCore to Claude or ChatGPT. Something not working? Use Report a problem inside VideoCore, and say which endpoint you called.