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.
Agentic ERC-8004 tool groups
Write tools prepare blockchain transactions and auto-sign/send when the session has a private key. Read tools use the API key when configured and otherwise fall back to x402.
Discovery, profiles, and transactions
get_agentsget_agent_infoget_agent_transactions
Agent registration and metadata
agent_registeragent_set_uriagent_set_metadataagent_set_walletagent_transfer_ownership
Feedback and responses
agent_give_feedbackagent_revoke_feedbackagent_append_feedback_response
Standalone ERC-20 operations
agent_create_tokenagent_mint_tokenagent_burn_tokenagent_transfer_tokenagent_transfer_from_tokenagent_approve_token
Delegated authority and compliance
rams_grant_mandaterams_revoke_mandaterams_extend_mandaterams_set_operatorrams_executerams_set_executor_actionrams_freeze_agentrams_unfreeze_agentrams_grant_principalrams_revoke_principalrams_get_mandaterams_can_executerams_get_statusrams_check_compliancerams_get_executor_actionrams_get_typed_data
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.