# RegSentry API and MCP authentication

This page describes how agents and scripts authenticate to the RegSentry REST
API v1 and the MCP endpoint. Neither offers OAuth, dynamic client registration
or any agent self-registration protocol; credentials are issued only by a human
account owner, as described below.

## 1. Public (no credentials)

- MCP endpoint: `POST https://regsentry.com/mcp` (Streamable HTTP). Without a key
  it lists six public, read-only tools: `inspect_site_tracking`,
  `inspect_runtime_consent`, `interpret_consent_evidence`,
  `compare_consent_observations`, `export_consent_report`,
  `get_remediation_playbook`.
- OpenAPI description: `GET https://regsentry.com/api/v1/openapi.json`.
- Docs: https://regsentry.com/docs and https://regsentry.com/agents.

Only inspect sites you own or are authorized to test.

## 2. Scoped bearer API key (account access)

1. A human account owner signs in at https://regsentry.com/login and creates a key
   under **API & agents** at https://regsentry.com/owner/dashboard. The token is
   shown once.
2. Send it on every request: `Authorization: Bearer rs_live_...`
3. Scopes: `read`, `scan`, `manage`. New keys default to `read` + `scan`;
   the owner can choose read-only or full access (`manage`, which implies the
   others) instead.
4. REST errors: no bearer token → `401 missing_token`; a malformed, unknown,
   revoked or unverified-account key → `401 invalid_token`; a valid key without
   the needed scope → `403 insufficient_scope`; a plan without the feature →
   `403 plan_required`.
5. The same key unlocks the REST API v1 (`https://regsentry.com/api/v1/*`) and the
   account tools on `https://regsentry.com/mcp`. API and agent access depend on
   the account's plan: https://regsentry.com/pricing.

Use is subject to the Terms (https://regsentry.com/terms) and Privacy Policy
(https://regsentry.com/privacy). Results are technical observations, not legal
advice or a compliance certification.
