Edge caching
Assets are cached close to your users. Cache-key rules, purge-by-tag and stale-while-revalidate are on by default.
Checking status…
Cache, sign and stream images, audio and video from a global edge network — over a plain HTTP API.
Serving — media requests a day across — edge locations.
# pull a transcoded clip through the edge cache
curl -sSL "https://content.megaval244.online/video/download?id=8f21c&fmt=720p" \
-H "Authorization: Bearer $MEGAVAL_KEY" \
-o clip.mp4
HTTP/2 200
content-type: video/mp4
x-cache: HIT x-edge: fra1 age: 142
Everything you need to store, protect and ship large files without running your own delivery stack.
Assets are cached close to your users. Cache-key rules, purge-by-tag and stale-while-revalidate are on by default.
Time-limited, token-signed links keep private media private. Scope access per file, per IP or per referrer.
Upload once, deliver many. On-the-fly transcoding to 360p–2160p and HLS packaging from a single source file.
Anycast routing sends each request to the nearest healthy edge. Automatic failover between points of presence.
Send a live call against the edge and see the response. No account needed for the sandbox.
Requests are rate-limited to 30/min per IP.
// Press "Send request" to call the sandbox edge.
Requests are answered from the nearest edge. When one falls behind, traffic reroutes in milliseconds.
Authenticate, upload, deliver. The API speaks plain HTTP — no SDK required.
MEGAVAL_KEY.POST /v1/assets with your file. You get back an asset id./video/download?id=…&fmt=… and the edge streams the cached result.# 1 — upload a source file
curl -X POST "https://content.megaval244.online/v1/assets" \
-H "Authorization: Bearer $MEGAVAL_KEY" \
-F "file=@intro.mov"
→ { "id": "8f21c", "status": "processing" }
# 2 — check health
curl "https://content.megaval244.online/v1/health"
→ { "status": "ok", "region": "fra1" }
# 3 — deliver, cached at the edge
GET /video/download?id=8f21c&fmt=720p