On this page
Skyzai Markets
API Pay. Compute for useful work.
Compare inference and GPU capacity from eligible cloud operators. Understand the supply, set a budget and trace the cost of what you use. Skyzai’s proposed service connects this compute to apps and product workflows.
- Define the work
Inference operations or an exact GPU configuration and reservation period.
- Compare eligible supply
Operator, runtime, region, data policy, support and full costs.
- Agree the supply arrangement
Permitted direct resale or a customer-owned provider account.
- Reconcile delivered usage
Provider costs, any Skyzai charge and any app premium stay distinct.
Choose inference or GPU capacity
Start with the work you need. An inference request buys a model operation; a capacity reservation supplies a defined compute resource for a period. They need different meters and commitments.
| Supply | Terms to compare |
|---|---|
| Inference | Model/version, supported interface, operator, region, token or operation units, latency evidence, data handling, permitted retries and failure charges. |
| GPU capacity | GPU type/count and memory, runtime, location, start/end period and billable compute time. State storage, network transfer, setup, idle time, interruption, cancellation and support costs. |
Skyzai’s capital-light direction uses direct agreements with eligible neo-cloud operators. It does not acquire speculative GPU infrastructure. Supplier rights, availability, customer-backed demand and payment timing must qualify before a supply commitment.
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 quantisation, 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. |
OpenRouter documents multiple-provider routing and provider constraints. Skyzai’s proposed service connects eligible compute to product knowledge, application usage and continuing service, with its own supply agreements and cost records.
“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 reviewed billing adjustment is recorded 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 public name for metered compute access. Tokens, compute time and service operations are possible units; each offer defines its meter and chargeable period. A robot rental does not automatically include or authorise cloud usage.
| Arrangement | Payment and responsibility |
|---|---|
| Permitted supply resale | Skyzai contracts directly with an eligible operator under explicit resale rights. The customer agrees the supply cost, separately disclosed Skyzai charge, limits and failure/refund terms. |
| Customer-owned provider account | The customer contracts with and pays the provider directly. Any Skyzai service fee is separately agreed. The provider bill is not Skyzai revenue or another Skyzai compute charge. |
The following example describes an app purchasing compute through Skyzai and adding its own publisher premium. It is not a profit calculation or the bill for every supply arrangement.
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
| Amount | Payer and recipient |
|---|---|
| Provider cost P | The eligible provider supplies the operation; P is its attributable delivery cost within the publisher’s Skyzai API cost C. Accepted supply terms identify who pays the provider, including permitted failed attempts. |
| Service charge G | If adopted, the business customer pays the identified Skyzai service operator for a separately described service. |
| Consumer subtotal U | In metered mode, the consumer pays attributable API cost C plus publisher premium A. The premium belongs to the publisher before its expenses. |
| Affiliate allocation | A seller-funded campaign may allocate part of its one pool to an eligible participant. It is not another API cost or an additional full pool for every recipient. |
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.
Individuals and organisations can supply work through agents and infrastructure providers. Service eligibility, context permission and spending authority remain separate. Continuing service terms need their own agreement.
Capabilities keep their own responsibilities
| Record or decision | What it needs to say |
|---|---|
| Direct inference | A model response from an identified eligible provider. |
| APU | Stored outline records, retrieval and revision. |
| Agentz | Conversation, contextual assistance and specialist coordination within the task’s permissions. |
| Cortex | The independent memory product: source-linked records, revisions and evidence. |
| Nexus permissions | Shared purpose-scoped context access; permission to read is distinct from permission to spend. |
| 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 organises stored records; Agentz provides conversation and contextual assistance; Cortex retains permitted memory; shared Nexus permissions control its disclosure. Current product direction is distinct from retained technical contracts and 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.
Commercial terms still to decide
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 a retained proposal, not an adopted current rate. The current direction is a disclosed cloud-expense premium with unresolved rates, separate from eligible completed-sale commission and any publisher terms; it is not proof of activated billing. Circle and RealityFutures remain near-cost candidates; their commercial admission is separate.
| 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. |
| Existing payment module | The historical API_PAY module concerns payroll and scheduled transfers. The public API Pay compute name preserves that module’s technical IDs and does not create another payment rail. |
This page explains the product model. No commercial API endpoint, accepted tariff or usage charge is activated by the website.
Discuss a compute requirement: describe the workload, configuration, region and budget before a supplier or price is selected.
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.
Explore the separate AX-14 fictional order as Me · buyer, We · author and accountable workshop or They · machine. Perspective controls preserve its record within a visit; a new page visit resets the example.
We · value creation · LIQUID · exchange and broader origination direction · SoResFi · instruments and obligations · Network · economic receipt requirements · Aureus · retained gold and other specified programmes
Product design, with local illustrative examples. Live inventory, billing, orders, attribution and payouts are not connected.
Continue exploringApp StoreAccess modes and separately stated app terms.Source: Skyzai API (retained source) 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.