HALO is a capability distribution and execution layer for AI products. A hardware maker or application team integrates one project boundary, then enables the model, memory, identity, service, and payment capabilities it needs.
#One project boundary
A project is the unit that owns client API keys, Memory namespaces, Authentication configuration, application users, and model settings. The HALO account owns one or more projects.
#Product surfaces
| Surface | What it owns | Primary caller |
|---|---|---|
| Model Gateway | Provider-native model requests, routing, and metering | Backend or trusted agent runtime |
| Memory | End-user scopes, topics, raw exchanges, summaries | Backend or model tool executor |
| Authentication | App users, identities, sessions, OAuth Apps | Application frontend and backend |
| Service Registry | Service metadata and ERC-8004 identity | Service publisher |
| Agent Access | Portable Access Identities, Connected Accounts, Client Access, Tool Grants | Client App backend and HALO account owner |
| Keeper | Inference provider supply, health, earnings, payouts | Model infrastructure provider |
#Credential boundaries
| Credential | Use | Exposure |
|---|---|---|
sk-… client key | Model Gateway, Memory, and Project-scoped Agent Access | Server only |
Project publishable key | Public Authentication endpoints | May be used by the project application |
Project user access token | Current Authentication user and OAuth consent | End-user session |
HALO platform user JWT | Project administration and owner-side Agent Access approval | HALO platform user session |
Provider/Resend/OAuth secrets | Server-to-server upstream access | Encrypted and never returned after save |
Agent Access accepts existing partner signup or HALO Project Authentication. An Identity OAuth Client handles Project identity only. Neither signup nor email equality grants Connected Account access; consent-based email linking and final Tool approval are explicit user actions.
#Request path
- 1Authenticate the project
The request presents the credential for its API surface.
- 2Resolve policy
HALO resolves project ownership, model configuration, usage limits, or Authentication settings.
- 3Execute
The gateway dispatches to a model, Memory selects project-scoped context, or Authentication issues a project-signed session.
- 4Meter and audit
Usage and security-sensitive operations are recorded without placing raw credentials in access logs.