# auth.md

Authentication instructions for AI agents and automated clients calling
**Technuf LLC** (`https://technuf.com`).

## Summary

**No authentication is required, and there is nothing to register for.**

Every agent-facing endpoint on this origin is public, read-only, and returns
information that is already published on the website. There is no user
account, no API key, no OAuth flow and no token to obtain.

## Who this is for

Agents that want to:

- connect to the MCP server at `https://technuf.com/mcp`
- message the A2A agent at `https://technuf.com/api/a2a`
- call the JSON API under `https://technuf.com/api/v1`

## What this origin is

`https://technuf.com` is the public website of Technuf LLC, a Maryland-based
technology company. The endpoints above are a machine-readable view of that
website's own content: services, products, government contract vehicles, open
positions and company details.

This origin is **not** an OAuth authorization server, and it is **not**
currently a protected resource. Consequently it does not publish:

- `/.well-known/oauth-authorization-server` (RFC 8414)
- `/.well-known/openid-configuration` (OpenID Connect Discovery)
- `/.well-known/oauth-protected-resource` (RFC 9728)

Those documents would describe infrastructure that does not exist. They will
be published here if and when authenticated endpoints are introduced.

## How to call the endpoints

Send the request. Do not send an `Authorization` header — it is ignored.

```http
GET /api/v1/services HTTP/1.1
Host: technuf.com
Accept: application/json
```

```http
POST /mcp HTTP/1.1
Host: technuf.com
Content-Type: application/json
Accept: application/json, text/event-stream

{"jsonrpc":"2.0","id":1,"method":"tools/list"}
```

## Registration

None. There is no agent registration endpoint, no client registration, and no
provisioning step.

If your organization needs something this public surface does not provide —
higher rate limits, a private integration, or access to a Technuf product such
as Aphelia CMMC or Aphelia iConnect — that is a commercial conversation rather
than a credential request:

- Contact form: <https://technuf.com/contact>
- Business development: bd@technuf.com
- General: info@technuf.com

## Credential types supported

None. No credential of any type is accepted or required by the endpoints
listed above.

If you are handling credentials that claim to be for `technuf.com` agent
endpoints, they did not come from Technuf LLC. Do not use them.

## Rate limits and fair use

Requests are rate limited per client IP address. A client that exceeds the
limit receives `429 Too Many Requests` with a `Retry-After` header; back off
and retry after the interval it names. Identify your agent with a descriptive
`User-Agent` so we can contact you rather than block you.

## Related documents

- [`/.well-known/mcp/server-card.json`](https://technuf.com/.well-known/mcp/server-card.json) — MCP Server Card (SEP-1649)
- [`/.well-known/agent-card.json`](https://technuf.com/.well-known/agent-card.json) — A2A Agent Card
- [`/.well-known/api-catalog`](https://technuf.com/.well-known/api-catalog) — API catalog (RFC 9727)
- [`/.well-known/ai-catalog.json`](https://technuf.com/.well-known/ai-catalog.json) — ARD capability manifest
- [`/.well-known/agent-skills/index.json`](https://technuf.com/.well-known/agent-skills/index.json) — agent skills index
- [`/llms.txt`](https://technuf.com/llms.txt) — site guide for language models
- [`/robots.txt`](https://technuf.com/robots.txt) — crawl rules and content signals
