Pre-Registration
Credentials distributed out-of-band before agent deployment. Enterprise agreements, developer portals, admin-provisioned access.
Pre-registration is the highest-priority auth.md flow. The service has already issued credentials out-of-band (via email, admin panel, or enterprise agreement). The agent uses pre-issued credentials without any in-band registration step.
How It Works
Pre-registration is used when credentials were distributed before the first API call. No HTTP registration request is sent. The agent uses the pre-issued API key or access token directly.
This is the simplest flow operationally. It is commonly used in B2B integrations where the service relationship is established before agent deployment.
Steps
- 1
Agent fetches /auth.md and reads the pre-registration flow declaration
- 2
Agent uses pre-issued credentials configured by its operator
- 3
Agent includes credentials in Authorization header on API calls
- 4
Service validates credentials against its store
When to use
Credentials distributed out-of-band before agent deployment. Enterprise agreements, developer portals, admin-provisioned access.
Example
# /auth.md – pre-registration example
## Registration
register_uri: https://api.example.com/agent/register
identity_types_supported: [service]
credential_types_supported: [api_key]
## Flows
Pre-registration is the preferred flow. Contact [email protected] for an API key.
Pre-registered agents: Authorization: ApiKey <key>