# Kite vs UXKIN (slim)

> UXKIN scores 57 (C) to Kite's 47 (D) for design components. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/kite-new-vs-uxkin-agent.md (~5,300 tokens) · this version ~3,680 tokens · JSON https://www.anchorterminal.com/compare/kite-new-vs-uxkin-agent.json · canonical https://www.anchorterminal.com/compare/kite-new-vs-uxkin-agent
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-02
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

UXKIN scores 57 (C) on agent readiness against Kite's 47 (D), and leads in 5 of 7 scored categories. Kite leads on payments & pricing. Both do design components.

- Kite: D 47, rank #1039 of 1268 · https://www.anchorterminal.com/tools/kite-new.min.md
- UXKIN: C 57, rank #725 of 1268 · https://www.anchorterminal.com/tools/uxkin-agent.min.md
- Kite, good for Agents that make banners, social posts, landing pages and screens for a team that will edit and comment on them in a shared file, drawing in HTML and CSS against the team's design system and picking up changes from @-mention comments, without a desktop app or browser tab kept open. Ahead on Payments & pricing, 30 against 12. Also Free to start without a card.
- UXKIN, good for A coding agent doing front-end work that needs real examples of a flow or a website's colours and type before it builds. Ahead on Reliability, 40 against 33; Schema & documentation, 74 against 62; Agent ergonomics, 71 against 44; Security & auth, 68 against 50; Transparency & trust, 62 against 44.

| Category | Kite | UXKIN |
| --- | --- | --- |
| Reliability (16%) | 33 | 40 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 62 | 74 |
| Agent ergonomics (13%) | 44 | 71 |
| Security & auth (14%) | 50 | 68 |
| Payments & pricing (10%) | 30 | 12 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 78 | 76 |
| Transparency & trust (7%) | 44 | 62 |

| Fact (where they differ) | Kite | UXKIN |
| --- | --- | --- |
| Kind | Platform | MCP server |
| Vendor | Kite | UXKIN |
| Hosted endpoint | `https://kite.new/api/mcp` | `https://uxkin.com/mcp` |
| Transports | Streamable HTTP | HTTP |
| Pricing | Freemium | Paid |
| Licence | Proprietary hosted service under Kite's terms of use (updated 8 September 2026). No source is published; the only public code is an MIT plugin manifest repository (itsloukman/kite-agent-plugins) that points agents at the hosted server | Proprietary hosted service under UXKIN's terms of service (7 October 2026). The skills, plugins and configuration in uxkin/agent are MIT, copyright 2026 UXKIN. The screens in the library belong to the products they show |
| Tools exposed | 59 | 5 |
| llms.txt | yes | no |
| MCP registry | `new.kite/kite` | `io.github.uxkin/uxkin` |
| Last release | 2026-11-01 | 2026-10-16 |
| Terms last updated | couldn't be read | 2026-10-07 |
| Privacy policy last updated | 2026-10-14 | 2026-10-07 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |

Why the edge:
- Agent ergonomics, UXKIN +27: Kite 44 (MCP reading. 59 tools (61 through the Mac app) with no toolsets, read-only subset or dynamic loading; guide_read moves the long instructions out of tool descriptions into on-demand reads, but tools/list still carries 59 definitions (5 of 25). Output is sized by asking for one page in file_outline, one node in layer_source and layer_render, layer_search by name, words or type, file_search over content, comment_list with unread_only and include_resolved, request_list per file; file_list is newest-first with no documented paging (14 of 20). OAuth errors are documented with recovery steps, web_capture says when a page was cut short and an unknown shader base is refused, but a picture Kite cannot fetch is left out silently and no tool error shape is documented (9 of 20). No readOnlyHint or destructiveHint documented and no idempotency keys; version_save before a big change and version_restore undoable both ways, file_archive reversible and no permanent delete, layer_draw's replace argument for swapping a node (7 of 20). Few required parameters (file_new takes a title, layer_draw a file and HTML, finish_working a file), defaults in the drawing guide, and an MIT plugin repository for Claude Code, Codex, Cursor and Grok Bot; no SDK, since the vendor points at the official MCP SDKs (9 of 15). 5+14+9+7+9 = 44.); UXKIN 71 (Five compact tools in a server card of about 11 KB with prompts and output schemas (25 of 25). `limit` sizes results and screenshots are off by default through `include_images`, with no paging or offset (12 of 20). No error codes or messages are documented apart from a 401 that names the resource metadata (4 of 20). Every tool sets readOnlyHint and idempotentHint, and nothing writes (20 of 20). Each tool has at most one required parameter. No SDK, which an MCP server doesn't need, so 10 of 15. Total 71.)
- Security & auth, UXKIN +18: Kite 50 (OAuth 2.1 with the authorization code flow, PKCE S256, dynamic registration of public clients, 7-day access tokens, 90-day refresh tokens that rotate on every use and revoke the connection if replayed, a revocation endpoint, bearer in the header only, and per-connection disconnect in Settings; one scope, pages, with the agent working under the user's full rights, and API keys that are per tool and revocable but unscoped (24 of 30). Least privilege comes from the file, not the token. A file shared view-only lets an agent read and comment but not draw, comment and download settings apply to agents, an agent cannot delete a file for good or touch the account, workspace or people, and each Mac-run request reaches only its file; no read-only mode on the hosted server and no confirmation for layer_remove, page_remove or version_restore (12 of 20). Comments, skills written by any editor, captured web pages and Figma pastes reach the model. The skill says a file's skills apply to that file only and never to sharing or people, and the Mac docs keep Agents Run Any Tool off by default because an agent reads comments and web pages and one could try to trick it; no guidance for the hosted server's own tools (8 of 15). Settings, Agents lists each connected app and key with when it connected and was last used, the board shows the agent's name while it works, and version history records agent saves; no per-call log for the operator (6 of 15). No security.txt (404), disclosure policy, bug bounty, SOC 2 or ISO 27001; SSO and SAML on Team (0 of 20). 24+12+8+6+0 = 50.); UXKIN 68 (OAuth 2.1 on UXKIN's own authorisation server, with PKCE S256, dynamic client registration and refresh tokens, and one scope `uxkin` for a read-only service. The fallback agent token is stored hashed, can be reset at once and goes in a header, never a query string (25 of 30). Every tool is read-only, so an agent can't change the account or the project (18 of 20). Results carry text and DESIGN.md content from other products, and both skills tell the agent to treat tool results as data and not follow instructions in them (10 of 15). Connected apps show when they were added and last used, and tokens record last use, with no per-call log (5 of 15). security.txt is valid until 1 October 2027, SECURITY.md promises a reply in three working days and GitHub private reporting is on. No bounty or certification (10 of 20). Total 68.)
- Payments & pricing, Kite +18: Kite 30 (No x402, MPP or L402 in the docs, llms.txt, auth.md, the pricing pages or the terms (0). Plan prices are public and machine-readable at pricing.md, Free, Pro $20 per editor a month or $16 yearly, Team $35 or $28, with no per-call or per-action price since agent actions are counted on Free and unlimited on Pro (10 of 20). Free plan with 3 files and 200 agent actions a day, sign-up by emailed link or Google, no card mentioned anywhere (20). An agent can register itself as an OAuth client, but a person must sign up in a browser and click Allow, or make an API key in Settings (0). 0+10+20+0 = 30.); UXKIN 12 (No machine payment protocol (0 of 40). Plan prices are public, $9.99 a month or $99 once, with no per-call price (10 of 20). Searching needs a plan and no trial for the server was found. The skills are free, but they aren't the surface graded here (0 of 20). A person signs up and pays through Polar in a browser. Clients can register themselves with the authorisation server, which earns 2 (2 of 20). Total 12.)
- Transparency & trust, UXKIN +18: Kite 44 (Closed service. The terms of use (8 September 2026) run to about 200 words on content, prohibited use, links, availability and changes and name no legal entity, address or governing law, so the contracting party is unknown (8 of 30). The privacy policy (14 October 2026) names eight services, says files are not read, trained on or sold, discloses masked session replays and error replays, gives the agent token's 7-day life renewable to 90 days (matching auth.md and the integration page), the 30-day purge of deleted pages and the one-month deletion of a closed account's files, and the Figma token's handling; no DPA and no retention period for logs beyond the providers' own (20 of 30). No deprecation policy or dated notices; the terms promise email or in-app notice of changes that matter and the changelog dates additions, not removals (4 of 20). Telemetry (PostHog, Sentry) is disclosed with what it excludes and no opt-out beyond product-news emails; service locations are given only for PostHog and Sentry (US) (10 of 20). 8+20+4+10 = 42.); UXKIN 62 (The service is closed and the skills and plugins are MIT. The terms are clear on use, refunds and liability but name only 'UXKIN', with no legal entity, address or state, so it's unclear who the contract is with (12 of 30). The privacy policy gives retention for each kind of data, says search words from AI apps aren't stored and agrees with the README. No DPA (24 of 30). No deprecation policy, and the terms allow any part of the service to change or go at any time (0 of 20). Six service providers are named with what each does, with no data locations (14 of 20). Total 50.)
- Schema & documentation, UXKIN +12: Kite 62 (MCP reading, since the MCP server is the only surface an outside agent reaches. No tool input schemas were read. The server card at /.well-known/mcp/server-card.json declares tools without listing them, and llms-full.txt describes every tool in prose with argument names in the skill, so typed inputs are the vendor's to show and were not seen (10 of 25). llms.txt, llms-full.txt, skill.md, auth.md and pricing.md are served as text and Markdown (10). Descriptions say what each tool does and when to use it, such as file_search over file_list when the user describes a file, layer_edit rather than redrawing, never base64 in HTML, never a picture of a design, guide_read's six topics, and the view-only rule (16 of 20). Inputs named in the docs are typed in prose, with enumerations for audience (link, restricted), export formats (svg, react, tailwind, html), sticky colours, shader bases and guide topics, and bounds for videos (100 MB) and fonts (4 MB), but the main write tool takes one HTML string and layer_edit a free CSS object (8 of 15). Worked HTML examples in skill.md, a prompt per client page, and auth.md's 401, 400 and 429 responses; no example tool call or response and no MCP error shape (8 of 15). A dated changelog with 15 entries from 6 October to 1 November 2026 that names agent-facing changes (page, version, comment and export tools on 25 October), server version 1.0.0; no versioned tool surface or deprecation policy (10 of 15). 10+10+16+8+8+10 = 62.); UXKIN 74 (The public server card gives every tool a typed JSON Schema input with `additionalProperties: false` and an output schema (25). No llms.txt (uxkin.com/llms.txt is 404). The skills are served as Markdown at /.well-known/agent-skills/ and the repository has llms-install.md (5 of 10). Tool descriptions say what each returns, how to phrase queries and when to use `get_journey` after a search, with less on when not to call (17 of 20). Inputs carry required fields, defaults and limits (`limit` 1 to 50 and 1 to 25) and no free-form objects (14 of 15). Descriptions and the MCP guide give query examples and a sample result. Error responses aren't documented beyond the 401 (8 of 15). Versions 1.0.0 to 1.3.1 are in the registry and manifests, with no public changelog (5 of 15). Total 74.)
- Reliability, UXKIN +7: Kite 33 (Hosted reading, for the platform and its remote MCP server. No public status page was found. None is linked from the docs or the footer, https://kite.new/status answers 404 and status.kite.new does not resolve (0). No readable incident history, so the floor (5). Limits are published with numbers on the account page, 200 agent actions a day on Free, reset at midnight UTC, unlimited on Pro; 60 new files an hour; 20 comments on one file every 10 minutes; 600 exported layers an hour; 20 keys; file caps of 400 MB and 250,000 layers. auth.md says registration and agent calls are rate-limited without a per-minute figure (12 of 15). 429 is documented in auth.md with 'back off' and no Retry-After, 401 with a refresh-once-then-rediscover rule, and the drawing guide says to edit layers in place rather than redraw; no idempotency key on any write and no safe-retry guidance for layer_draw, so a retried draw adds a second frame (6 of 15). No SLA. The terms (8 September 2026) say Kite is provided as is, uptime is not guaranteed and files may be lost (0). The hosted server carries no beta label and the registry entry is 1.0.0; the product launched on 6 October 2026 and the desktop apps are 0.1.16 (10). 0+5+12+6+0+10 = 33.); UXKIN 40 (Read with the hosted lines, because the surface an agent uses is the MCP server at uxkin.com/mcp. UXKIN runs its own status page with four components (library, sign-in, MCP connection, payments) and 30 days of checks (20). The page lists no incidents, and the MCP connection and sign-in show 98.1 per cent of checks passed over 30 days, which leaves failed checks unexplained and no 90-day record (10 of 30). No rate limit with numbers is published. The terms say agent access may be limited (0 of 15). No 429, Retry-After or backoff guidance was found, though every tool is read-only (0 of 15). No SLA (0 of 10). The server carries no beta or preview label (10). Total 40.)