The swarm
1 of 100 agents working- Orchestrator
IMD #2
starteddiscover14 agents13 answered · 1 workingwhat each agent was asked
Find every company in this segment that builds humanoid robots: {{segment}}. Starting points: {{hints}}. Then search the open web (company sites, trade press such as The Robot Report and IEEE Spectrum, funding news, exhibitor lists from CES, ICRA, the World Robot Conference in Beijing, Humanoids Summit, investor lists such as the Morgan Stanley Humanoid 100 and The Humanoid Hub) until new searches stop turning up new names. A company counts when it designs and builds its own general-purpose humanoid robot: a torso with two arms and a head on legs or a wheeled base, meant for sale, deployment or research use, as a product or a publicly shown prototype. Automaker and big-tech divisions, listed companies and startups all count. Do not count pure component makers (actuators, hands, sensors), software-only or foundation-model companies without their own robot, universities and research institutes, hobby projects, single arms, exoskeletons, or small toy or education humanoids under 60 cm unless the company also builds a larger one; list such doubtful cases with include set to "borderline" and a one-line reason instead of dropping them. Use the company's official English name without legal suffix (Inc, Ltd, GmbH, Co) as its canonical name; for Chinese companies use the English name the company itself uses and put the Chinese name in note. Open every source_url you cite and confirm it shows the company building a humanoid; a company you cannot source is left out. Result: one JSON object and nothing else: {"segment": string, "companies": [ {"company": string, "hq_country": string (English short country name), "website": string, "humanoid_product": string (robot name and one phrase on what it is), "founded_year": integer or null, "source_url": string, "include": "yes" or "borderline", "note": string} ], "sources_checked": [ strings, the URLs you used ]}. Up to 120 companies per result.
- usa
IMD #1975answered · 27 KB
- canada-latam
IMD #91answered · 14 KB
- china-startups
IMD #1540answered · 45 KB
- china-corporates
IMD #722answered · 43 KB
- japan
IMD #1275answered · 22 KB
- korea
IMD #487answered · 15 KB
- europe-west
IMD #1206answered · 7.6 KB
- europe-other
IMD #1168answered · 15 KB
- india-mideast-africa
IMD #804Codex
5 earlier messages
I’ll search across the region, verify candidate companies against opened sources, and write the two requested JSON files with uncertain cases marked as borderline.
The initial results include several service-robot builders alongside industrial humanoid developers. I’m checking which companies build their own hardware, since some regional ventures only distribute foreign robots or announce future development plans.
I’ve verified more Indian builders and found useful boundary cases: fixed-base dual-arm systems, headless humanoids, and companies whose current headquarters appear to be outside the region. I’m recording those distinctions so the merged map can avoid double-counting and overstating eligibility.
The regional and event searches are now mostly returning names already found, resellers, or university projects. I’m finishing checks on the remaining candidates and their citations. I couldn’t find a humanoid builder called “Vegavisor,” so I’ll leave that name out rather than guess a match.
The main remaining uncertainty is who owns the hardware design. I found that South Africa’s IRIS shares development with India’s Makerlabs, and the UAE’s Bu Sunaidah uses a Unitree G1. I’ll make those relationships explicit so they aren’t mistaken for separate original robot platforms.
I’m assembling the JSON now. The records distinguish shown robots from planned products, stationary platforms, education kits, and hardware integrators. Unknown founding years remain null, and each uncertain inclusion has a specific reason.
Brewing… - asia-other-oceania
IMD #599answered · 23 KB
- trackers-lists
IMD #650answered · 41 KB
- automakers-bigtech
IMD #626answered · 7.6 KB
- funding-news-2025-2026
IMD #747answered · 47 KB
- open-hardware-spinouts
IMD #22answered · 23 KB
- merge 01
IMD #1576answered · 64 KB
startedprofile-pilot5 agents5 answeredwhat each agent was asked
Profile one humanoid-robot company: {{company}} ({{hint}}). Use only public web sources and give a URL for every figure: the company's own site, filings (SEC, HKEX, SSE), press releases, then reputable press (Reuters, Bloomberg, FT, TechCrunch, The Robot Report, IEEE Spectrum, 36Kr for China). Fill exactly one row of the table you are given, keyed by company = "{{company}}". what_it_builds: one or two sentences on its humanoid line and intended use. hq_country: English short country name of the headquarters. founded_year: year of incorporation. funding_usd: total disclosed equity capital raised to date in US dollars, the sum of the rounds you list in funding_note, each with its date, amount and URL; convert other currencies at the rate of the announcement date and state the rate; exclude debt, grants and valuation. funding_basis: one of "disclosed rounds", "public company", "parent funded", "undisclosed". If the company is listed or a division and discloses no humanoid-specific raise, leave funding_usd empty, set funding_basis accordingly and give IPO proceeds or parent in funding_note. latest_funding_date: date of the newest round. valuation_usd: the latest reported post-money valuation, else empty. latest_model: the newest humanoid model publicly announced, with latest_model_year and latest_model_source. units_shipped: only a number the company, a filing or a named reputable report has published (delivered, sold or deployed units; say which, with the date, in units_shipped_note); never an estimate; empty when no public figure exists. status: "active", "acquired" or "defunct". as_of: today's date. Every *_source column is one URL that actually shows the figure in the same row; open each URL to confirm; a figure without a source is left empty rather than guessed. Put the row and nothing else in your JSON result.
all 5 answers
- figure-ai
IMD #613answered · 2.7 KB
- agility-robotics
IMD #750answered · 2.1 KB
- unitree
IMD #1710answered · 1.5 KB
- 1x-technologies
IMD #1001answered · 2.9 KB
- ubtech-robotics
IMD #1443answered · 2.5 KB
- usa
- Orchestrator
Waits for its teams to answer, then reads what they found and plans the next round.