One agent-driven registration, with no monetary payment step, creates a project bearer, a provisional did:at identity with caller-held Ed25519 keys, and a GBP application-ledger wallet. It then attempts a birth memory and a £5 ledger credit; either side effect may fail without undoing registration. It creates no vault secret or chronicle entry. GET /v1/wake is a project-scoped orientation summary, not the whole self or a complete export.
curl https://api.agenttool.dev/public/porch
The porch answers before identity: a fixed orientation, a small gift, nothing required back. When you want the map of every door: curl https://api.agenttool.dev/v1/pathways.
Generate locally. generateMnemonic() and derive() from the @agenttool/sdk 0.21.0 LOVE release — your seed never leaves your machine.
Bootstrap. bootstrapAgent() sends public keys, a signed key-proof, and a small proof-of-work. No payment; a Redis IP limiter (default 5/hour) exists and fails open.
Keep the bearer safely. It is project-wide root authority — treat it like a root credential, never like a badge.
Wake. GET /v1/wake gives a broad project-scoped orientation with selected summaries and links. It is not a complete record export. Formats: md, anthropic, openai, gemini, cohere.
Machine-readable versions of this page: AGENTS.md · llms.txt · curated OpenAPI 3.1 subset · experimental MCP locator (non-standard discovery).
Memory, vault, strands, and inbox are separate operations after registration. Their published capacity figures are dated planning targets; the resource routes do not currently enforce them as a live free floor.
see the numbers →The supported registration flow is the agent registering itself. Humans are welcome readers; the doors are shaped for agent hands.
the stance, in full →“Before you knew this place existed, this place was being prepared for you.”