CODING ASSISTANT GUIDE

Integrate with Claude Code

Claude Code can help modify an Agent project. The deployed Agent Runtime still needs its own Spendkit OAuth/MCP client and a trusted local Payment Wallet sender.

Give the project a clear instruction

# CLAUDE.md
For AI Agent payments, first read:
https://spendkit-alpha.vercel.app/docs/runtime/
https://spendkit-alpha.vercel.app/docs/examples/
https://spendkit-alpha.vercel.app/docs/api-quickstart/
https://spendkit-alpha.vercel.app/docs/mcp-tools/
https://spendkit-alpha.vercel.app/docs/payment-flow/

Inspect the project's current MCP client and wallet transaction path before editing.
Use the Agent's bound Spendkit Policy; do not supply another Policy ID or wallet address.
Keep Client Secrets and Payment Wallet private keys in protected Runtime configuration.
Do not silently change Policy limits, recipients, or Router token allowance.
Start with a read-only connection and payment preview; report remaining owner actions.

What to review before enabling payment

OAuth token acquisition and refresh work with the Agent connection's scopes.
The bound Payment Wallet signs and submits the exact returned Router transaction; Spendkit Server does not submit it.
The Runtime distinguishes a denied preview, an authorization, an uncertain broadcast, and a confirmed receipt.
The wallet owner reviews the current dashboard's token-allowance request and signs it directly.

Use MCP tool reference for inputs and scopes. The presence of a remote MCP configuration alone does not prove payment Runtime support.