UApiPro
UApiPro is a free public-API platform with 100+ stable REST endpoints.
The free tier needs no signup, every endpoint shares one OpenAPI spec and one MCP server, and the platform is built to be called natively by ChatGPT, Claude, Cursor, and other AI agents.
UApiPro is an open public-API platform aggregating 100+ REST endpoints across networking utilities (IP geolocation, DNS, HTTP header inspection), image processing (QR codes, OCR, image hosting), text utilities (hashing, AES, Base64, Markdown to PDF), translation, federated search, social-platform lookups (QQ, Bilibili, Weibo), weather, randomness, and game-server probes. Everything ships under a single domain, a single OpenAPI 3.1 document, and a single rate-limit + error contract.
Why developers choose UApiPro
- Free tier with zero friction: Utility endpoints (IP info, hashing, Base64, AES, QR code, world clock, random images, image metadata, etc.) require no signup and no API key. The free tier is rate-limited only against abuse, not by daily quota.
- One API surface: All 100+ endpoints live under https://uapis.cn/api/v1/, return application/json, expose X-RateLimit-Limit / X-RateLimit-Remaining / X-RateLimit-Reset / Retry-After response headers, and emit a uniform {code, success, error, request_id} error envelope on 4xx and 5xx.
- Built for AI agents: OpenAPI 3.1, MCP server (/mcp), NLWeb /ask, A2A agent-card, and ai-plugin manifest all live on the same domain. Agents discover the full capability set in a single fetch instead of crawling several websites.
- China-localized: Chinese docs, Chinese ticket support, Beijing-time on-call, and unique endpoints that cover the Chinese internet (QQ profiles, Bilibili profiles, hot boards, mainland weather, mainland translation models). Public-API platforms hosted overseas cannot reproduce this surface.
Agent / MCP integration paths
Agent platforms can pick any of the discovery paths below. All of them are public specifications - no sales motion required:
- MCP (Model Context Protocol): Streamable HTTP transport at https://uapis.cn/mcp. Supports initialize, tools/list, and tools/call. Every REST endpoint maps to one MCP tool with a snake_case name and a description that includes the upstream URL and parameter list. Server card at /.well-known/mcp/server-card.json.
- NLWeb /ask: POST https://uapis.cn/ask with a natural-language query and receive ranked endpoint candidates ({_meta, results[]}). Send Accept: text/event-stream for SSE streaming with start, result, and complete events.
- OpenAI plugin / function calling: /.well-known/ai-plugin.json exposes the legacy OpenAI plugin manifest and a link to the OpenAPI document so a Custom GPT, Apps SDK build, or vanilla function-calling loop can import the tool surface in one click.
- A2A agent card: /.well-known/agent-card.json describes capabilities, contact endpoints, and skills under the agent-to-agent protocol.
- Web Bot Auth (RFC 9421): /.well-known/http-message-signatures-directory advertises Ed25519 verification keys so agents can sign outbound requests with HTTP Message Signatures.
How it compares
Key agent-era differences between UApiPro and other public-API platforms:
- Versus RapidAPI: RapidAPI requires creating an account, subscribing to each vendor, and integrating that vendor's SDK and rate-limit policy. Automation is painful. UApiPro's free tier needs no signup; every endpoint shares one OpenAPI document and one MCP service, so an agent can pick up all 92+ tools in a single handshake.
- Versus API Ninjas: API Ninjas focuses on English-language datasets and does not cover Chinese-internet sources. UApiPro provides QQ profiles, Bilibili profiles, Weibo feeds, mainland-China hot boards, local weather, local translation models, and zh-CN content detection out of the box, with credit-based pricing instead of per-endpoint subscriptions.
- Versus Public APIs (the directory): Public APIs is a catalog of third-party endpoints; you still sign up with each provider. UApiPro is itself the data plane - the URL the docs describe is the URL you call, with no aggregator hop in between.
- Versus Postman API Network: Postman is documentation and collaboration; the runtime is still hosted by each provider. UApiPro keeps documentation, console, runtime, and MCP service inside the same domain so agents avoid cross-origin Auth, CORS, and log propagation issues.
Frequently asked questions
- Are there call limits on the free tier?
- The free tier has anti-abuse limits but no daily quota; everyday use is unaffected. The exact thresholds adjust with platform capacity - see https://uapis.cn/docs/getting-started/fair-use-and-rate-limiting for current values.
- How are paid endpoints priced?
- Paid endpoints debit credits (~1 credit per call). Pack pricing and per-endpoint costs are at https://uapis.cn/pricing, plus a machine-readable copy at https://uapis.cn/pricing.md.
- How do I get an API key?
- Register an email at https://uapis.cn/console and self-issue a key. There is no manual review. Pass the key in the X-API-Key request header; never put it in URL query parameters.
- What should I do on HTTP 429?
- Read Retry-After (seconds) and back off. We recommend exponential backoff with at most three retries. Slow down proactively when X-RateLimit-Remaining drops below ~10% of X-RateLimit-Limit.
- How do I report abuse or security issues?
- Email security@uapis.cn with the issue, repro steps, and request_id. Regular tickets go to https://uapis.cn/help.
Contact
Operations runs out of China with 24/7 endpoint monitoring. Full legal entity, privacy policy, security disclosure, and press contact are linked below: