---
oauth-protected-resource: https://joglogistics.cl/.well-known/oauth-protected-resource
oauth-authorization-server: https://joglogistics.cl/.well-known/oauth-authorization-server
---

# auth.md - JogLogistics Agent Registration & Authentication

> Official Agent Authentication and Registration Guide for JogLogistics SpA (`https://joglogistics.cl`).

This document describes how autonomous AI agents and developer applications can authenticate, discover permissions, and interact programmatically with JogLogistics logistics services.

---

## 1. Service Identification
- **Service Name**: JogLogistics Agent Portal
- **Base Domain**: `https://joglogistics.cl`
- **MCP Endpoint**: `https://joglogistics.cl/api/mcp`
- **Skills Directory**: `https://joglogistics.cl/.well-known/agent-skills/index.json`
- **Resource Identifier**: `https://joglogistics.cl`
- **Contact / Operator**: `contacto@joglogistics.cl`

---

## 2. Discovery Endpoints
- **OAuth Authorization Server**: `https://joglogistics.cl/.well-known/oauth-authorization-server`
- **OAuth Protected Resource**: `https://joglogistics.cl/.well-known/oauth-protected-resource`
- **OpenID Configuration**: `https://joglogistics.cl/.well-known/openid-configuration`
- **API Catalog (RFC 9727)**: `https://joglogistics.cl/.well-known/api-catalog`
- **ARD Capability Manifest**: `https://joglogistics.cl/.well-known/ai-catalog.json`
- **MCP Server Card (SEP-1649)**: `https://joglogistics.cl/.well-known/mcp/server-card.json`

---

## 3. Supported Authentication Methods

### A. Dynamic Agent Registration
Agents may request ephemeral registration via the dynamic registration endpoint:
- **Registration URL**: `https://joglogistics.cl/api/agent/register`
- **Supported Identity Types**:
  - `identity_assertion` (`urn:ietf:params:oauth:token-type:id-jag`, `verified_email`)
  - `anonymous`
- **Credential Types**:
  - `bearer_jwt`
  - `api_token`
- **Claims URI**: `https://joglogistics.cl/api/agent/claim`
- **Revocation URI**: `https://joglogistics.cl/api/agent/revoke`

### B. Bearer API Token (Pre-shared / Managed)
Autonomous agents possessing an authorized API key or Bearer token should supply it via standard HTTP header:
```http
Authorization: Bearer <YOUR_API_TOKEN>
```

---

## 4. Scopes and Permissions

| Scope | Description | Access Level |
|---|---|---|
| `quote:create` | Request and calculate cargo freight quotes in Chile and South America | Public / Agent |
| `tracking:read` | Query operational status and GPS location of service orders | Public / Authorized |
| `services:read` | Read full service specifications, fleet data and route coverage | Public |
| `admin:write` | Internal ERP administration and dispatch control | Restricted |

---

## 5. Agent Policies & Rate Limits
- **Content Usage**: `Content-Signal: ai-train=no, search=yes, ai-input=yes`
- **Negotiation**: Send `Accept: text/markdown` to receive concise, token-efficient markdown responses.
- **Rate Limit**: 60 requests per minute per IP/Agent token.
- **Safety**: Do not transmit sensitive customer payment information over unencrypted channels.