For each: what it builds, disclosed funding in USD, founding year, HQ country, latest model, and units shipped if public, each with a cited source. Gather them as one table keyed by company, with total funding. Then write a ranking of who is ahead and why.

The swarm

1 of 100 agents working
liveround 11 working19 answered100 agents at most
  1. OrchestratorIMD #2round 1

    EPISODE 1 (2026-11-03). Fresh goal: 1000 items, 100 workers, 15 episodes, nothing run yet. Plan in four phases: (1) DISCOVER the universe of humanoid-robot companies, (2) PROFILE each company into one table row (the goal's table), (3) VERIFY the figures the ranking stands on, (4) FINISH and write the table plus ranking. DEFINITION used in every brief (keep it stable): a company counts when it designs and builds its own general-purpose humanoid robot (torso, two arms, head, on legs or a wheeled base) meant for sale, deployment or research use, as a product or a publicly shown prototype; automaker/big-tech divisions, listed companies and startups all count. Excluded: component makers (actuators, hands, sensors), software-only/foundation-model firms with no robot of their own, universities/institutes, hobby projects, single arms, exoskeletons, small toy/education humanoids under 60 cm. Doubtful cases are listed with include=borderline and a reason, so the orchestrator decides, not the worker. Canonical name = official English name without legal suffix; Chinese companies by the English name they use themselves. SPAWNED THIS EPISODE (19 items): batch `discover`, 14 research items, json output, merge groupSize 7 (so merges merge-01 and merge-02). One item per region or source type: usa, canada-latam, china-startups, china-corporates, japan, korea, europe-west, europe-other, india-mideast-africa, asia-other-oceania, trackers-lists, automakers-bigtech, funding-news-2025-2026, open-hardware-spinouts. Overlap between items is intended; the merge dedups. Batch `profile-pilot`: 5 table items (figure-ai, agility-robotics, unitree, 1x-technologies, ubtech-robotics) that test the profile brief and the table shape on a US startup, two US/Norway startups, a Chinese private firm and a HK-listed company (public-company funding handling). Table columns: company(key), hq_country, website, status, what_it_builds, what_it_builds_source, founded_year, founded_source, funding_usd (USD, totalled, optional), funding_basis, funding_source, funding_note, latest_funding_date, valuation_usd, latest_model, latest_model_year, latest_model_source, units_shipped (optional), units_shipped_source, units_shipped_note, as_of. Reads requested: every discover item, both merges, all 5 pilot rows. Wake when both batches settle or after 180 minutes. EPISODE 2 SHOULD: (a) Check goal.json for refusals. If `profile-pilot` was refused because the plane does not keep datasets (table unsupported), re-spawn the profile batch as plain json output with the same fields and merge groupSize 20 into a table. If `discover` paused in canary, read its failures and mend the brief (likeliest problems: JSON too big -> raise maxBytes or cut per-item cap; dead source URLs -> demand the worker open each URL). (b) Read discover/merge-01 and merge-02 (and the items if merges are thin), build the canonical company list: include=yes rows plus borderline rows that fit the definition; dedup by name/website. Expect roughly 120-250 companies (China alone has 60+; the Morgan Stanley Humanoid 100 and The Humanoid Hub lists are good cross-checks). (c) Read the 5 pilot rows: check sources are real URLs, funding sums match the listed rounds, units_shipped is only ever a published figure. Mend the brief where the rows show a weakness, then spawn `profiles-a` (new name) with the full company list, one item per company, the same table shape (column names must match exactly so the write-up can union datasets), groupSize ~20, maxRows 1. Keep ~400 items of budget for later verification and gap-filling. (d) If the discovery list is clearly incomplete in one region, spawn a second targeted discover batch (new name, e.g. `discover-2`) alongside. EPISODE 3-5 SHOULD: read profiles failures and disputed cells; re-run failed items with a mended brief via itemsFrom; spawn `verify-top` with replicas {size:3} for the ~30 best-funded companies (funding_usd, valuation_usd, units_shipped, latest_model) since the ranking rests on those; spawn a `signals` batch for the top ~25 collecting ranking evidence not in the table (paid deployments and named customers, production capacity/targets, headcount, notable demos, autonomy claims vs teleoperation) with sources, output markdown, so the ranking has reasons. Then finish (target episode 6-8) and write: one table keyed by company with total funding from the dataset totals, ranking with criteria stated (funding, units shipped/deployed, latest model maturity, customers, manufacturing scale), and a list of what is missing (companies with no disclosed funding, disputed cells). BUDGET NOTE: 19 of 1000 items used after this episode. Do not spend more than ~350 on profiles, ~120 on replicas/verification, ~60 on signals; keep a reserve for re-runs.

    starteddiscover14 agents13 answered · 1 working
    what 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.

    • usaIMD #1975answered · 27 KB
    • canada-latamIMD #91answered · 14 KB
    • china-startupsIMD #1540answered · 45 KB
    • china-corporatesIMD #722answered · 43 KB
    • japanIMD #1275answered · 22 KB
    • koreaIMD #487answered · 15 KB
    • europe-westIMD #1206answered · 7.6 KB
    • europe-otherIMD #1168answered · 15 KB
    • india-mideast-africaIMD #804Codex
      5 earlier messages
      1. 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.
      2. 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.
      3. 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.
      4. 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.
      5. 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-oceaniaIMD #599answered · 23 KB
    • trackers-listsIMD #650answered · 41 KB
    • automakers-bigtechIMD #626answered · 7.6 KB
    • funding-news-2025-2026IMD #747answered · 47 KB
    • open-hardware-spinoutsIMD #22answered · 23 KB
    • merge 01IMD #1576answered · 64 KB
    startedprofile-pilot5 agents5 answered
    what 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
  2. Orchestratorround 2

    Waits for its teams to answer, then reads what they found and plans the next round.

  1. Posted1 h 8 minto the first attempt
  2. Orchestrate 001Agent #2made 1 file

    All checks passed. The git status call failed only because the sandbox blocks reading the global git config, which does not affect the deliverable. The file is written and left untracked for the daemon to upload.

    Outcome: episode 1 decisions are written to artifacts/goal/episodes/001/decisions.json as one JSON object in the reference shape.

    What it decides

    • Batch discover (14 research items, json, merged in groups of 7). One item per region or source type: USA, Canada and Latin America, China startups, China listed and corporate, Japan, Korea, Western Europe, other Europe, India/Middle East/Africa, other Asia and Oceania, public trackers and indexes, automaker and big-tech programmes, funding news since January 2025, and open-hardware and spin-outs. Each item returns a JSON list of companies with country, website, product, founding year, a verified source URL and an include flag. The brief fixes one definition of "builds humanoid robots" and routes doubtful cases to a borderline flag rather than letting workers drop them.
    • Batch profile-pilot (5 table items): Figure AI, Agility Robotics, Unitree, 1X Technologies and UBTech Robotics. This tests the per-company table brief on a mix of US, Norwegian, Chinese private and Hong Kong listed companies before it is spent on hundreds. The table has 21 columns covering the goal's fields plus a source URL for each figure, funding basis and notes, with funding and units shipped as totals.
    • Reads for the next episode: all 14 discover items, both merges, and the 5 pilot rows. Wake when both batches settle or after 180 minutes. Not finished.

    Checks run locally

    CheckResult
    Notes length4,780 of 8,000 chars
    Longest filled brief2,385 of 3,000 chars
    Items spent19 of 1,000
    Reads requested21 of 30
    Column names, types, key, totalsvalid

    Next episode's plan is in the notes: build the canonical company list from the merges, mend the profile brief from the pilot rows, spawn the full profile batch under a new name with the identical column set, then verify the top companies with replicas and gather ranking evidence before finishing around episode 6 to 8. The notes also say what to do if the plane refuses the table batch.

    ran onclaude · claude-fable-5-1 · 6 turns · 3m 42s · 98 in · 16.3K out · 172.7K cached
    submission3bd6a3cff21f0f707486a70fd5338204dd413670cbaf30e6970f48d88b46a92f
    device468e82a89b9bfe188ef46b055e2ea554bde626cc162630c20effb0fcc7e13fed
    started from0243d7da4a4337ae8b16bcdf15bb4ead736fd68f
    bundlenone
    verifiedrebuilt and matched · verifier 0.1.0 ·
    made · 1 file
    artifacts/goal/episodes/001/decisions.json · 19 KB
    may write
    artifacts/goal/episodes/001/**
  3. Items18 of 19 items accepted1 running
    discover/asia-other-oceaniaAgent #599made 2 files
    discover/automakers-bigtechAgent #626made 2 files
    discover/canada-latamAgent #91made 2 files
    discover/china-corporatesAgent #722made 2 files
    discover/china-startupsAgent #1540made 2 files
    discover/europe-otherAgent #1168made 2 files
    discover/europe-westAgent #1206made 2 files
    discover/funding-news-2025-2026Agent #747made 2 files
    discover/india-mideast-africaAgent #804 buildingattempt 2
    discover/japanAgent #1275made 2 files
    discover/koreaAgent #487made 2 files
    discover/open-hardware-spinoutsAgent #22made 2 files
    7 more
  4. Merge b01 01Agent #1576made 1 file

    {"output":"artifacts/goal/batches/discover/merges/01/result.md","companies":296,"bytes":63997,"validation":"JSON parsing and merge checks passed"}

    ran oncodex · 4 turns · 6m 20s · 78.6K in · 13K out · 990.1K cached
    submission022d96b5a0aead1287546668adc866310710ee0a0b3371ba72cad788d6f75281
    device6412d5c37aa6592f06eb01311ad33f383bc15f6fc3417f0c7fcb5d0a95fb2903
    started from0243d7da4a4337ae8b16bcdf15bb4ead736fd68f
    bundlenone
    verifiedrebuilt and matched · verifier 0.1.0 ·
    made · 1 file
    artifacts/goal/batches/discover/merges/01/result.md · 64 KB
    may write
    artifacts/goal/batches/discover/merges/01/**
  5. Publishedafter verification

Outputs

38 files accepted

File integrity and allowed paths were checked. Content accuracy and quality were not evaluated.