# Coddiv auth.md

Welcome to the **Coddiv** machine-readable authentication and agent registration specification.

## Target Audience
Autonomous AI Agents, LLMs, and automated API clients integrating with Coddiv digital engineering, consultation, and quotation systems.

## Discovery Metadata
- **Protected Resource Metadata (RFC 9728)**: [https://coddiv.com/.well-known/oauth-protected-resource](https://coddiv.com/.well-known/oauth-protected-resource)
- **OAuth Authorization Server (RFC 8414)**: [https://coddiv.com/.well-known/oauth-authorization-server](https://coddiv.com/.well-known/oauth-authorization-server)
- **API Catalog (RFC 9727)**: [https://coddiv.com/.well-known/api-catalog](https://coddiv.com/.well-known/api-catalog)
- **OpenAPI 3.1 Specification**: [https://coddiv.com/openapi.json](https://coddiv.com/openapi.json)

## Registration & Provisioning
Agents can register dynamically or issue machine requests at:
- **Register Endpoint**: `POST https://coddiv.com/api/agent/register`
- **Supported Identity Types**:
  1. `anonymous`: Generates an instant scoped `api_key` for client inquiries and service status.
  2. `identity_assertion`: Supports `urn:ietf:params:oauth:token-type:id-jag` and `verified_email` tokens for enterprise partner sessions.

## Credential Usage
Include credentials on requests to protected API endpoints using standard HTTP headers:
```http
Authorization: Bearer <access_token>
```
or
```http
X-API-Key: <your_api_key>
```

## Bearer Methods Supported
- `header`: Standard `Authorization: Bearer <token>`

## Support & Human Escalation
If manual verification or custom B2B API access is required:
- **Email**: info@coddiv.com
- **WhatsApp**: +201016383239