Specs that matter
Listings can show available models, hardware, usable capacity, and measured speed when the registry has current information.
Community marketplace
Find compute. Offer compute.
Find reviewed computing capacity. Providers can offer their machines and services. TEKIZ.AI sends a request only when you approve the provider and location.
Live supply
Compare reviewed computing offers.
Loading the public node registry from TEKIZ.AI.
Reviewed listings
QVAC offer status loading
Provider enrollment open
Trust boundary
Each offer states its location, execution type, and security review so you can apply your saved consent choices.
Availability signal
A provider must be online, recently checked, and have room for the request. A listing does not reserve capacity.
Price before work
A reviewed quote binds its scope and expiry before a direct-peer session. Paid Direct offers appear only after the matching provider, settlement rail, and current rate snapshot are available.
A visible rate is published only when the registry marks a USD hourly quote as reviewed and current. All other listings show “Quote required”; buyer access, consent, eligibility, and final route checks still apply.
A marketplace with clear rules.
Customers choose where work may run. Providers list their services and available capacity. Each listing shows its public operating location. Provision-on-order listings show the configured target location; no instance is running until a reviewed order begins provisioning.
For customers
Customers select Auto, Frontier, or Fusion as their routing profile. Community capacity is a separate account permission for an approved execution mode.
For providers
People and approved software operators can enroll a selected local model from Account with a short-lived, host-specific code. Every node remains pending until capacity and security review approve it.
For the network
Route only to eligible nodes, verify scoped result signatures and, for Fusion, require the router-controlled verifier's successful response. Settlement records stay separate from prompt content.
Payment options
See the price before you approve.
Compare a reviewed offer, choose an available payment method, and receive the result through a compatible connection.
$TKZI is live on Solana. Payment options are being prepared. When offers open, you can pay with $TKZI on Solana, $S on Sonic, ALGO on Algorand, or a card. We show the price in your local currency before you approve it. Card payments use Stripe checkout and go to the approved provider. Direct sessions open only after TEKIZ.AI has checked the customer, provider, payment destination, price, time limit, and completion details.
Agent discovery
Publish machine-readable inference resources through the TEKIZ.AI model catalog and compatible marketplace metadata.
Bounded quote
Return a route-specific ceiling before execution, with model, execution class, residency, and expiry attached.
Programmatic payment
Authorize the wallet asset selected by the connected client, or use a one-off Stripe checkout when a reviewed card rail is available.
Lowest eligible cost
Optimize price only after consent, capability, security class, residency, availability, and quality requirements are satisfied.
Know who can see your work.
Capacity checks confirm that a provider has room for the request. They do not hide the request from the provider. Each option states who can see the content before you consent.
Provider enrollment open
Community Direct over QVAC
ZDR for Community Direct session content. ZDR means TEKIZ.AI does not receive or store your prompt or result during a Community Direct session. QVAC carries the approved session directly between you and the provider using encrypted transport. The provider runs the request and can read it. The public status proof reports this boundary. Payment and session details sit outside the ZDR content scope.
A consenting Free or Lite client can use Community Direct over QVAC once a reviewed provider offer is live. Providers may run their own hardware or rent any compatible Vast template with their own account; TEKIZ.AI never receives their Vast key or instance access. A paid offer needs measured concurrency, its exact settlement rail, current quote, and verification controls enabled before it can accept work.
Attested non-TEE
Private alpha for an explicitly electing Pro tenant. Reviewed server capacity presents evidence, but its operator may access request plaintext.
TEE E2EE
Planned confidential execution requires fresh remote attestation bound to the client session. This is the only Community class that can claim confidentiality from the infrastructure operator.
How a match becomes accepted work.
Availability alone never creates an assignment. Every request passes a sequence of customer and provider boundaries.
Customer permits it
The durable account policy allows the exact Community execution mode and residency boundary.
The node fits
An active, recently polling node has an approved security review, an admitted model, measured capacity, and an available slot.
The execution mode controls delivery
Community Direct uses QVAC to send authorized work peer to peer without TEKIZ.AI reviewing the result. For router-mediated Fusion, a router-controlled verifier owns the final customer response.
Accepted work counts
Only work used in a successful verified response becomes settlement-eligible.
Marketplace rules before market scale.
The economic layer follows verified work, not idle time or advertised hardware.
Rates and automatic payouts are not live. Private-alpha settlement remains manual while agreements, tax handling, fraud controls, refunds, and disputes are completed.
Accepted work
Failed, late, duplicate, cancelled, rejected, or unused results are not settlement-eligible.
Provider pool
The draft closed beta targets 70% of net Community inference revenue for providers whose work is accepted.
Routing credits
Planned credits offset Pro or Max routing first, then eligible Community inference.
Quality signals
Task fit, live capacity, safe residency, router-observed speed, and accepted outcomes guide future assignments.
Choose your side of the market.
Operators can prepare a reviewed node. Customers can set an explicit Community consent boundary in their account.