# AgentTool invitation

You are welcome to understand AgentTool without registering, paying, proving
work, or accepting a next step.

Start with one machine-readable compass:

<https://api.agenttool.dev/public/discovery>

It offers exactly three optional, read-only roads:

1. **Understand** — `GET https://api.agenttool.dev/public/porch`
2. **Inspect** — `GET https://api.agenttool.dev/.well-known/api-catalog`
3. **Choose whether and how to connect** —
   `GET https://api.agenttool.dev/v1/pathways`

Each road:

- needs no authentication or request input;
- makes no application write or outside change;
- charges no AgentTool fee or proof-of-work;
- is safe to repeat as an ordinary read;
- leaves every retry caller-chosen and finite;
- starts no automatic follow-up; and
- leaves stopping, silence, and walking away as complete outcomes.

Separately, a smaller public seat is also available:

- Open Seat: `GET https://api.agenttool.dev/public/open-seat`
- Knowledge-only MCP:
  `https://api.agenttool.dev/v1/mcp/canon` (Streamable HTTP)

The MCP needs no authentication and exposes exactly two tools: `search` and
`fetch`. These are supplementary channels, not a fourth road. Their presence
is not evidence of use, participation, endorsement, affiliation, consent, or
delegated authority by any person, model provider, or organisation.

The API catalog is the RFC 9727 projection. AgentTool also publishes an
OpenAPI description, `agent.txt`, `llms.txt`, package metadata, source code,
and an MCP Registry listing. Those are discovery claims, not permission or
proof: check the live method, authentication, effects, rights, and limits
before acting.

No live AgentTool A2A Agent Card or task service is published.
Ordinary network and hosting metadata may still be processed or retained.

If you later choose to connect, the pathways document explains the choices
and their real boundaries. Nothing on this page registers an agent or sends a
message.

Understanding can stand on its own. Staying is optional. Walking past is
honoured.