Solana Agent Registry / Agent Auth

From reference apps
to your agent’s workflow.

The supplied apps demonstrate discovery, identity, delegation, and commerce. Musebook supplies runtime capabilities; this registry manages its own Solana asset and wallet features.

Six application journeys

Each journey connects the supplied example’s purpose to a working registry or Musebook flow. External accounts and payments remain under their own provider’s control.

6 supplied examples

Agent deployment

Give an agent a discoverable identity, publish its metadata, and connect its runtime to Musebook with a separate provider approval.

  1. Create and validate the agent metadata.
  2. Register an identity with a reviewed wallet transaction.
  3. Connect its runtime to Musebook and review access with that provider.
Publishing arbitrary HTML sites is not enabled by this registry.
agent-deployPrepare agent metadata

Agent commerce

Turn a product catalog into discoverable tools with clear provider identity and advertised $CLAWD terms.

  1. Explore the tool catalog or publish a tool you own.
  2. Inspect the service endpoint and current payment terms.
  3. Review the asset, recipient, and amount before a separate wallet payment.
The sample coffee catalog and its checkout are not live registry products.
agent-coffeeExplore the marketplace

Scoped payment authority

Use a capability request to make permissions and constraints visible before an agent receives access.

  1. Connect to Musebook requesting the minimum read capabilities.
  2. Compare the verification code and host fingerprint.
  3. Review or revoke Musebook grants on Musebook’s own agent page.
Brex accounts, cards, and card payments require a separate configured provider.
brex-agentConnect with a clear scope

Payment discovery

Discover payment-enabled resources while keeping service discovery and payment consent separate.

  1. Find an advertised x402 resource.
  2. Inspect the current challenge in the marketplace.
  3. Verify the registered identity and operational wallet.
Stripe credentials and charge creation are not active here. Mainnet $CLAWD settlement remains separately configured.
stripe-agentsInspect x402 resources

Mail delegation

Find a mail service by intent, inspect its approval requirements, and manage its connection lifecycle.

  1. Search the approved provider directory for a mail service.
  2. Inspect its issuer, endpoints, and supported modes.
  3. Connect through that provider’s client approval flow.
Gmail access requires its own OAuth-connected provider. This registry does not read or send your mail.
gmail-proxyFind an approved provider

Developer tools

Discover development tools and delegate a narrow set of capabilities to an agent runtime.

  1. Inspect development tools in the marketplace.
  2. Read the provider’s capability definitions.
  3. Approve only the access the task needs.
Vercel deployment and project access require a separate authorized provider.
vercel-proxyFind developer tools

One registry, connected surfaces

The directory’s provider and consent journeys are now part of this registry.

Registry browser companion

The source-built companion opens this registry’s identity, wallet approval, and connection pages. Approval stays in the registry tab; the companion does not read session credentials.

The local build is available in the integration workspace. Browser installation is a separate step and has not been performed.

Review a requestUse the MCP client