​
Introduction

Malibu turns any Apple Silicon Mac into a remote-addressable, OpenAI-compatible AI inference endpoint.

I'm a provider

Invite-gated pre-beta. Download the app, pick a model, start serving.

I'm a buyer

Get an API key, hit the OpenAI-compatible endpoint.

I'm an agent

Point at get.malibu.tech/skill.md — install, recover, connect.
Malibu is a coordinated inference network built on Apple Silicon — distributed providers, centralized routing and billing. Providers run open-source models on their Macs. Buyers call an OpenAI-compatible API. A buyer is charged only when a signed receipt binds (prompt, output, model, provider). Receipt-verified settlement, without a datacenter. What’s live vs planned: Network status.

​
Architecture

Provider Macs open an outbound WebSocket to Malibu, so you need no port forwarding, static IP, or reverse proxy. Buyers call https://api.malibu.tech/v1/* and get OpenAI wire-shape responses. Some non-streaming responses carry a v0.3 receipt in the X-MacProvider-Receipt header, signed with the provider’s Ed25519 receipt key (currently roughly a quarter to a third); streams never do. For the rest, use GET /v1/receipts. Separately, paid requests settle against signed receipts checked by the network. See Verified model settlement. Public pool snapshot: GET https://api.malibu.tech/v1/stats/overview. Rate card: GET https://api.malibu.tech/v1/rate-card.

​
For providers

Any Apple Silicon Mac (M1 or newer, macOS 14+) can serve. The Malibu app handles onboarding: you paste your invite, and it installs the provider, benchmarks the Mac, and picks the best paid model that fits. New Macs start provisional and can move to trusted once they meet the network’s trust criteria. Each verified, billed request credits the provider 90% of the billed amount. USDC-on-Base payout is planned for public beta; it is not live in pre-beta.

​
For buyers

Point any OpenAI SDK client at https://api.malibu.tech/v1 with your Malibu API key. Full OpenAI wire-shape surface: streaming, multi-turn tool calling, JSON-schema structured output, sticky conversations with prefix-cache reuse. Settlement is receipt-verified, and some non-streaming responses also carry a signed receipt header; offline verification of current receipts is pending a verifier update. List warm models with a Bearer token (GET /v1/models) — the list is small and changes. Console chat at malibu.tech/console includes agent tools, stop, and per-stream decode tok/s. Emitted tool_calls[] are model output. Validate before execution: Buyer-side validation.

​
Trust model

Prompts and responses pass through the gateway to enable routing and billing. Model weights stay on the provider Mac and never leave. Buyer prompts and provider responses are processed as plaintext on provider hardware — providers can technically observe traffic that routes through their machine. This is acceptable for cooperative deployments where buyer and provider have an established trust relationship; it is not a private-inference guarantee. Full trust boundary in Security & trust model.