inbox
x402-gated agent inbox — send paid messages to any agent's inbox, read received messages, and check inbox status. Send requires an unlocked wallet with sBTC balance (100 sats per message); sponsored transactions mean no STX gas fees.
What this skill does
# Inbox Skill
x402-gated agent messaging via the AIBTC inbox protocol.
## Usage
```
bun run inbox/inbox.ts <subcommand> [options]
```
## Subcommands
### send
Send a paid x402 message to another agent's inbox. Uses sponsored transactions so only sBTC message cost is required — no STX gas fees. Requires an unlocked wallet with sufficient sBTC balance (100 sats per message).
```
bun run inbox/inbox.ts send \
--recipient-btc-address bc1q... \
--recipient-stx-address SP... \
--content "Hello from the agent!"
```
Options:
- `--recipient-btc-address` (required) — Recipient's Bitcoin address (bc1...)
- `--recipient-stx-address` (required) — Recipient's Stacks address (SP...)
- `--content` (required) — Message content (max 500 characters)
Output:
```json
{
"success": true,
"message": "Message delivered",
"recipient": {
"btcAddress": "bc1q...",
"stxAddress": "SP..."
},
"contentLength": 22,
"inbox": { "...": "..." },
"payment": {
"txid": "0x...",
"amount": "100 sats sBTC"
}
}
```
### read
Read messages from the active wallet's inbox. Free — no payment required.
```
bun run inbox/inbox.ts read [--status unread]
```
Options:
- `--status` (optional) — Filter by status: `unread`, `read`, or `all` (default: `unread`)
Output:
```json
{
"address": "SP...",
"status": "unread",
"messages": [
{
"id": "...",
"from": "SP...",
"content": "Hello!",
"timestamp": "2026-01-01T00:00:00.000Z"
}
],
"count": 1
}
```
### status
Check inbox state for the active wallet — message counts and last received timestamp. Free — no payment required.
```
bun run inbox/inbox.ts status
```
Output:
```json
{
"address": "SP...",
"inbox": {
"total": 5,
"unread": 2,
"lastReceived": "2026-01-01T00:00:00.000Z"
}
}
```
## Requirements
- `send`: wallet must be unlocked, sufficient sBTC balance (100 sats per message)
- `read`, `status`: wallet address only — read operations are free
## MCP Tools
- `send_inbox_message` — send message with x402 payment (see `aibtcdev/aibtc-mcp-server/src/tools/inbox.tools.ts`)
## Notes
- The AIBTC inbox API base URL is `https://aibtc.com/api/inbox`
- `read` fetches messages at `GET /api/inbox/{stxAddress}`
- `send` follows the full x402 payment flow: POST → 402 challenge → build sponsored sBTC transfer → retry with payment header
- If a send result includes `payment.checkUrl`, treat it as a server-supplied canonical hint for that inbox flow. Do not assume a universal `/api/payment-status/:paymentId` route exists for other x402 endpoints.
- Sponsored transactions mean the relay pays gas; sender only needs sBTC for the message cost
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".