On this page
We · Skyzai Markets
One API. A choice of supply.
The proposed business interface connects models and services to the apps that use them. Choose the model, inspect the provider and follow the cost of each operation.
- A model or capability
Exact version and the kind of work it supports.
- An eligible provider offer
Operator, runtime, region, data policy and price version.
- An app’s measured usage
Actual delivery cost and separately disclosed service charges.
- The consumer’s usage bill
Attributable API cost plus the app’s known premium.
A model can have many providers
A model identifies a capability and version. A provider identifies who runs it and on what terms. The same model may be offered by several operators with different runtimes, precision, locations, prices and data policies. Those differences belong in the offer.
| Record or decision | What it needs to say |
|---|---|
| Model | Model/version, supported interface, capabilities, licence and permitted use. |
| Provider offer | Operator, endpoint, runtime or quantization, region, data handling, price schedule, observed performance and dated eligibility evidence. |
| Request policy | Pinned choice or permitted alternatives, required features, budget, data/region constraints and explicit fallback permission. |
| Usage receipt | Actual model and provider, operation and attempt references, billable units, price version, separate costs and error/refund status. |
The owner’s OpenRouter comparison describes the model-access starting point. OpenRouter already documents multiple-provider routing and provider constraints. Skyzai’s proposed extension connects that access to application economics, product/service offers, XaaS and commerce-funded distribution.
“Any model” is an ambition for a broad eligible catalogue. It is not a promise that every proprietary model may be resold, every endpoint is available, or two providers produce equivalent results.
One operation. A separate cost record.
Analysis can cost something even when you buy nothing.
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.
- Equipment purchase
- not decided · no agreement or payment
- Usage permission
- None · no purchasing authority
- Gross usage / cap
- USD 0.00 / USD 5.00
- Corrected statement / payment
- USD 0.00 / not paid
Inspect the shared usage record
{
"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.
Follow the cost into an app
API Pay is the conversational name for the usage-pricing direction: a digital service bills declared usage, rather than a fixed app subscription. Tokens, compute time and service operations are possible units; each product must define a meaningful meter.
Simplified cost lineage; rates and general cost bases remain open
- Provider or service deliveryAttributable underlying supply cost.
- P
- Separate Skyzai service chargeIts basis and value must be disclosed; hidden supplier-price spread is not pass-through.
- G, if adopted
- App’s B2B API costThe accepted cost base for the consumer’s operation.
- C = P + G
- Publisher premiump is the app’s known premium rate, expressed as a fraction.
- A = C × p
- Consumer usage subtotalExcludes actual taxes and other separately agreed items.
- U = C + A
Follow one illustrative operation
Change the app’s attributable B2B cost and publisher premium. The starting values are an arithmetic example, not Skyzai prices or an adopted app rate.
Taxes and any separately adopted charge are excluded. The publisher’s premium is revenue before its own expenses. Real billing needs accepted price versions, meters, failures, refunds and rounding rules.
A statement can aggregate usage each month without charging a monthly subscription. A balance top-up, model listing or failed attempt is not automatically consumer-billable use. Provider costs from retries or failed operations need an explicit allocation; metering must not count duplicate events twice.
A route must respect the request
Eligibility comes before price or speed. A cheaper route that violates the buyer’s required model, region, privacy policy or capability does not qualify. A fallback may use only the alternatives the customer permitted.
The business should be able to set a spend cap, inspect an estimate or maximum charge and trace the actual provider used. If no offer qualifies, the service should say so. A shared credential authenticates access; it does not grant access to private memory, conversations or every connected product.
The proposed routing contract retains separate identity, permissions and service admission. Individuals in Me and shared organisations in We could provide services through machine intelligence participating through the protocols explained in They, supported by compute, storage and mesh networks. Provider routing eligibility remains a separate contract. A DAV or DAC’s legal-person status requires actual registration evidence in an identified national jurisdiction; agent identity confers neither that status nor authority. The proposed Skyzai XaaS standard needs its own adoption decision.
Capabilities keep their own responsibilities
| Record or decision | What it needs to say |
|---|---|
| Direct inference | A model response from an identified eligible provider. |
| APU | Voice, text, navigation and controls for permitted work. |
| Agentz | Specialist reasoning and orchestration, with Cortex memory and Nexus connections. |
| Circle | Sourced observations and their evidence. |
| RealityFutures | Forecasts with uncertainty and stated assumptions. |
| Other apps and services | Their own meaningful usage unit, permissions, support owner and admission evidence. |
APU is the interface; Agentz owns Cortex memory, Nexus connections and specialist coordination. Current product direction is distinct from the retained technical contracts and from live availability.
A common integration or invoice does not make these outputs interchangeable. Each capability keeps its own release, data and commercial conditions. The near-cost thesis for first-party services needs a defined cost basis and a named subsidy owner.
A model-service request is separate from a financial order. LIQUID owns the proposed exchange and application-level settlement functions; organisations in We retain issuance and investor obligations. They explains SPECTRE, the proposed monetary Layer 1 and SKY/ZAI mechanics. An API credential grants neither trading authority nor access to a live DEX.
The retained API source records an owner-selected rate under the label apu.bot model usage: provider cost + 30%. That historical label preserves the source proposal; it does not assign model reasoning or orchestration to APU. The label, accountable service and tariff need reconciliation with Agentz’s current responsibilities before commercial admission. It is not a universal App Store premium or proof of activated billing. Circle and RealityFutures remain near-cost candidates; their commercial admission is separate.
Commercial terms still to decide
| Record or decision | What it needs to say |
|---|---|
| Usage and cost basis | Units, supplier schedules, discounts, caching, retries, failures, refunds, currency and rounding. |
| Service charge and platform fee | Recipient, payer, value basis and how the two proposals coexist without duplicate charging. |
| Provider admission | Rights, contracts, availability evidence, data-route restrictions and exact service commitments. |
| Naming | The existing source product called API PAY concerns payroll and scheduled transfers. Usage pricing does not rename it or create another payment rail. |
This page explains the product model. No commercial API endpoint, accepted tariff or usage charge is activated by the website.
Keep the next decision attached to its record.
Pin the actual model, provider, meter, price and usage permission. A failed app result can leave permitted provider costs; a duplicate operation must not create another bill.
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 exploringApp StoreTwo access modes and a known app premium.Source: Skyzai API 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.