#video

Live data from DLive, the blockchain-based livestreaming platform, with no key. Look up any streamer's public profile (followers, following, partner status, whether they are live and what they are streaming); read DLive's front-page recommended channels; pull the live-stream directory ordered by trending/new; browse the game and category directory with live viewer counts; read a single category's detail; and search streamers by name. The creator / livestreaming / audience-stats layer for stream dashboards, creator tools, analytics and discovery — distinct from the Kick and other streaming readers. Live from DLive; short cache only.

api.oanor.com/dlive-api

Live rankings and video engagement from AcFun (acfun.cn, "A站"), the pioneering Chinese ACG (anime-comic-game) video community, read keyless from AcFun's public ranking endpoint and video pages. Founded in 2007, AcFun is the platform that brought danmaku (bullet comments scrolling across the video) to China and is the cultural older sibling of Bilibili, with its own famously devoted fandom and its signature "banana" votes — the currency fans throw at videos they love. The ranking endpoint returns AcFun's video ranking over a period (day, three days or week), optionally for one channel, each video with its views, danmaku, likes, banana votes, favourites, shares and comments, its uploader and their follower count, duration and tags. The video endpoint returns one video in full by its AcFun id (the "ac" number) — the same engagement figures plus the description, read from the video page's embedded data. This is the AcFun platform cut — a distinct social and video platform, separate from Bilibili and the other video and social feeds in the catalogue, with its own banana-vote culture. Banana votes are AcFun-specific (a fan vote, not views or likes); danmaku are the scrolling comments. Counts are the real, live numbers AcFun shows; a short cache fronts the upstream. Keyless.

api.oanor.com/acfun-api

Live video, search and engagement data from Niconico (nicovideo.jp), the pioneering Japanese video platform that invented danmaku — the comments that scroll across the video itself — read keyless from Niconico's public Snapshot Search API and video-info endpoint. Niconico is one of Japan's biggest video communities, the home of Vocaloid, "Let's Play" culture and a vast catalogue with videos counting tens of millions of views and millions of overlaid comments. This exposes what is popular, who is watching and how each video is performing across Niconico's distinctive engagement signals — views, the famous scrolling comments, mylist bookmarks and likes. The search endpoint finds videos by keyword, sorted by views, comments, mylists, likes or upload date — the way to surface the platform's most-watched and most-discussed content. The tag endpoint browses an exact Niconico tag (the platform's main discovery axis — VOCALOID, ゲーム/games, 音楽/music, アニメ/anime) ranked by views, so you can see what leads a category. The video endpoint returns one video's full detail by its watch id (the sm/nm/so id), including its description, tags, length, upload date and uploader. This is the Niconico platform cut — a distinct social/video platform, separate from the YouTube, Bilibili, TikTok, BitChute and other platform feeds in the catalogue. View, comment, mylist and like counts are live; nothing is stored beyond a short cache. Counts are integers; dates are as the platform reports them (JST).

api.oanor.com/niconico-api

Live video, channel and trend data from BitChute — the alt-tech video-sharing platform and YouTube alternative — read straight from BitChute's public web API, no key. BitChute is one of the larger free-speech video platforms, with channels holding millions of views; this exposes what is trending, who the creators are and how each video and channel is performing. The trending endpoint returns the videos trending today or this week, ranked by view count, each with its channel, duration and publish date. The search endpoint finds videos by query, sorted by views, relevance or recency — sort by views to surface the platform's genuinely most-watched content. The channel endpoint returns one channel's full profile by id: subscriber count, total channel views, video count, when it was created and its category. The video endpoint returns one video's full detail by id, including its description, hashtags, view count and channel. This is the BitChute platform cut — a distinct social/video platform, separate from the YouTube, TikTok, Odysee, Kick and other platform feeds in the catalogue. View and subscriber counts are live. Built for social-monitoring, creator-analytics, media-research and content-discovery tools.

api.oanor.com/bitchute-api

Live data from RUTUBE, the largest Russian video platform with tens of millions of users — served straight from its public web API, no key, nothing cached. Search videos by query and get their view counts, duration and channel; pull one video's full stats (views, duration, publish date, category and author); and list a channel's recent uploads by its person id. A distinct video-platform feed, separate from YouTube, Vimeo, Bilibili, Dailymotion, PeerTube and other video APIs.

api.oanor.com/rutube-api

Live looping-video data from Coub, the social platform built around short, seamlessly looping video clips, served straight from Coub's public API — no key, nothing cached. The explore endpoint returns the trending feed (rising, hot or random coubs across the whole site), each with its title, view, like and recoub counts, duration, channel and tags, plus ready-to-use loop-preview image URLs at several sizes. The tag endpoint returns the newest coubs for a tag — cats, gaming, music — the hashtag feed of Coub. The channel endpoint returns a creator's profile (title, follower and recoub counts) together with their most recent coubs. Every clip comes back cleaned up: the watch URL, the channel handle, the human tags and several preview-image sizes. Everything is live from Coub, nothing stored. This is the looping-video discovery layer for any feed, meme, moodboard, embed or social app. Distinct from YouTube, Vimeo, Dailymotion and other video APIs — this is Coub's looping clips by trend, tag and channel. 3 endpoints, no key on our side.

api.oanor.com/coub-api

Live data for Odysee, the decentralised video platform built on the LBRY blockchain — a censorship-resistant YouTube alternative — served straight from the public Odysee/LBRY backend with no key and nothing cached. The channel endpoint resolves a @channel handle to its title, description, avatar and cover art, the number of videos it has published, the LBC staked on it and its tags and languages: @Odysee resolves to the official channel with 134 published claims. The videos endpoint lists a channel's most recent uploads with the title, description, duration, thumbnail, release date and a ready-to-open watch URL. The search endpoint searches the whole platform for videos by keyword, returned in trending order with their channel, title and link. This is the channel-and-video discovery layer for any app building on decentralised, creator-owned video — read live on-chain from the LBRY network, nothing stored. Distinct from centralised-platform and other video APIs — this is the on-chain Odysee/LBRY catalogue. 4 endpoints.

api.oanor.com/odysee-api

Time-lapse photography maths as an API, computed locally and deterministically — the clip-length, interval and storage numbers a photographer, filmmaker or camera app plans a sequence with. The clip-length endpoint trades a long shoot for a short clip: the frames captured = the shoot duration ÷ the interval, and the clip length = those frames ÷ the playback frame rate — shooting for 60 minutes at one frame every 5 seconds gives 720 frames, and at 24 fps that plays back in 30 seconds, a 120× speed-up. Longer intervals compress time harder but can stutter on fast motion. The interval endpoint works backwards from a target clip: the frames needed = the target clip length × the frame rate, and the interval = the shoot duration ÷ those frames, so a 60-minute shoot for a 20-second clip at 24 fps needs 480 frames, one every 7.5 seconds. The storage endpoint sizes the card and disk: total storage = the frame count × the size of one frame, and because time-lapse shoots full-resolution stills (RAW ~20–30 MB each), 720 RAW frames at 25 MB is about 18 GB for a single 30-second clip — which is why a long lapse eats cards fast. Everything is computed locally and deterministically, so it is instant and private. Ideal for time-lapse and intervalometer apps, photography-planning tools, and production calculators. Pure local computation — no key, no third-party service, instant. 3 compute endpoints. For video bitrate and file size use a bitrate API.

api.oanor.com/timelapse-api

Media, file-size and data-transfer maths as an API. The file-size endpoint relates bitrate, duration and file size: give any two and it computes the third — so you can find the size of a video at a given bitrate and length, the bitrate of a file of known size and length, or how long a file will play. The transfer-time endpoint computes how long a file takes to download or upload over a given bandwidth (with optional protocol overhead), or the bandwidth needed to move it within a target time. The storage endpoint works out how many hours of media at a bitrate, or how many items of a given size, fit in a storage capacity. Bitrates use decimal units (kbps, Mbps, Gbps) and sizes are reported in both decimal (KB/MB/GB/TB) and binary (KiB/MiB/GiB/TiB). Everything is computed locally and deterministically, so it is instant and private. Ideal for video and audio encoding, streaming and CDN planning, storage and backup sizing, and download-time estimates. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is bitrate and transfer maths; for plain byte-unit conversion use a bytes API.

api.oanor.com/bitrate-api

Work with subtitle and caption files — parse, convert and re-sync, entirely locally. The parse endpoint reads SubRip (.srt) or WebVTT (.vtt) text into clean, structured cues — index, start, end (as both HH:MM:SS,mmm timecodes and milliseconds), duration and the cue text (multi-line preserved) — auto-detecting which format you sent. The convert endpoint converts between SRT and WebVTT, getting the details right: the timestamp separator (comma for SRT, dot for WebVTT), adding or removing the WEBVTT header, and renumbering cues. The shift endpoint moves every timestamp by an offset in milliseconds, positive or negative, to fix a track that runs early or late, clamping at zero so nothing goes negative. Everything is computed locally and deterministically, so it is instant and private — your media files never leave the request. Ideal for video and streaming pipelines, caption editors and players, localization and translation workflows, accessibility, and fixing out-of-sync subtitles. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This handles subtitle files; for SMPTE video timecode (HH:MM:SS:FF) use a timecode API.

api.oanor.com/subtitle-api

Aspect-ratio and resize maths on plain dimensions — no image upload needed. The ratio endpoint reduces a width×height to its simplest integer ratio (1920×1080 → 16:9), its decimal value and a common name. The resize endpoint scales a dimension while preserving the ratio: give a new width or a new height and get the other side. The fit endpoint fits a source size into a target box using contain (letterbox) or cover (crop), returning the resulting size, the scale factor and the centering offset. Perfect for responsive layouts and CSS aspect-ratio, video and thumbnail framing, image-grid planning and print sizing. Pure local computation — it works on numbers only and never touches image files. Live, nothing stored. 4 endpoints. Distinct from image processing/resizing (which operates on actual files) and from geometry of shapes.

api.oanor.com/aspectratio-api

Convert SMPTE timecode for video, film and broadcast. Turn a timecode (HH:MM:SS:FF) into an absolute frame number or into real-time seconds, and turn a frame count back into a timecode — at 23.976, 24, 25, 29.97, 30, 50, 59.94 or 60 fps. Crucially it handles drop-frame correctly: at 29.97 and 59.94 fps it drops the right frame numbers each minute (notated with a semicolon, 01:00:00;00) so an hour of timecode lines up with an hour of real time, and it computes real seconds with the exact fractional rate (30000/1001). Perfect for NLE and editing tools, subtitle and caption timing, playout and broadcast automation, and media asset management. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. Distinct from date/time, duration and relative-time tools.

api.oanor.com/timecode-api

Read Vimeo in real time — no login or key needed. Fetch any video's detail (title, description, duration, dimensions, owner, thumbnails, stats), resolve its playable stream URLs (progressive MP4 + HLS) from the public player config, and pull any user's profile, their uploaded videos and the videos they've liked. Browse the videos of any channel, album or group. Users are addressed by Vimeo username or numeric id; every call is live (no cache) and returns the upstream Vimeo shape. 8 endpoints. Built for video discovery, creator analytics and content aggregation on Vimeo. A Vimeo data API — distinct from YouTube, Dailymotion and PeerTube (different platform). No upstream key, no cache.

api.oanor.com/vimeo-api

Read Bilibili — China's largest video community (300M+ users) — in real time, no account or key needed. Full-text search for videos and users; pull the popular feed and the ranking charts; fetch any video's full detail, its statistics (views, likes, coins, favourites, shares), tags, related videos and paginated comments; and look up any user's card (name, avatar, sign, follower/following counts, level). Video lookups accept the BV id; comments take the numeric aid (returned by the video endpoint). Requests are wbi-signed exactly as the Bilibili web client does and routed through a managed proxy, with transient anti-bot responses retried automatically. Every call is live (no cache) and returns the upstream Bilibili shape. 11 endpoints. Built for video discovery, creator and audience analytics and content aggregation on Bilibili. A Bilibili data API — distinct from YouTube/Dailymotion/PeerTube (different platform). No upstream key, no cache.

api.oanor.com/bilibili-api

Read PeerTube — the federated, open-source video network — in real time, with no key. Federated search (powered by SepiaSearch) finds videos, channels and playlists across thousands of PeerTube instances at once. Per instance you can list and sort videos, fetch any video's detail, its comment threads and subtitle/caption tracks, look up any channel or account and their videos, and read the instance config, server statistics and the video-category list. Federated handles (name@instance) resolve transparently, and you can point any per-instance call at a specific server with ?instance=<host> (default framatube.org). Every call is live (no cache) and returns the upstream PeerTube REST shape, paginated with limit + start. 14 endpoints. Built for federated video discovery, creator and channel analytics, and content aggregation. A PeerTube (federated video) data API — distinct from single-platform video APIs like YouTube or Dailymotion. No upstream key, no cache.

api.oanor.com/peertube-api

Read Dailymotion in real time — no login or API key needed. Look up any user (followers, following, total videos and views) and pull their videos, playlists, followers, following and liked videos. Fetch any video's detail (views, duration, likes, comments, tags), its comments, related videos and subtitle tracks, and resolve its playable stream URLs (adaptive HLS) and a direct download link via the public player metadata. Get playlists and their videos, browse channels (categories) and their videos, list all categories, and discover content with full-text video and user search plus trending and most-viewed (featured) feeds. Every call is live (no cache) and returns the upstream Dailymotion Data API shape, paginated with page + limit. 22 endpoints — broader than the typical Dailymotion wrapper. Built for video discovery, creator and audience analytics, content aggregation and media back-ends. A Dailymotion data API — distinct from the YouTube API (different platform). No upstream key, no cache.

api.oanor.com/dailymotion-api

The Internet Archive as an API — the non-profit digital library of over 40 million freely accessible items: books and texts, audio and live-music concerts, films and video, software, images and archived web pages. Search the entire archive by keyword with full Lucene field syntax (by creator, title, subject, collection and more), filter by media type (texts, audio, movies, image, software, web, live concerts) and sort by downloads, date or trending popularity, getting each item's identifier, title, creator, media type, year, download count and collections; read an item's full metadata including its description, creators, subjects, language, collections, publisher, license, dates and total size; list an item's downloadable files with their format, size, length and a direct download URL; and look up the closest Wayback Machine snapshot of any web page — the archived flag, the snapshot date and HTTP status, and the web.archive.org link, optionally near a target timestamp. Ideal for research, digital preservation, media discovery, dataset building, link-rot recovery and apps that surface public-domain and openly-licensed culture. Data from the Internet Archive (archive.org).

api.oanor.com/archive-api