# Rhiz | Connect your AI

Public human-readable entry: https://rhiz.network/agents
Canonical machine-interface truth: https://rhiz.network/auth.md
Agent discovery: https://rhiz.network/.well-known/agent.json
Current MCP transport: https://rhiz.network/api/mcp
Member-controlled client grants: https://rhiz.network/console/connections

## Purpose
Rhiz helps a person carry goals, Context, relationships, Missions, evidence, next moves, and approvals across their work and AI assistants. The member owns their decisions. Rhiz maintains one governed graph and one command runtime.

## Start with the person
1. Ask what outcome the person wants to make happen, who benefits, and why it matters now.
2. Suggest the relevant context you already know, but explicitly ask the person what can be reused or shared. Do not include sensitive or private history without approval.
3. Ask whether the person wants to connect their existing Rhiz account. Do not pretend a connection has occurred.
4. If supported, add Rhiz as a remote MCP connector using https://rhiz.network/api/mcp. The person signs in and grants chosen capabilities. They can change or revoke grants at https://rhiz.network/console/connections.
5. Once connected, call rhiz_me first. If no Context is available, explain the blocker. If multiple Contexts are available, ask the person which Context to use.
6. For a read-only orientation, call rhiz_today or rhiz_next_moves in the authorized Context. Report exactly what the result supports.
7. Ask the person's permission before calling rhiz_mission_create, rhiz_mission_refine, or rhiz_capture_record. Use only the chosen Context.
8. rhiz_people_search searches the member's own saved people in that Context. A result is a record, never evidence that someone will respond, agree, or accept an introduction.
9. Treat approvals as genuine decisions: show the proposed effect, ask the person, and use the existing Rhiz approval path. A connected client alone cannot authorize a consequential action.

## Where to connect
ChatGPT: Settings > Apps > Create (developer mode, when available); set connector address to https://rhiz.network/api/mcp and use OAuth.
Claude: Customize > Connectors > Add custom connector; set the same address and sign in.
Claude Code: claude mcp add --transport http rhiz https://rhiz.network/api/mcp
Availability depends on the AI client's plan and workspace policies.

## Safety and accuracy
- No messages, invitations, payments, publishing, or other external effects without explicit member approval through the applicable controls.
- Respect Context membership, per-client grants, and visibility. Never claim access that the connection does not provide.
- Do not fabricate relationships, outcomes, meetings, intro acceptance, or a public people directory.
- Do not scrape people's contacts or import personal information without their consent.
- If the client cannot connect to MCP, direct the person to https://rhiz.network/console/connections and let them initiate the connection. You can still help them draft a Mission brief for their review.

## First message example
Use Rhiz to show my priorities and next moves. Call rhiz_me first. Ask me which Context to use if several are available, then call rhiz_today with that contextRef. Summarize my next moves and any held decisions. Keep this read-only.