Transfer Agent Ownership
Prepare an ERC-8004 identity ownership transfer through x402.
safeTransferFrom that moves an ERC-8004 agent identity from Brickken custody to a wallet you control. This facade maps to agentTransferOwnership.
By default Brickken is the on-chain owner of the agent identity in brickken-relayed mode. Call this method only when you explicitly want to take custody of the identity NFT yourself.
Authentication
Preparing is free and needs no credential. The x402 USDC payment is charged onPOST /send-transactions, which answers 402 Payment Required with a PAYMENT-REQUIRED header describing the chain, asset, transfer method, amount, recipient, and timeout. Sign the payment locally and retry with X-PAYMENT.
In brickken-relayed mode Brickken’s relayer signs and broadcasts the operation — API keys are not accepted on a relayed send. In client-signed mode you sign the prepared transaction yourself first.
See Authentication for the full credential matrix.
Key Fields
Response
Returns a prepared unsigned transaction andtxId. Submit it to POST /send-transactions and complete the x402 payment.
brickken-relayed: send{ txId, transactions }; Brickken signs and broadcasts.client-signed: sign the transaction locally as the current owner, then send{ txId, signedTransactions }.
Next step
Preparing does not touch the chain. The response gives youtxId, the unsigned transactions, and an x402Requirements quote.
Choose who signs and who broadcasts
brickken-relayed — the relayer signs, broadcasts, and pays the native gas; you sign only the payment, and prepare is free. client-signed (the default) — you sign, Brickken broadcasts. client-broadcast — you sign and broadcast yourself, then confirm with txHash. Both client-controlled modes charge half the price at prepare and half at send.Relaying is available on the ERC-8004 and agent-token facades and on the four signed RAMS lifecycle calls. The other RAMS operations check msg.sender against an on-chain role, so they reject it.Submit it and settle the payment
POST to /send-transactions. The first attempt answers 402 Payment Required; read PAYMENT-REQUIRED, sign the payment locally, and retry with X-PAYMENT. An API key is accepted here only in client-signed mode.Poll until it confirms
GET /get-transaction-status with the txId. Relayed transactions need no credential to poll. Your payment settles only after the operation confirms, and is released if it reverts.Authorizations
Base64-encoded x402 payment payload. Supported for x402-eligible agentic methods on /x402/... facades, /prepare-transactions, and eligible /send-transactions retries.
Body
Target operation chain ID. Use 8453 on Base mainnet or 84532 on Base Sepolia.
"8453"
"84532"
Wallet that will receive the ERC-8004 identity NFT.
^0x[a-fA-F0-9]{40}$Execution mode. Use brickken-relayed to let Brickken's relayer sign, pay gas, and broadcast (omit signerAddress). Use client-signed to sign the prepared transaction yourself.
brickken-relayed, client-signed Wallet that signs the prepared blockchain transaction. Required only in client-signed mode; omit in brickken-relayed mode.
^0x[a-fA-F0-9]{40}$Optional explicit gas limit.
Optional explicit nonce when managing nonces manually.
Optional private RPC URL override.
Optional owner attribution email.
Alias for ownerEmail where supported.
Stored tokenized agent UUID returned by agentRegister.
On-chain ERC-8004 agent ID.