Skip to main content

​
What it does

The sign tool requests a cryptographic signature from your Base Account. Like all write tools, it requires your approval in Base Account. Two signature types are supported:

​
What you can ask

Signing is usually invoked by protocols or integrations, not directly prompted by users. Your assistant will handle the signing flow when a service requests it.

​
How it works

1

Your assistant calls sign()

Passes the message type and payload to Base MCP.
2

You receive an approval link

Open the approval link to review what you’re signing in Base Account — the message content is shown in full.
3

You approve

Confirm the signature in the approval UI.
4

Signature returned

Your assistant polls get_request_status to retrieve the completed signature, then passes it to the requesting service.

Execute contract calls

Batch multiple contract interactions into one approval.

Native plugins

Moonwell, Uniswap, Avantis, and other protocol plugins — approval and signing patterns in the skill repo.