How do I install the Unifapi skill?

Run npx skillmds@latest add zuoguyoupan2023/unifapi in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Unifapi safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Unifapi?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Unifapi free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Unifapi?

zuoguyoupan2023 (@zuoguyoupan2023) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Unifapi by zuoguyoupan2023 — Agent Skill

Name: Unifapi
Rating: 4.2 (5 reviews)
Author: zuoguyoupan2023

Unifapi

Use when working with UnifAPI public-data APIs or the UnifAPI MCP server: connecting OAuth MCP clients, discovering operations, calling social/search/scrape/news APIs, troubleshooting UnifAPI auth, or deciding between MCP OAuth and API-key fallback. Always use before asking for UnifAPI credentials or calling UnifAPI tools.

File contents

UnifAPI

Default Path: OAuth MCP

Use the hosted MCP server first:

https://mcp.unifapi.com

Let the MCP client complete browser OAuth when it asks. Do not ask the user to paste OAuth tokens into chat. Do not ask for an API key unless the client cannot complete OAuth and the task genuinely needs live UnifAPI calls.

Read references/mcp.md for OAuth protected-resource metadata, client setup, and the API-key fallback.

References

references/mcp.md - OAuth protected-resource metadata, client setup, and API-key fallback.
references/public-data.md - when UnifAPI is the right data boundary.
references/http-api.md - direct HTTP integration guidance.
references/twitter-x.md - current X/Twitter route map and response shapes.

Agent Workflow

Name the artifact the user wants: ranked table, creator brief, social listening report, market scan, SERP summary, scrape summary, or another decision output.
Use MCP tools such as list_operations and get_operation to find exact public-data operations and schemas.
Call live APIs through call_api only for evidence you need.
Return an artifact, not a raw dump. Include evidence, assumptions, confidence, operations used, and billing metadata when available.
If a live call fails with 401 unauthorized, restart OAuth or use the documented API-key fallback if OAuth is unavailable.

Public-Data Boundary

UnifAPI is for public data: social profiles and posts, search results, trends, web scrape outputs, news, comments, communities, videos, and public company or creator signals.

OAuth authorizes the UnifAPI workspace and credit balance. It does not grant access to a user's private Twitter/X, Google, CRM, email, or SaaS accounts. Use a connector platform when the workflow needs private user-authorized SaaS data.

Read references/public-data.md when choosing whether UnifAPI is the right data path.

Direct HTTP

Prefer MCP for agent workflows. Use direct HTTP only when the user is building an integration, running scripts, or using a client that cannot call MCP tools.

Read references/http-api.md before writing direct HTTP calls.

---name: unifapidescription: Use when working with UnifAPI public-data APIs or the UnifAPI MCP server: connecting OAuth MCP clients, discovering operations, calling social/search/scrape/news APIs, troubleshooting UnifAPI auth, or deciding between MCP OAuth and API-key fallback. Always use before asking for UnifAPI credentials or calling UnifAPI tools.license: MIT---# UnifAPI## Default Path: OAuth MCPUse the hosted MCP server first:```texthttps://mcp.unifapi.com```Let the MCP client complete browser OAuth when it asks. Do not ask the user to paste OAuth tokens into chat. Do not ask for an API key unless the client cannot complete OAuth and the task genuinely needs live UnifAPI calls.Read [references/mcp.md](references/mcp.md) for OAuth protected-resource metadata, client setup, and the API-key fallback.## References- [references/mcp.md](references/mcp.md) - OAuth protected-resource metadata, client setup, and API-key fallback.- [references/public-data.md](references/public-data.md) - when UnifAPI is the right data boundary.- [references/http-api.md](references/http-api.md) - direct HTTP integration guidance.- [references/twitter-x.md](references/twitter-x.md) - current X/Twitter route map and response shapes.## Agent Workflow1. Name the artifact the user wants: ranked table, creator brief, social listening report, market scan, SERP summary, scrape summary, or another decision output.2. Use MCP tools such as `list_operations` and `get_operation` to find exact public-data operations and schemas.3. Call live APIs through `call_api` only for evidence you need.4. Return an artifact, not a raw dump. Include evidence, assumptions, confidence, operations used, and billing metadata when available.5. If a live call fails with `401 unauthorized`, restart OAuth or use the documented API-key fallback if OAuth is unavailable.## Public-Data BoundaryUnifAPI is for public data: social profiles and posts, search results, trends, web scrape outputs, news, comments, communities, videos, and public company or creator signals.OAuth authorizes the UnifAPI workspace and credit balance. It does not grant access to a user's private Twitter/X, Google, CRM, email, or SaaS accounts. Use a connector platform when the workflow needs private user-authorized SaaS data.Read [references/public-data.md](references/public-data.md) when choosing whether UnifAPI is the right data path.## Direct HTTPPrefer MCP for agent workflows. Use direct HTTP only when the user is building an integration, running scripts, or using a client that cannot call MCP tools.Read [references/http-api.md](references/http-api.md) before writing direct HTTP calls.

Frequently asked questions