On this page
Partner information
Skyzai data room
The proposal, the responsibilities and the evidence behind an agent-first marketplace. Public materials for prospective robotics partners.
Start with the proposal
Public materials. Confidential agreements and partner data are not hosted here. Marketplace capabilities describe a proposed programme, not operating services.
Skyzai for robotics
An HTML pitch covering product twins, source-linked assistance, order books, Menexus XaaS and sales-funded affiliate distribution.
Read the presentation as a continuous page, or switch to slide view. No PDF download or account is required.
A bounded first agreement
The ambition is a common buying interface across leading robotics manufacturers. The first proposed agreement is a non-exclusive design-partner pilot for one product family and one procurement job.
- Product and data. Approve exact variants, documents, licensed spatial assets and update owners. Confidential CAD stays under manufacturer control.
- Commercial responsibilities. Name the seller, territory, inventory authority, delivery, installation, acceptance and remedies. Agree fees and customer relationships explicitly.
- Support and lifecycle. Define escalation, warranty and any qualifying Menexus XaaS offer, with accountable providers.
- Measurement and exit. Agree thresholds before starting; measure answer quality, buyer outcomes and manufacturer contribution margin. Include termination and portable records.
This is a drafting scope, not a contract for signature. No manufacturer partnership or service commitment is established by this room.
One price, explicit responsibilities
Exact-configuration order books expose eligible buyer bids and seller asks. Makers can publish offers or sell into qualified demand. Custom systems may begin with requests for quotation. Order books may reduce reliance on promotions; they do not eliminate discounts, negotiation or no-fill risk.
Every proposed listing must offer a qualifying Menexus XaaS route. Most physical products would be purchased with an optional, separately priced monthly lifecycle companion; selected products may instead offer subscription access. Insurance and upgrade rights require named providers, funding, eligibility and agreed terms. No coverage is offered here.
Keep product price, shipping, taxes, platform fees, API costs, developer premiums, lifecycle costs and affiliate commissions distinct. Downline commissions share one funded pool from eligible sales; recruitment alone earns nothing. Rates and allocations remain undecided.
What the proposal rests on
- Khronos glTF supports spatial asset exchange. A display-ready asset is not a validated robot simulation or fit certificate.
- Retrieval-augmented generation informs grounded assistance, not a guarantee of fully automated support.
- TypeSafe’s Jev documentation describes candidate typed decision support. Skyzai integration and robotics suitability are not established.
- Apple’s US iPhone Upgrade terms are a lifecycle analogy, not Menexus terms or proof of available cover.
Public source review: . Pilot economics, manufacturer adoption, safety assurance and operational readiness still need their own evidence.
Confidential diligence comes separately
This public room does not accept uploads or store confidential partner documents. An unlisted link is not access control.
- Manufacturer agreement
- Planned — not yet available. Scope and terms need partner negotiation.
- Insurance and upgrade schedules
- Planned — not yet available. No provider commitments have been established.
- Restricted partner workspace
- Planned — not yet available. Requires authenticated access, partner-specific permissions, revocation and protected downloads.
For the first email, share only your organisation, product family and discussion goals—not confidential CAD, customer records or credentials.