Skip to main content
Skip to the site menu

Partner information

Skyzai data room

Explore an OpenQR business-profile pilot, direct manufacturer partnerships or an API Pay compute requirement. Scope, suppliers and responsibilities are agreed before work begins.

A business profile people can find

Give people a simple way to find your business. In the proposed OpenQR pilot, visitors could scan a code to open a profile with the information you choose to publish, such as your logo, contact details and locations. Publish contact details only with appropriate permission.

The full pilot also aims to let visitors ask questions using only your business-approved public information, with a way to reach a person. Qualified guest assistance and the complete hosted experience are not yet available here.

Discuss an OpenQR pilot

This opens an editable email to yves@menexus.net; the website sends nothing automatically. Share public business information and the questions you want to answer. An inquiry does not create an account, start a pilot or establish an agreement.

What the pilot still needs

The proposed pilot would use APU to organise permitted business information and Agentz to help visitors ask questions. A pilot should name a human contact for questions that need attention. Available languages would depend on the connected model and the qualified experience. Showing locations on a globe is part of the intended pilot and still needs qualification.

A development revision of the Flutter app generates a public-profile URL containing a Nostr public key and includes QR scanning; signed profile publication is a separate capability. Adoption of that revision still needs qualification. The complete hosted experience still needs qualification.

A bounded first agreement

The ambition is a common buying interface across leading robotics manufacturers. Start with a product twin and its permitted documentation, then qualify customer assistance and exact maker offers in a bounded, non-exclusive pilot. A selected evaluation task does not restrict the eventual knowledge base to one question.

For the marketplace, our initial focus is rental access to embodied-AI products, especially humanoid robots, directly from their manufacturers. Identify the exact configuration, use, location, period, support, handover and return terms. The manufacturer issues the offer; any appointed delivery or service partner has named duties. Skyzai does not own or finance the fleet. Purchase remains an alternative.

  1. Product and data. Approve exact variants, documents, licensed spatial assets and update owners. Confidential CAD stays under manufacturer control.
  2. Commercial responsibilities. Name the seller, territory, inventory authority, delivery, installation, acceptance and remedies. Agree fees and customer relationships explicitly.
  3. Support and lifecycle. Define escalation, warranty and any qualifying Skyzai XaaS offer, with accountable providers.
  4. Measurement and exit. Agree thresholds before starting; measure answer quality, buyer outcomes and manufacturer contribution margin. Include termination and portable records.

Discuss a design-partner pilot

Your email draft asks for your organisation, optional manufacturer/product identification, product knowledge, customer-assistance or order-book need, any rental period/location and desired outcome. The Skyzai team receives it only when you choose to send it. The next step is to discuss scope; no pilot is accepted automatically.

The draft is addressed to yves@menexus.net. You can also copy that address into your mail app. This website sends nothing automatically.

Agree the pilot’s measures

Before a pilot starts, agree which attempts count, how answers will be judged, the permitted product knowledge, representative tasks, evaluation window and accountable evaluator.

  • Customer assistance: report source-supported answers, justified handoffs or refusals, incorrect answers and unanswered or abandoned attempts separately across all eligible attempts.
  • Buying and service: assess whether participants can explain configuration, full delivered costs, responsible parties and continuing commitments. Track incomplete reviews and abandonment.
  • Business results: if a real pilot is separately agreed, evaluate independently accepted orders, fulfilment, remedies and contribution after the relevant costs. Website comprehension alone establishes none of these results.

Evaluator: unappointed. Targets: unset. Pilot outcomes: not measured. Collection begins only after scope and responsibility are agreed.

Proposed rental measures
From a compatible request to useful work
Track eligible requests and repeat rentals. Report fulfilled periods against all agreed periods due in the evaluation window; retain unmatched requests and late, cancelled or disputed periods separately. Agree task acceptance evidence and report human intervention.
Continuing service
Measure available time, downtime, maintenance and turnaround within the agreed period. Retain interrupted and disputed periods; define the denominator before evaluating uptime.
Economics for both parties
Compare rental proceeds with agreed platform charges, delivery, operator, maintenance and remedy costs. Include the manufacturer’s explicit capital-cost allocation once; Skyzai does not finance the fleet.

Proposed measures. Evaluator: unappointed. Targets: unset. Rental outcomes: not measured. Agree the window and data sources before collection begins; this website collects no pilot results.

This is a drafting scope, not a contract for signature. No manufacturer partnership or service commitment is established by this room.

Start with a compute requirement.

Describe the workload before choosing supply: inference model or GPU configuration, region, timing, expected usage, data constraints and spending limit. Compare eligible direct neo-cloud supply with a customer-owned provider account; their contracts, costs and responsibilities differ.

Skyzai’s capital-light model does not acquire speculative GPU infrastructure. Supplier rights, capacity, support, cancellation and payment timing must qualify before any commitment. A robot rental creates no automatic compute purchase.

Discuss API Pay compute

The editable draft is addressed to yves@menexus.net; you can copy that address into your mail app. Share public information only, with no credentials, customer data or confidential workloads. The team receives it only when you choose to send it. This website sends nothing automatically. An inquiry reserves no capacity and accepts no agreement.

Compare inference and GPU capacity and inspect the supply and service charges.

Proposed compute measures
Accepted work and cost
Define a successful workload with the customer. Count all permitted attempts, including failures, retries and abandonment, and their applicable costs. Track completion latency. With no accepted workload, cost per accepted workload is unavailable, not zero.
Usage that reconciles
Compare the meter, supplier invoice and customer charge for the same units and period. Keep a customer-owned provider account separate from Skyzai’s service charge.
Repeat value
Evaluate repeat purchase and contribution after variable support, payment and remedy costs. A robot rental does not establish additional compute demand.

Proposed measures. Evaluator: unappointed. Targets: unset. Compute outcomes: not measured. Agree the window and data sources before collection begins; this website collects no pilot results.

A separate storefront inquiry: NFC or palm.

For chain stores, explore NFC acceptance or an opt-in palm experience with a qualified payment/provider partner. They are separate integrations requiring exact provider, device, consent, fallback, refund and reconciliation qualification. Skyzai does not currently provide biometric enrolment or payment processing through this website.

Discuss a provider-led storefront pilot

The editable email asks for public business context only. Do not send biometric samples, customer payment data or credentials.

Start with the current design

Public materials. Confidential agreements and partner data are not hosted here. Marketplace capabilities describe a proposed programme, not operating services.

Skyzai Markets

Explore the current product design, actuator example and conditional buyer proposal. These website chapters are the working explanation while new pitch work is deferred.

Website-first reset · 8 October 2026

Explore Skyzai Markets

The earlier robotics presentation is archived. View the archive record and source custody. A new Markets pitch and separate organ decks will follow the finished websites.

One price, explicit responsibilities

Skyzai’s proposed revenue is a disclosed premium on agreed cloud expenses and a commission on eligible completed sales, completed rentals and fulfilled service periods through Skyzai. Sales and rentals completed elsewhere carry no Skyzai marketplace commission. Rates are unresolved; this page does not activate billing.

Refundable deposits, reservations and future renewals are not completed service. Each fee needs an agreed base, payer, recipient and completion evidence, with cancellation, dispute, refund and reversal rules. A customer-owned provider account is paid directly by the customer; any Skyzai service fee is separate. Count provider cost, platform charge, publisher premium and affiliate allocation once each.

Exact-configuration order books expose eligible buyer bids and maker asks. The initial physical-order design takes one eligible ask covering the full requested quantity, at the ask price within the buyer’s full delivered-cost cap. Unmatched bids wait; seller-taking of bids and partial or multi-ask fills remain broader designs. 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.

Product listings would come from verified makers, not retailers. XaaS may become a Skyzai standard of direct maker commitments and customer reviews of actual fulfilment. Ownership with optional support or agreed access/usage are possible forms. Standard adoption and admission remain open; Skyzai adds no separate lifecycle intermediary or platform-financed insurance.

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 your pilot quote will include

Start with the business-profile pilot’s proposed scope or with real manufacturer or compute-supplier terms. The following is a discussion worksheet; amounts and rates remain unknown until a scoped proposal is reviewed.

Business-profile scope
For a profile pilot, describe the proposed setup, ongoing profile and support work, permitted knowledge sources and any inference usage. Identify the payer, billing arrangement and any separately agreed service charge; amounts remain to be agreed.
Exact offer and unit
Record the maker or supplier, asset owner, offer version, configuration, location, availability and expiry. Specify the rental period or compute billing unit and permitted use.
Proposed price and Skyzai charge
Name the currency, payer and recipient for each charge. For compute, separate eligible provider cost from the proposed expense premium. For rentals, state the maker’s price, eligible commission base and proposed rate. Count included compute once, not as another API Pay sale.
Complete service cost
Identify delivery, installation, support, taxes and third-party charges. Keep refundable deposits separate and name their holder. Any protection or insurance needs the actual provider’s terms.
Completion and reversals
Agree what proves eligible completed work or a fulfilled rental period. State cancellation, downtime, dispute and refund treatment, including credits for previously collected fees when the eligible charge is reversed.
Limits and review
Record the customer’s spending limit, responsible parties, support commitments, quote expiry and required acceptance. An inquiry accepts no quote, reserves no capacity and authorises no spending.

No price is selected by this worksheet. Discuss a business-profile pilot, a manufacturer pilot or a compute requirement before agreeing a proposal.

Inspect the complete order costs and cloud and inference usage costs before agreeing any charges.

What the proposal rests on

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.

Discuss a design-partner pilot

For the first email, share only your organisation, product or question and discussion goals—not confidential CAD, customer records or credentials.

Context: Partner data room.

Skyzai, close at hand.

Keep this website on your home screen and read saved pages offline. The connected app at skyzai.com is still in development.

On iPhone or iPad, open this site in Safari, choose Share → Add to Home Screen, then Open as Web App if offered. On Android or desktop, use your browser’s Install app or Add to Home screen menu when available.

Offline reading & privacy

Offline reading becomes available after the initial download. External sites are not saved. Your browser may evict saved pages.

Conversations and drafts are never saved by the offline cache. Reloading clears them. To remove downloaded pages, clear this website’s data in browser settings; uninstalling alone may not clear it.