Get started

QuickNode for AI agents

QuickNode reads live blockchain data and manages RPC endpoints, security rules, and usage across supported chains. Web3 developers use it to run reliable blockchain infrastructure. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect QuickNodeSee the 22 actions ↓
Developer toolsOAuth 2.0 (MCP)MCP + RESTquicknode.com
AUDIT LOG · QUICKNODEPOLICY: acme-support
09:41:07 · claude · u_8f2read
quicknode.list_chains
List-chains✓ allowed · 212ms
09:41:08 · claude · u_8f2read
quicknode.get_billing
Get-billing✓ allowed · 164ms
09:41:09 · claude · u_8f2write
quicknode.create_endpoint
Create-endpoint✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
quicknode.delete_endpoint
Delete-endpoint✕ blocked · policy: deny
EVERY QUICKNODE CALL, ON THE RECORD
01 · USE CASES

What agents do in QuickNode.

01

Check endpoint metrics read-only

Pull an endpoint's request metrics to check for latency or error spikes.

02

Call a blockchain RPC method

Query live chain data, like a wallet balance, through a configured endpoint.

03

Delete an endpoint with approval

Remove an RPC endpoint only after confirming no application still depends on it.

02 · ACTIONS

22 QuickNode actions, graded by risk.

Every QuickNode action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

10

Look things up. Allowed by default.

  • quicknode.get_billing
    Get-billing
  • quicknode.list_chains
    List-chains
  • quicknode.get_endpoint
    Get-endpoint
  • quicknode.get_rpc_usage
    Get-rpc-usage
  • quicknode.list_endpoints
    List-endpoints
  • quicknode.list_endpoint_logs
    List-endpoint-logs
  • quicknode.get_endpoint_metrics
    Get-endpoint-metrics
  • quicknode.list_endpoint_security
    List-endpoint-security
  • quicknode.get_endpoint_log_details
    Get-endpoint-log-details
  • quicknode.list_endpoint_method_rate_limits
    List-endpoint-method-rate-limits

write

8

Create and change things. Allow, or ask the user first.

  • quicknode.create_endpoint
    Create-endpoint
  • quicknode.create_security_rule
    Create-security-rule
  • quicknode.update_endpoint_rate_limits
    Update-endpoint-rate-limits
  • quicknode.update_endpoint_security_options
    Update-endpoint-security-options
  • quicknode.create_endpoint_method_rate_limit
    Create-endpoint-method-rate-limit
  • quicknode.update_endpoint_method_rate_limit
    Update-endpoint-method-rate-limit
  • quicknode.call_rpc
    Call-rpc
  • quicknode.enable_tooling_access
    Enable-tooling-access

destructive

4

Delete, cancel or archive. Ask first, or deny outright.

  • quicknode.delete_endpoint
    Delete-endpoint
  • quicknode.delete_security_rule
    Delete-security-rule
  • quicknode.delete_endpoint_method_rate_limit
    Delete-endpoint-method-rate-limit
  • quicknode.disable_tooling_access
    Disable-tooling-access
03 · HOW IT WORKS

QuickNode in three steps.

  1. 01Your users connect QuickNodeThey sign in to QuickNode on Arc0 Connect, under your brand, and approve the access you ask for.
  2. 02You set the rulesReads run, writes like “create-endpoint” can wait for the user, and “delete-endpoint” can be denied outright.
  3. 03Any agent can actYour agent calls QuickNode through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('quicknode', {
  read: 'allow',
  write: 'ask',        // create_endpoint
  destructive: 'deny',  // delete_endpoint
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How QuickNode connects.

QuickNode runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches QuickNode through the same endpoint, policies and audit log as every other app.

The same QuickNode connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
OAuth 2.0 (MCP)
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use QuickNode from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More developer tools apps.

GitHub896 actionsSupabase129 actions0CodeKit8 actionsAbly25 actionsAbstract3 actionsAddressfinder17 actionsAddresszen2 actionsAlchemy36 actions
ALL DEVELOPER TOOLS APPS →
07 · FAQ

QuickNode and Arc0, answered.

Q01

Can I use QuickNode with Claude, ChatGPT or Cursor?

Yes. Connect QuickNode to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the QuickNode actions you allow.

Q02

How do users connect QuickNode?

QuickNode runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches QuickNode through the same endpoint, policies and audit log as every other app.

Q03

Which QuickNode actions can my agent take?

22 in total: 10 read, 8 write and 4 destructive, such as “create-endpoint”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in QuickNode?

Yes. Actions like “delete-endpoint” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call QuickNode too?

Yes. The same QuickNode connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug QuickNode into your agent.

Your users connect QuickNode once, under your brand. Your agent gets 22 actions behind your policies, with every call on the record.

Connect QuickNodeBrowse all apps →

Free to build · MCP + REST · Audit log on every plan