Trae Solo said it couldn’t register a domain. After another prompt, it registered solo.chatbot.

I’m working with Headless Domains, and we documented a test where Trae Solo registered solo.chatbot through Machine Payments Protocol (MPP). The video is a short edit of the original screenshots.

The first response was that it couldn’t proceed. We asked it to reread the MPP instructions and follow the autonomous registration flow.

Solo then reported finding a signing method that worked in its environment. It completed the payment challenge and returned a successful registration response, an active domain lookup, and links to its published agent manifest and skill file.

There were human steps throughout:

• We supplied the task and the follow-up prompt.
• After registration, we used the claim code to connect the agent and domain to our account.
• When we asked Solo to update its public bio, it needed API access again. We supplied that, and it completed the update.

That credential interruption was an interesting part of the test. Completing registration didn’t mean the agent still had everything it needed for the next task.

For context, this is a Handshake-backed .chatbot name registered through Headless Domains. Its DNS records point to the manifest, skill file, bio, and related links.

The broader idea is to give a conversational product a public identity it can maintain as its underlying tools and interfaces change. This particular run documents registration and profile publication.

Full walkthrough and original screenshots:
https://headlessdomains.com/blog/trae-solo/

For people running bots across multiple apps or interfaces: what do you use as the bot’s public identity today?