# Brifing auth.md

How AI agents, crawlers and other automated clients authenticate with Brifing (https://brifing.si).

## Audience

This document is for software agents — assistants, MCP clients, A2A agents, crawlers and scripts — that read Brifing on their own or on behalf of a person.

## Summary

- **Everything public needs no credentials.** Story pages, topics, publisher pages, the REST API, the MCP server and the A2A agent are anonymous and read-only.
- **There is no agent registration.** You do not need to sign up, request a key or provide an identity to use the public surfaces.
- **Personal data is not available to agents.** A person's daily briefing, saved stories, lists, comments and subscription live behind their own Brifing sign-in and are not exposed through any agent interface. Delegated (OAuth) access for agents is not offered yet; this document will describe it when it is.

## Supported methods

| Method | Identity type | Credentials | Where |
| --- | --- | --- | --- |
| Anonymous | `anonymous` | none | `GET https://brifing.si/api/v1/*`, `POST https://brifing.si/mcp`, `POST https://brifing.si/a2a`, any page with `Accept: text/markdown` |

There is no provisioning or registration endpoint. Do not send passwords, session cookies or tokens from a person's Brifing account to these endpoints; they are ignored.

## Credential use

None. Requests carry no `Authorization` header. Responses are the same for every caller and are cached at the edge, so please:

- reuse responses for at least a few minutes instead of polling,
- identify your client in `User-Agent`,
- cite the publisher and the original article URL included with every story.

## Discovery

- API catalog: https://brifing.si/.well-known/api-catalog
- OpenAPI: https://brifing.si/openapi.json
- MCP server card: https://brifing.si/.well-known/mcp/server-card.json
- A2A agent card: https://brifing.si/.well-known/agent-card.json
- Developer docs: https://brifing.si/developers

## Contact

hello@horusstudios.com — Horus Studios, publisher of Brifing.