# auth.md

This document describes how AI agents and automated clients discover, authenticate, and register to interact with TransAsia Integrate Services Ltd. per the [auth.md specification](https://workos.com/auth-md), RFC 9728 (OAuth Protected Resource Metadata), and RFC 8414 (OAuth 2.0 Authorization Server Metadata).

## Site Identity

- **Name**: TransAsia Integrate Services Ltd. (RL-1472)
- **Domain**: https://www.transasia.ltd
- **Description**: Bangladesh Government Licensed (BMET RL-1472) and ISO 9001:2015 certified international recruitment agency.

## Access Model

All public resources, services information, recruitment catalogs, and discovery endpoints on this site are **open and accessible**. AI agents and automated crawlers may read content without credentials.

For interactions requiring identity assertions or authenticated agent submissions:
- Anonymous access is supported for read operations and public inquiries.
- Agent and User identity assertions are supported via Bearer token authorization headers.

## Agent Registration & Auth Endpoints

- **Register URI**: `https://www.transasia.ltd/auth.md`
- **Registration Endpoint**: `https://www.transasia.ltd/auth.md`
- **Identity Endpoint**: `https://www.transasia.ltd/auth.md`
- **Claim URI / Endpoint**: `https://www.transasia.ltd/auth.md`
- **Revocation Endpoint**: `https://www.transasia.ltd/.well-known/oauth-authorization-server`
- **Identity Types Supported**: `anonymous`, `agent`, `user`, `identity_assertion`
- **Credential Types Supported**: `none`, `bearer`
- **Assertion Types Supported**: `urn:ietf:params:oauth:token-type:id-jag`, `verified_email`
- **Bearer Methods Supported**: `header`
- **Scopes Supported**: `openid`, `profile`, `email`, `agent_access`, `read`, `public`

## OAuth & OIDC Discovery Metadata

TransAsia publishes complete machine-readable discovery documents:

| Standard | Discovery Endpoint |
|---|---|
| **OAuth Protected Resource (RFC 9728)** | `https://www.transasia.ltd/.well-known/oauth-protected-resource` |
| **OAuth Authorization Server (RFC 8414)** | `https://www.transasia.ltd/.well-known/oauth-authorization-server` |
| **OpenID Connect Discovery 1.0** | `https://www.transasia.ltd/.well-known/openid-configuration` |
| **HTTP Message Signatures Directory** | `https://www.transasia.ltd/.well-known/http-message-signatures-directory` |

## Agent Discovery Resources

| Protocol / Standard | Endpoint URL | Description |
|---|---|---|
| **API Discovery Catalog (RFC 9727)** | `https://www.transasia.ltd/.well-known/api-catalog` | RFC 9727 API catalog linkset for REST & OpenAPI discovery |
| **Agent Skills Index (RFC v0.2.0)** | `https://www.transasia.ltd/.well-known/agent-skills/index.json` | Catalog of structured skill markdown files |
| **MCP Server Card (SEP-1649)** | `https://www.transasia.ltd/.well-known/mcp/server-card.json` | Model Context Protocol server capabilities & SSE endpoint |
| **ARD Capability Manifest** | `https://www.transasia.ltd/.well-known/ai-catalog.json` | Agentic Resource Discovery manifest with semantic queries |
| **DNS-AID Discovery** | `https://www.transasia.ltd/.well-known/dns-aid` | DNS-AID service parameter directory |
| **Sitemap** | `https://www.transasia.ltd/sitemap.xml` | XML sitemap of all public pages |
| **OpenAPI Specification** | `https://www.transasia.ltd/docs/api/openapi.json` | OpenAPI 3.0 specification |

## WebMCP (Browser Model Context)

For in-browser agent tools, TransAsia implements WebMCP via `navigator.modelContext.registerTool()` and `navigator.modelContext.provideContext()`. Agents executing inside compatible browsers have immediate access to `get_company_info`, `search_services`, `submit_employer_inquiry`, `submit_jobseeker_inquiry`, and `contact_support`.