Make your assistant easy to find.

Let your coding agent install it

In Installation, choose Set up with your coding agent. Copy the setup prompt or download SKILL.md. It contains your workspace’s exact snippet, public connection instructions, and checks for the published site.

1. Save and verify your website

Open your workspace, choose Agent → Installation, and save the website where the assistant will appear. Follow the domain verification instructions, then allow that website for your assistant. You can also keep a workspace private while you prepare it.

2. Publish the website snippet

Copy the snippet from Installation into your website template. It includes one HoverChat loader and links to the assistant’s manifest and public connection instructions. Use the generated values for your workspace.

Already installed the HoverChat loader? Keep that script once and add the new links. Merge the generated connection block into your site’s llms.txt or agents.md, and update any developer or authentication guide. Then publish the website.

The downloadable human guide and setup skill include these steps together.

3. Check the published installation

Return to Installation and choose Check installation. It checks your public website without sending a chat message or using inference credits.

• HoverChat: the published page includes this workspace’s loader.
• Agent discovery: the website advertises this assistant’s manifest.
• Agent instructions: agents can find the guest connection instructions, and the public API identifies the right workspace.
• Assistant endpoint: the hosted manifest and authorization metadata agree.

If one needs attention, follow its result, republish your website, and check again. A saved result describes the page at the time it was checked.

4. Help agents that read your site

Installation gives you Markdown for /llms.txt or /agents.md and, under advanced options, an entry for an existing /.well-known/ard.json directory. Include the guest connection instructions so an agent can ask a question even without a PAP client. Keep your other entries when adding it.

Your canonical manifest ends in /.well-known/poppy.json on the Ambipath assistant host. Link to that address. Do not copy its contents onto another domain, or rename it to agent.json.

If your host supports real HTTP redirects, it can redirect your website’s /.well-known/poppy.json to the canonical manifest. Static hosts such as GitHub Pages can instead publish the HTML link and reading-guide pointers.

5. Try the agent your customers use

Ask it to find your assistant, report the manifest URL, and describe the available connection. Then ask it to make a test conversation if it supports that connection.

Public questions can use the guest HTTP API without a browser or customer sign-in. Clients that support PAP can instead sign each request with their own published identity. Installation includes both connection paths.

Ask one question, then read its result. If the reply is still being prepared, keep reading the same conversation. The connection examples handle delayed replies and interrupted requests.

Keep the conversation useful

Visitors can ask immediately. The conversation menu lets them add context, share contact details, or request follow-up when they want to. Your team sees those details beside the conversation, with their source clearly labeled.

For developers

The public manifest advertises the assistant’s endpoints and authorization server. Public PAP questions need a signed request proof; account-specific access additionally needs customer authorization.

• Personal Agent Protocol 0.3 specification
• Agent Resource Discovery specification
• MCP authorization specification
• Agent Skills format
• Skills installer