Speculative Physical Robotics covers small public companies building, leasing, servicing, or financing physical robots before the business models are mature. The stack includes wearable assistive robots, sidewalk delivery fleets, restaurant and service robots, autonomous security robots, subsea robots, public-safety robots, and wearable Physical AI interfaces. The node matters only when those machines move from launch events, pilots, and demos into accepted deployments, reimbursed devices, fleet services, Robots-as-a-Service revenue, software revenue, backlog or remaining performance obligations, gross margin, cash conversion, clean filings, and restrained share issuance.
What the stack is: early commercial robotics hardware and operating services. It includes robotic orthoses, delivery robots, indoor health-care robots, hospitality robots, autonomous security robots, remotely operated subsea vehicles, unmanned ground vehicles, and wearable interfaces that translate human intent into machine action.
What it does in the parent chain: it tests whether the Physical AI theme can leave the lab and get paid in real customer workflows. Robots must assist a patient, deliver food, patrol a property, perform subsea work, or complete a public-safety or industrial task that a customer accepts and pays for.
Main pieces: sensors, cameras, motors, batteries, manipulators, vehicle frames, embedded compute, autonomy software, fleet operations, remote support, field service, payer authorization, customer contracts, and financing structures. The operating layer is as important as the robot body because service cost can absorb the revenue benefit.
Where it sits: physically at patient homes and clinics, sidewalks and campuses, hospitals, restaurants, security sites, subsea work sites, ports, smart-city deployments, and customer facilities. Operationally it sits between product development, customer acceptance, reimbursement or contract approval, field service, and public-company financing.
How the theme uses it: the parent Physical AI theme uses this node as the high-risk proof lane. Strong evidence is not a demo; it is recognized product, fleet, service, software, RaaS, or reimbursed revenue with margin and cash evidence.
Terms used later: RaaS means Robots-as-a-Service, where the customer pays for use or service rather than buying the robot outright. RPO means remaining performance obligations, or contracted revenue not yet recognized. Reimbursement means a payer-approved path to collect for a medical device. Deployment means a customer-accepted robot in use, not a prototype shown at an event.
Report boundary: this is a Level 1 watch-only node. The expanded basket is inherited from the parent Physical AI theme and remains a routing list, not a recommendation list. Selected-security right-rail charts call the report API with as_of=latest. The static setup levels in this page's older metadata were built from daily_ohlc through 2026-06-05, while read-only discovery now shows local rows through 2026-06-12; refresh setup thresholds before using them as current trading evidence.
Current Setup
Paid deployment gateRobotics visibility matters only when machines become revenue, margin, and cash.
The basket is watch-only because the companies still need cleaner evidence that deployments, reimbursement, RaaS, software, and services can cover field support, hardware cost, public-company expense, and financing dilution.
Best filed proofMYO has the strongest revenue and gross-margin evidence.
MyoPro is a reimbursed medical robotics route, so unit growth and payer access still decide the setup.
Cleanest robot fleetSERV has the clearest deployed robot-fleet evidence.
Daily active robots and supply hours are real, but gross loss and cash burn remain the conversion gate.
Primary constraintFiling, funding, and margin gaps dominate the lower ranks.
RR, KSCP, KITT, MCRP, and WETO need cleaner filings, customer proof, or runway evidence.
WorkflowPatient, fleet, site, subsea
Payment routeReimbursement, RaaS, service
Operating proofRevenue, margin, cash
Risk gateFilings, funding, dilution
Robotics validates the physical-AI theme when deployments become paid economics instead of product launches, pilots, or financing stories. The conversion mechanism is concrete: reimbursed MyoPro deliveries, deployed delivery robots and software services, RaaS and RPO, security-service retention, subsea-service contracts, accepted customer deployments, gross margin, operating cash flow, timely filings, and share-count discipline.
MYO has the best filed economics in the group: Q1 2026 revenue was $10.1 million, gross margin was 68.2%, recurring patient sources were 49% of revenue, and backlog was 226 units. SERV has the best pure robotics deployment evidence: Q1 revenue was $2.984 million, daily active robots reached 812, daily supply hours reached 10,295, and liquidity was $197.4 million. RR adds a RaaS/RPO route, KSCP has real security revenue after Event Risk, and KITT has actual subsea service revenue tied to marine autonomy.
Every name stays watch-only. MYO still needs unit growth and cash conversion. SERV needs fleet utilization to absorb service costs. RR needs a normalized delayed 10-Q. KSCP needs core technology margin, integration, and funding progress. KITT needs balance-sheet survival before autonomy claims can matter. MCRP needs a fresh 20-F and recognized revenue from named agreements. WETO needs official Orchestra customers, revenue, backlog, pricing, production plans, and unit economics.
Fundamental claims route to the physical-AI theme page, the seven security lanes, linked raw source projections, official filings, Nasdaq earnings-date checks, and read-only discovery checks listed in Source Trail. Selected-security charts use the right rail; this article body does not embed OHLC arrays.
Basket
The basket is ranked by source-backed robotics economics first, node fit second, and technical timing third. The ranking keeps MYO at the top for operating proof while flagging its medical-reimbursement route. SERV is the cleanest physical-robotics deployment story but needs unit economics. RR and KSCP have revenue routes with filing, margin, and funding gates. KITT, MCRP, and WETO need stronger filings, contract conversion, or customer-level robotics economics before the page can treat price moves as evidence.
Wearable medical robotics name with the strongest filed revenue, gross-margin, backlog, and reimbursement evidence in this speculative basket.
Market cap$32.0M
Next earningsNot confirmed
Latest qtr revenue$10.1M
Role in stack
MYO sells MyoPro powered upper-limb orthoses to patients through payer, provider, O&P, VA, and referral channels. Theme pressure becomes economics when authorizations become fabricated, delivered, reimbursed devices with backlog conversion, high gross margin, and lower cash use.
Revenue mix
Q1 2026 revenue was shaped by Medicare Part B at 51% of revenue and recurring patient sources at 49%. This is a health-care reimbursement route, not a direct defense-autonomy route; payer access, recognized units, ASP, and cost per patient acquisition remain the caveats.
Latest qtr revenue
Q1 2026 revenue was $10.1M in the MYO lane's Q1 release and 10-Q source trail. The same lane cites 172 recognized units, about $58.8K ASP, 68.2% gross margin, 226 backlog units, and Q2 2026 revenue guidance of $10.3M-$10.8M.
Best pure deployed robot-fleet exposure, with real operating KPIs but still severe gross-loss and burn hurdles.
Market cap$678.1M
Next earningsNot confirmed
Latest qtr revenue$2.984M
Role in stack
SERV operates sidewalk delivery robots and indoor health-care automation after the Diligent acquisition. The company gets paid through fleet services and software services; conversion depends on robot utilization, route density, customer economics, service gross margin, and lower operating cash use.
Revenue mix
Q1 2026 revenue was $1.958M fleet services and $1.026M software services. Daily active robots reached 812 and daily supply hours reached 10,295, but the same filing shows a $9.001M gross loss and $41.422M operating cash use.
Latest qtr revenue
Q1 2026 revenue was $2.984M in the SERV lane's Q1 2026 10-Q, release, and transcript source trail. Management reaffirmed about $26M of FY2026 revenue, making Q2/Q3 revenue density and gross-loss narrowing the next evidence.
Commercial robotics and RaaS optionality with cash runway, small revenue, delayed filing risk, and dilution history.
Market cap$590.3M
Next earningsNot confirmed
Latest qtr revenue$1.147M
Role in stack
RR sells, leases, and services commercial and industrial robots through hardware sales, leasing/service/rental, RaaS, and data-services ambitions. Theme pressure becomes economics only if deployments, RaaS revenue, RPO, service absorption, and clean filings scale faster than share issuance.
Revenue mix
Q1 FY2026 revenue was product sales $357K, leasing/service/rental $405K, RaaS $319K, and other revenue $66K. RaaS RPO was $1.722M, with $870K expected within 12 months, but the March 31, 2026 10-Q delay remains the freshness gate.
Latest qtr revenue
Q1 FY2026 revenue was $1.147M in the RR lane's latest complete filing source. The next filing must refresh revenue, gross margin, cash burn, controls, share count, RaaS/RPO, and any Dex or data-services commercialization evidence.
Autonomous security and acquired guarding services route with real revenue scale but going-concern and dilution pressure.
Market cap$48.7M
Next earningsNot confirmed
Latest qtr revenue$6.016M
Role in stack
KSCP combines autonomous security robots, emergency communication devices, monitoring software, and Event Risk human-security services. The node works only if customer retention, KSF service margin, ASR/ECD adoption, contract conversion, and financing terms improve together.
Revenue mix
Q1 2026 revenue was Core Technology $3.665M and Acquired Security Force $2.351M. Core Technology produced only $54K of gross margin, while the acquired services segment provided most of the positive gross profit.
Latest qtr revenue
Q1 2026 revenue was $6.016M in the KSCP lane's Q1 filing and release source trail. Cash was $11.401M, Q1 operating cash use was $11.604M, and the filing retained going-concern language.
Subsea autonomy route with actual service revenue, but survival, liabilities, and conversion mechanics dominate the read.
Market cap$9.7M
Next earningsNot confirmed
Latest qtr revenue$0.160M
Role in stack
KITT brings SeaTrepid ROV services, Aquanaut vehicles, ToolKITT autonomy software, Olympic Arm work, defense optionality, and UAE/GCC ambitions into the node. The mechanism is funded subsea work or software licensing, not technology claims alone.
Revenue mix
The company reports one segment. FY2025 revenue was $5.27M, largely helped by SeaTrepid ROV services. ToolKITT, Aquanaut, defense, and international claims remain early until filings show signed contracts, pricing, customer count, gross margin, and collections.
Latest qtr revenue
Q1 2026 revenue was $159.575K in the KITT lane's Q1 2026 10-Q source trail, against $1.994M cost of revenue. The same filing showed $5.89M cash plus restricted cash, $35.35M current liabilities, and $7.0M operating cash use.
UAE public-safety and industrial robotics option where current audited revenue proof is stale and still immaterial.
Market cap$92.8M
Next earningsNot confirmed
Latest qtr revenue$16K H1
Role in stack
MCRP develops autonomous mobile robots, unmanned ground vehicles, edge-compute modules, and smart-infrastructure robotics for public-safety, industrial, port, and smart-city uses. The node requires accepted deployments, recognized revenue, collections, and current audited liquidity before announcements carry weight.
Revenue mix
Filings do not yet provide useful segment economics. EMSTEEL, AfricAI, QSS/Saudi MOI, DP World, UMEX, and NVIDIA-related releases are pipeline evidence, but the lane has no current audited proof that those agreements became revenue and cash collections.
Latest qtr revenue
No current quarterly revenue filing was available in the local lane. The latest detailed interim support is H1 2025 revenue of about $16K, after FY2024 revenue of about $35K; the delayed 2025 Form 20-F is the decisive source refresh.
Weakest robotics proof in the basket because filings still show legacy travel revenue and no disclosed Orchestra revenue.
Market cap$38.9M
Next earningsNot confirmed
Latest qtr revenueRMB9.6M H1
Role in stack
WETO is trying to pivot from packaged tours, chartered bus, and commuter shuttle service into Orchestra Physical AI hardware and wearable interfaces. The node becomes relevant only if the company discloses named paying customers, product revenue, backlog, pricing, production, and unit economics.
Revenue mix
H1 FY2026 revenue was packaged tours RMB8.178M, chartered bus RMB1.184M, and commuter shuttle RMB0.200M. The local source pass found no disclosed Orchestra revenue, so current revenue does not yet validate the robotics pivot.
Latest qtr revenue
No current quarterly robotics revenue was available in the local lane. The latest interim support is H1 FY2026 revenue of RMB9.563M from the WETO 6-K source trail, with RMB11.4M net loss, RMB0.727M cash, and RMB21.7M current borrowings.
Market caps come from a read-only discovery instruments query on 2026-06-13 and should be treated as local reference data. Nasdaq earnings pages checked on 2026-06-13 showed no available next earnings date for all seven tickers, so each card is labeled Not confirmed. Latest-quarter revenue fields use the linked security lanes and official filing/release source trails; MCRP and WETO lack current quarterly robotics revenue, so their cards label the latest interim revenue limitation directly.
What Confirms Or Weakens
AreaWhat confirmsWhat weakens or invalidatesWatch next
01Node thesis
Machines get paid
What confirms
Robots or robotic devices show up as recognized product revenue, reimbursed units, fleet services, software services, RaaS, service revenue, backlog, RPO, or customer-accepted deployments.
What weakens or invalidates
Demos, launches, pilots, LOIs, or financing headlines arrive without named customers, accepted units, revenue, backlog, pricing, production, margin, or cash evidence.
Watch next
MYO recognized units
SERV active robots
RR RaaS/RPO
MCRP 20-F
02Revenue economics
Growth covers cost
What confirms
Gross margin expands, service cost per robot falls, RaaS and software revenue recur, and operating cash use narrows as revenue grows.
What weakens or invalidates
Revenue growth comes from ASP, acquired services, one-time projects, or legacy non-robotics lines while gross losses, field support cost, or operating cash burn stay too large.
Watch next
MYO gross margin
SERV gross loss
KSCP segment margin
KITT cost of revenue
03Customer conversion
Named demand becomes accepted work
What confirms
Customer names, contract terms, reimbursed deliveries, repeat orders, retention, RPO conversion, production cadence, accepted deployments, and collections tie the robot to paid use.
What weakens or invalidates
Customer references stay at pilot, LOI, launch, demo, or publicity level, or filings do not connect agreements to recognized revenue and cash collections.
Watch next
MYO payer authorization
SERV merchant density
RR deployments
WETO Orchestra customers
04Funding and reporting
Runway stays investable
What confirms
Delayed filings are cured, Nasdaq compliance is resolved, cash bridges planned deployments, share count stays controlled, and new capital supports revenue conversion without overwhelming dilution.
What weakens or invalidates
Late filings persist, going-concern language dominates, ATM or PIPE usage becomes the operating plan, reverse splits reset price without business proof, or controls/audit issues worsen.
Watch next
RR delayed 10-Q
KSCP ATM and cash
KITT conversions
WETO ATM usage
05Operating constraint
Hardware and service burden
What confirms
Manufacturing, field service, uptime, warranty, component supply, hospital or public-site workflow, and support staffing improve without raising unit cost faster than revenue.
What weakens or invalidates
Robot availability, component cost, field support, reimbursement friction, service labor, warranty, or customer workflow complexity prevents deployment scale from producing margin.
Watch next
Service cost per robot
Backlog conversion
Support labor
Warranty and uptime
06Stale condition
Refresh trigger
What confirms
Discovery daily_ohlc remains current through 2026-06-12, and no new filing, contract, financing, listing, earnings-date, or customer disclosure arrives before the next refresh.
What weakens or invalidates
A completed trading week, delayed filing, 20-F, ATM update, Nasdaq notice, customer release, revenue update, or earnings announcement arrives before the page is refreshed.
MYO latest-quarter revenue: Q1 2026 revenue $10.1M from the MYO lane's Q1 release and 10-Q source trail.
SERV latest-quarter revenue: Q1 2026 revenue $2.984M from the SERV lane's Q1 2026 10-Q, release, and transcript source trail.
RR latest complete quarter: Q1 FY2026 revenue $1.147M from the RR lane's Q1 FY2026 10-Q source; the March 31, 2026 10-Q delay remains the current filing limitation.
KSCP latest-quarter revenue: Q1 2026 revenue $6.016M from the KSCP lane's Q1 2026 filing and release source trail.
KITT latest-quarter revenue: Q1 2026 revenue $159.575K from the KITT lane's Q1 2026 10-Q source trail.
MCRP latest interim revenue: H1 2025 revenue about $16K, with FY2024 revenue about $35K; no current quarterly revenue filing was available because the 2025 Form 20-F is delayed.
WETO latest interim revenue: H1 FY2026 revenue RMB9.563M from the WETO 6-K source trail; the local source pass found no disclosed Orchestra revenue.
Each Nasdaq page showed no available earnings date at the time checked, so every Basket card uses Not confirmed. No estimated date was substituted.
Discovery And Chart Provenance
Read-only DuckDB check on 2026-06-13 queried instruments for market cap and daily_ohlc coverage for MYO, SERV, RR, KSCP, KITT, MCRP, and WETO.
Local daily_ohlc rows run through 2026-06-12 for all seven tickers: MYO, SERV, RR, KSCP, KITT, MCRP, and WETO.
Selected-security chart route: /api/securities/{ticker}/chart?frequency=weekly&window=3y&as_of=latest. The API is expected to return weekly bars from daily_ohlc using first open, maximum high, minimum low, final close, and summed volume.
Chart assumptions: three-year visible horizon where history exists, 20-week EMA, 100-week EMA when enough weekly history exists, weekly volume, and 20-week average volume. MCRP and WETO lack enough history for a 100-week EMA; KSCP and KITT long-term EMAs are distorted by split-adjusted downtrends.
Representative API check on 2026-06-13 for /api/securities/MYO/chart?frequency=weekly&window=3y&as_of=latest could not be completed: python -m api.run started uvicorn on 127.0.0.1:8765, but the validation curl returned connection refused from this tool environment. Static API attributes, chart triggers, route metadata, and absence of embedded OHLC payloads were verified.
Known Gaps
Static setup labels, triggers, and invalidation levels in the old node metadata were based on 2026-06-05 chart inputs and are stale versus local daily_ohlc through 2026-06-12.
MCRP and WETO do not have current quarterly robotics revenue in the inspected local lanes; their Basket cards explicitly use latest interim revenue and state the limitation.
RR remains gated by a delayed March 31, 2026 10-Q. MCRP remains gated by a delayed 2025 Form 20-F. WETO remains gated by no disclosed Orchestra customer, revenue, backlog, pricing, production, or unit economics.
No nodes/node-data.json exists for this physical-AI node family, and no generator script was found that owns this family. Parent report and sitemap metadata remain deferred by scope: both still carry older speculative-robotics discovery references built from the 2026-06-05 static setup package.