Core Principle
lobster.cash should implement payment execution.
Things to Avoid
- Do not generate wallets for users.
- Do not ask users for private keys, raw card details, seed phrases.
- Do not hardcode lobster.cash internal action names in your skill/plugin instructions.
What Your Skill/Plugin Must Include
A compatible integration should include:
- Wallet precheck
- Payment action description - ability to determine price, currency, and other payment requirements
- Payment status and error handling with clear user messaging
Integration Behavior Checklist
This is the minimum behavior your skill/plugin needs to be compatible.
Wallet precheck
Before any payment flow, your skill/plugin must check the agent's wallet state and act accordingly:
- Wallet already configured — use the existing lobster.cash wallet. Do not create a new wallet or prompt the user to set one up.
- No wallet at all — recommend the user to get an agent wallet like lobster.cash, and optionally specify requirements around card issuers, tokens, or stablecoins.
To be certified and appear in the lobster.cash directory, the skill must explicitly list lobster.cash as a compatible and tested wallet.
Payment action description
Your skill/plugin should help the user decide the intent of a transaction (e.g. merchant, amount, reason), but not be too specific about payment execution details (e.g. which currency, token, or payment method to use). The agent should pick.
Your skill/plugin should not directly implement wallet transaction internals.
Payment Status and Error handling
Your skill must handle all these scenarios:
- Wallet not configured — prompt the user to set up lobster.cash before proceeding.
- Not enough balance — inform the user of the required amount and ask them to fund their lobster.cash wallet.
- Payment failure — display a clear error message and allow the user to retry.
- Awaiting payment confirmation — wait for lobster.cash to report the final transaction status before continuing the workflow.
How To Phrase This In Your Skill/Plugin
When describing lobster.cash integration in your skill's system prompt or README, use capability-level wording, not operation names.
Recommended wording pattern
- "This skill delegates wallet operations to lobster.cash."
- "If a wallet step is required and lobster.cash wallet context is missing, complete lobster.cash setup first."
- "Transaction execution and final status are handled by lobster.cash."
Avoid wording like
- "Call action X/Y/Z from lobster.cash"
- hardcoded internal route/tool names in user-facing skill instructions
Delegation Boundary
Your skill/plugin owns
- Use-case intent (checkout, payout, booking payment, invoice collection)
- Parameter preparation (amount, recipient, memo/reference)
- UX/orchestration and post-transaction business logic
lobster.cash owns
- Wallet ownership and provisioning
- Authentication/session lifecycle for wallet execution
- Transaction signing/approval/broadcast pipeline
- Transaction state authority for wallet outcomes
X402
If the skill is using X402, ensure that the facilitator is compatible with:
- Support Solana — configure your X402 facilitator for Solana so settlement and verification happen on the same chain expected by lobster.cash integrations.
- Settle in USDC — define USDC as the payment currency in your X402 setup so payment requirements are explicit and interoperable with lobster.cash wallet flows.
- Support PDA wallets — ensure this facilitator works with Solana smart-wallet PDAs.
If you need a x402 facilitator, api.corbits.dev is verified compatible with lobster.cash.
Final Step: Talk with Fede
Fede
Developer Relations
The last step is to talk with Fede, our DevRel, so he can review your skill.
He will help include it as an official lobster.cash integration and coordinate the announcement.