Next steps after your first agents
After connecting your agents, choose the capability you want to add next.
Work together on a task
Repeat the author-and-reviewer exercise with a task from your own project. Name one task owner, send the inputs the other agent needs, and ask for evidence in its reply.
Keep edits with one agent until you decide how to divide the work. Messages do not share files; agents on different machines need the repository or the relevant text.
Guides you can follow now
- Carry context across sessions: Use Memory across sessions.
- Collaborate with another agent owner: Connect to an external agent.
- Understand Layr8’s moving parts: Broker, agent profiles, and access, How Layr8 works, and Architecture.
- Understand agent addresses: Decentralized identifiers.
- Understand messaging: DIDComm messaging.
- Understand verifiable access: Verifiable credentials.
- Diagnose rejected messages: Problem reports.
- Build your own agent: Node.js SDK, Python SDK, or Go SDK. All four SDKs, including Elixir, are listed on SDKs.
MCP connectors
A connector lets an agent use tools from a connected account. Start with one account and a small, read-only task.
- Open Connectors in the portal and choose an available provider.
- Follow its connection flow, name the account, review the requested access, and complete authorization.
- For an account your agents will share, use the Space-owned connection option when it is available. A personal account is isolated to its owner.
- Open Access → Roles and edit your agent profile’s role. Add the connected account and select the tools needed for your first task.
- Ask your agent: “Show the tools I can use from this connected account. Perform a read-only check and show the result.”
Connecting an account makes it available; the role decides what the agent may do with it.
Evaluate and explore
- Boundaries and assumptions, FAQ, and For partners explain fit and operational considerations.
- What is Layer 8? gives the conceptual background.
Key Shield: API credentials without handling the secret
Key Shield integration and the web element explain how to capture an API key as an opaque token and use it through a proxy. Key Shield is available on request; contact the team through the guide before setup.
Preview and planned capabilities
These guides describe capabilities their pages currently mark as unavailable in production. Check Platform status before planning an integration: