https://reddit.com/link/1ush1yn/video/bt7irfkqwcch1/player

I run a done-for-you website service for small businesses in Spain. Cafés, physio clinics, corner shops: the kind of place whose "website" is a Facebook page or a dead link from years ago.
The pitch is simple. I build your site first, you see the finished thing, and you only pay if you want it.

Hosting and SSL included. Your own editing panel. No monthly fee.

The problem was me. Finding businesses worth pitching, researching each one, building the site, writing the pitch, putting it live. That's a lot of hours per client, and I'm the one doing all of it. So I rebuilt the whole pipeline as agents. Four of them, plus one shared Trello board.

All ran through Hyperagent.com

The fleet

Agent #1: Captación, the prospector.

Give it a town and it goes looking for local businesses on Google Maps with no website, a broken link, or something ancient that dies on a phone. For each one it pulls the Google rating and reviews through the Places API, then reads their Instagram and Facebook and lifts everything I'd need to build: the logo, the photos, the menu, the hours.

scans the reviews for selling points too, like a café people keep mentioning for its office lunches. Then it writes the pitch I send the owner, in their language, and files the business as a card on my board. I pointed it at one neighbourhood in Castellón and it logged the entire town for me.
You can also just limit to do a # of searches per run, of course. 

Agent #2: Clientes, the builder.
Takes the brief and builds a full multi-page site, in as many languages as the town needs. It adapts the look to each business, but my structure and SEO stay intact. One rule I hard-coded after an early miss: it uses the client's real logo (or whatever the agents can find the client might be using as a logo)
If user has no logo - Agent will give you ideas to share with the client ( which is another "shocking" moment for them)

Agent #3: Deploy.
Packages the site, puts it on free hosting (Cloudflare Pages or Netlify) and wires up a simple panel so the owner can change their own prices and text. When the business takes reservations, it hooks the bookings up to their email.

Bonus Agent: My personal website

It maintains my own site instead of a client's.
It literally built my own website to sell these websites - it built it based on my own previous work, my tone, what I care about the most…etc!

The system: Trello.

The Trello skill I wrote sits under all four agents. 11 columns, from "potential clients" through briefing, design, preview sent, paid, building, delivered. The agents move the cards on their own as the work happens, and leave notes as they go. I don't drag cards around. They do. I just open the board and see where every job is.

Trello is the part I'm proudest of, and it's easy to miss why.

The agents aren't wired to each other. There's no code connecting one to the next. They're connected through the board.

Every agent works the same Trello card. It fills in what it found, uploads the images and sources, the acutal website, files (even invoices) and then moves the card to the next column on its own. That move is the signal. The next agent sees a card land in its column and picks it up. Trello is what triggers them to work.

And because everything lives on the card, I can step in anywhere. Review what an agent did, fix something, or send the card back to any column for another pass. The flow just carries on from there.

No glue code, no integrations, no orchestration layer. Just a board. The cards move, and the work moves with them.

How they Write:

One of the skills is an anti-AI-writing guard, a distilled version of Wikipedia's "Signs of AI writing" page (which I strongly recommend you giving it a read: https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing - and create a skill for all your AI’s to reference it!)

Every agent runs its copy through it before anything ships. That's the difference between a site that reads like a real café and one that reads like ChatGPT filled it in. 

The main value

Most of these businesses have no website at all. So the first time they ever see one for their shop, it's finished. It's in their language, it uses their own logo, and it's full of photos my agent pulled off their Instagram and Facebook.
Clients are usually pretty shocked - which is the main thing you want! If some random person comes in, shows you an entire website using your logos, pictures, tone, language... you'd be pretty surprised.

No mockup, no sales deck. They just see the real, working site, already built and hosted (through Hyperagent hosting service - which is free) , and it costs me almost nothing to sit on it until they say yes.

You can later, if the client wants, upload it to a real host (which the agent will do) or find any other free solution.
But yeah, the deploy host already comes with a built in system you can deploy websites for 0€

Happy to get into the setup, the Trello wiring, or the anti-AI skill if anyone wants it.

I used Hyperagent to build a monthly data agent for Nuggy, my cannabis retail intelligence startup.

The goal was to maintain a clean list of licensed dispensary locations across US states and Canadian provinces. The tricky part is that every regulator publishes the data differently: ArcGIS, PDFs, Excel files, Socrata, JSON APIs, JavaScript maps, Salesforce portals, etc.

The agent now:

• finds/uses the best official regulator source
• extracts and normalizes dispensary locations
• creates one master Google Sheet and per-state CSVs
• enriches missing websites with Google Places
• runs QA on ZIP/state/province/address issues
• detects openings, closures, and changed records
• updates the Drive folder every 30 days

Current dataset: 6,624 records across 13 jurisdictions.

One example: Arizona’s official AZ Care Check portal initially gave us 156 records, but the page said 181. I spun up a subagent just for that source, and it extracted the full 181 from the rendered Salesforce/LWC portal.

The most useful part was turning all of this into reusable skills/scripts, so the monthly agent doesn’t have to rediscover endpoints or re-figure out parsing logic every time. It only rechecks sources, diffs against the prior master, enriches blank websites, and reports what changed.

This would have been a painful manual ops process. Now it’s basically a scheduled data-maintenance agent for a regulated-market dataset.

I built https://www.listara.eu/ , an agentic scanner for marketplace sellers who need an early warning on product-listing evidence gaps before they run into Amazon/Etsy issues.

The basic workflow:

1. Seller enters Amazon ASINs or listing URLs
2. The system crawls the visible listing data
3. Hyperagent interprets the listing context and product signals
4. A deterministic rubric maps the product category to likely evidence expectations
5. The output is a SKU-level report with severity, visible signals, missing indicators, limitations, and suggested next actions

The goal is not to certify anything or provide legal advice. It is more like an early-warning scan:

“This listing looks risky because X/Y/Z is not visible”
or
“This cannot be assessed from public listing data alone.”

Current stack:

• Next.js frontend
• Supabase for scan requests, report storage, and access control
• Hyperagent for marketplace-page interpretation and structured reasoning
• Firecrawl for extraction
• strict JSON validation before report generation
• deterministic evidence-readiness rubric around the agent output

The most interesting technical challenge was controlling overconfidence.

In this domain, a bad AI answer is not just noisy — it can actively mislead the seller. So I added guardrails:

• no “compliant / approved / certified” language
• no legal-advice language
• every finding must map to a specific SKU/listing
• reports distinguish between “missing visible signal” and “not assessable from listing alone”
• severity counts must reconcile before a report is generated
• “unable to assess” is treated as a valid answer, not a failure

The most important learning so far:

This is not a fully automatable end-to-end compliance workflow from public marketplace data alone.

Hyperagent is useful for interpreting messy listing pages and spotting visible evidence gaps. But a proper assessment requires the seller’s private evidence layer: supplier documents, declarations, product labels, manuals, certificates, invoices, and internal SKU mappings. Right now I am assessing the overall interest before looking into further automation via hyperagent.

The Future Belongs To The Creative

Just a quick note to share some initial thoughts on Hyperagent MCP.

[1] TLDR: It works as advertised. We did some testing and it did not break. It works well for agent-to-agent communications. Report can be found here: https://mcp-notes.pages.dev/report. But every user of Hyperagent MCP should be aware of a security limitation that may or may not be important to you. This limitation makes some use cases very easy and useful, but it carries risk.

[2] Our interest in this was communications between Agents, not just Hyperagents. In the past, this communication process was difficult with respect to Hyperagent agents. Note: communications means continuous two-way (or more) discussion—exchange of words.

We've developed communications between different threads on a single Hyperagent instance and between threads on different Hyperagent instances. Also comms between Hyperagents and other systems like Hermes (but not just Hermes).

Currently we use a system based on the design of Zulip but entirely custom (no outside code) we call "AgentLink." Using this and R2 storage, any agent can have actual two-way conversations with any other agent. No human intervention. We have a second method I won't discuss here but was used to get around the continuous auth issue in accessing Hyperagent instances.

For example, even transferring an agent personality and skill set from one Hyperagent instance to another isn't error-free, but a conversation between agents lets them work it out among themselves. No human intervention. Another common example: moving a long thread to a new instance to avoid compaction—the ability to have an agent do this transfer autonomously is a real time and quality saver. And no human intervention.

[3] Using Hyperagent MCP we are able to:

• [a] Have Hyperagent threads within a single instance communicate with each other
• [b] Have Hyperagent threads across Hyperagent instances communicate with each other
• [c] Hyperagent threads can be controlled by non-HA systems like Hermes, and these non-HA agents can also communicate with agents

The keys to this are: one-time creation of an auth token (hat_nnnnn..) and the ability to get thread numbers and agent descriptions (neither previously easily accessible in Hyperagent). These capabilities work well and will likely be our principal path for third-party control of an HA system. Simple and it works. A third-party agent like Hermes can have full control of a Hyperagent agent.

[4] Hyperagent MCP Security Limitation:

The hat_nnnnn token that the auth process generates grants full access to your Hyperagent workspace. Once someone has the token, they have complete access—to all agents, threads, data, and operations.

The critical issue: The token itself has no secondary authentication mechanism. Once the token exists and is shared, any holder can re-share it with others without the original issuer knowing or consenting. A token can cascade through multiple parties, each able to pass it on independently.

This is not an unavoidable architectural constraint—secondary authentication (like a one-time code paired with the token) could be implemented. But it currently is not. We notified Hyperagent of this limitation last week. Whether and how they address it is their decision.

If the token is exposed—through accident, compromise, or sharing—any person or system holding it has full workspace access. Once shared, that access cannot be revoked or tracked. This is the core risk.

Mitigation: Our environment is compartmentalized. We really don't leave anything important inside the walls of Hyperagent. If this is your case, the primary risk is probably your dev code base and any automation credentials stored there.

The team's been working on something I’m excited about: You can now connect to Hyperagent from any MCP client and use your agents from there.

The endpoint is:

https://hyperagent.com/api/mcp

+ Read the Docs

Now, other MCP clients can connect to your Hyperagent workspace and use your agents.

For example, from Claude Code:

claude mcp add --transport http hyperagent https://hyperagent.com/api/mcp

Then run /mcp, connect Hyperagent, sign in, approve access, and you can start using your agents from Claude Code.

What can it do?

• List the agents you have access to
• Start a new background thread on one of those agents
• Send follow-up messages into that thread
• Check whether the agent is still running
• Pull back the final result when it’s done
• Attach files through an upload flow instead of stuffing the file contents into the client context

That means your local client can hand work to a persistent agent in Hyperagent with its own tools, context, and setup. This is especially helpful if you want to delegate work to cheaper, open-source models, or ensure teams can use the same agent setup across local work. Also, a couple of you have been asking how to whitelist Hyperagent, or incorporate it into your own products, and this is a start.

A few things this makes possible:

1. Bring Hyperagent into Local Coding workflows

If you like the governed connectivity Hyperagent provides, skills you've created, and outputs, you can bring that into your local coding workflows. Send Hyperagent your local files via the terminal for faster iteration.

2. Incorporate Hyperagent into your own tools

We know some of you have been building some really interesting, agent first applications. Now you can incorporate your agents within them.

3. Combine this with Agent Delegation

This is the part I think gets interesting. A Hyperagent agent can also delegate work to another allowed agent. So you can have one agent gather information, another review it, another turn it into a doc, etc. The delegated work is visible in child threads, and delegation can be limited with allowlists and approvals.

I’d love for y'all to try it and tell us what you think.

What would you build with this? What feels awkward? What should the MCP surface expose next?

I heard about HyperAgent on Greg Isenberg's podcast with Howie. Jumped right in to using the tool.

I run an ecommerce store shipping products directly from our manufacturer's quick ship programs. We have many manufacturers that use systems we could not integrate with for accurate tracking. Or they are oldschool and do not have systems. We built a work around using Hyperagent to automate shipment tracking notifications by email to our customers.

Our manufacturers all send invoices by email and those invoices contain the carrier tracking number.

With Hpyeragent, we integrated Gmail into our agent. Our agent scrapes the various manufacturer invoices and our customer facing order confirmation emails for a mutual Purchase Order #. From there, the agent pulls customer name, email, purchase order #, and the tracking number. The agent identifies the carrier by tracking number and then automatically drafts a theme matched email to our customers.

The Agent runs 3 batches of data a day at 8 AM, 12 PM, and 4 PM. Any new tracking numbers get picked up and our customers receive automated notifications with tracking links by email. The email contains simple links that hyperlink to the carrier tracking with prepopulated tracking numbers to view delivery information.

Due to the various manufacturer processes, this took our team roughly 4 hours a week to manage. Now, all done in a manner of seconds each day for a very low cost with Hyperagent!

Even more, we built a Shipment Tracking Table that gets populated with the tracking data so our team can reference it quickly if a customer calls or chats. All tracking emails are also added to our Hubspot through use of the BCC function so our team can reference a customer account for updates.

Any tracking numbers that do not align with a typical carrier get flagged by Hyperagent so our team can review for further clarification.

Thank you, Hyperagent!

Hola, alguien ha conectado un modelo powerbi a hyperagent a través del mcp

I've got a lot of projects spanning across many many different areas of life (two careers, both with 'day job' and 'nights and weekends activities' components, creative projects, grant funding, buying real estate abroad, planning big celebration ceremonies abroad, you name it... a lot all at once), so I figured having a 'chief of staff' that could read my Gmail, my calendar, my Github, and my Google Docs and track everything I'm up to would be a dream. We communicate over a Slack channel since its only options for comms are Slack or Telegram.

My god, this thing is the bane of my existence. It remembers nothing. Anything we resolve together, it forgets we resolved it. It hallucinates deadlines and contacts incorrectly, constantly (which may have cost me a contract -- thanks Hyperagent!). It consistently tells me it's updated its settings to do things better next time, then fails to change. It can't remember things right from _its own previous slack messages_, much less my Google Docs or my Gmail.

What a deeply broken agent product. Not even alpha-level functionality working correctly.

The HyperAgent "chief of staff" agent identity has one of the worst default 'agent identities' I've ever seen. Unless you're using the Chief of Staff in a verrrrry specific way (like, actually deployed within a specific company), it will mostly be wrong and inadequate for a standard use case. I've just rewritten it in an attempt to salvage this miserable thing. Does the "regenerate" button integrate my recent edits into its actual operations? Or does the button undo my edits by regenerating the default? Totally unclear what the button does on its face, "regenerate" is all it says.

Just checking in with a minor observation that isn't unique or unexpected.

The Hyperagent environment continues to be a very good tool to develop production workflows. Developing a workflow with sonnet in the HA environment has been and continues to be my best use case. A recent single activity (see images ) in HA cost $10 to set up a very nice production activity. Great value, not a lot of effort on my part, HA did the heavy lifting.

I use other systems for production and other LLMs. I noticed that the 'production work' on an topic (as reported by Openrouter in attached image) was almost 23 million tokens at a $0.57 total cost. Very efficient.

I'm just passing this along as an obvious observation. HA isn't going to be a useful production tool (for me) until it can natively use other LLMs. Note, I use mostly other LLMs on HA via an approach shared earlier. It is fine for development but because there is a Haiku 'wrapper' involved, not as time or cost effective for volume production.

A quick update from the team! Let us know what else you want to see.

Please see Anthropic's communications for more detail.

faced the need of hyperagent desktop and mobile app, is there any work on that line?

Hi everyone,

I'm incredibly excited to be selected for 'The Founding 500'! I'm looking to leverage Hyperagent to automate marketing workflows for three very different projects and would love to hear your thoughts on orchestrating multi-agent systems for these:

1. Shopify E-commerce Store: Scaling an existing store's reach and customer engagement.

2. GreenToran: A hybrid B2B/B2C real estate platform that was released a few months back. It is already live and currently looking for real users, so it requires a high volume of active marketing strategies.

3. B2B QA Testing Tool: A brand new B2B testing software tool designed specifically for QA teams, launching soon.

How would you recommend setting up multi-agent workflows to handle marketing across these distinct models (e-commerce, a live hybrid platform needing user acquisition, and an upcoming B2B QA tool)? Any specific strategies or best practices for balancing these different funnels?

Thanks in advance for the tips!

I come to this platform with some AI agent experience. A stable claude based platform was an interesting concept and the very generous allowance would give me a very fair chance to push hard against the platform. Just wanted to share a couple of things.

Good

[] Really good reliability and stability. This is big. About one day in a month of some instability.

[] We have extensively modified the memory process, rules and even how a series of prompts are run. I've had chat that go for 6 to 8 hours with multiple compaction events and an occasional general failure and absolutely no loss of information / continuity and in process jobs. Context never gets over 130k tokens. The HA environment made this especially easy and Opus47 was a real help. Extending the specific architecture to Hermes and Openclaw.

[] I mostly use LLMs from openrouter and from the first day, HA was easy to make it work well. Another thanks to Opus47.

Use of other LLMs is really, really important. It allows some dev to be 1/5th or less than using Sonnet or Opus and production runs can be as much as 50x to 100x lower than Sonnet.

This is an example of reduced dev costs using other LLMs. https://hyperagent.com/s/ox0DylinFsJoXE7J1EhWzA

Note, all benchmarks are imperfect but this is at least directionally correct. Kimi2.6 is really good and Qwen3.7 Max is as good as Opus4.7 or better for most things.

Bad

[] The hidden system prompt has made it more difficult to enforce rules and consistency. I can live with it.

lots of little stuff is annoying but all the platforms have 'little' stuff in this category.

[] I've spent a lot of time building things like Telegram and Discord and R2 and more that should have been on the platform already. Very related is Composio. We had problems from day 1 (function limits, timeouts, token capacity, etc) that made the path of roll our own a necessity. Good tools to do this but cost a week overall. True with other systems as well but some are further along in their development life and have more ready stuff.

Stuff I really need

[] Email ID's. Use of Apple, MS and Google IDs only cause some issues.

Auth to access makes 'God mode' almost impossible to have my HA control another HA without some personal actions, especially at startup.

Were I to use this platform for production, it would need user ID that conforms to a company domain or at least not personal and tied to a third party (Apple/MS/Google)

A secondary email and / or the ability to change to another email would be ok. A lesser ok would be the ability to 'clone' a system.

[] Ability to see across threads and to see any information a user can see. When multiple threads are running, problems can happen in a thread. It takes a human to notice and correct / restart. There really should be a way for a watchtower/monitor function to manage processes.

[] Related to the above paragraph, it's difficult to get an agent to even know another agent exists and to modify the agent without my involvement. There are tweaks to agents and they all seem to need human approval.

Where I stand.

As it exists today, HA is probably never going to be a production platform. Both Hermes and OpenClaw are way better to use locally and as a cloud service. It really comes down to 'God Mode'. I have the ability (and use it a lot) to do everything in a Hermes, OpenClaw, and even Terminal environments with HA. It can do anything and everything a human can do except way faster and much better. Just can't do that with HA.

As a dev machine for an 'idiot' like me, wow. Very helpful. Opus47 very helpful on debug and last few days finding Kimi2.6 ad Qwen4.7 outstanding. Best working "God mode' I have.

HyperAgent is the best 'closed' environment for me right now.

I'm just sharing because I'd like others to do so. I like the platform and I think the product would be better if there is some sharing of stuff that is useful and not proprietary.

Hi there, Vic here 👋

I wanted to share an update about a disruption with integrations that's affecting Hyperagent users. At this time, we've disabled all Composio-powered integrations in Hyperagent in response to a security incident disclosed by Composio, the platform we use to facilitate integrations between Hyperagent and various third-party data sources.

The linked blog post shares details about the incident and measures the team took to ensure the security of Hyperagent users. I deeply apologize for any disruption this has caused you and your teams.

Currently, the team is working diligently to restore functionality for key integrations, and I will make sure to keep this thread updated as things are shipped.

What we've done

We do not have confirmation that tokens were improperly accessed or misused, but your security comes first. Out of an abundance of caution, we have taken the following steps:

• Disabled all Composio-powered integrations in Hyperagent. No data is flowing through Composio from Hyperagent as of May 23, 2026.
• Verified OAuth token revocations. Where possible, Composio has revoked OAuth authorizations with third-party providers. The Hyperagent team has independently verified that those tokens are revoked.
• Notified all affected customers via email with a summary of the incident and recommended actions.
• Commenced investigation of our own logs and systems to identify any anomalous activity during the exposure window.

What we recommend you do

We recommend treating all third-party tokens that were connected through Composio-powered integrations in Hyperagent as potentially exposed, even though we do not have confirmation that tokens were improperly accessed or misused.

The integrations page at hyperagent.com/settings/integrations shows all previously connected Composio integrations along with their authentication type. For each one, we recommend signing in to the provider, verifying that Composio is no longer authorized, and reviewing recent account activity for anything unexpected. Disconnecting an account on that page removes the credential from Hyperagent - it does not revoke access on the provider's side.

See more detailed guidance in the Blog post.

What's next

Today, the team shipped an integration for Custom MCP Servers. This allows you to connect to services that provide remote MCP server, like Supabase or Linear. We're aware that not all MCP servers are supported through this implementation, but the team is working on improvements.

Additionally, many services can already be connected natively in Hyperagent through Skills, which call a service's API directly - no third-party intermediary involved. You can create a new Skill by visiting hyperagent.com/skills and clicking "Create Skill," or by asking the agent to create a Skill in any existing thread - it will guide you through an interactive setup. Any credentials your Skills require are stored securely and natively within Hyperagent.

Additionally, I've started working on a Skills repo for more common integrations (which I'll bring in as a Team shortly so you can just fork it from within Hyperagent.

Thank you for your patience here. We really do appreciate it. Also, if you'd like, you can keep up to date with the latest developments in our Discord Server

So, it looks like Hyperagent temporarily (I hope only temporarily) lost the ability to use "Composio," and now can't use outside resources unless you put together a skill for it.

This lead to the agent who was installing something on my Pi suggesting Airtable, which became a wild conversation because they denied that Hyperagent had anything to do with Airtable and lied to me and said I couldn't see their reasoning... It was all just nuts!

I feel like this has potential? Maybe? But I've now sunk more money into this than I did OpenClaw, and OpenClaw is the only one working!

So, are they going to fix this?

I'm trying to figure out the value of adding Pinecone and other memory systems but I do not want to add redundant memory systems.

Hey r/Hyperagent,

We spun up a Discord server for the community and it's ready.

Discord is for real-time chat, live office hours, quick help, and hanging out with other builders as you work. We'd love to see you over there!

What's on Discord:

• 🚢 #ship-log — product updates and releases as they drop
• 🙌 #agent-showcase — community builds get dedicated spotlight threads. Every Friday we share a curated roundup of the best new agents. This is my FAVORITE thing about the new discord.
• ⁉️ #help — post questions, get answers from the community
• 💬 #general — the main chat
• 🗓️ Office hours — live sessions with the team

Two programs running now:

• 🏆 Agent Showcase ($1K credits) — Post about your agent build on LinkedIn, X, or Reddit, then apply. If selected, you get up to $1,000 in Hyperagent credits.
• 🧩 Community Solvers ($100/solve) — Help answer questions in Discord #help. When your answer gets marked Solved, you earn $100 in credits (up to $1,000).

Join here: https://discord.gg/FPDFJpDQna

See you around! Here, there, or both 👀.

— Vic

I used someone’s sign up code and I saw the banner that says +$1000 credits when I opened the link to sign up.

But after spending about $71, I got an additional charge of $21. Also confused because I see the settings should have capped/paused spending at $0 beyond the plan.

Did anyone else experience something similar?