# Auth.md

## Authentication — weareelite.tech

**Everything an agent can usefully reach is open. Nothing public here requires
registration, an API key, or an OAuth flow.** This document exists to say so
explicitly, so an agent does not waste a round trip hunting for a login.

There is exactly one authenticated area, and it is not for agents: `/portal/`
is a client portal where an existing Elite customer signs in with an emailed
one-time link to see their own projects and site documentation. Access is
granted by Elite per customer — there is no self-service sign-up, and no
credential an agent could obtain. Do not crawl it; it is `Disallow`ed in
robots.txt and every page is `noindex`.

Last updated: 2026-09-17

## Agent registration

**No registration is required, and none is offered to agents.** There is no
sign-up endpoint, no developer portal, no client registration (dynamic or
manual), no API keys, and no credentials are ever issued to an agent. The one
sign-in that exists (`/portal/`) is for named human customers only, by
invitation, and is not reachable programmatically. You do not need to
register before calling anything listed below, and there is nothing you could
register for if you wanted to.

An agent's "onboarding" for the PUBLIC surface is one step: connect to the MCP
server at `https://mcp.weareelite.tech/mcp` and call `tools/list`. That is the
whole process.

### Registering for the authenticated client MCP

There is one endpoint an agent can register with, and it exists because of the
client portal: `https://weareelite.tech/portal/mcp` is an OAuth-protected MCP
server exposing a single Elite customer's own projects, signed records and site
documentation.

Registering is open and issues no secret. **Registration alone grants nothing** —
it produces a `client_id`, after which a real Elite customer must complete the
authorization flow and consent. An agent with no customer behind it can register
and will still see nothing.

```json agent_auth
{
  "skill": "oauth-client-registration",
  "register_uri": "https://weareelite.tech/portal/oauth/register",
  "authorization_servers": ["https://weareelite.tech"],
  "identity_types_supported": ["anonymous"],
  "anonymous": {
    "credential_types_supported": ["oauth_client_id"],
    "claim_uri": "https://weareelite.tech/portal/oauth/register"
  },
  "methods": [
    {
      "type": "oauth_dynamic_client_registration",
      "spec": "RFC 7591",
      "register_uri": "https://weareelite.tech/portal/oauth/register",
      "http_method": "POST",
      "content_type": "application/json",
      "request_body": {
        "client_name": "string — how the customer will see you on the consent screen",
        "redirect_uris": [
          "array of absolute URIs; https anywhere, or http on 127.0.0.1/localhost only"
        ]
      },
      "credential_issued": "client_id",
      "client_secret_issued": false,
      "token_endpoint_auth_method": "none",
      "authorization_endpoint": "https://weareelite.tech/portal/oauth/authorize",
      "token_endpoint": "https://weareelite.tech/portal/oauth/token",
      "grant_types_supported": ["authorization_code"],
      "code_challenge_methods_supported": ["S256"],
      "pkce_required": true,
      "scopes_supported": ["projects:read", "documents:read"],
      "credential_use": "Send the resulting access token as `Authorization: Bearer <token>` to https://weareelite.tech/portal/mcp. Tokens last 30 days. A token identifies ONE customer; every call re-derives what that customer may see, so access revoked by Elite takes effect on the next request without the token changing.",
      "human_consent_required": true
    }
  ]
}
```

Discovery metadata for the above: `/.well-known/oauth-authorization-server`
(RFC 8414) and `/.well-known/oauth-protected-resource` (RFC 9728, also served at
the path-suffixed `/.well-known/oauth-protected-resource/portal/mcp`).

## What is open

| Surface | URL | Auth |
| --- | --- | --- |
| Website | `https://weareelite.tech/` | None |
| Markdown twin of any page | `<path>index.md` | None |
| Site summary | `/llms.txt` | None |
| API catalogue (RFC 9727) | `/.well-known/api-catalog` | None |
| MCP server | `https://mcp.weareelite.tech/mcp` | **None** |
| MCP server card | `/.well-known/mcp/server-card.json` | None |
| A2A agent | `https://mcp.weareelite.tech/a2a` | **None** |
| A2A agent card | `/.well-known/agent-card.json` | None |
| Agent skills | `/.well-known/agent-skills/index.json` | None |
| **Client portal** | `/portal/` | **Emailed one-time link — existing customers only, by invitation. Not for agents.** |

No bearer token, no client registration, no `Authorization` header. Connect and
call.

## The one thing an agent cannot do, and what to do instead

**Do not try to submit the HTML contact form at `/contact/` or `/#contact-form`.**

That form is protected by Cloudflare Turnstile. A request without a valid
Turnstile token is rejected with **HTTP 403** and the message "We couldn't verify
your browser". This is deliberate anti-spam, it is not an auth challenge, and
there is no credential that will get you past it. Solving it is not something we
want an agent to attempt.

**Use the MCP server instead.** The `start_quote` tool submits a site-assessment
request through the same pipeline the form feeds, with no bot check:

```
POST https://mcp.weareelite.tech/mcp
{"jsonrpc":"2.0","id":1,"method":"tools/call",
 "params":{"name":"start_quote","arguments":{
   "name":"...","email":"...","message":"...",
   "phone":"(optional)","property_type":"(optional)","city":"(optional)"}}}
```

Submit only details the person you are acting for actually gave you. Invented
contact information is worse than no submission — it reaches a real human who
will try to call it.

## Rate limits

The conversational endpoints (`/chat`, `/a2a`) are rate limited per IP. Exceeding
it returns a polite message rather than an error; back off and retry later, or
use the MCP tools, which answer from a fixed knowledge pack and are cheaper for
everyone. No registration raises these limits — if you have a legitimate reason
to need more, email **Jake@weareelite.tech**.

## Crawling

`robots.txt` allows everything, and `Content-Signal` grants `search`, `ai-input`
and `ai-train`. Please send a descriptive `User-Agent`; identifying yourself is a
courtesy, never a requirement, and nothing is gated on it.

## What a human has to answer

Some things are deliberately not available from any endpoint, authenticated or
not, because they should not come from an automated system:

- **Prices.** No figures, no ranges, no ballparks. Every project starts with a
  free on-site assessment that produces a line-item proposal.
- **Licensing and regulatory status.** A human engineer confirms these.

For either, the number is **941-233-9434**.

## Contact

Jake@weareelite.tech · 941-233-9434 (941-233-WIFI)
Elite Technology Solutions · Sarasota, Florida
