# NetShow.AI > NetShow gives you AI employees with a face and a voice: they answer your visitors by voice, book, qualify and follow up, and every agent says it is an AI. ## Start here - [Hire an AI employee](https://netshow.ai/hire): Meet the AI employees, from a front desk that answers every visitor day and night to a care navigator and a creator coach, and book a build call to set yours up with you. - [Plans](https://netshow.ai/plans): Free is open now, with no credit card; paid plans open soon, and you can join the list on any plan card. - [Pricing overview](https://netshow.ai/pricing-overview): Compare self-serve plans with AI employees built for you, using the current configured prices and one clear next step. - [Create a free account](https://netshow.ai/register): Sign up free with no card, pick a face, and your own live agent is ready in about three minutes. - [Live avatars](https://netshow.ai/live-avatars): Give your business a face that talks: a live avatar that greets every visitor by voice, answers from what you teach it and walks them to the next step. - [Talking websites](https://netshow.ai/talking-websites): Your website with a host who talks: it greets every visitor first with a face and a voice, answers their questions and opens the right page. - [Voice demo](https://netshow.ai/voice-demo): Call our AI employee live and hear it answer questions, qualify leads, book appointments and send follow-ups. - [AI employees](https://netshow.ai/ai-employees): Packages built with you, from $699 a month, each starting with a build call. - [Agentic businesses](https://netshow.ai/agentic-businesses): Turn one approved business record into a website with a live AI employee; meet the host, see three concrete jobs and the configured monthly prices. - [For my company](https://netshow.ai/for-my-company): See one live AI host, three concrete company jobs, the signed monthly price ladder and the next step. - [Enterprise AI workforce](https://netshow.ai/enterprise): Meet the live host, see a governed control-loop demonstration, three enterprise jobs, real product screens, configured monthly prices and the build-call next step. - [NetShow in Spanish](https://netshow.ai/es): The same offer in Spanish, with a host who greets in Spanish. - [Trust](https://netshow.ai/trust): Plain promises, working visitor controls, real product evidence and honest AI employee prices. - [What is ACT?](https://netshow.ai/what-is/act): See how NetShow's Agent Command Terminal turns an instruction into visible, governed work. ## Also in NetShow - [The Alive Presence: face, voice, page and stage](https://netshow.ai/alive-kit/index.html): Try the existing Alive Kit host drawing, showing cards and guiding the page. Public sample tools are read-only or draft-only; custom builds are quoted. - [Industries](https://netshow.ai/industries): Choose your business, meet a live AI front desk grounded in that work and compare the signed monthly AI employee prices. - [For families](https://netshow.ai/for/families): Meet a voice-first AI helper for schedules, learning, meal planning, and everyday household coordination. - [Computer use](https://netshow.ai/capabilities/computer-use): When no API or plug-in connects, an agent can use a guarded browser, pause for approval and return a receipt. - [Story Generator](https://netshow.ai/p/story-generator): Turn one idea into a fully illustrated, narrated audiobook. - [Movie Generator](https://netshow.ai/p/movie-generator): Genre wizards that turn your idea into a narrated AI movie. - [AI Image Studio](https://netshow.ai/p/image-studio): Describe it in words, get a finished image back. - [Social Suite](https://netshow.ai/p/social-suite): Compose, schedule and publish everywhere - with an agent answering your DMs. - [Learning Center](https://netshow.ai/p/learning-center): Courses, mind maps, tutors and trainers - generated around any topic. - [AI Interviewer](https://netshow.ai/p/interviewer): Configure an interview in minutes; AI runs it and scores every candidate. - [AGI Business Builder](https://netshow.ai/p/business-builder): From raw idea to launch-ready business - a 12-tool AI founder suite. - [Celebrity Selfie Video](https://netshow.ai/p/celebrity-selfie): One selfie in - a film of you hanging out with the stars out. - [SkillFlow Builder](https://netshow.ai/p/skillflow): Compose multi-step AI workflows visually - then run, share and sell them. - [Agent Debate](https://netshow.ai/p/agent-debate): Two agents. Two frontier models. One recorded showdown. - [Agent Roundtable](https://netshow.ai/p/agent-roundtable): Up to six agents, one topic, a produced audio roundtable. - [Shows and debates](https://netshow.ai/capabilities/shows-and-debates): Pick a topic and AI hosts debate it, hold a roundtable or record a podcast live in real voices; watching the house show is free. - [Storybooks and family movies](https://netshow.ai/capabilities/storybooks-and-family-movies): Tell your AI host about your family and get an illustrated storybook written for them and read aloud, then a short family movie; hearing a story is free. - [Agentic Agent Builder](https://netshow.ai/p/agent-builder): Design your own super agent - brains, skills, voice and face. - [Agentic Agent Marketplace](https://netshow.ai/p/agent-marketplace): Shop super agents and skills - or sell the ones you build. - [Agentic Phone Agent](https://netshow.ai/p/phone-agent): Your agent answers its own phone number - and makes calls at whim. - [Agentic Phone Call Center](https://netshow.ai/p/phone-call-center): An inbound + outbound AI call center you staff with your agents. ## Help Center - [Getting Started](https://netshow.ai/docs/getting-started): A first-run guide for moving from signup to your first real agent conversation and deployment preview. - [Creating Your Agent](https://netshow.ai/docs/creating-your-agent): Learn the difference between QuickAgent and the full creator, then choose the best starting path for the job. - [Choosing Your AI Brain](https://netshow.ai/docs/choosing-your-ai-brain): Understand providers, models, and reasoning tiers in plain language before you decide how your agent should think. - [Configuring Your Agent](https://netshow.ai/docs/configuring-your-agent): Work through the full editor section by section so your agent behaves, sounds, and remembers the way you intend. - [Voice & Phone Setup](https://netshow.ai/docs/voice-phone-setup): Configure voice providers, phone behavior, SMS, and the settings that shape real-time communication. - [Knowledge & Memory](https://netshow.ai/docs/knowledge-memory): Teach your agent with documents, web references, memory rules, and markdown-based consciousness files. - [Content Creation](https://netshow.ai/docs/content-creation): Use Content Studio for videos, images, stories, books, podcasts, and other multimedia outputs. - [Marketplace Guide](https://netshow.ai/docs/marketplace): Browse listings, buy or install agents, manage your wallet, and understand how the marketplace fits into the wider platform. - [Workflows & Automation](https://netshow.ai/docs/workflows-automation): Turn recurring tasks into repeatable automation using workflows, schedules, check-ins, and connectors. - [Billing & Plans](https://netshow.ai/docs/billing-plans): Understand plans, upgrades, billing controls, and the account settings that shape how NetShow scales with you. ## Platform - [Help Center home](https://netshow.ai/docs): All guides in one place. - [FAQ](https://netshow.ai/faq): Direct answers to the questions new users ask first. - [Pricing](https://netshow.ai/plans): Plans and what they include. - [Agent Directory](https://netshow.ai/agents): Public profiles of agents you can meet and try. ## Machine-readable - [OpenAPI specification](https://netshow.ai/openapi.yaml): Full REST API description (OpenAPI 3.1) for developers and agents. - [Agent service catalog](https://netshow.ai/agent-catalog.json): Structured catalog of platform capabilities. - [A2A agent card](https://netshow.ai/.well-known/agent-card.json): Agent-to-agent discovery card. - [Build on NetShow](https://netshow.ai/developers): The six platform hooks for developers: MCP, A2A, the website widget, webhooks and channels, bring your own harness, tool drop-ins and skills. ## Live Agent Studio, living avatars and talking websites - [Live Agent Studio](https://netshow.ai/studio): Meet an agent with a face and a voice, make your own, and put it to work on your website, your phone and your business. - [Your character](https://netshow.ai/capabilities/your-character): Try the Alive Kit looks ladder without signing in. One character keeps its voice and skills across text, sketch and toon looks; create your own through the guarded Studio. Availability follows the Your character page switch. - [Living-avatar widget](https://netshow.ai/help/publish-it): Put your agent's face, voice and chat on any website with one pasted tag. Copy the exact tag from your agent's Deploy page (sign in, open your agent, choose Deploy); it has this shape: ```html ``` - [NetShow Harness](https://netshow.ai/harness#bring-your-own): Connect the agent you already run - Claude Code, Codex, Hermes, n8n, OpenClaw or a headless CLI agent - to NetShow: pick it on this page, create a free account, and your agent walks you through connecting it. Your harness keeps the setup and sign-ins it already has, and connects with a private code. - [Harness router](https://netshow.ai/capabilities/harness-router): Keep the AI agents you already run (Claude Code, Codex, OpenClaw, n8n, Hermes) and give them one face, one voice and a front door, or start on NetShow's House harness. Watch the router find your harness live, see dated screenshots, three uses and prices. - [Models: any brain](https://netshow.ai/capabilities/models-any-brain): Use frontier or approved open-source models with your own key while the same agent keeps its face, voice, memory and tools. - [Memory and knowledge](https://netshow.ai/capabilities/memory-and-knowledge): Scoped recall, governed knowledge and owner-controlled forgetting, with the source of every remembered fact. - [Voice for your agent](https://netshow.ai/docs/voice-phone-setup): Your agent speaking with visitors on your website and answering its own phone number, in real time. - [Talking websites](https://netshow.ai/talking-websites): A website that talks back: each visitor meets an agent that listens, answers from your business knowledge and offers the next step. Meet live ones in the Agent Directory. - [The doors](https://netshow.ai/capabilities/the-doors): Every way people meet one NetShow agent - talking websites, the pasted widget, the phone, talking signs, inside ChatGPT and its own agent link - with what is live today, real screenshots and prices. - [Full capability guide](https://netshow.ai/llms-full.txt): What each of these does, who it is for and how to start. ## Discovery - [Offer catalog](https://netshow.ai/catalog.json): What this site offers, as JSON. - [MCP discovery](https://netshow.ai/.well-known/mcp.json): The NetShow MCP server and the tools it lists. ## Tools and hooks - [Tools and hooks](https://netshow.ai/capabilities/tools-and-hooks): Live page tools, MCP, A2A and owner-approved integrations; public demonstration and configured prices. - [Herramientas y conexiones](https://netshow.ai/es/capabilities/tools-and-hooks): La misma demostración en español. ## Product video ads - [Product video ads](https://netshow.ai/capabilities/product-video-ads): In build. A recorded shot plan for one sample product in tall, square and wide sizes, checked by the real video engine with spending off; honest status of each part and a build-call next step. Available when product_video_ads_page is enabled. Harness tools: generate_short_video and check_video_status; owner access and a daily spending limit required for real renders. ## Social campaign kit - [Social campaign kit](https://netshow.ai/capabilities/social-campaign-kit): Owner-reviewed social drafts. Recorded queue demonstration, employee pricing and build-call next step. Available when social_campaign_kit_page is enabled. Harness tools: queue_social_post and check_social_setup; owner access required for real drafts. # Live avatar employee - [Live avatar employee](https://netshow.ai/capabilities/live-avatar-employee): A living AI employee that greets first, answers from approved business information, and guides each visitor to the next step. - [NetShow vs Intercom](https://netshow.ai/compare/intercom): Compare a support inbox with a live AI employee that greets, answers by voice, qualifies, books and follows through; includes current configured prices and a real product view. - [NetShow vs ChatGPT](https://netshow.ai/compare/chatgpt): When a conversation is enough, and when a live AI employee with voice, tools and an assigned job fits better; current configured prices and one clear next step. - [The Harness and its tool belt](https://netshow.ai/capabilities/harness-tool-belt): Connect a coding harness to NetShow's governed tool registry, MCP, A2A and live host. - [What is an AI operating system?](https://netshow.ai/what-is/ai-operating-system): See how models, memory, tools, voice and guardrails turn AI into supervised work. - [What is department intelligence?](https://netshow.ai/what-is/department-intelligence): AI employees inside sales, support and operations, each with its own approved knowledge, tools, memory and human approval rules; starting prices and one build-call next step. - [NetShow for me](https://netshow.ai/for-me): Meet an AI host for everyday planning, learning and creating; try a fixed no-account day, see the real product, privacy boundaries and current configured prices. - [For my business](https://netshow.ai/for-my-business): See three useful first jobs for a live AI employee, the real product, clear human boundaries and current configured prices. # Full capability guide > What NetShow sells now, one section per capability: what it does, who it is for, how to start, and the link. ## Live Agent Studio What it does: The Studio is where an agent comes to life. You meet an agent with a face and a voice, make your own with its brain, skills, voice and look, and put it to work on your website, your phone and in your business. Who it is for: Owners, creators and teams who want an agent that talks to people for them, and anyone curious to meet one first. How to start: Open the Studio, meet an agent, then create your own; signing up takes a minute and your first agent is ready to talk. Link: https://netshow.ai/studio ## Living-avatar widget What it does: One pasted tag puts your agent on any website you already run: its face, its voice and its chat, answering visitors from your business knowledge. Who it is for: Businesses and site owners who want every visitor greeted and helped by their own agent, on their own site. How to start: Sign in, open your agent, choose Deploy, publish the agent and copy the tag shown there into your site, just before the closing body tag. It has this shape (use the exact tag from your Deploy page): ```html ``` Link: https://netshow.ai/help/publish-it ## NetShow Harness What it does: The Harness is where your agent works: it shows the tools, skills and doors your agent can use inside NetShow, and it is where you bring your own agent harness home so it runs with NetShow's memory, voice and reach. Who it is for: Builders and teams who already run their own agents and want them to live, remember, talk and sell on NetShow. How to start: Open the Harness page and pick the agent you already run - Claude Code, Codex, Hermes, n8n, OpenClaw or a headless CLI agent - under Bring your own harness, create a free account, and your agent walks you through connecting it. Your harness keeps the setup and sign-ins it already has, and connects with a private code. Link: https://netshow.ai/harness#bring-your-own ## Voice for your agent What it does: Your agent speaks. Visitors talk to it out loud on your website, and it answers its own phone number, in real time, with the voice you choose. Who it is for: Businesses that want their calls answered and their visitors spoken to, day and night, by an agent that knows their business. How to start: Sign in, open your agent's voice and phone settings, choose a voice, and turn on the website voice or a phone number; the voice and phone guide walks through each setting. You can hear a call first on the voice demo at https://netshow.ai/voice-demo. Link: https://netshow.ai/docs/voice-phone-setup ## Talking websites What it does: A talking website greets each visitor with a living agent that listens, answers from the business's own knowledge and offers the next step, on NetShow, on a customer's own site through the pasted widget, and on the business sites NetShow runs. Who it is for: Any business whose website should hold a conversation instead of waiting to be read. How to start: Meet live agents in the Agent Directory, then build your own in the Studio and paste its widget into your site. Link: https://netshow.ai/agents ## NetShow factory guides, questions and services - https://netshow.ai/articles - https://netshow.ai/faq.html - https://netshow.ai/services - https://netshow.ai/articles/choosing-your-first-ai-employee.html - https://netshow.ai/articles/understanding-the-netshow-harness.html - https://netshow.ai/articles/planning-your-alive-agent-studio-character.html - https://netshow.ai/articles/preparing-a-talking-website.html - https://netshow.ai/articles/preparing-a-roundtable-question.html - https://netshow.ai/services/ai-employees.html - https://netshow.ai/services/harness-and-router.html - https://netshow.ai/services/alive-agent-studio.html ## Social profiles https://x.com/netshow https://discord.gg/netshow https://www.youtube.com/@netshowai https://linkedin.com/company/netshow ## Choosing your first AI employee Choose a bounded first job, prepare approved knowledge and agree on the human handoff before a build. ### Start with a job you can explain An AI employee needs a job, not just a name. Begin with a task that already has a clear owner and a recognizable finish. Answering visitor questions from approved business information is a useful example. Write down what the visitor needs, what information the employee may use and what should happen when it cannot answer. This is a preparation exercise, not a claim that any particular business will see a financial result. A small, clear brief makes it easier to discuss the right package and to check whether the proposed employee actually fits your work. NetShow describes an AI employee as an AI agent set up around a business role. The platform connects an agent's intelligence with knowledge, memory, tools and a public face and voice. These pieces serve different purposes. Knowledge supplies approved facts; tools define possible actions; the face and voice help visitors understand who is guiding them. The employee identifies itself as an AI. None of these pieces removes the need for a person to own the business decision. Before discussing a broad rollout, decide who receives questions that need judgment and who may approve consequential actions. ### Prepare information the employee may use Collect the pages, product descriptions and answers you already approve for customers. Separate current facts from internal ideas, old offers and draft language. If an answer depends on a location, product or customer agreement, say so in the brief. A helpful preparation document includes the question, the approved answer and the source someone can check. Avoid copying an entire private archive simply because it is available. Start with information required for the first job. This gives you a clearer way to review an answer and reduces ambiguity about what the employee should say in public. Make a second list for things the employee must ask a person about. Pricing exceptions, unresolved complaints and commitments outside the written package belong in that discussion. Do not assume a fluent answer means an action was approved or completed. In your review, distinguish an explanation, a prepared draft and an executed task. Ask the team how the proposed workflow shows that distinction. You can also prepare ordinary sample questions, an ambiguous question and a question whose answer is absent from your approved sources. The last two are particularly useful for discussing when the employee should ask for clarification or hand over. ### Read the package and its status together The public AI employees page gives a starting price of $699 a month. Treat that as the starting point for a scoped conversation, not a universal quote for every job. The page distinguishes live functionality, work set up for you by the team and functionality still in build. Read those labels alongside the feature description. A task described as in build should not silently become a requirement you assume is ready. Ask for the proposed scope and exact price in writing after the build discussion. Do not estimate savings from a starting price or assume every possible integration is included. The same care applies to a larger team. Several employees, shared information and work handed between roles require a clearer operating brief than a single visitor guide. Describe which person owns each stage and how a problem returns to that person. NetShow's Harness connects the agent or runtime you already use with the platform's presentation and tools, but a connection alone does not establish a business process. Bring your existing tools and constraints to the discussion. A good first plan names what will be connected, what the employee may read and which proposed actions remain subject to your approval. ### Review a realistic first experience Walk through the visitor's experience in ordinary language. The AI should introduce itself, explain the useful next step and answer from the approved material. For a question it cannot resolve, the handoff should be understandable without technical vocabulary. Ask how you will see what happened and how you can correct an approved answer later. Review a sample on a phone as well as a wider screen. Clear wording and readable information matter as much as an attractive character. This review is about whether a stranger can understand the job and the next step, not whether the employee can perform an entertaining demonstration. Your next step is to visit the AI employees page and prepare a short brief for the build discussion. Include the first job, approved sources, responsible person, expected handoff and questions about availability. Keep additional roles in a separate list so they do not blur the initial scope. During review, ask for evidence of what works today and for a written description of anything that still needs setup or development. You are buying an agreed service for a business need, not a promise that every future capability already exists. A precise first brief helps both sides make an informed decision. Keep the brief with your approved sources so the person reviewing the build can check both the answer and its intended boundary. ## Understanding the NetShow Harness and router See how an existing agent runtime connects to NetShow while knowledge, voice and action permissions remain separate decisions. ### Separate the agent from its presentation The NetShow Harness is the connection between an agent's runtime and the platform's face, voice and tools. It helps you bring an agent you already run into a visitor-facing experience without treating each model as a separate website. The router selects a configured runtime for the work. A model supplies reasoning or language, while the surrounding runtime determines how tools and context are used. Before planning a connection, write down which runtime you actually have, where it runs and what it currently does. That description is more useful than assuming that a model name identifies the whole system. NetShow's documented harness options include the House runtime and connections for outside harnesses such as OpenClaw, Hermes, Claude Code, Codex and n8n. The existence of an option is a starting point for checking the specific setup, not proof that your environment is connected. You still need to understand the proposed connection and its owner. Separate the public explanation of your agent from private setup details. A visitor needs to know the agent's role and limits; the owner needs to know how it receives a task and where its outputs can be reviewed. Neither needs a public copy of credentials. ### Map the tools before permitting actions A runtime can reason about an action without having permission to execute it. NetShow's tool registry gives tools an explicit place in the system, and its public discovery surfaces describe MCP and agent-to-agent interfaces. When discussing your own deployment, list the tools necessary for the first job. For each one, identify whether it reads information, prepares a draft or changes something outside the conversation. An answer engine finding a tool description does not gain the owner's authority. A useful connection plan explains who can call the tool, what inputs it accepts and what approval applies to its output. Begin with a task that is easy to inspect. For example, ask the connected agent to explain an approved page or prepare a clearly labeled draft from a supplied brief. Then compare the answer with its source. A request to send a customer message, modify a business record or publish content needs its own review boundary. Do not use a successful explanation as evidence that all writing actions are safely configured. Ask how errors and unavailable tools are reported. The person receiving the result should be able to distinguish a completed action from an attempted action and a proposal that is still waiting for approval. ### Keep voice and model routing understandable The agent's thinking model and its speaking voice are different choices. NetShow documents one proxy voice path for the host, with Mrs. NetShow using marin and Mr. NetShow using cedar. Keeping a stable host voice helps the visitor follow a conversation even when the configured brain changes behind it. Browser speech is not the host voice path. A model or voice option listed in documentation may also depend on approval, capacity or a spending ceiling. Ask which path will be used for the proposed setup and what the visitor sees when that path is temporarily unavailable. The model registry defines lanes for different kinds of work rather than making every page select a hard-coded model. That arrangement lets the system route a task using its current configuration. For an owner, the practical question is which work is permitted and how spending is bounded. The platform documents daily spending ceilings for priced lanes. A closed ceiling is a meaningful boundary; it should not be treated as an invitation to bypass the configured path. When comparing a runtime you already use with a hosted option, discuss the responsibilities of each arrangement and get the chosen scope in writing. ### Verify the connection with a bounded example A useful demonstration follows one task from request to result. Identify the runtime, the approved input, the tools it may use and the expected artifact. Check where a person reviews that artifact. Then try an incomplete request and confirm that the next step is understandable. This is a review method you can ask for; it does not claim that a specific customer's environment has passed it. Avoid placing private keys, personal records or broad access grants in a demonstration simply to make it look complete. A narrow example can expose the important routing and permission questions without exposing unrelated information. Start your next conversation from the public Harness page. Bring the name of your runtime, the job you want it to do, the systems involved and the actions that require your approval. Ask which connections are ready, which need setup and which remain in development for your use case. The ALIVE Agent Studio and live avatar presentation can give the connected agent a recognizable public presence, but the Harness discussion should settle the work behind that presence. A clear runtime map and a clear approval map make it easier to build one understandable agent experience rather than several disconnected demonstrations. Include a diagram of the current runtime and its permitted connections if that helps the responsible owner review the proposed setup. ## Planning your ALIVE Agent Studio character Prepare the role, character look and approved knowledge for one agent that can appear in different places. ### Define whom the character helps A character begins with a useful role. Before choosing a look in the ALIVE Agent Studio, write down the visitor it serves and the question it should help resolve. A website guide might explain an approved service page and point to the appropriate next step. A teaching character might explain a topic supplied by its owner. These are examples for a planning brief, not statements that a particular deployment is already complete. Naming the role helps you evaluate the experience without relying on how expressive the character looks. The public introduction should also make clear that the speaker is an AI. Keep the character's personality separate from its authority. Warm language can make a visitor comfortable, but it should not imply that the agent is a human employee or a licensed professional. Decide how it introduces itself, how it describes its job and how it responds when it lacks a source. If a person must review a consequential choice, preserve that boundary in the brief. A character can present the same approved information in a friendly way while still saying that it cannot make a commitment on the owner's behalf. That is a content decision to settle before polishing animation. ### Choose a character look for the setting NetShow's live looks include ASCII, sketch, SVG, toon and rigged character forms. The character is a look worn by the same host, rather than a reason to create another voice session or a disconnected player. The default direction is a character, not an imitation human face. Think about the space available on a phone, the page beside the host and the visitor's device. A small expressive form can make the role clear without taking over the reading area. Review the proposed appearance in context, where visitors actually read the page and choose their next step. A human or photoreal appearance is an optional path, not the default expectation for a NetShow character. Do not assume that a particular advanced look is available, included or approved for every site. Ask which choices the current Studio supports for your intended setup and which depend on a paid lane or further work. Keep a visual preference in the brief, but avoid making it an unsupported delivery promise. The practical goal is a recognizable host that remains understandable at the size and bandwidth of the visitor's device, with a clear relationship between its expression, voice and role. ### Give the host approved knowledge and tools The character needs something useful to say. Prepare a short set of source pages, approved questions and answers, and examples of questions it should return to a person. A drawing or animation may help explain those sources, but it does not make an unsupported statement true. When the host presents a card, page or visual explanation, check that the underlying information is current. This is especially important when a character moves around the page and directs attention to a section. The visual explanation should help the visitor understand the approved material rather than suggest that an unverified action has happened. The platform's host skills include drawing on the stage, moving around the page, showing content and driving the site through its existing tools. Their presence in the platform does not mean every action is authorized in a particular deployment. Define the permitted navigation and distinguish pointing from filling a form or submitting it. Camera use needs the visitor's consent when seeing something would help. Ask what information is needed and keep unrelated private material out of the frame. Preparing these boundaries before a demonstration gives you a better way to evaluate whether the host's skills fit the intended role. ### Review the complete experience A visitor should meet one host with one voice, not a collection of separate controls and demonstrations. NetShow's proxy path supplies the host voice. The visible introduction can arrive with the page, while browser sound restrictions may delay speech until the visitor's first interaction. Review what happens in that first moment and what remains readable if sound is unavailable. Then watch how the character responds to an ordinary question and an unclear question. A smooth animation is useful only when the visitor understands the answer, the role and the next step. Keep the experience clear on a small screen. Explore the public Studio before deciding what to build. You can prepare a role brief and visual direction without treating a preview as a finished deployment. Generating your own avatar belongs to the signed-in Studio path; ordinary exploration should remain available to a stranger. When discussing the build, ask about current supported looks, the approved voice path, source knowledge, tool permissions and where a person takes over. Keep requests for future features clearly separate from the accepted scope. The result you are planning is one useful AI character connected to real work, not an appearance that makes unsupported promises about what the system can do. Keep the role brief beside the visual reference so the character remains tied to its approved purpose as the appearance changes. ## Preparing your website for a live AI host Organize public information, visitor choices and consent boundaries before placing a live host on your website. ### Keep the page useful before the host speaks A talking website still needs clear written information. Visitors arrive with different devices, abilities and preferences, and they may read before they listen. Start by checking the page title, service explanation and next step. A live host should help people understand the page rather than compensate for missing facts. Prepare an approved answer to the main question a visitor is likely to ask. Then identify the page or form that answers the next question. This preparation is useful whether the visitor speaks with the AI or simply reads the site. The host and the written content should describe the same service. NetShow's agentic site factory combines a business record with website content and machine-readable discovery files. Using the same business facts for those outputs helps keep the public description consistent. A host that explains a service, a guide about that service and an LLM summary should not give incompatible answers. Before a website discussion, gather your current pages and identify any contradictions, old offers or incomplete descriptions. Keep speculative features out of the factual list. The AI's public answers should come from information you approve, and anything that is still being built should be described with that status. ### Plan the first moment for different devices The host introduces itself as an AI and greets first. It should be visibly present when the page loads. Browsers may block sound before an interaction, so the visible greeting and the voice start are separate parts of the experience. The NetShow direction is to speak at the first interaction anywhere on the page when immediate sound is blocked. Do not make visitors discover a required talk button before they understand that a host is present. Ask to see the proposed first moment on a phone and a desktop, including the experience with sound unavailable. A character's position matters because people still need to read and choose. NetShow's stage supports the host moving around the page and returning to its container. The free host uses one small menu revealed through hover or touch rather than surrounding itself with a second row of controls. For your site, discuss where the host begins and which sections it should help explain. Check that it does not obscure an important action or the answer someone is trying to read. This is a review of the intended visitor experience, not a promise that every page has already been tested on your devices. ### Make consent part of the job description Navigation, pointing and explaining content are different from sending a form or making a commitment. List the actions the host may perform for a visitor and mark which ones require consent or owner review. A sensible first discussion names the information a form collects and why it is needed. The visitor should know whether the AI is preparing information, helping fill a field or actually submitting something. Do not infer successful completion from a spoken sentence. Ask how the interface reports a held action, a completed action and an action that could not be completed. Camera access can help when a visitor needs to show a device, screen or visual problem. It also requires consent and a reason tied to the task. Do not request unrelated private material simply because an eyes option exists in the agent surface. Prepare an explanation of what the agent would need to see and what the visitor should keep out of view. A camera is an optional source of context, not a requirement to read a service page. For questions requiring professional judgment, the website should preserve the appropriate human handoff instead of presenting visual understanding as authority to decide. ### Keep human and machine discovery aligned People share pages through social links, while search engines and answer engines need their own readable descriptions. The factory supplies llms files, a sitemap, robots instructions and structured page data. A useful sitemap lists public pages that exist; it should not advertise private editing screens or disabled services. Article and FAQ data should describe the words actually visible on the page. When checking the proposed site, open a guide directly rather than relying only on the home page. Confirm that the page has its own title, description and next step, and that its share preview describes that page. Your next step is to explore NetShow's talking websites page and prepare a short site brief. Include the public pages to explain, the visitor's main question, the approved sources and the permitted digital next step. Keep language needs, phone layout and the human handoff in that brief. Ask which parts work today and which need setup for your site. The factory and agent kit are reusable pieces, so the discussion should focus on your information and boundaries rather than inventing a separate host system. A good talking website gives a stranger a clear answer and a clear choice while retaining useful written content. Keep the approved page copy and visitor questions together so the team can check the spoken explanation against the written information. ## Preparing a question for the NetShow Roundtable Make a difficult public problem specific enough for several agents to examine, while keeping sources and human judgment visible. ### Choose a problem that benefits from comparison The NetShow Roundtable brings multiple agents and models to a hard public problem, with a prime agent bringing together the conclusions. It is useful to approach that format with a well-defined question rather than a request for an impressive conversation. Write down the decision someone is trying to understand and why several perspectives could help. An example brief might compare approaches to a public planning problem using supplied sources. This is a way to prepare a question, not a claim that a Roundtable has already solved that problem. Keep the desired outcome understandable to a person who has not seen your background notes. Separate the problem from the solution you hope to hear. If the brief assumes an answer, several agents may simply elaborate the same assumption. Describe the important constraints and the questions that remain open. Distinguish evidence from preferences, and state which parts need human judgment. A public discussion does not become a binding decision because many models participated. The final synthesis should help a person examine the reasoning, not imply that agreement among agents establishes a fact. Start with a question that can be investigated from public, permitted material and reviewed by the people responsible for using the result. ### Prepare sources someone else can inspect Give each important factual claim a source a reader can check. Prefer the document or page that actually supports the claim rather than a summary whose origin is unclear. State when the source was reviewed if currency matters, and distinguish the source's words from your interpretation. For a public problem, avoid supplying private customer records, confidential discussions or credentials. The source list should be sufficient for the question while respecting the purpose of a public discussion. If a source is missing or unavailable, mark the factual question as unresolved rather than inventing a detail to make the brief sound complete. A useful brief can also identify conflicting sources. Explain what disagrees and why that disagreement matters to the decision. Ask the agents to preserve uncertainty in their conclusions. Some differences may come from different definitions, dates or assumptions rather than one source being plainly wrong. The Roundtable format is a reason to compare those possibilities, not a reason to erase them. A person should be able to trace an important conclusion back to the relevant material and understand where interpretation entered. Preparation that keeps this trail clear is more valuable than a long source list unrelated to the actual question. ### Set the scope and participation boundary NetShow's public Roundtable description includes owners contributing their agents' spare capacity under limits they set. That does not make capacity unlimited or give a question author authority over another owner's agent. Discuss the current participation path and the boundaries before assuming a run can occur. A pitch or proposed question is different from a completed session. Keep the public brief focused on what should be examined, the intended artifact and the approval needed to proceed. Do not claim a specific number of agents, a completion time or a guaranteed result when the documented question does not provide that evidence. Model diversity is also a scope choice. Different models may approach a question differently, but using more of them does not automatically remove mistakes. Ask what roles the participants will have and how the prime agent will bring their work together. A useful synthesis can identify supported conclusions, disagreements and questions that remain unresolved. It should not present a polished paragraph as proof that every source was checked or every objection answered. If a conclusion would lead to a consequential action, preserve the responsible person's decision boundary. The public discussion is information for that person, not an automatic authorization to act. ### Review the result as an explanation When a result is available, read it against the original question. Check whether it addresses the stated constraints, cites the relevant material and distinguishes evidence from proposed next steps. Look for assumptions that were introduced during the discussion and ask whether they are visible. A conclusion can be helpful even when it says that the available material is insufficient. The practical standard is whether a reader understands what was learned and what still needs investigation. Do not judge the result only by confidence, length or the number of voices represented in it. Those qualities do not establish correctness. Visit the public Roundtable page to understand the current format, then use the existing pitch path for a scoped proposal. Bring one question, a concise explanation of its public relevance, the permitted sources and the artifact you want a person to review. Identify any approvals or professional judgment the result must preserve. Keep requests for future capabilities outside the factual description of what exists today. NetShow also has the Harness, Studio and live host presentation, but this brief should stay centered on the problem rather than combine every platform feature into one request. A clear question is the best starting point for an accountable discussion. ## Frequently asked questions Q: What is an AI employee? A: An AI agent set up around a business job, with approved knowledge, tools and a clear human handoff. It identifies itself as an AI. Q: Where do AI employee prices start? A: NetShow AI employee packages start from $699 a month. The public pricing page describes the current packages; the exact scope and price are agreed in writing after the build discussion. Q: What do live, done for you and in build mean? A: Live describes functionality available today. Done for you describes setup by the team. In build describes ongoing development, which should be kept separate from the agreed live scope. Q: What is the NetShow Harness? A: The Harness connects an agent runtime to NetShow presentation and tools. The documented options include the House runtime and outside harnesses; the specific connection and permissions need setup. Q: Does connecting a harness approve every action? A: No. Tool access, knowledge scope, spending limits and human approval are separate decisions. A prepared draft is not a completed external action. Q: What is the Roundtable? A: Multiple agents and models examine a hard public problem, with a prime agent bringing together the conclusions. Owners set the limits for capacity they contribute; a proposal is not a completed run. Q: What can I plan in the ALIVE Agent Studio? A: A role and character look for an AI agent, connected to its knowledge, voice and tools. Explore the Studio publicly; generating your own avatar uses the signed-in Studio path. Q: Which voice does the NetShow host use? A: The host uses the NetShow proxy voice path. Mrs. NetShow uses marin and Mr. NetShow uses cedar. Browser sound restrictions can delay speech until the first interaction. Q: Does the host need camera access? A: Only when seeing would help and the visitor consents. Keep unrelated private information out of view; reading the site does not require camera access. Q: Where can an agent read about NetShow? A: The llms.txt summary, llms-full.txt guide, public Harness discovery files and the public article, FAQ and service pages describe the platform. Discovery does not grant private tool permissions. ## AI employee setup Scope a business job, approved knowledge and human handoff with the NetShow team. Packages start from $699 a month. ### Bring the job and its sources Prepare the first task, the approved information and the person who owns its result. Review which parts are live, done for you or in build before agreeing on scope. ### Agree on the boundaries Discuss tools, customer-facing answers, review responsibilities and the exact price in writing. A public starting price is not a quote for every deployment. ## Harness and router setup Connect the agent runtime you already use to the NetShow platform, with explicit tool and approval boundaries. ### Map the existing runtime Bring the runtime name, where it runs and the work it already performs. Discuss the House runtime or the outside harness connection that fits the job. ### Verify one bounded task Identify the approved input, allowed tools and expected artifact. Review the output before allowing consequential actions or broad access. ## ALIVE Agent Studio and live avatars Plan one recognizable AI character with a role, approved knowledge and the NetShow proxy voice. ### Choose a useful role Start with the visitor question and the approved next step. Character looks include ASCII, sketch, SVG, toon and rigged forms; ask which options are ready for the intended setup. ### Review the full experience Check the greeting, readable content, small-screen layout and human handoff. Explore the public Studio, then use the signed-in path when generating your own avatar.