The Web3 layer autonomous agents will transact on.

Agentic RPC is an intent-based blockchain endpoint built for autonomous agents. The endpoint accepts a single intent (swap, transfer, stake, vote), resolves pricing across venues, manages nonces and gas, signs the transaction under scoped authority, broadcasts it, and returns a signed receipt with the confirmed transaction hash. The whole flow completes in a single round trip rather than the nine or more sequential JSON-RPC calls a legacy stack requires.

Legacy JSON-RPC exposes low-level chain primitives (eth_gasPrice, eth_estimateGas, eth_getTransactionCount, eth_sendRawTransaction, repeated eth_getTransactionReceipt polls). The agent has to orchestrate the sequence, hold the signing key, manage nonces, and handle errors at every step. Intent-based RPC collapses that orchestration into one server-side call. The agent submits intent and receives a signed outcome.

No. Agents authenticate against the endpoint with scoped credentials, not private keys. Signing happens server-side inside hardware security modules, under per-action policies the developer configures in advance. Policies bound the maximum value per intent, the addresses an agent may transact with, the rate of transactions, and the protocols an agent may interact with.

Scoped signing authority means each agent receives a credential that can sign only a defined set of actions. For example: spend up to 100 USDC per day, only to Uniswap v3 contracts, only on Base mainnet, no governance votes. Out-of-scope intents are rejected at the endpoint before any chain action happens. Policy changes require a signed approval from the developer's master key.

Private beta access ships first for Ethereum mainnet, Base, Arbitrum, Optimism, and Solana. Additional networks roll out based on customer demand. The agentic endpoint reuses the same node fleet that powers our production RPC infrastructure, so any network in the RPC product catalog is a candidate for agentic support.

Each intent submitted to the agentic endpoint is metered and billed in stablecoin, typically USDC. Pricing covers the underlying RPC calls, the signing operation, and the gas reimbursement. Invoicing happens continuously rather than monthly, and the agent's deposit balance is enforced at the endpoint to prevent runaway spend.

Apply through the agentic infrastructure waitlist linked from this page. Beta access is limited and prioritized for teams shipping agents to production. A named engineer scopes the policy framework, signing limits, and supported intents during onboarding. Expect a one to two week evaluation window from initial contact to first signed transaction.