We · Skyzai Markets
The Skyzai App Store is designed around usage and a visible publisher premium. Every app would also offer an own-API mode with zero app fee, in exchange for advertising and information sharing under terms still to be defined.
Skyzai supplies eligible models or connected capabilities.
Usage is measured against an accepted cost basis.
Metered use plus a known premium, or own API with zero app fee.
Show money, provider costs, advertising and data terms separately.
All proposed store apps integrate with Skyzai’s API. The publisher buys business services and delivers an application to consumers. The store direction requires two working access modes, rather than a nominal “free” button that cannot run the app.
The consumer pays the app’s attributable Skyzai API cost for their operation plus its known publisher premium. There is no fixed app subscription in this direction.
The rate and eligible cost base are visible before use; the bill itemizes both afterwards. A publisher premium pays the app, before its own hosting, development, support and other expenses.
The user brings API access they are entitled to use. The app usage fee is zero. The underlying provider can still charge for inference or other use.
Advertising and the owner’s “total information sharing” direction are the proposed nonmonetary exchange. This requires defined terms before activation. The scope of supported own-API providers remains to be selected.
No duplicate inference charge should be disguised as an app fee.
Paid-mode data and advertising terms are also undecided. “Paid” alone does not establish an ad-free or private mode. Each mode needs a clear comparison and an exit path.
Fictional local example. The analysis operation and the actuator purchase are separate records; this example starts independently on each page visit.
Buyer: compare the cost with the result. Declining equipment does not erase a separately permitted analysis attempt. Fictional Analysis Operator · Inspection Analyst · demo-v1 · ANALYSIS-TERMS-1-DEMO One metered analysis attempt: USD 2.00 provider usage plus USD 0.40 publisher premium, even if the app fails after that usage. No automatic retry. A disputed duplicate is credited separately. These are fictional terms, not selected Skyzai rates. Separate usage-only cap: USD 5.00 for this page session, ending on reset or reload. No credentials, requests, ads, referral tracking or live payment rail.Inspect provider, meter and exact fixture terms
No usage permission, cost or equipment purchase is recorded.
{
"grant": null,
"purchase": "not-decided",
"entries": []
}The shared equipment order follows its own quote and agreement. These examples do not share live state across pages. Usage permission never supplies authority for that purchase.
| Record or decision | What it needs to say |
|---|---|
| Publisher and purpose | A named publisher, support contact, intended work and exact Skyzai dependencies. |
| Both access modes | Supported credentials and functional paid/own-API paths; a placeholder does not qualify. |
| Price and spending controls | Known premium, eligible B2B cost base, accepted price version and estimate or maximum charge. |
| Failure and remedy | Retry, failed-run, cancellation, refund and billing-dispute treatment. |
| Mode-specific data terms | Advertising, sharing, recipients, consent choices and withdrawal. |
| Skyzai XaaS | Proposed direct publisher commitments for support, continuity, remedy and exit. Standard adoption and admission remain open. |
Publisher admission, model/provider eligibility and XaaS qualification are separate checks. A technically reachable app does not establish available service capacity or accepted consumer terms.
apps.skyzai.com is the intended App Store address. This website documents the design; it does not claim a live store at that address.
The owner’s thesis is that software can move from fixed subscriptions to API usage with a known application premium, while commerce and advertising support wider access. This is a hypothesis to test, not a demonstrated end of SaaS.
A percentage premium creates its own tradeoff: falling API costs also reduce publisher revenue per operation, while avoidable retries can increase the cost base. Measure useful outcomes, failed-run costs, support, retention and contribution before treating the model as efficient.
Nudge could fund some free services through retained product sales. That is a separate seller-funded campaign allocation, not proof that every app or non-buying user is already funded. Store premiums, API supply costs, advertising proceeds and affiliate allocations must not be counted twice.
The publisher owns its app terms, premium and support. Provider charges, app failure, accepted output, information sharing and a corrected statement are separate decisions.
Open the same fictional order as Me · buyer, We · author and accountable workshop or They · machine. Each visit starts a new local example; perspective controls within it preserve the record.
We · value creation · LIQUID · exchange scope · SoResFi · instruments and obligations · Network · economic receipt requirements · Aureus · asset origination
A product twin does not transfer title. Local logs do not issue OFN receipts. An order or accepted result does not establish payment. The originator, issuer, venue operator, chain operator and custodian retain separately specified responsibilities.
Product design, with local illustrative examples. Live inventory, billing, orders, attribution and payouts are not connected.
Continue exploringProduct twinsAssemblies, exact revisions and evidence.Source: Skyzai App Store product model and public explanation and decision map. GitHub repository access may be required. These pages describe the design; they do not adopt commercial terms.
Context: App Store · two access modes.