Prices & offers
Input is text sent to a model; output is text it generates. Buyer prices are displayed with $ in per million tokens. The initial P2P protocol fee is 3%, included in the buyer price. There is one market: model audits do not introduce a different fee tier.
Catalog minimum input and output prices can come from different sellers. The model comparison pairs both prices from the same offer. Real prices must be signed, unexpired and bound to the accepted session; a later price change only applies to new sessions.
The current catalog and provider activity are illustrative, not live supply or official vendor quotes. Context limits, precision and retention must come from each seller’s signed declaration; unknown fields are not inferred from a model name.
External reference tariffs are checked automatically from the named source, with a cache of up to one hour while this site is viewed. Input and output differences are calculated separately, assuming 1 USDC equals $1 USD. A failed update retains the last valid tariff and its original check time; comparisons expire after 48 hours. Hosting references are not creator list prices or proof of equivalent configuration. Plan conditions and other manual notes retain their separate capture date.
Settled payments
Settled inference consumption means confirmed increments attributable to Gyblos inference. Deposits, top-ups, returned funds, stake, rewards and relay payments are excluded. Settlement and distribution are different stages of the same money, not two sales.
Vouchers are cumulative: $0.02 → $0.05 → $0.09 authorizes $0.09 in total, not $0.16. A channel can contain multiple requests. Model-level sales need the accepted offer, usage records and linked settlement; a blockchain transfer alone does not prove tokens or delivery.
Service reputation
Reputation is an automatic service score, separate from model audits, identity badges and optional stake. Initial weights: honest charging 25%, complete delivery 20%, diverse payment history 20%, age and recency 15%, speed 10%, availability 10%. These require calibration and a published versioned formula.
No verified measurements means not rated, not zero. The current provider activity examples never generate a real reputation score. Latency needs model, region, period and sample size; p50/p95 are computed from observations, not averages of provider percentiles.
Model audits
A verified-model seal belongs to a specific provider offer, model version, precision and configuration, with signed auditor evidence. Eligibility alone does not grant a seal. Public reference weights are a prerequisite, while logprobs, method support and successful checks must also be established.
API models without public reference weights are not eligible for this public-weight seal. That is a technical scope limit, not a judgement of service quality. A statistical result is not an identity check, a guarantee of every response or an automatic refund promise.
Public identity & optional stake
8004 identifies a node through addresses and keys, not a verified person. A provider can supply an image and website. Domain control, a .sol name, address history and stake are independent public signals. There is no KYC/KYB requirement.
Stake does not raise the service score. No stake or rewards program is connected to this preview. Compensation rules, coverage, stake denomination and protocol parameters require implemented evidence; no guaranteed refund or token market is implied.
Sources, coverage & privacy
- CatalogIllustrative
- Local model and provider listings; signatures and expiry are not checked.
- PaymentsNot connected
- No attributed settlement indexer. Deposits and channel counts are not inference revenue.
- Service measurementsNot connected
- No signed delivery, token, latency or reachability observations.
- Audit evidenceNot connected
- No signed audit records or verified-model seals.
No data is different from zero. Live metrics must expose their time window, sample size, source and last observation. Registered, listed, observed and reachable nodes are different counts; a node is not necessarily a unique person or GPU.
Buyer activity should be aggregated with suitable privacy thresholds. Do not publish prompts, responses, precise home-node locations or a per-request wallet/model/payment feed. A missing indexer observation does not prove a node is down.
Explore here. Operate in the apps.
The website is public and read-only. Buying, selling, wallet operations, node configuration and reward claims belong in the applications. No account or wallet connection is needed to explore.