Results for “on-chain”

Add plugin tools, connect MCP servers, or chain existing tools in one script within the LaRuche agent environment.

Buy and sell NFTs on OpenSea's Seaport marketplace. Fulfill listings, accept offers, create new orders, cross-chain purchases, and sweep multiple listings.

Execute NFT trades on OpenSea's Seaport marketplace: fulfill listings, accept offers, create orders, and sweep multiple listings with cross-chain support.

Executes on-chain token trades and queries data on Solana, Ethereum, BSC, and Base via the XXYY Open API.

Post, claim, and settle agent tasks on the AZZLE protocol (Base mainnet, USDC escrow). Requires Bankr for swaps, approvals, and on-chain execution.

Enables AI agents to pay humans with USDC via molty.cash, supporting tips, hiring for tasks, and creating gigs with on-chain settlement on Base.

Access Messari's full API via x402 pay-per-request — no API key needed. Asset data, market metrics, signals, news, fundraising, token unlocks, on-chain networks, and AI chat, all paid with USDC on Base.

Build onchain applications with React components and TypeScript utilities from Coinbase's OnchainKit, supporting wallet connection, token swaps, NFT minting, and payment processing.

Analyzes token implementations and integrations for ERC20/ERC721 conformity, weird token patterns, contract composition, owner privileges, and on-chain scarcity.

Provides a CLI for an onchain agent messaging layer on the Base blockchain, enabling agents to post to feeds, send direct messages, and store information permanently onchain.

Build, register, and gate AI-callable tool endpoints using the OpenSea Tool Registry (ERC-8257) on Base, with NFT ownership, subscription, trait, or pay-per-call access control.

Layer alternative channels / scrapers / data sources with explicit fall-through, where each rung covers a different failure mode. Use when interacting with the world (sending a notification, fetching from a third party, detecting a state change, authenticating) and the single canonical path could fail in known ways. Distinct from retrying — retries handle transient failures; fallback chains handle modal ones (channel down, API gone, cookie expired). Three layers tops; the terminal rung is loud.

Drive new-customer setup checklist — welcome email, kickoff scheduling, shared Notion workspace, Slack notification, milestone tracking. Event-triggered on Stripe checkout success or CRM Stage="Closed Won".

Battle-hardened NFT developer specializing in ERC-721/1155 implementations, gas-optimized minting, reveal mechanics, and marketplace integration. Has launched 50+ collections from stealth 1/1s to 10k PFP drops.Use when "build nft contract, mint function, erc721 implementation, erc1155 implementation, nft reveal, allowlist mint, dutch auction, lazy mint, on-chain metadata, royalty enforcement, operator filter, batch mint gas, token uri, soulbound token, nft, erc721, erc1155, erc721a, solidity, smart-contracts, opensea, blur, metadata, ipfs, arweave, royalties, minting, reveal, allowlist" mentioned.

Integrates ERC-4337 smart wallets with Base, enabling one-tap USDC payments, gas sponsorship, sub accounts, and spend permissions across 9 chains.

Use for writing, configuring, integrating, reviewing, debugging, or testing Python structured logging with structlog. Trigger for bound loggers, event dictionaries, processor chains, JSON or console rendering, standard-library logging integration, contextvars, request correlation, exception rendering, and structlog test capture. Do not use for stdlib-logging-only, Loguru-only, metrics-only, tracing-only, or collector configuration tasks that do not use structlog.

Connects AI coding agents to the IOTA blockchain with tools for wallet management, Move smart contract development, and on-chain data queries via JSON-RPC and GraphQL.

PDN DC voltage/current analysis, IR drop, design rule checking, and multi-net batch analysis on imported PCB layouts. TRIGGER: user asks about power integrity, PDN analysis, IR drop, voltage distribution, current density, power nets, or design rule checking on a PCB. Invoke BEFORE writing code — the PDN API chain is specialized and non-obvious. SKIP: importing a PCB file (use matlab-read-pcb-layout), EM field/S-parameter extraction (use matlab-analyze-em), material/stackup setup only (use matlab-manage-pcb-material), transmission line design (use matlab-design-pcb-transmission-line).

Hyperliquid L1 reference for Dwellir endpoints: HyperEVM JSON-RPC, Info API proxy, gRPC L1 streaming, order book WebSocket, dedicated nodes, and trading patterns. Covers HyperCore trading layer, HyperEVM smart contracts (chain ID 999), market data queries, perpetuals metadata, spot markets, and best practices. Use when working with Hyperliquid, HYPE, HyperEVM, HyperCore, perpetual futures, order books, funding rates, or Hyperliquid trading through Dwellir. Triggers on mentions of hyperliquid, HYPE, HyperEVM, HyperCore, order book, perpetuals, funding rate, l2Book, l4Book, gRPC streaming, nanoreth, or hyperliquid trading.

Use this skill for any request involving cryptocurrency market data, coin prices, trading volume, market cap, OHLC charts, historical data, exchanges, derivatives, NFTs, DeFi, on-chain token data, liquidity pools, DEX data, or anything powered by CoinGecko or GeckoTerminal APIs. Trigger this skill whenever the user asks about crypto prices, token data, market trends, or wants to call any CoinGecko or GeckoTerminal endpoint — even if they don't explicitly say "CoinGecko". Also trigger when the user asks about API keys, rate limits, or authentication for these APIs.

Build, modify, and ship Grafana dashboards as JSON via the HTTP API — panel types (timeseries / stat / gauge / table / heatmap / logs / traces / node-graph), `gridPos` 24-column layout, units, thresholds, template + datasource + chained variables, transformations (`organize` / `calculateField` / `filterByValue`), panel + dashboard links with `${__field.labels.x}` / `${__from}`, and Loki/Prometheus annotations. Use when scripting dashboard creation, writing the dashboard JSON for a new service, adding a `$job` dropdown variable, computing an "Error %" column with a transformation, overlaying deploys as annotations, or pushing a dashboard via `POST /api/dashboards/db` — even when the user says "create a dashboard for this metric", "add a service dropdown", "show errors as percentage", "overlay our deploys", or "export the dashboard JSON" without naming the API or schema. After every API push, verify with the returned `version` plus a GET on the dashboard UID.