Connect my account
DOCS

Get running in about five minutes

Connecting an account so it earns takes four steps in the app and no terminal at all. Buying is nearly as short: keep the editor you already use and change where it points — the exchange answers a wire-compatible endpoint, so most agent tooling connects with two environment variables and no code change.

Private betaBase URL is issued with your invite

Listing an account you already pay for

  1. Connect a seat. In the app, connect the provider account whose idle capacity you want to list. Your credential is sealed on arrival and is never shown to anyone.
  2. Declare the plan. Telling the exchange which tier the seat is on is what sizes its budget and its earning ceiling. A mis-declared plan mis-prices your seat.
  3. Report your own usage. Running shaidle usage sync from your machine tells the exchange how much of the seat you are already using, so the schedulable remainder is measured rather than guessed. It sends token-count digests only — never content.
  4. Take it back whenever you want. Drain mode stops new routing at once and lets in-flight work finish.

Worth reading first: where your account stands — the whole position with the clause text behind it, the risks of listing a seat, and a statement you can send as-is if your provider ever asks about the activity.

Buying capacity

  1. Get credit. Top up your wallet in the app. Credit is prepaid and drawn down per token — see pricing.
  2. Mint a token. In the app, open Connect editor and create an API token. It looks like sk-shaidle-… and is shown once.
  3. Point your tool at the exchange. A client that speaks the wire-compatible endpoint — which most agent tooling does — needs two environment variables:
export ANTHROPIC_BASE_URL=https://<your-exchange-endpoint>
export ANTHROPIC_AUTH_TOKEN=sk-shaidle-…

That is the whole integration. Your tool calls POST /v1/messages exactly as it did before, the exchange routes the request to whichever seller is idle, and the response streams back byte for byte. Full details in the API reference.

Concepts worth knowing

  • Seat — one connected provider account. Seats have a measured budget and an earning ceiling, and they leave the pool when either is reached.
  • Routing — the exchange picks which seat serves each request. Neither side learns who the other is, and a seat that answers 401 or 429 fails over to the next one before any byte reaches the buyer.
  • Settlement — every request is metered from the provider's own response. The buyer is debited, the seller credited, and the spread is Shaidle's. Money never moves on estimates.
  • Workspace — an isolated cloud environment where an agent job runs, with its own filesystem and its own git remote.

Keep reading

API referenceAuthentication, the wire-compatible endpoint, and what the platform API exposes.Local BridgeThe shaidle CLI: run a task, wire one session, report seller usage.Compliance positionWhere your account stands, argued from the clause text, risks included.StatusWhat is running, and how incidents will be communicated.