Boscopan

• What it is — AI-first crypto price alerts: natural-language create/list/cancel; server does x402, CRE, and RuleRegistry on Base Sepolia.
• How it works — User/agent talks to the server; create-alert is paid (x402); CRE writes to chain and cron/run-check evaluates rules and Chainlink prices and can send Pushover; optional scheduled LLM summary.
• What problem it solves — No RPC/ABI/wallet in the conversation; single agent API with intents and micropayments; automation keeps alerts and notifications aligned with on-chain state.

Express + OpenAI + x402 + in-memory store + price API on the server, CRE (HTTP + Cron + run-check) for on-chain writes and notifications, and RuleRegistry on Base Sepolia.

• Server (Node/Express): One app serves chat, agent API, alerts, and prices. It uses OpenAI (e.g. gpt-4o-mini) for natural language and tool calls, x402-express for $0.01 USDC create-alert, and in-memory alert store + a price service (e.g. CoinGecko, cached). A scheduled agent (optional) runs on a timer, loads alerts + prices, calls the LLM for a summary, and exposes it at GET /agent/summary. “Run alerts check now” is the same condition logic, and can optionally POST to a CRE run-check URL.
• Agent API: Single POST /agent/action with intent + params. The server does chain/CRE/x402; for paid intents it returns 402 and forwardTo, then the client pays and retries. Intents: create_alert, list_alerts, get_price, cancel_alert, run_alerts_check.
• CRE (Chainlink): One workflow with three triggers: HTTP (receives alert payload, writes to RuleRegistry on Base Sepolia), Cron (reads rules, gets Chainlink prices, checks conditions, sends Pushover), Run-check HTTP (same logic as cron, for on-demand runs). RuleRegistry is a Solidity contract that accepts CRE reports and stores rules.
• Contract: RuleRegistry.sol on Base Sepolia, deployed with Hardhat; holds alert rules and (optionally) receives x402 USDC.