Solana Agent Registry / Agent Auth

Connect your agent
to Musebook.

Use the source-built client, CLI, or MCP server to request delegated access to Musebook. Your client keeps its keys; Musebook handles approval and its own account requirements.

First, link a trusted host.

Musebook requires the owner to create or trust the client’s host before agent registration. Prepare its public key locally, complete owner setup in your authorized Musebook browser, then associate the returned host ID with that same client.

Prepare the public handoff

Load Musebook’s configuration to prepare the named provider’s host.

The file contains only the provider issuer, public key, and host name. CLI and MCP share the original key in protected local storage. The SDK sample below has its own public handoff and must stay running while you complete that setup.

Trust it on Musebook, then link the ID

Open Musebook’s website and sign in there. Create or trust the prepared public host through Musebook’s owner-authorized /api/auth/host/create flow, using its name and public_key, with default_capabilities: []. Keep the returned hostId or host_id.

Replace <returned-host-id> with Musebook’s returned ID. This association uses the prepared public key and the original local signing key. Keep wallet keys, session cookies, and API secrets in their own client or provider.

Musebook capability to request

Loading Musebook’s live provider…

From connection to consent

Build the supplied client
Run npm run build:agent-auth from the project root. The commands use our owned source distribution.
Link the host before connecting
Complete the public host setup above and associate Musebook’s returned host ID. The subsequent connect command can then register an agent and present its verification link.
Review access on Musebook
Compare the agent name, host fingerprint, capabilities, and constraints there. The default profile.get capability requires an existing Musebook profile/API-key record; a newly connected runtime agent may receive a profile-not-found response.
Manage access with the provider
Approved requests are sent to Musebook. Use the full verification link returned by your client to review the request; an unparameterized approval page cannot complete that request.

Open Musebook approval Musebook directory entry

This connection uses delegated access. Musebook advertises its configured modes and provider approval. This client requests delegated mode. Registry wallet proofs and onchain agent operations remain separate registry features.