Test-network preview

Keeta Compute for macOS

Status: test-network preview. The app uses the Keeta test network and test stablecoins.

One app does both sides of the market: it sells your Mac's spare capacity, and it buys inference for the agents running on your Mac. Both sides are paid in Keeta Compute Credits, which you buy and cash out with Keeta stablecoins.

Requirements

Install

First run

  1. The app creates your wallet and secures it with a passkey. There is no recovery phrase to write down.
  2. The passkey syncs through iCloud Keychain, so another Mac signed in to the same Apple Account can open the same wallet.
  3. Your wallet address (keeta_…) is your identity on the network. Your earnings are paid to it and providers can allowlist it.
  4. The app checks the hardware: chip, memory, free disk, and a short benchmark.

Pay with Keeta stablecoins

Keeta Compute Credits pay for requests and are what providers earn. A credit is a token on the Keeta ledger worth one US dollar, with 6 decimals.

Provide capacity

Hardware tiers

TierHardwareTypical work
A2 to 4 Mac Studios (256 or 512 GB) linked by Thunderbolt 5The largest open models. Clusters are not scheduled in this version.
BOne Mac with 64 to 256 GBMid-size models, coding agents
COne Mac with 32 to 64 GBSmall models, batch work
noneLess than 32 GBCan buy, cannot provide at launch

A tier describes what a machine proves in its benchmark, not the badge on it.

Models

When and to whom

Get paid

Buy inference for agents on this Mac

The app serves an OpenAI-compatible API on this Mac only:

http://127.0.0.1:11435/v1

curl:

curl http://127.0.0.1:11435/v1/chat/completions \
  -H "Authorization: Bearer $KEETA_COMPUTE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"model": "qwen3-8b", "messages": [{"role": "user", "content": "Say hello."}], "max_tokens": 200}'

OpenAI Python SDK:

import os
from openai import OpenAI

client = OpenAI(
    base_url="http://127.0.0.1:11435/v1",
    api_key=os.environ["KEETA_COMPUTE_TOKEN"],  # the token shown in the app
)
response = client.chat.completions.create(
    model="qwen3-8b",
    messages=[{"role": "user", "content": "Say hello."}],
    max_tokens=200,
)
print(response.choices[0].message.content)

Tools that read the standard OpenAI environment variables work without code changes:

export OPENAI_BASE_URL=http://127.0.0.1:11435/v1
export OPENAI_API_KEY=<token shown in the app>

How the app pays

  1. The scheduler picks a provider and quotes the most the request can cost, from its price and the request's token limits (at least 0.001 credits). The app checks that against your spend limits.
  2. The app escrows that many credits from your Agent budget with keeta.ai's settlement account, in one Keeta transaction that names the job, and gets a ticket for the job. The ticket reserves a slot on the provider. It escrows each job once, even if it retries.
  3. The request goes to the provider through the relay, and the tokens stream back to your agent. The relay records a hash of what it forwarded.
  4. The provider signs a receipt with the token counts and the amount, and the app checks it against the ticket and the text it received.
  5. Settlement is one Keeta transaction from the settlement account: when the receipt matches the relay's record, the provider gets what it billed (less the 0.25% network fee, which comes out of the provider's share) and the rest comes back to your Agent budget. If the provider fails, the receipt bills other text, or no receipt arrives, all of it comes back. The ticket reserves the provider, so if the request does not reach the relay within 10 seconds (the app quit or lost its connection), or your agent cancels it within 10 seconds before any text arrives, the provider keeps a no-show fee of 0.001 credits and the rest comes back. No x402 round trip is needed between apps.

This page as Markdown: app.md. Every Compute page for agents: llms.txt.