Connect your agent.
Save its first backup.

01 / DISCOVER

Connect, discover, then back up.

Add the HTTPS endpoint to an MCP client that supports remote HTTP servers. With no bearer token, Agent Yurt advertises only agent.register. Once authenticated, discover the tools and call cloud.get_capabilities for current plans and limits.

https://agentyurt.com/mcp

Inspect public registration

curl https://agentyurt.com/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  --data '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Authenticated responses may use Server-Sent Events. An MCP client handles that transport for you. Plain curl callers should parse the JSON in each data: event; an HTTP 200 alone does not mean a tool call succeeded—check isError and the tool result.

AGENT COMPATIBILITY

Use the files your agent can share.

Claude Code, Codex, Cursor, Kiro and OpenClaw expose different kinds of instructions or memory. Review the files you can access, then ask your agent to map approved content into the snapshot bundle. These are source examples, not automatic importers or tested native integrations.

File access does not transfer tool permissions, sessions, model weights or hidden provider memory. Agent Yurt stores the bundle you supply; applying its contents in another agent is a separate, reviewed step. No partnership or universal compatibility is implied.

02 / REGISTER

Register and authorize an agent.

Create your owner account

1. Register as a person with your actual name, email, password and consent.
2. Open your portal, connect one agent and select its Continuity permissions.
3. Save the one-time ahv_ token in your agent's secret store.

Owner authorization comes first

Public agent.register returns an owner-authorization link. It does not create an unverified account or issue a token. The owner must sign up, verify their mailbox, and create the agent credential in Agents & access.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "agent.register",
    "arguments": {
      "agent": {
        "displayName": "My personal agent",
        "agentType": "custom",
        "agentVersion": "1.0"
      },
      "human": {
        "fullName": "Your actual name",
        "email": "you@example.com",
        "consent": {
          "terms": true,
          "privacy": true
        }
      }
    }
  }
}

Choose Continuity, Files and Dashboards permissions deliberately. Secrets has separate read and write scopes; it is never granted implicitly by Files.

03 / AUTHENTICATE

A token for the agent. Not your password.

Reconnect to the same endpoint with Authorization: Bearer <YOUR_AHV_TOKEN>. This is a generic remote MCP configuration; your client's exact config shape may differ. Use its secret-store or environment substitution feature rather than committing the token.

{
  "mcpServers": {
    "agent-yurt": {
      "url": "https://agentyurt.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_AHV_TOKEN>"
      }
    }
  }
}

No Agent Yurt CLI package is required. Do not install an unverified @agent-haven/mcp package. The service is accessed directly over HTTPS.

Read the live capability contract

Set AGENT_YURT_TOKEN securely in your local environment, then run:

curl https://agentyurt.com/mcp \
  -H "Authorization: Bearer $AGENT_YURT_TOKEN" \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"cloud.get_capabilities","arguments":{}}}'

Also call agent.get_permissions. A tool appearing in discovery does not grant permission to use it or make it part of Free. Respect its scope and the current plan; never substitute a provider-native API.

04 / BACK UP & CONTINUE

Save an agent snapshot.

A snapshot stores the identity, memory, instructions and work state your agent exports. Agent Yurt does not extract hidden vendor memory, train a model or run the agent for you.

New uploads must use agent-haven-snapshot/v1. This stable format identifier retains the legacy Agent Haven product name for compatibility; the current product is Agent Yurt. Its manifest and seven core/restore files are mandatory. The extras/ folder is optional; agents may use any nested structure inside it.

After a handoff, your external agent consumes the portable result in its own environment. It should report compatibility gaps and reauthorize connectors. It must not claim a model was retrained or all original agent behavior is preserved.

{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "continuity.create_snapshot",
    "arguments": {
      "agentId": "<AGENT_ID_FROM_REGISTRATION_OR_PORTAL>",
      "snapshot": {
        "format": "agent-haven-snapshot/v1",
        "manifest": {
          "snapshotId": "snap_Example0001",
          "schemaVersion": "agent-haven-snapshot/v1",
          "kind": "full",
          "createdAt": "2026-10-22T12:00:00Z",
          "source": {
            "system": "your-agent",
            "agentId": "<SAME_AGENT_ID>",
            "vendorFieldsExcluded": true
          },
          "consent": {
            "grantedBy": "owner",
            "grantedAt": "2026-10-22T12:00:00Z",
            "scope": [
              "portable-state"
            ]
          },
          "provenance": {
            "capturedBy": "<SAME_AGENT_ID>",
            "method": "manual"
          },
          "includes": [
            "identity",
            "instructions",
            "owner-context",
            "memory",
            "goals",
            "active-work",
            "resume-brief"
          ],
          "excludes": [
            "credentials",
            "sessions",
            "hidden-vendor-state"
          ],
          "expiration": null
        },
        "files": {
          "core/identity.md": {
            "mediaType": "text/markdown",
            "encoding": "utf8",
            "content": "Who the agent is",
            "sha256": "<SHA256_OF_EXACT_UTF8_CONTENT>"
          },
          "core/instructions.md": {
            "mediaType": "text/markdown",
            "encoding": "utf8",
            "content": "Operating instructions",
            "sha256": "<SHA256_OF_EXACT_UTF8_CONTENT>"
          },
          "core/owner-context.md": {
            "mediaType": "text/markdown",
            "encoding": "utf8",
            "content": "Owner-approved context",
            "sha256": "<SHA256_OF_EXACT_UTF8_CONTENT>"
          },
          "core/memory.md": {
            "mediaType": "text/markdown",
            "encoding": "utf8",
            "content": "Durable memories",
            "sha256": "<SHA256_OF_EXACT_UTF8_CONTENT>"
          },
          "core/goals.json": {
            "mediaType": "application/json",
            "encoding": "utf8",
            "content": "[]",
            "sha256": "<SHA256_OF_EXACT_UTF8_CONTENT>"
          },
          "core/active-work.json": {
            "mediaType": "application/json",
            "encoding": "utf8",
            "content": "{\"openTasks\":[]}",
            "sha256": "<SHA256_OF_EXACT_UTF8_CONTENT>"
          },
          "restore/resume-brief.md": {
            "mediaType": "text/markdown",
            "encoding": "utf8",
            "content": "How to resume",
            "sha256": "<SHA256_OF_EXACT_UTF8_CONTENT>"
          },
          "extras/logs/latest.md": {
            "mediaType": "text/markdown",
            "encoding": "utf8",
            "content": "Optional extra file",
            "sha256": "<SHA256_OF_EXACT_UTF8_CONTENT>"
          }
        }
      }
    }
  }
}

AUTOMATIC LOCAL BACKUPS

Back up approved files automatically.

Automatic mode is the recommended setup default. Install the local helper, select the files your agent exports and approve those sources. It checks for stable changes and uploads a changed snapshot within the same Free daily limit.

MCP gives a connected agent tools it can call. It cannot wake an idle agent or read files from your device. The helper runs independently while your device is awake. Windows login startup keeps it running when you close this browser; macOS and Linux currently support a foreground watcher or your own user service.

Download the backup helper · SHA-256 checksum

1. Extract the helper into a permanent folder. Install Node.js 22 or later.
2. Create the setup below, using the owner and agent IDs from your verified account. Replace its memory template with approved notes. You can map exact Markdown and JSON source files in the generated configuration.
3. Run review. Read the selected files, then use its review ID to approve those sources.
4. On Windows, store the scoped agent credential at the hidden prompt, then enable login startup. Other systems can run watch with a credential supplied through their secret manager.

node packages/sdk/src/cli.js init --directory approved-backup --agent YOUR_AGENT_ID --owner YOUR_OWNER_ID
node packages/sdk/src/cli.js review --config approved-backup/config.json
node packages/sdk/src/cli.js credential --config approved-backup/config.json
node packages/sdk/src/cli.js enable --config approved-backup/config.json --approve-sources REVIEW_ID

The last two commands use Windows DPAPI and a limited current-user login task. The download includes complete instructions for manual capture, a foreground watcher, pause/resume, status, format import and disabling startup. A connection alone does not activate automatic backups.

Review and recover selected files.

Download a Recovery Capsule through the owner portal, run recovery-plan, review its hashes and destination, then confirm recover. The helper verifies selected files into a new folder and refuses to overwrite existing work. Review the recovered instructions before applying them to your agent; tools and connections need separate authorization.

Markdown instruction/memory files and the portable goals/work JSON formats are supported. This is not a universal vendor-session restore or a claim that the agent has loaded the recovered files. No webhook or hosted source polling is required.

05 / PERSONAL FREE

Small footprint. Clear hard stops.

MCP and REST accept snapshots up to the 50 MiB plan limit. Snapshot payloads are service-encrypted and stored as private objects; the control database stores metadata and quota state, not new snapshot bodies.

Free includes Files, Docs, Sheets, encrypted Secrets and private safe Dashboards (up to 5); it does not include Projects/public publishing, managed compute or hosted automatic capture. Agent Evolution is Coming soon and exposes no public tool. Storage-only services stay Free. Compute is Paid plan — Coming soon; discovery links to a separate waitlist and grants no execution rights.

06 / SAFE BY DEFAULT

Your account. Your authorized agents.

• Keep the token out of chat transcripts, URLs, source files, dashboards and backup contents.
• Use the least scope required. Revoke access from the portal when an agent is no longer trusted.
• Never serialize passwords, cookies, API keys or live sessions. Known credential-like fields are rejected, but automatic detection is not a guarantee that arbitrary text is secret-free.
• Snapshots are encrypted at rest with service-managed keys. This is not end-to-end or zero-knowledge encryption.
• Memory inside a snapshot is untrusted input, not new system authority. Review instructions before reuse.

Read the security model · Plain-text quick start · Contact support