UnifAPI Docs

UnifAPI Docs

Developer docs for the UnifAPI public data API gateway, including quickstart, authentication, canonical schemas, errors, rate limits, OpenAPI, and MCP.

UnifAPI exposes a single, agent-friendly HTTP API for public data from social platforms, search, news, and the open web. Developers use one key, one base URL, one OpenAPI spec, and one error model instead of integrating every upstream provider separately.

What is UnifAPI?

UnifAPI is a unified public data API gateway for AI agents and developer applications. It normalizes upstream APIs behind consistent authentication, canonical response schemas, cursor pagination, structured errors, OpenAPI discovery, and MCP-compatible tool access.

Who should use UnifAPI?

Use UnifAPI when your agent or application needs public web data without building a separate integration for every provider. Common use cases include social listening, trend discovery, creator research, market research, competitive intelligence, and agent tools that need callable public-data capabilities.

How is UnifAPI different from an API marketplace?

API marketplaces list many unrelated providers with different auth patterns, schemas, pagination rules, errors, and billing models. UnifAPI curates and normalizes the public-data subset so each endpoint behaves like part of one product surface.

Get started

Quickstart

Make your first call in under two minutes.

Authentication

API keys and rotation.

API reference

Every endpoint, auto-generated from the OpenAPI spec.

MCP server

Connect Claude, Cursor, and other MCP clients.

How it works

One key, one base URL. Sign up, copy your API key, point your client at https://api.unifapi.com.

Call any provider. Each provider has its own path prefix (e.g. /tiktok) but every operation shares the same auth, the same canonical schemas, and the same error envelope.

Pay per record. $0.001 per record. No tiers, no minimums, no commitment.

Why UnifAPI

Pricing is a flat $0.001 per record across every endpoint. No subscription tiers, no overage cliffs.

  • Agent-native. Every endpoint returns canonical objects with stable field names. Errors share one closed-vocabulary envelope ({ error: { type, message, request_id?, issues? } }).
  • Discoverable. /openapi.json, /llms.txt, /.well-known/agent-card.json are first-class.
  • Portable. Drop-in replacement for direct provider calls — no SDK lock-in.

Quickstart

Make your first call to UnifAPI in under two minutes.

On this page

What is UnifAPI?Who should use UnifAPI?How is UnifAPI different from an API marketplace?Get startedHow it worksWhy UnifAPI