pinion-send

Construct unsigned ETH or USDC transfer transactions on Base for client-side signing.

95|6|Updated Feb 11, 2026

Search Tags:#blockchain #payments #base-network #unsigned-tx #eth-transfer #usdc-transfer

Ready to run

npx skills add https://github.com/chu2bard/pinion-os --skill pinion-send-chu2bard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pinion-send
Source: https://github.com/chu2bard/pinion-os/tree/main/skills/send
Command: npx skills add https://github.com/chu2bard/pinion-os --skill pinion-send-chu2bard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill constructs an unsigned ETH or USDC transfer transaction on Base and returns the raw transaction object for the client to sign and broadcast, enabling secure, payer-initiated payments without exposing private keys in the app.

Core Features & Use Cases

Construct unsigned ETH or USDC transfer transactions on Base for client-side signing.
Return the raw transaction object with fields needed to broadcast after signing (to, value, data, chainId).
Use case: fund sub-wallets, pay for services, or orchestrate multi-step payment flows where the client signs the transaction.

Quick Start

Provide the recipient address, amount, and token to generate an unsigned transfer transaction.

Frequently Asked Questions about pinion-send

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I construct an unsigned ETH or USDC transfer on Base?▼

To construct an unsigned ETH or USDC transfer on Base, provide the recipient address, amount, and token to generate the raw transaction object ready for client-side signing and broadcast.

Can I prepare unsigned Base transfers without exposing my private keys?▼

Yes, you can prepare unsigned Base transfers without exposing private keys by returning the raw transaction object for the client to sign, enabling secure payer-initiated payments within your application.

What fields are included in the raw transaction object for a Base transfer?▼

The raw transaction object for a Base transfer includes the required broadcast fields: destination address, value, data payload, and chainId, ensuring the transaction is ready for signing.

Does generating an unsigned transaction on Base work for sub-wallet funding?▼

Generating an unsigned transaction on Base works for sub-wallet funding, payment orchestration, and client-side signing workflows where the user or agent securely signs and broadcasts the transaction.

What is the cost to generate an unsigned ETH or USDC transfer transaction?▼

The cost to generate an unsigned ETH or USDC transfer transaction is priced at $0.01 USDC per call via the x402 payment protocol.

Why use an unsigned Base transfer instead of a signed transaction?▼

You use an unsigned Base transfer to separate transaction construction from signing, allowing secure payment orchestration and sub-wallet funding without exposing private keys in the application.