Sign & Submit API

Synchronous endpoints for signing messages and submitting transactions directly — no polling required.

Overview

Unlike /agent/prompt (async with job polling), these endpoints return immediately.

POST /agent/sign

Sign data without broadcasting to the network.

Signature Types

Prompt Examples

Sign a message:

• "Sign this message: Hello World"
• "Sign in to MyApp with nonce abc123"

Sign typed data (EIP-712 permit):

• "Sign this EIP-712 permit for USDC approval"

Sign a transaction without broadcasting:

• "Sign this transaction but don't send it"

Success Response

{
  "success": true,
  "signature": "0x...",
  "signer": "0xYourWalletAddress",
  "signatureType": "personal_sign"
}

Common Errors

POST /agent/submit

Submit raw transactions directly to the blockchain.

Transaction Fields

Prompt Examples

Submit a raw transaction:

• "Submit this transaction on Base: {to: 0x..., data: 0x..., value: 0}"

Simple ETH transfer:

• "Submit a transfer of 1 ETH to 0x..."

Success Response

With confirmation:

{
  "success": true,
  "transactionHash": "0x...",
  "status": "success",
  "blockNumber": "12345678",
  "gasUsed": "21000",
  "signer": "0xYourWalletAddress",
  "chainId": 8453
}

Transaction Status Values

Use Cases

• Authentication: Sign messages to verify wallet ownership
• Gasless approvals: Sign EIP-2612 permits without gas
• Pre-built transactions: Submit calldata from external tools
• Multi-step workflows: Execute approve + swap in sequence

Comparison with /agent/prompt

Security Notes

• /agent/submit executes immediately with no confirmation prompt
• Validate all transaction parameters before submission
• Use waitForConfirmation: true for important transactions
• Read-only API keys cannot use these endpoints (403)