Improve a product page with Agentzia

Use Agentzia's hosted MCP to investigate how ChatGPT, Claude, Gemini, and Grok discover, evaluate, and compare a product. Turn supported findings into changes the user requested, then retest within the agreed budget. Agentzia supplies research; your normal coding tools make the edits.

Connect when needed

The server is https://www.agentzia.dev/mcp (Streamable HTTP with browser OAuth). Follow the client's native remote-MCP setup or the public setup guide. Installation and authentication are separate. The human completes sign-in; never request their password, payment details, or OAuth token. If a client cannot load the connection in the current session, leave a short continuation note for a fresh session. The skill alone does not supply MCP tools.

Use the connected server's current instructions and tool schemas as the contract. Tool names may have a client-specific prefix.

Choose the smallest useful study

• Establish the public page and the user's question from the conversation. Read list_runs first; use relevant existing research when a fresh study is unnecessary.
• Before a new study, read get_credits. A study costs one channel credit per selected assistant; the default four assistants cost four credits. Availability is advisory, not a reservation. Follow an existing user-approved budget; if none is established, explain the selected channels and cost before spending. Do not start unattended recurring tests.
• Prefer analyze_url for a public landing page. Use analyze_content for public-safe supplied marketing copy; text-only studies do not measure unprompted web discovery or provide an automatic before/after comparison.
• Only send public marketing material or material the user explicitly intends to publish and authorizes for external processing. Do not send private repository contents, secrets, personal/customer data, or confidential drafts. Agentzia stores inputs and traces and sends research to external providers.
• Create a UUID requestId for each intentional new study. After a lost response, reuse the same ID and arguments so a retry does not become a new charge.

Read results efficiently