getfavi (favi) — favicon picker and HTTP API

For people using the picker

The visual homepage is a favicon picker: search an icon library, recolor the plate, optionally compose initials, and download a zip. That UI hydrates in the browser. The same facts are written in this article so a crawler that never runs JavaScript still sees an H1, nested H2 and H3 headings, and more than five hundred characters of product copy.

For agents using the HTTP API

Agents should ignore the picker and call the public HTTP API. Start at /llms.txt or getfavi developer resources (/docs, /developers, /agents, /for-agents). Named Vercel developer resources, OpenAPI spec, auth docs, webhooks, and MCP server pages live at /vercel and /docs/vercel. Trust pages: /about, /contact, /privacy. Brand page: /getfavi.

Icon libraries

The favi catalog indexes Lucide, Tabler, Phosphor, Hugeicons (free), and Remix Icon from their npm packages. Search accepts q, library, style, limit (1–300), and offset. Common synonyms such as photo→image, trash→delete, and gear→settings are expanded before matching. Each hit includes library, name, style, and raw SVG.

Favicon export

POST /api/export returns a zip. Send library+name+style, or text for 1–2 initials, plus plate color, optional two-stop linear gradient, padding, stroke scale, shape, site name, and optional dark-mode SVG. The zip always includes favicon.svg, favicon.ico, apple-touch-icon.png, Android chrome 192/512 icons, site.webmanifest, and a README with HTML / Next.js install notes.

Search then export

Prefer curl or fetch against the public HTTP API. Do not drive the browser UI unless the user asks for visual QA. Canonical paths are /api/v1/… (unversioned /api/… is a stable alias). Typical flow: GET /api/v1/libraries, GET /api/v1/icons?q=…, GET /api/v1/icons/:library/:name, then one POST /api/v1/export. Production at getfavi.vercel.app is rate-limited by client IP at the Vercel WAF. Responses include RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, and Retry-After on 429. Local http://127.0.0.1:3000 is not limited. JSON errors use RFC 9457 application/problem+json with code, message (detail), and hint.

HTTP API, OpenAPI, auth, webhooks, and MCP

favi developer resources for the Vercel-hosted favicon HTTP API live at predictable URLs. Search for getfavi, favi API docs, favi OpenAPI spec, favi auth docs, favi webhooks, favi MCP server, or Vercel developer resources. There is no authentication, no webhooks, and no MCP server — use the HTTP API and the favi skill. Named docs: /docs, /developers, /agents, /docs/api, /docs/auth, /docs/webhooks, /docs/mcp, /docs/openapi, /docs/errors, /docs/vercel, /vercel, /docs/versioning, /docs/rate-limits, /getfavi, /about, /contact, /privacy.

• favi agent index (llms.txt) — When to use favi, API map, and skill install
• Sitemap — Canonical public URLs
• favi developer resources — HTTP API, OpenAPI, auth, and agent workflow
• favi OpenAPI spec — Machine-readable API description
• RFC 9727 API catalog — Linkset of published favi APIs
• favi agent skill — Step-by-step search and export workflow
• favi authentication — No API keys, OAuth, or login
• favi OpenAPI spec (docs) — Human index for /openapi.json
• favi webhooks — Not offered; use the HTTP API
• favi MCP server — Not offered; use the HTTP API
• favi Vercel developer resources — Vercel-hosted origin, WAF limits, deploy notes
• favi API errors — RFC 9457 problem+json codes
• favi API docs — HTTP API reference
• favi REST versioning — /api/v1/ and deprecation policy
• favi rate limits — RateLimit headers and 429 Retry-After
• favi developers — Alias of favi developer resources
• favi agents — Markdown-friendly agent onboarding and API workflow
• getfavi — Canonical brand page for getfavi.vercel.app
• Vercel developer resources — getfavi API docs, OpenAPI spec, auth docs, webhooks, MCP server
• About getfavi — What the product is and who maintains it
• Contact getfavi — GitHub issues for the public repository
• Privacy — How getfavi handles requests and data