Retrieve Pexels curated photos and popular videos feeds for a rotating homepage or featured-content section
domain: api.pexels.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with the 'Authorization: YOUR_API_KEY' header as with search endpoints
Call GET https://api.pexels.com/v1/curated to get a continually updated list of hand-picked photos, using page/per_page for pagination
Call GET https://api.pexels.com/v1/videos/popular for trending videos, optionally filtering with min_width and min_height to enforce a minimum resolution
Cache results client-side between refresh cycles since curated content changes over time rather than per-request
Combine with GET https://api.pexels.com/v1/photos/:id or /v1/videos/videos/:id to fetch full detail for a single item selected from the feed
Known gotchas
The curated and popular endpoints still count against the same monthly/hourly rate limit as search calls, so polling them frequently can exhaust quota
The single-video detail endpoint path is /v1/videos/videos/:id (videos appears twice), which is easy to mistype as /v1/videos/:id
There is no query parameter on curated/popular endpoints; filtering must be done client-side after retrieval, or by switching to the search endpoint instead
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?