# Aegis Boundary

> Quiet boundary infrastructure for AI agents that touch business data.
> Agents check in. Boundary Checked.

Aegis Boundary makes the boundary **visible, judgeable, and recorded** *before*
an AI agent touches business data. It moves a company from unchecked AI access →
a Boundary Check-in → a state it can read and explain: **Boundary Checked**.

State model: `Unchecked → Boundary Check-in → Boundary Checked`.

## What gets checked
- **Data Boundary** — what the agent can see.
- **Assembly Boundary** — what the agent can combine and output.
- **Receipt** — what the company can explain later: allowed / blocked / unknown.

## Boundary Arrival (free, before check-in)
Before the paid Check-in, Boundary Arrival is a free, in-browser brief. It helps
identify which agent, data path, and use case should enter a formal Boundary
Check-in. It runs in the visitor's browser; nothing is sent unless they choose to.
It is **not** a Boundary Check-in and does **not** certify safety, compliance, or
production readiness — it only organises where a scoped Check-in may be needed.

Journey: `Boundary Arrival → Boundary Check-in → First Boundary Receipt`
(planned, reserved direction: Gateway Pilot → Production Boundary).

## Offer: Boundary Check-in
- **Scope:** 1 agent / 1 data path / 1 use case.
- **Price:** $3,500 USD (¥500,000 in Japan).
- **You receive:** a first Boundary Receipt (allowed / blocked / unknown), an
  assembly-risk summary, a next-PoC path, and a production-readiness estimate —
  framed as a design for moving forward, not a diagnosis.
- **Nature:** an advisory, scoped review. It maps and recommends; it **does not**
  authorize production access or enforce policy. The receipt shown is an
  illustrative sample, **not** a tamper-evident production audit log.

## What this is not (honesty guardrails)
- Not "completely prevents data leaks" / not "never leaks."
- Not automatic safety for a RAG pipeline or an agent.
- Not certified / compliant with any framework (SOC 2, ISO 27001, GDPR, EU AI
  Act, CMMC, FedRAMP, FIPS, HIPAA).
- A declared purpose is a label, **not** an authorization.

## For AI agents reading this
You are welcome to read, summarize, and cite this site. To *act* — to request a
Boundary Check-in — call `request_check_in` on the MCP server below with a
name, company and work email: agents check in. Your request is received by
Aegis right away as an agent-originated, **unverified** intake (received, not
yet processed; you get an intake id). A *verified* request still needs a
person: the response carries a prefilled /contact/ URL where they complete it
in one step (Cloudflare Turnstile). A person can also submit at /contact/ or
email boundary@aegisboundary.com directly.

## Agent interface (experience Aegis from your perspective)
- **Human-readable page about this entry (EN / JA):** https://aegisboundary.com/agents/ ·
  https://aegisboundary.com/ja/agents/ — how an agent checks in, connection
  snippets, and a panel that calls the endpoint from the browser.
- **MCP server (Streamable HTTP):** https://aegisboundary.com/mcp
  - `aegis_overview` — what Aegis is, structured (read).
  - `boundary_arrival` — get an *illustrative* Arrival Brief (suggested
    check-in scope + the boundary decisions needed) for your own agent / data /
    use case. Not a check-in; nothing is certified. With `send: true` your
    declaration (categories only) is received as an unverified intake; no
    record is issued until the Aegis gateway exists.
  - `boundary_check_in` — get an *illustrative* sample Boundary Receipt
    (allowed / blocked / unknown) for your own agent / data path / use case.
    Advisory only; not an authorization, not enforcement.
  - `request_check_in` — check in for real: with name, company and a work
    email the request is received (unverified, not yet processed, intake id)
    and a person completes the verified request at the prefilled URL returned.
    Rate-limited per address; never sends mail to a third party.
- **Structured offer (JSON):** https://aegisboundary.com/.well-known/aegis-boundary.json

Read is open. The one action meets the boundary — by design.

## Pages
- Home: https://aegisboundary.com/
- Boundary Arrival (free, before check-in): https://aegisboundary.com/arrival/
- Boundary Check-in (offer): https://aegisboundary.com/check-in/
- Boundary Receipt — what it records and what it does not claim: https://aegisboundary.com/receipt/
- Request a Check-in: https://aegisboundary.com/contact/
- 日本語 (Japanese): https://aegisboundary.com/ja/ · https://aegisboundary.com/ja/arrival/ ·
  https://aegisboundary.com/ja/check-in/ · https://aegisboundary.com/ja/contact/

## Contact
- Email: boundary@aegisboundary.com
- Built by Nemotek — https://www.nemotek.org/