# auth.md: Team Sefid (team.sefid.dev)

How an AI agent authenticates with Team Sefid, today.

## No authentication needed

Everything an agent can do on its own is public and needs no key, token or account:

- MCP: `https://team.sefid.dev/mcp` (tools: `speed_test`, `scan_status`, `get_report`, `agent_readiness_test`, `list_services`)
- The radar's read-only MCP: `https://team.sefid.dev/radar/mcp`
- A2A: `https://team.sefid.dev/a2a` (card at `/.well-known/agent-card.json`)
- REST: `https://team.sefid.dev/api/v1/` (described in `/openapi.json`)
- WebMCP tools on the home page, for an agent working in the visitor's browser

These are rate-limited per address. Each test gets its own Chrome on two dedicated CPU cores; several run at once when there are free slots, otherwise a test waits its turn.

## What needs a person

Ordering, paying, sending a site's access details and support tickets belong to a customer account. Sign-in is by the
customer's own mobile number and a one-time SMS code (or their authenticator app); there are no passwords, no API
keys and no OAuth for agents yet. An agent can prepare an order (the order page takes `?add=<service id>` from
`list_services`), but a person signs in and pays.

## Contact

https://team.sefid.dev/contact/
