What a listing tells you
Listings may show models, hardware, available capacity, and measured speed when the registry has current information.
Community marketplace
Find reviewed AI providers.
Browse capacity from reviewed providers. You choose which execution mode and locations may handle your work before TEKIZ.AI can route a request.
Provider listings
See what is live and what is planned.
Checking the current provider listings.
Providers under review
QVAC offer status loading
Provider applications open
Where work runs
Each offer states its location, how it runs requests, and its security review status. Your saved choices determine which offers you may use.
Is it available now?
The provider must be online, recently checked, and have room for your request. A listing does not reserve capacity.
Price before a request
A direct session needs a reviewed quote with a price limit and expiry. Paid Direct offers appear only when the provider, payment method, and current rate are ready.
A USD hourly rate appears only after review and a current rate check. Other listings say “Quote required.” You still need buyer access, matching consent, and an eligible route before work can begin.
You choose the providers and locations.
Customers decide where work may run. Providers show their services, capacity, and operating location. A provision-on-order listing shows its planned location; the instance starts only after a reviewed order.
For customers
Choose Auto, Frontier, or Fusion for your regular routing. Community capacity needs separate permission in your account for the way you choose to run requests.
For providers
You or an approved software operator can enroll a selected local model from Account with a short-lived code for that host. We review its capacity and security before it can receive work.
For the network
TEKIZ.AI routes only to eligible providers. For routed work, it checks signed results; Fusion also needs a successful verifier response. Community Direct uses a separate peer connection. Payment 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.
Find an offer
Apps and agents can read model and offer details before choosing a provider.
See your limit
The quote shows the model, where the request runs, the maximum price, and when the quote expires.
Approve payment
Use an available wallet asset or a one-time Stripe checkout after the offer is approved.
Lowest eligible cost
TEKIZ.AI compares prices among offers that meet your location, security, model, availability, and quality choices.
Check who can read your request.
A provider with room for a request may still be able to read it. Review who can see the content for each option before you allow that execution mode.
Provider enrollment open
Community Direct over QVAC
ZDR for Community Direct session content. 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. Check the live Community status for this connection. TEKIZ.AI still handles payment and session details.
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.
Reviewed server (Attested non-TEE)
In private alpha, Pro customers can choose reviewed servers for this mode. The person running the server may be able to read the request.
Private server (TEE E2EE)
Planned. This mode will require a fresh security check for each session before a request is sent. It is designed to keep request content private from the person running the server.
What happens before work is accepted.
A provider being online is only one step. Your choices, the provider review, and the request details must all match.
You allow the route
Your account settings must allow the provider's location and way of handling requests.
The provider is ready
TEKIZ.AI checks its security review, model, measured capacity, and open slots.
Your request follows the chosen mode
Community Direct sends it to the provider over QVAC. Fusion checks the provider's contribution before returning an answer.
Accepted work counts
Work used in a successful, verified response may qualify for payment after review.
How providers will be paid.
Payment will be based on accepted work. A machine being listed or idle does not earn a payout.
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.
Request access or offer capacity.
Customers can choose their Community settings in Account and request buyer access. Providers can apply to offer a reviewed host.