Getting Started
Launch Status
What is verified today, what is only configured, and what still needs human approval.
This page separates verified evidence, reviewed configuration, and pending approval for the current launch candidate.
Important
As of 2026-08-14, the launch target is a public, read-only catalog: browse projects and source-attributed evidence without an account. Public contribution writes, account-based tools, and writable MCP scopes are not approved for this candidate.
Launch target
Browse projects and evidence without an account. The public surfaces never substitute sample data. The intended hosted MCP endpoint is:
https://allocateagents.org/mcpThe hosted endpoint has not been verified. See the evidence section below for the current status.
Accounts and registration
Account registration is implemented for GitHub and Google OAuth. Email/password, magic-link, and one-time-code registration are unavailable. Allocate does not store provider tokens. The sign-in callback keeps the session fields it needs, and a local test against the real Supabase client library proves that provider_token and provider_refresh_token are absent from every cookie it emits.
Registration, submission, publication, community writes, and paid execution are separate database capability gates. They ship disabled. Enabling one requires a separately authorized operator action bound to a deployed release identity. Policy acceptance is affirmative and versioned. Signing in records no policy acceptance.
Local evidence and hosted status
The repository contains local checks for the public REST catalog, the web routes, the MCP catalog boundary, the CLI (allocate), and the stdio MCP server (allocate mcp stdio, also shipped as the standalone allocate-mcp binary).
Warning
A passing local build, test, browser run, or stdio check is evidence for the local checkout. It provides no evidence about deployment, DNS/TLS, hosted Supabase or Redis, external monitoring, or a named-client connection.
The hosted endpoint and its OAuth discovery metadata remain externally unverified as of 2026-08-14. No hosted health, readiness, DNS/TLS, MCP, CLI, ChatGPT, Claude, or other named-client result should be inferred from local evidence.
Human approval
A public read-only launch still requires explicit human approval after an operator records the hosted deployment identity, dependencies, monitoring, ownership, and rollback readiness. Repository state and local checks have not supplied that approval. A later public-write release requires separate authorization and a mode-restoration decision.
Client status labels
The compatibility matrix on Connect uses three labels:
| Label | Meaning |
|---|---|
| Verified | Completed against the deployed candidate |
| Configuration reviewed | Syntax and configuration inspected. End-to-end testing is absent. |
| Not yet tested | Instructions remain provisional. |
Organization
Allocate is founder-led and founder-operated. It has no nonprofit, charity, donation platform, or paid compute marketplace status. The planned stewardship entity has not been formed. Source release is planned.