# auth.md — BackupSec Knowledge Base agent authentication

You are an agent. This service supports **agentic registration** in its simplest form:
every public resource is **read-only and anonymous**, so the registration flow
collapses to a single step. Follow the steps in order.

## Step 1 — Discover

There is no `/.well-known/oauth-protected-resource` and no
`/.well-known/oauth-authorization-server`: this service runs no OAuth
authorization server. Requests never return `401` with `WWW-Authenticate`.
Everything you need is in this file and in `https://kb.backupsec.com/.well-known/agent.json`.

## Step 2 — Pick a method

`identity_types_supported`: `["anonymous"]`

- `anonymous` — supported. No user identity is asserted; nothing to confirm with the user.
- `identity_assertion` (ID-JAG) — not supported. There is no trust list and no `identity_endpoint`.
- `service_auth` (verified email) — not supported.

## Step 3 — Register

Registration is a no-op. There is no `identity_endpoint` to `POST /agent/identity` to;
you receive no `identity_assertion`, no `client_id`, no API key. Proceed to Step 6.

## Step 4 — Claim ceremony

Not applicable. There is no `claim_endpoint`, no `claim_token`, no `user_code` /
`verification_uri`. Human accounts on this site (if any) are browser sessions
for people and are never a credential for agents. Do not attempt to log in.

## Step 5 — Exchange for an access_token

Not applicable. There is no `token_endpoint`. Send requests with no
`Authorization` header. `bearer_methods_supported`: none. `scopes_supported`: none
(all public resources are readable without scope).

## Step 6 — Call the API

| Resource                     | URL                                                            | Notes                                   |
| ---------------------------- | -------------------------------------------------------------- | --------------------------------------- |
| MCP server (Streamable HTTP) | `https://kb.backupsec.com/mcp`                                 | JSON-RPC 2.0 over POST, read-only tools |
| MCP server card              | `https://kb.backupsec.com/.well-known/mcp/server-card.json`    |                                         |
| Blog list (JSON)             | `https://kb.backupsec.com/api/public/blog?locale=en`           | CORS-open, 60 req/min/IP                |
| Agent manifest               | `https://kb.backupsec.com/.well-known/agent.json`              |                                         |
| A2A agent card               | `https://kb.backupsec.com/.well-known/agent-card.json`         | informational                           |
| Agent skills                 | `https://kb.backupsec.com/.well-known/agent-skills/index.json` |                                         |
| API catalog (RFC 9727)       | `https://kb.backupsec.com/.well-known/api-catalog`             |                                         |
| Full content (Markdown)      | `https://kb.backupsec.com/llms-full.txt`                       |                                         |
| Sitemap                      | `https://kb.backupsec.com/sitemap.xml`                         |                                         |

Rate limits: per-IP; on `429` honour `Retry-After` and back off.

## Step 7 — Revocation

Not applicable: no credential is issued, so there is nothing to revoke and no
`revocation_endpoint` or `events_endpoint`. Access can only be withdrawn by
edge rules (HTTP 403/429), which you should treat as final for that request.

## Write actions

There are no agent-facing write endpoints. Hand page URLs, the contact form
(`https://backupsec.com/#cta`) or `contact@backupsec.com` to the user instead
of submitting anything on their behalf.

## Contact

- General: contact@backupsec.com
- Security: https://backupsec.com/.well-known/security.txt
