x402 Agentic Methods

Brickken MCP Server for x402 Agentic Methods

Connect MCP-compatible AI agents to Brickken ERC-8004 agent identity, reputation, and agent-owned token operations. Configure a private-key backed session with no API key to use the x402 payment flow when the backend requires it.

Official Brickken docs CLI on npm

Agentic ERC-8004 tool groups

These tools prepare blockchain transactions and auto-sign/send when the session has a private key.

Identity

Agent registration and metadata

agent_register
agent_set_uri
agent_set_metadata
agent_set_wallet
agent_transfer_ownership

Reputation

Feedback and responses

agent_give_feedback
agent_revoke_feedback
agent_append_feedback_response

Agent-owned tokens

Standalone ERC-20 operations

agent_create_token
agent_mint_token
agent_burn_token
agent_transfer_token
agent_transfer_from_token
agent_approve_token

1. Add the MCP server

Add Brickken as a remote MCP server in your client configuration.

{
  "mcpServers": {
    "brickken": {
      "url": "https://mcp.brickken.com/mcp"
    }
  }
}

2. Configure production

Call the configure tool with a private key, production environment, and an empty API key.

{
  "env": "production",
  "privateKey": "0xYOUR_PRIVATE_KEY",
  "apiKey": ""
}

Sandbox configuration

Use sandbox when testing agentic flows before switching the same MCP session pattern to production.

{
  "env": "sandbox",
  "privateKey": "0xYOUR_PRIVATE_KEY",
  "apiKey": ""
}

Use get_config to confirm the active session environment, base URL, and whether credentials are present. Secret values are not returned.