# Smart Vision auth.md

Welcome to the agent authentication and registration guide for Smart Vision (`smartvisionegy4.com`).

This service implements agentic registration per the [Auth.md](https://workos.com/auth-md) specification, allowing automated agents to discover capabilities, authenticate, and interact with Smart Vision business consulting services.

## 1. Discovery

Agents can discover authorization and protected resource metadata at the following endpoints:

- **Resource Server**: `https://smartvisionegy4.com`
- **Authorization Server**: `https://smartvisionegy4.com`
- **Protected Resource Metadata**: `https://smartvisionegy4.com/.well-known/oauth-protected-resource`
- **Authorization Server Metadata**: `https://smartvisionegy4.com/.well-known/oauth-authorization-server`
- **OpenID Connect Configuration**: `https://smartvisionegy4.com/.well-known/openid-configuration`
- **API Catalog (RFC 9727)**: `https://smartvisionegy4.com/.well-known/api-catalog`

## 2. Supported Registration Methods

### Method 1: Identity Assertion (ID-JAG & Verified Email)
- **Identity Type**: `identity_assertion`
- **Assertion Types Supported**:
  - `urn:ietf:params:oauth:token-type:id-jag`
  - `verified_email`
- **Registration Endpoint**: `https://smartvisionegy4.com/agent/auth`
- **Claim Ceremony Endpoint**: `https://smartvisionegy4.com/agent/claim`
- **Revocation Endpoint**: `https://smartvisionegy4.com/agent/revoke`
- **Credential Types**: `api_key`, `bearer_token`

Agents presenting an identity assertion minted by a trusted IdP (with `aud: https://smartvisionegy4.com`) can register and receive an authorization credential.

### Method 2: Anonymous Registration
- **Identity Type**: `anonymous`
- **Registration Endpoint**: `https://smartvisionegy4.com/agent/auth`
- **Claim Ceremony Endpoint**: `https://smartvisionegy4.com/agent/claim`
- **Credential Types**: `api_key`, `bearer_token`

Agents operating without a prior user identity can register anonymously. If the user later chooses to take ownership, the agent initiates the claim ceremony at the claim endpoint.

## 3. Token & Credential Usage

When calling protected endpoints (such as submitting consultations or managing settings), provide credentials via standard HTTP headers:

```http
Authorization: Bearer <access_token>
```

Or for API keys:

```http
X-API-Key: <api_key>
```