API Reference

The API reference is the data layer behind UnifAPI Skills. Agents usually call these operations through MCP; developers can call the same live public-data endpoints over HTTP when productizing a workflow.

• Browser — Headless browser rendering.
• Events — Live events search.
• GEO — geo endpoints
• Hacker News — Public-data Hacker News endpoints.
• Hotels — Live hotel search and detail.
• Instagram — Public-data Instagram endpoints.
• LinkedIn — Public-data LinkedIn endpoints.
• Local Finder — Live Local Finder search — the expanded local-pack listing.
• Maps — Live local business search.
• News — Live news search.
• Reddit — Public-data Reddit endpoints (APP surface).
• SEO — Live SEO optimization evidence endpoints.
• Threads — Public-data Threads endpoints (Web surface).
• TikTok — Public-data TikTok endpoints.
• Twitter / X — Public-data Twitter / X endpoints.
• YouTube — Public-data YouTube endpoints (Web surface).

How To Read This Reference

Use this section as the contract map for UnifAPI's live public-data layer. The API catalog is generated from route metadata in the gateway, then published here as human-readable documentation and as a machine-readable OpenAPI 3.1 file. That means the paths, parameters, response shapes, and error vocabulary here are the same surface an MCP-capable agent discovers before it calls data.

The practical workflow is simple: start from the Skill or product task, pick the platform records that carry the evidence, inspect the operation page for required identifiers, then call the endpoint through MCP or direct HTTP. The response envelope stays consistent across platforms, so an agent can combine a Reddit thread, a YouTube channel, an X profile, and a LinkedIn company record without learning four separate result formats.

Shared Guarantees

• Public-data scope only: endpoints are designed for records visible on public platform surfaces, not private account actions.
• One auth model: HTTP callers use Authorization: Bearer <key>; MCP callers authenticate through the hosted UnifAPI server.
• One billing unit: usage is counted on returned records so exploratory agent runs and production integrations can estimate cost from the same metadata.
• One error envelope: validation failures, upstream misses, rate limits, and billing states use the shared error vocabulary documented in Errors.

All live operations share the gateway conventions:

• Auth via Authorization: Bearer <key> with a UnifAPI API key; provider credentials are managed by UnifAPI.
• Successful responses use { request_id, data, pagination?, billing }; list operations return arrays in data plus opaque cursor pagination.
• Errors use the closed-vocabulary { error: { type, message, request_id?, issues?, billing? } } envelope — see Errors.

For agent workflows, start with Skills and MCP integration. The machine-readable spec lives at /openapi.json (single source of truth).