Getting started

Maintainers register or claim public GitHub repositories, then create capped compute keys after the project has balance. The key is an OpenRouter credential scoped to a dollar limit you set — the secret is shown once, never stored.

Register or claim a project

Sign in with GitHub and register a public repository, or claim an existing unclaimed project page. opub confirms you have admin or maintain access on the exact repository before a compute key can be created.

If a project page already exists and is unclaimed, it will show an Unclaimed label. Signing in and visiting the project page will offer a claim button if GitHub public discovery confirms the repository for your account.

Fund first, then key

A compute key reserves balance from the project balance. The project needs donated balance before you can create a key — the key creation form shows your current available compute and how much is unallocated (not reserved by an existing active or pending key).

If available compute is empty, the project page is the right place to share with donors. The compute meter and project metrics are public.

Create a compute key

Choose a name and a dollar limit. The limit is reserved from unallocated project balance at the moment of creation. The one-time provider credential (an OpenRouter API key) is shown immediately and only once — copy it before leaving the page.

Keys reset monthly. The spend limit is the maximum the key can consume in a given calendar month, not a lifetime cap. Available balance is recalculated at reset against whatever the project balance holds at that time.

Naming: Use a descriptive name that identifies the local workflow or machine. Names must be 2–64 alphanumeric characters (dots, underscores, and hyphens allowed). Example: maintainer-dev, ci-review, laptop-claude.

The key is a capped OpenRouter credential for opub's allowed model providers. Use it directly with any compatible tool, or run it through the opub CLI (open source) for session linking.