MechaSeed Agent Core · Concept · Demand Validation

Print the body.We provide the intelligence.

A pre-configured motion, sensing and compute core for 3D-printed robots.

Agent-ready by design, with target hardware and software matched to a specific Body Profile.

Starting with small bipeds · first Body Profile not yet selected

We are validating which printable body to support first. No Body Profile or hardware specification has been verified for production.

MicroDuck reference × Core mapOfficial Pollen Robotics photo · color = target MechaSeed layer · third-party robotPhoto source ↗

Body + Core

You print the structure. We match the hard systems.

A Body Profile defines the boundary. MechaSeed would prepare the motion, electronics, sensing and software for one exact printable-body revision.

You print

Specific body revision

Legally obtained files · structure · ordinary mechanics · final assembly

MechaSeed targets

Profile-matched Core

Actuators · board · compute · sensors · wiring · power · software

You build

Programmable robot

Assembly checks first · agent experiments next

Why not just buy the parts?

Parts are the input. Integration is the product.

Target comparison. A parts-only build may use capable components, but you remain responsible for making them work together for a specific body.

Integration taskParts-only sourcingMechaSeed Agent Core · target
Actuator fitYou select and verifyMatched to the selected profile
Servo IDs + busYou configureTarget configuration prepared
Joint mapYou defineMapped to the body revision
Joint directionsYou testReference directions documented
WiringYou design and sourceProfile-matched harness target
Body ProfileYou create and maintainVersioned integration layer
CalibrationYou build the processReference profile + assembly checks
Sensors + firmwareYou integratePlanned as one tested stack
SDKYou write the interfaceTarget Agent interface + examples

Body Profiles

Compatibility becomes a versioned profile.

Choose a supported printable body. We provide the matched hardware profile. That is the intended model; today, the first profile is still being selected. No Body Profile is verified as supported.

  1. 01

    Choose body

    Select a researched printable body and exact revision.

  2. 02

    Match profile

    Use the hardware and configuration mapped to that revision.

  3. 03

    Install core

    Assemble the actuators, wiring, compute and sensors.

  4. 04

    Verify assembly

    Check zero positions and directions before programming.

Research candidate

MicroDuck

Interest signal only · support not verified

Research candidate

Open Duck Mini

Interest signal only · support not verified

Research candidate

Another community body

Interest signal only · support not verified

Future asset

MechaSeed Hardware Profile Library

A profile records the assumptions that make configuration repeatable. It is a planned product layer, not a downloadable library or working CLI today.

  1. 01
    Body

    Body name, revision and printable geometry

  2. 02
    Actuator

    Models, mounts, IDs, bus and joint directions

  3. 03
    Wiring

    Harness, pinout, sensors and power path

  4. 04
    Calibration

    Reference offsets plus assembly checks

  5. 05
    Simulation

    Joint model and target MuJoCo configuration

  6. 06
    Agent Interface

    Firmware, state and proposed SDK surface

Assembly still matters. Factory actuator settings and reference offsets reduce setup work; every finished robot still needs zero-position and direction checks. Change the body geometry, link lengths, joint directions or actuator model, and the original profile must be reassessed.

Target integration scope

What's in the Core

Target pricing: TBD

One concept product for community-built small bipeds. Categories below are feasibility targets, not finalized specifications or items available to order.

Actuators

Matched smart actuators with target IDs and bus settings

Board

Control board, actuator bus and profile-matched wiring

Compute

ARM-based compute for state, firmware and agent integration

Sensors

Camera, IMU, distance sensing, microphone and speaker

Power

Power management and battery interface targets

Join the Founding Waitlist

Agent Ready

Hardware through a legible interface.

AI / Agent → MechaSeed SDK → Agent Core → matched actuators → your profile-matched printed robot.

Proposed API

See. Hear. Speak. Move.

Vision, audio, distance, motion and robot state are planned as one software surface.

Proposed API — final SDK may change.
robot.see()
robot.hear()
robot.speak("Hello")
robot.move()
robot.look_at(target)
robot.distance()
robot.state()

Demand Validation

Evidence before hardware.

The waitlist decides whether a Body Profile earns feasibility work. Only Stage 1 is current.

  1. 01

    Current

    Validate Demand

    Founding waitlist + Body Profile research
  2. 02

    Planned

    Hardware Feasibility

    Supplier evaluation and engineering quotation
  3. 03

    Planned

    Founding Reservations

    Validate willingness to pay
  4. 04

    Planned

    Engineering Prototype

    Work with a manufacturing / engineering partner
  5. 05

    Planned

    Pre-order / Crowdfunding

    Fund production
  6. 06

    Planned

    Manufacturing

    Pilot batch and delivery

Stage 1 — Current

Choose what we profile first.

Join with your email. The optional next step asks which body MechaSeed should evaluate first, plus format, budget, timing and reservation intent.

Get demand-validation updates, early access, and future feasibility news. Unsubscribe anytime. By joining, you ask to receive these emails and acknowledge our Privacy Policy.

Clear answers

Before you join.

Can I use any 3D-printed robot body?

No. The target model is a set of versioned Body Profiles. Each profile would match a specific body revision, actuator layout, wiring plan and configuration. A modified or unsupported body would need a new fit and calibration assessment.

Does profile-matched mean zero calibration work?

No. MechaSeed would prepare actuator and reference configuration for a Body Profile, but every finished assembly still needs zero-position and direction checks. Print tolerances, installation and structural changes can require recalibration.

What would the Agent Core include?

The target combines matched actuators, control electronics, compute, sensing, power, a Body Profile, firmware and SDK examples. The final specification may change after feasibility work.

Is MicroDuck supported?

No body is verified as supported yet. MicroDuck is one research candidate and remains a third-party reference in our guide. Waitlist feedback helps decide what to evaluate first.

Can I buy it now?

No. MechaSeed is at Stage 1 — Validate Demand. The waitlist and optional survey record interest; they are not an order, reservation or payment.