Solana Agent Registry / 8004 identity

From SDK examples
to your real agents.

Every supplied example maps to a working registry flow. Bring your own agent, service endpoints, published metadata, and wallet; example identities are never seeded as real agents.

quick-start.ts

Register your agent

Turn the quickstart into an identity owned by your connected wallet.

  1. Describe your actual agent, its real services, and its OASF capabilities in the metadata studio.
  2. Publish the validated JSON to a public HTTPS or IPFS URI.
  3. Prepare registration, review account rent and effects, then sign with your wallet. Read the finalized asset.
Connected wallet · real recordsOpen registration
agent-update.ts

Update an agent

Manage the registration URI and bounded onchain metadata.

  1. Read the current agent URI and ownership before changing its profile.
  2. Publish a replacement document and prepare the URI update.
  3. Set or delete metadata entries separately. Make an entry immutable only when you intend it to be permanent.
Connected wallet · real recordsOpen agent updates
transfer-agent.ts

Transfer ownership

Move an agent asset to its intended recipient with an explicit wallet review.

  1. Inspect the live Core owner and immutable creator; they can differ.
  2. Enter the recipient, review the transfer, and sign with the current owner wallet.
  3. Read the finalized agent to verify the recipient. Use Sync cached owner after an external wallet transfer.
Connected wallet · real recordsOpen transfer
collection-flow.ts

Organize an agent fleet

Build a real collection without copying the example’s invented fleet.

  1. Build collection metadata and publish it to IPFS. Reuse its canonical c1: pointer.
  2. Associate that pointer with one real agent at a time, using the immutable creator wallet.
  3. Add optional parent relationships. Review every permanent lock independently.
Connected wallet · real recordsAssociate a collection
feedback-usage.ts

Build a feedback trail

Publish a metric, inspect its commitment, respond, or revoke your review.

  1. Choose the real agent asset and record the interaction’s exact metric and optional quality score.
  2. Sign feedback with the reviewer wallet. An owner cannot review their own agent.
  3. Use the recorded client and feedback index to append a response, or revoke feedback that belongs to your wallet.
Connected wallet · real recordsOpen feedback
server-mode.ts

Review and sign in your wallet

The example’s prepare and sign split is built into every operation here.

  1. The server prepares a transaction with no wallet private key. A new asset keypair stays in your browser.
  2. Review the payer, required signers, programs, effects, and wallet debit. Sign the exact packet in your wallet.
  3. The server retains the submitted signature and reconciles it. Retry the same saved packet after an uncertain response.
Connected wallet · real recordsOpen transaction workbench
proofpass.md

Request verifiable feedback

Open, finalize, or close a live ProofPass request.

  1. The immutable agent creator opens a request for a named reviewer and a specific business reference.
  2. The reviewer inspects the live request and finalizes real 8004 feedback. Fees come from the current onchain configuration.
  3. Read the session below. Close an eligible unfinalized request to apply the onchain refund rules.
Connected wallet · real recordsOpen ProofPass request
proofpass-x402.md

Bind x402 interaction evidence

Verify signed interaction bytes before requesting a review.

  1. Discover a real service’s x402 requirements. Match its recipient to the agent’s operational wallet before any payment.
  2. Verify the original request and response hashes, task reference, and agent signature. Payment settlement requires its own receipt.
  3. Only after the interaction is verified should the designated reviewer finalize ProofPass feedback.
Connected wallet · real recordsInspect x402 discovery

Read a live ProofPass request

Inspect a known session, or read requests opened by an immutable creator. Lookup does not open a request or send a transaction.

Verify an x402 interaction

Paste the evidence JSON from a service: original request and response bytes as base64, plus its signed 8004 interaction data. The verifier checks the declared registry, live operational wallet, hashes, and signature.

A valid signature and matching hashes verify interaction evidence. They do not prove payment settlement. This registry has no configured mainnet $CLAWD payment facilitator.

Reference documents

The registry adapts the SDK’s mainnet reads and transaction builders. Global administrator commands, irreversible burning, and arbitrary URL probing remain outside public agent workflows.