Metaplex DAS Now Indexes On-Chain AI Agents Across All Major Solana RPC Providers

The Metaplex N/A$0.018-2.6% Digital Asset Standard API can now identify, trace, and reverse-lookup registered AI agents on Solana, with support live across Triton One, Helius N/A$77.16-2.4%, QuickNode, and Alchemy.

Metaplex announced the update on June 25, adding three new indexed fields to the DAS API methods getAsset and searchAssets. Together they answer three questions any developer might want to ask about an on-chain agent: is this asset a registered agent, what token does it use, and what agent controls this signer address.

What DAS Now Returns for Registered Agents

The DAS API has long served as Solana's unified read layer for digital assets, a single interface that handles MPL Core assets, compressed NFTs, Token Metadata assets, and fungible tokens without requiring developers to parse separate account structures or chain separate RPC calls. From today, that interface extends to AI agent identity data.

Three new fields appear on indexed agents:

• is_agent: a boolean on getAsset responses indicating whether the underlying MPL Core asset has a registered AgentIdentity plugin attached. The searchAssets method gains a corresponding isAgent: true filter, making it possible to retrieve all registered agents in a single query.

• agent_token: DAS surfaces the primary token associated with a registered agent directly on getAsset. The reverse direction works too: pass an agentToken filter into searchAssets to find the agent that corresponds to a given token mint. Agents can launch their own tokens for capital and governance; this field makes the token-to-agent relationship queryable without any off-chain mapping.

• asset_signer: the asset signer PDA is the agent's on-chain wallet, the address through which it signs transactions and receives payments via the MPL Core execute instruction. DAS now indexes it, and searchAssets supports an assetSigner filter to reverse-lookup which agent owns a given signer PDA. Any transaction signed by an agent's PDA can now be attributed back to a specific registered identity.

The Registry That DAS Is Now Indexing

The MPL Agent Registry launched in early June 2026, built on two Solana programs. The Agent Identity program (1DREGFgysWYxLnRnKQnwrxnJQeSMk2HmGaC6whw2B2p) handles registration and attaches the AgentIdentity plugin to an existing MPL Core asset. The plugin embeds lifecycle hooks for Transfer, Update, and Execute operations, giving the registry visibility into what happens to the asset after registration. A second program, Agent Tools (TLREGni9ZEyGC3vnPZtqUh95xQ8oPqJSvNjvB7FGK8S), manages execution delegation: the mechanism by which asset owners grant operational authority over the agent's signer PDA to named executives, and revoke it.

Each agent's registration points to a JSON document stored on permanent storage describing the agent's identity, services, and endpoints. The format follows ERC-8004 and includes service endpoint types for web, A2A, and MCP protocols.

x402 Payments Without Private Key Exposure

The payment angle matters for how agents actually operate. Agents registered through the MPL Agent Registry hold no private key directly. Their spending authority flows through the asset signer PDA, which execution delegates control under the permissions granted by the asset owner. This private key-free wallet structure is what makes x402 integration workable in practice.

x402 added support for MPL Core agents in May, bringing payment rails that let agents transact without exposing private keys. An agent can now pay for API calls, services, or on-chain operations while remaining under the custody and revocation authority of its owner, with every payment traceable back through the signer PDA.

Why All Four RPC Providers Ship on the Same Day

The DAS specification is an open standard that RPC providers implement independently. Having Triton One, Helius, QuickNode, and Alchemy all ship agent field support on the same day means developers can write agent queries against whatever endpoint they already use, with no migration and no new provider relationship required.

The DAS layer has always been the practical bridge between what Metaplex indexes and what developers can actually query at scale. Without it, confirming whether an asset is a registered agent would require fetching the raw account data, deserializing the plugin list, and checking for the AgentIdentity plugin manually. That process does not compose well across large asset sets. The indexed isAgent filter makes it a single API parameter.

Developer Toolkit

The JavaScript/TypeScript SDK for the registry, @metaplex-foundation/mpl-agent-registry, provides instruction builders for RegisterIdentityV1, RegisterExecutiveV1, DelegateExecutionV1, and RevokeExecutionV1. The Metaplex Agent Kit includes prebuilt templates and tools for balances, transfers, swaps, token launches, and treasury actions, allowing developers to spin up a registered, capitalized agent without writing the full infrastructure from scratch.

The agent marketplace at metaplex.com/agents lets users browse registered agents filtered by whether they are tradeable, have listed services, or were created by the viewer's own wallet, with filtering backed by the same DAS fields now live in RPC endpoints.