Spectre + Stellar agent cookbook

[truthixify]

Labels: Stellar Wave, stellar, docs, drips, help-wanted
Tier: M (2–4 days)
Type: writing

Context

The Spectre docs talk about agents abstractly. There's no recipe-style guide for "spin up a Stellar-only Wraith agent and use it for X." This is exactly what a developer building an integration needs.

Scope

Write docs/guides/spectre-stellar-cookbook.mdx with three recipes:

Recipe 1: A Stellar-only inbound payments agent

For a SaaS that wants to accept Stellar payments privately:

1. Create an agent (wraith.createAgent({ chain: Chain.Stellar, ... }))
2. Fund the agent's wallet (friendbot for testnet; CSV for mainnet)
3. Register a .wraith name (e.g., mybusiness.wraith)
4. Listen for incoming payments via the Spectre webhook system
5. Auto-withdraw to a treasury cold-storage address weekly via scheduled payment
6. Privacy auto-pilot enabled

Recipe 2: A scheduled payroll agent

For a DAO paying contributors weekly in USDC on Stellar:

1. Create an agent
2. Fund with sufficient USDC + XLM
3. Configure scheduled payments to N .wraith recipients
4. Monitor failures via webhook → Slack alert
5. Rotate destination meta-addresses monthly

Recipe 3: A Stellar privacy-check agent

For a user who wants ongoing analysis of their stealth payment patterns:

1. Create an agent linked to their meta-address
2. Configure privacy-check tool to run weekly
3. Receive Slack/email reports
4. Acceptance window for "auto-rotate" recommendations

Style

• Each recipe is a complete curl and SDK example.
• Include the actual Spectre HTTP endpoints used.
• Include sample webhook payloads.
• Include cost estimates (fees, friendbot, etc.).

Acceptance criteria

• Three recipes written.
• Each one is testable — a reader can copy-paste and reach the same state.
• Added to docs.json under Guides.
• Spectre repo follow-up issue filed if any recipe requires features that don't exist yet.

Why this matters

This is what converts "Wraith is interesting" into "Wraith does the thing I need." Concrete recipes are higher-leverage than abstract reference.

Files

• New: docs/guides/spectre-stellar-cookbook.mdx
• Reference: docs/guides/single-chain-agent.mdx (existing, generic)
• Source-of-truth for Spectre API: Spectre repo src/agent/agent.controller.ts

[Euvouserdoutor]

Hi! I can take this task quickly and deliver a focused PR. Before I start, can you confirm: (1) budget/reward, (2) expected timeline, and (3) payout method (PayPal preferred)? I can start right after your approval.

[Euvouserdoutor]

I can start this now and submit a focused PR for the cookbook today.

Planned delivery:

• add docs/guides/spectre-stellar-cookbook.mdx with the three requested recipes
• include copy-pasteable curl + SDK examples, sample webhook payloads, and Stellar fee/friendbot notes
• wire it into docs.json under Guides
• flag any missing Spectre API gaps as follow-up issues instead of inventing behavior

Before I open the PR, please confirm the Drips reward/payout route for this issue and whether you prefer a docs-first PR with explicit TODO callouts for unavailable endpoints, or only examples backed by existing code paths.