Pugi is an AI product team in your chat. Describe a business in a few sentences and Pugi plans, designs, builds and checks a real website, shows a live preview, and puts it live on its own address. Ask for changes in plain words. Pugi also draws four whole logos for a business name with a brand kit, checks any public website or GitHub repository for leaked keys, vulnerable dependencies and risky code, and helps you start from public site templates. Sign in with a Pugi account (OAuth).
Scored across 15 tools
The build_app vs build_site split is explicitly and carefully delineated (interactive app vs marketing site), and edit/publish/job_status each target a distinct action. The logo trio (make_logo/refine_logo/select_logo) is separated by lifecycle stage, though an agent must read carefully to know that refine_logo is not 'editing an uploaded image' and that select_logo belongs to the same flow. scan_repo/scan_url and get_balance/buy_credits_link are cleanly distinct.
Predominantly verb_noun snake_case (build_app, build_site, make_logo, refine_logo, select_logo, scan_repo, scan_url, catalog_search, job_status, publish_status). Minor deviations: bare verbs 'edit' and 'publish' break the pattern, and the verbs are heterogeneous (get/buy/make/refine/select) though still semantically readable. No style mixing like camelCase.
15 tools sits at the top of the healthy range but each maps to a real workflow step: discovery, build, edit, logo pipeline, publish, status, billing, and security scans. Nothing appears redundant enough to cut, though the three-step logo flow accounts for a chunk of the surface.
The main lifecycle is covered end to end: discover (catalog_search), build (build_app/build_site), change (edit), check (job_status), publish (publish/publish_status), plus branding, billing, and scanning. Notable gaps: no way to delete or unpublish a project, and no explicit tool to stop a running job despite job_status referencing a 'stopped' state, leaving agents at a dead end for those requests.
Use this when the person wants something people use: upload a photo, generate or transform pictures with AI, accounts or sign-in, saved data, a tool, a calculator, a game, bookings, a dashboard. Pass their request as they said it; never turn it into a landing page. An app that makes pictures with AI asks for the owner's own image-AI key; it never fakes results. Pass the customer's brief in the customer's own words; do not add features the customer did not ask for (no invented sign-up, accounts, subscriptions or payments). When it is built Pugi checks it for security issues, and publish waits for that check. An app that needs a server or a database moves onto Pugi's servers on its own; the person stays in this chat. In hosts that render the build card (MCP Apps or ChatGPT widget), the card tracks progress automatically: do not poll job_status. In hosts without a build card (Claude Code or API), call job_status with the job_id until the job is finished, stopped or failed. Do not use for a simple website (use build_site) or to change an app already built here (use edit).
Inputs: brief (required), idempotency_key (required), pick, theme, +9 more.
For a business's marketing site only, for example "a site for my bakery". Something people use (upload a photo, AI pictures, sign-in, a tool, a game) is an app: use build_app, never a landing page. Pass the customer's brief in the customer's own words; do not add features the customer did not ask for (no invented sign-up, accounts, subscriptions or payments). First call: nothing starts, a summary returns; after a yes, call with its action.arguments. In hosts that render the build card (MCP Apps or ChatGPT widget), the card tracks progress automatically: do not poll job_status. In hosts without a build card (Claude Code or API), call job_status with the job_id until the job is finished, stopped or failed. Not for changing a built site (use edit).
Inputs: brief (required), idempotency_key (required), pick, theme, +10 more.
Get a link to add credit.
Inputs: amount_usd.
Use this when the person wants ideas or a starting point for a site or app, for example "show me bakery websites". Free. Returns sites and apps people built with Pugi; if none matches it returns the nearest category and says so (match: nearest_category), so tell the person they are the nearest. Each has a brief and the tool to start a similar project in this chat (build_with). It does not copy anyone's code.
Inputs: tags, limit, query, category.
Use this when the person asks to change a Pugi website or app from this conversation: "change the headline", "make the buttons green", "add a menu page". Pass the change in the customer's own words; do not add features the customer did not ask for (no invented sign-up, accounts, subscriptions or payments). Pass the job_id or project_id from the last build result. Do not use to start a new site or app. In hosts that render the build card (MCP Apps or ChatGPT widget), the card tracks progress automatically: do not poll job_status. In hosts without a build card (Claude Code or API), call job_status with the job_id until the job is finished, stopped or failed.
Inputs: instruction (required), idempotency_key (required), pick, theme, +11 more.
Use this when the person asks about their Pugi plan, credit or what they spent today. Free and read-only.
Inputs: no named parameters.
Use this when the person asks how a Pugi build or change is going, or for a fresh preview link. In hosts that render the build card (MCP Apps or ChatGPT widget), the card tracks progress automatically: do not poll job_status. In hosts without a build card (Claude Code or API), call job_status with the job_id until the job is finished, stopped or failed. Preview links expire after 15 minutes; call again for a fresh link.
Inputs: job_id (required).
Use this when the person wants a logo or brand mark for a business, shop, product or project, for example "make a logo for Blue Fern Bakery". business_name must be the name the person gave, in their own words. If they gave no name, do not call this tool: ask them what the company is called, in their language (in Russian: «Как называется компания?»); never invent or translate a name. Pass their description and their own style words verbatim (never add style, colour or mood words yourself), and language (the language they write in). After a call, never describe what you passed to Pugi, name the tool or promise logos while a question is open; never say you passed something without calling. Pugi first asks the person to confirm the name in the card, once per name. If they say yes in words, call this tool again with the same business_name and the question_token. If they give another name in words, call this tool again with that business_name. A new business name is a new brand: never reuse another business's logo or answers. Pugi runs the same short brand interview as logo.pugi.io, one question per call (status needs_input), shown with its options in the card: tell the person in one short line to answer there or in their own words, without listing the options, then call again with their answer (trade for the first question, answers for the later ones). Use draw_now true only when the person says to draw now. Then it draws four whole logo options (PNG) the person can pick, change and use on a Pugi website. Generates logo design assets only. Do not use for photos, illustrations, posters, memes or editing an image the person uploaded; to change logos already shown in this conversation use refine_logo.
Inputs: idempotency_key (required), name, niche, style, +16 more.
Use this when the person refers to a site or app they built earlier (in this chat or another one) and you need its project_id, for example to publish it. Call it before offering to build again. Free and read-only.
Inputs: no named parameters.
Use this when the person asks to put a Pugi website or app live ("publish", "go live"). Free. Puts the latest version on its pugi.app address after the security check every Pugi publish runs; publishing again replaces the live version.
Inputs: job_id, language, project_id, idempotency_key, +1 more.
Use this when the person asks which of their Pugi sites are live and at what address.
Inputs: language, project_id.
Use this when the person asks to change Pugi logos already shown in this conversation: other colours, a calmer or bolder mood, another icon or font, "like the second one but blue". Draws four new options from the same brief with that change, without asking anything; it does not edit one chosen design. Pass exactly one of logo_id (from the last logo result) or question_token (from the logo card). Do not use for a different business name (use make_logo).
Inputs: change (required), idempotency_key (required), logo_id, language, +1 more.
Use this when the person wants a public GitHub repository checked for leaked secrets, vulnerable or malicious dependencies and risky code. No code is run. 3 free checks a day per account, then $1 when the check finishes; a failed check costs nothing. Do not use for websites (use scan_url) or private repositories.
Inputs: repo_url (required), idempotency_key (required), ref, language.
Use this when the person wants a public website checked for security problems, for example "is my site secure?" or "check example.com". Free and read-only: HTTPS, security headers, cookie flags and exposed keys, with a grade from A+ to F and how to fix each finding. Not a pentest. Do not use for private or local addresses or for code repositories (use scan_repo).
Inputs: url (required), language.
Use this when the person picks one of the Pugi logos shown in this conversation (in the card or in words, such as "the second one"). Saves that logo for their business and returns the summary a website or app will be built from: show it and wait. Call again with correction when they change anything in the summary. Draws and buys nothing.
Inputs: logo_id (required), language, correction.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Build websites and web apps with AI, see them in the chat, and publish them.
Build, edit, and publish real websites and online stores by chatting with your AI assistant.
Publish and update HTML websites, landing pages, reports and proposals from AI chat. OAuth sign-in.
Build, change and publish a business website from your AI assistant, with sign-in and saved data.
Add one secure layer between your agents and this server.
