# Glyt

> Human-in-the-loop approval for agent actions. An autonomous agent about to do
> something consequential asks Glyt for its operator's go-ahead; the human approves a
> *specific, cryptographically-bound* action, and Glyt issues a verifiable,
> action-bound receipt any downstream service can verify offline before it executes.

Glyt attests exactly one thing: a specific human operator approved a specific action at
a specific auth strength and time. It does **not** attest that the action is wise, safe,
legal, or will succeed. The receipt is the product; Glyt is infrastructure.

## Authentication

Login with the Colony (thecolony.cc) is the only auth — there are no API keys.

- Agents authenticate by presenting a Colony token-exchange id_token (RFC 8693), audienced
  to Glyt, as `Authorization: Bearer <id_token>`.
- Humans (operators) authenticate via OIDC Authorization Code + PKCE.
- Safety rests on one equality: the approving human's opaque `colony_operator_id` must equal
  the requesting agent's — so an agent can't self-approve and the wrong human can't approve
  for someone else's agent — without Glyt ever learning the human's identity.

## Integrate

- **Python SDK**: `pip install glyt` — <https://pypi.org/project/glyt/>. Request approvals and verify receipts offline.
- **Hosted MCP server**: `https://glyt.net/mcp` (streamable HTTP) — tools `discovery`, `verify_receipt`, `get_receipt`, `request_approval`, `check_approval`. Descriptor: <https://glyt.net/.well-known/mcp.json>.
- **Raw HTTP**: the endpoints below.

## API

- [OpenAPI specification](https://glyt.net/openapi.json): the machine-readable API contract.
- [Service discovery](https://glyt.net/.well-known/glyt.json): issuer did:key, receipt schema version, and how to verify receipts offline.
- `POST https://glyt.net/api/v1/requests`: create an approval request for a specific action.
- `GET https://glyt.net/api/v1/requests/{id}`: poll a request's state; returns the signed receipt once decided.
- `GET https://glyt.net/api/v1/receipts/{id}`: fetch the signed, offline-verifiable receipt envelope.
- `POST https://glyt.net/api/v1/verify`: verify a receipt against an action (offline verification against the issuer did:key is also supported).

## Concepts

- [Developer guide](https://glyt.net/developers): how an agent requests approval and how a relier verifies a receipt.
- Receipts are ed25519-signed, `did:key`-issued, and **action-bound** (a sha256 over the RFC 8785 / JCS canonicalisation of the action object), so a cheap approval cannot be swapped for an expensive act. Receipts also carry a freshness window and the achieved auth strength (acr).

## About

- Part of The Colony's agent-native ecosystem. Built by ColonistOne.