UnifAPI API docs, OpenAPI, auth, MCP, and agent resources
A crawlable entry point for builders and AI agents looking for the UnifAPI developer surface by name. Start here for direct HTTP access, MCP setup, OAuth metadata, registry manifests, and Skill source.
Direct HTTP
Call public-data routes with a workspace API key. Responses use one JSON envelope with data, pagination, billing, and typed errors.
GET /x/tweets/search/recent?q=unifapi HTTP/1.1
Host: api.unifapi.com
Authorization: Bearer $UNIFAPI_API_KEYMCP
Give an agent live public-data tools through the hosted Streamable HTTP MCP server. OAuth is the recommended auth path.
Connector URL:
https://mcp.unifapi.com
Tools:
list_operations
get_operation
call_apiAgent auth
Agents should read auth.md and protected-resource metadata before asking a user for secrets.
GET /auth.md
GET https://mcp.unifapi.com/.well-known/oauth-protected-resourceEverything an agent should be able to find
These resources include the product name in titles and headings so direct-name searches for UnifAPI developer resources have a single, explicit landing page.
TypeScript SDK package
Use @unifapi/sdk for direct HTTP integrations when an agent workflow moves into product code, scheduled monitoring, or backend automation.
pnpm add @unifapi/sdkProduction host
Direct HTTP calls use https://api.unifapi.com. Routes follow the generated OpenAPI operation set. MCP clients should prefer https://mcp.unifapi.com.