For customers
Customers select Auto, Frontier, or Fusion as their routing profile. Community capacity is a separate account permission for an approved execution mode.
Community inference marketplace
Independent compute. Accountable inference.
Match approved AI work with reviewed provider nodes, under explicit customer consent.
Two sides. One controlled exchange.
Customers define where work may run. Providers declare models and capacity; the router admits concurrency after measurement, while authenticated polling establishes current availability.
For providers
Offer selected local models through an outbound worker. Keep concurrency, model residency, and availability under local control.
For the network
Route only to eligible nodes, verify scoped result signatures and, for Fusion, require an independent verifier's successful response. Settlement records stay separate from prompt content.
Agentic commerce direction
Built to be found—and paid—by agents.
TEKIZ.AI is targeting x402-compatible quotes, payment authorization, and Bazaar discovery so an agent can find eligible inference, compare a bounded price, pay programmatically, and receive an OpenAI-compatible result.
x402 payments are planned. Paid Community Direct offers are currently disabled. They can launch after a reviewed payment rail binds authorization to the customer, API key, client peer, provider peer, tariff, and expiry.
Agent discovery
Publish machine-readable inference resources through x402 Bazaar metadata and TEKIZ.AI's model catalog.
Bounded quote
Return a route-specific ceiling before execution, with model, execution class, residency, and expiry attached.
Programmatic payment
Target x402's HTTP-native payment handshake, including usage-based authorization where the reviewed scheme supports it.
Lowest eligible cost
Optimize price only after consent, capability, security class, residency, availability, and quality requirements are satisfied.
Execution class determines the trust boundary.
Capacity evidence confirms available compute; it does not protect request contents from the node operator. Each execution class states who can see plaintext so customers can consent to that exact boundary.
Not yet available
QVAC direct peer
A consenting Free or Lite client is designed to connect directly to a Community peer over QVAC's encrypted transport. TEKIZ.AI does not see the content, but the provider processes plaintext. Offers remain disabled until a reviewed payment authorization rail is implemented.
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, operator-attested node has an admitted model and available slot.
Work is reviewed
For router-mediated Fusion, an independent 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.