@oracle-agent/oracle 0.28.27 → 0.28.29

package/README.md

@@ -13,7 +13,7 @@ oracle doctor                           # verify local posture
 
 `oracle setup model` offers Anthropic, OpenAI Codex, and Grok OAuth plus secure
 API-key setup for OpenRouter, OpenAI, Anthropic, xAI, DeepSeek, Gemini, Kimi,
-Mistral, Nous, and custom OpenAI-compatible providers. `oracle auth status` reports
+Mistral, Nous Portal, Qwen, GLM, and custom OpenAI-compatible providers. `oracle auth status` reports
 providers without printing credentials. Linux, Windows, and macOS apps are in beta.
 
 The CLI, source, and desktop beta are public to everyone. Locals Only holders
@@ -83,6 +83,13 @@ const prepared = await data.call("hl-perps", "prepareOrder", {
 // Oracle stops here. The user's wallet reviews, signs, and submits.
 ```
 
+Hosts that need a prepare-only task turn can import
+`createTaskAdapter` and its shared request/result types from
+`@oracle-agent/oracle/task`. The entrypoint advertises only `oracle_cli` and
+`trade_lifecycle`; the host injects both its model provider and read/prepare CLI
+runner. It does not install an HTTP route or UI. See
+[docs/task-adapter.md](docs/task-adapter.md).
+
 See [SETUP.md](SETUP.md) for clean installation and troubleshooting,
 [docs/locals-only-fee-waiver.md](docs/locals-only-fee-waiver.md) for the 0% holder fee, and
 [docs/buzz-integration.md](docs/buzz-integration.md) for the Buzz HTTP contract.
@@ -242,7 +249,7 @@ known answer. This matters: the canonical QuoterV2 address also has bytecode on
 Base, but does not price that chain's pairs. A codesize check would have
 allowlisted the wrong contract.
 
-**88 provider modules** in the read/quote catalog, covering **220 unique
+**93 provider modules** in the read/quote catalog, covering **220 unique
 protocols/venues** across EVM, Solana, and Bitcoin (115 EVM + cross-chain, 98
 Solana venues backed by 101 verified Jupiter program IDs, 6 Bitcoin surfaces).
 One module can cover many protocols: the Jupiter module alone routes 98 Solana
@@ -258,7 +265,7 @@ venues, so provider-module count and protocol count are different numbers.
 | Perps / lending / yield | GMX v2, Morpho, Pendle |
 | Bridges | Across, Hop, Relay |
 | Venues | Hyperliquid (core perps + HIP-3 builder dexs + HIP-4 outcomes), Polymarket (read + local CLOB prepare) |
-| NFT | OpenSea, Satflow, Magic Eden (Solana) |
+| NFT | OpenSea, Satflow, Magic Eden (Solana); additive owner-local P2 catalog |
 | Bitcoin | mempool/Esplora, Ordinals, Runes, UniSat, Best-in-Slot, Satflow |
 
 Every provider and every scanner capability declares an honest tier —

package/SETUP.md

@@ -114,6 +114,9 @@ model. Use `--no-browser` when the browser must be opened manually.
 
 ```bash
 oracle setup model openrouter
+oracle setup model qwen
+oracle setup model glm
+oracle setup model nous
 # also supported: openai, anthropic, xai, deepseek, gemini, kimi, mistral, nous, custom
 ```
 

package/dist/assets/skills/bankrbot/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: bankrbot
+description: Use Bankr wallet data and swap quotes through Oracle's read-only adapter without giving Bankr execution authority.
+---
+
+# BankrBot
+
+Oracle integrates Bankr as a bounded Wallet API data source, not as its model, wallet executor, or signing backend.
+
+Configure `BANKR_API_KEY` locally with a Bankr key restricted to read-only access and enable Wallet API access in Bankr. Never paste the key into chat. The endpoint is pinned to `https://api.bankr.bot`; a custom host does not receive the credential.
+
+Available Oracle calls:
+
+```text
+oracle_cli data call bankr wallet
+oracle_cli data call bankr portfolio
+oracle_cli data call bankr swapQuote fromChain=<chain> fromToken=<token> toChain=<chain> toToken=<token> amount=<decimal> slippageBps=<10-2000>
+```
+
+`swapQuote` is research data only. Compare it against Oracle's native best-execution routes, gas, fees, slippage, minimum received, and custody path before recommending it.
+
+Oracle deliberately excludes Bankr `/wallet/swap`, transfer, sign, submit, token-launch, automation, Agent API prompt, and LLM gateway surfaces. Do not use a Bankr response to bypass Oracle's prepare-only hosted plane or armed-local signer policy. A Bankr-managed wallet is vendor custody and must be labeled separately from Oracle's encrypted local vault and the user's connected wallet.
+
+Sources: https://docs.bankr.bot/wallet-api/overview/, https://docs.bankr.bot/wallet-api/swap/, https://docs.bankr.bot/cli/, and https://github.com/BankrBot/skills/tree/main/bankr

package/dist/assets/skills/oracle-agentic-crypto/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: oracle-agentic-crypto
+description: Choose current crypto-agent standards by leverage and custody risk instead of adopting every new primitive.
+---
+
+# Agentic crypto stack
+
+Use the narrowest surface that completes the task.
+
+## Available now
+
+- Uniswap v4: quote and inspect hook permissions/code/pool state; prepare guarded unsigned Universal Router calldata only for static-fee, zero-hook pools.
+- x402 v2: inspect `PAYMENT-REQUIRED` and prepare an exact-payment template under explicit network, asset, recipient, and atomic caps.
+- ERC-8004: inspect and prepare agent identity metadata without inventing registry deployments.
+- Permit2: surface the exact approval requirement for reviewed swap routes. Never infer unlimited approval.
+- Intents and aggregators: compare CoW, 1inch, 0x, ParaSwap, LI.FI, Across, Relay, and native pools net of gas, fees, timing, and signing semantics.
+- Simulation and receipts: simulate prepared EVM calls, bind guard data to calldata, then reconcile the real receipt after user-authorized execution.
+
+## Next, only behind wallet capability checks
+
+- EIP-5792 wallet call batches for wallet-mediated multi-call UX.
+- EIP-7702 delegated EOAs and ERC-4337 smart accounts for scoped account behavior.
+- ERC-7579 modules and ERC-7715 permissions for session-limited capabilities.
+- EIP-7739 defensive typed-data validation for smart-account signatures.
+- EIP-7710 delegation chains when x402 or wallet tooling can prove revocation, expiry, target, selector, token, and spend caps.
+
+These are not execution-ready merely because a wallet or SDK advertises them. Before arming any of them, require chain support, exact implementation/version, revocation path, expiry, selector and destination allowlists, token caps, simulation, and receipt reconciliation.
+
+## Decision rule
+
+1. Read-only discovery first.
+2. Prepare an unsigned or typed-data artifact with explicit bounds.
+3. Keep hosted Oracle keyless and prepare-only.
+4. Use armed-local signing only for a user-requested action through an already reviewed signer surface.
+5. Treat unattended scheduling, session keys, delegated accounts, and recurring x402 payments as a separate risk class.
+
+Avoid vendor AI gateways inside providers. Providers return deterministic external data or prepared artifacts; Prime/Oracle remains the reasoning harness.
+
+Canonical references: https://eips.ethereum.org/EIPS/eip-5792, https://eips.ethereum.org/EIPS/eip-7702, https://eips.ethereum.org/EIPS/eip-4337, https://eips.ethereum.org/EIPS/eip-7579, https://eips.ethereum.org/EIPS/eip-7715, https://eips.ethereum.org/EIPS/eip-7739, https://eips.ethereum.org/EIPS/eip-7710, https://www.erc8004.org/, and https://docs.uniswap.org/contracts/permit2/overview

package/dist/assets/skills/oracle-chain-graphs-telegram-cards/SKILL.md

@@ -46,6 +46,8 @@ cards.
 - `/approve` / `/deny` are owner-only fallbacks for WhatsApp, Discord, Signal,
   and any chat that cannot render inline buttons. Do not prefer them on Telegram
   when the card is available.
+- Allow / `/approve` must execute on the local signer (sign + broadcast). A
+  confirmation nonce with no fill is not an approval.
 
 ## Graph schema
 

package/dist/assets/skills/oracle-desk-product/SKILL.md

@@ -97,7 +97,7 @@ does not prove npm users receive it. A locally hosted model/data/policy loop doe
 a bundled signer. A merged feature is not public until the npm artifact containing it is
 published and inspected.
 
-**Candidate release in this source tree:** public package `@oracle-agent/oracle@0.28.27`
+**Candidate release in this source tree:** public package `@oracle-agent/oracle@0.28.29`
 ships the encrypted local vault + short-lived loopback signer. Hosted/keyless
 Oracle cannot hold keys or move funds. Self-host after `oracle sign init|import` is **auto-armed**
 for user-initiated actions. Public still charges the disclosed fee card; Administrator

package/dist/assets/skills/oracle-uniswap-v4-hooks/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: oracle-uniswap-v4-hooks
+description: Inspect and prepare Uniswap v4 hook pools without trusting arbitrary hook contracts.
+---
+
+# Uniswap v4 hooks
+
+Inspect a nonzero hook before quoting it as usable or preparing calldata:
+
+```text
+oracle_cli data call uniswap-v4 inspectHook chainId=8453 tokenIn=<address> tokenOut=<address> fee=<uint24> tickSpacing=<int24> hooks=<hook>
+```
+
+Read `hook.permissions.enabled`, `hook.codePresent`, `pool.initialized`, `pool.dynamicFee`, and `risk`. Permission bits come from the deployed hook address. They describe which callbacks can run, not whether the code is safe.
+
+Risk rules:
+
+- No code or uninitialized pool: refuse.
+- Any `ReturnsDelta` permission: high risk custom accounting.
+- Swap or donate callbacks and dynamic fees: medium risk until contract-specific review.
+- Every nonzero hook requires review. `risk.audited` is always false because bytecode presence and permission decoding are not an audit.
+
+Preparation is currently restricted to static-fee, zero-hook pools after a fresh quote:
+
+```text
+oracle_cli data call uniswap-v4 prepare chainId=<id> tokenIn=<erc20> tokenOut=<erc20> amountIn=<raw> fee=<static-fee> tickSpacing=<spacing> hooks=0x0000000000000000000000000000000000000000 recipient=<wallet> slippageBps=<0-100> deadlineSeconds=<30-600>
+```
+
+Dynamic-fee, nonzero-hook, opaque-hookData, custom-accounting, native, multihop, exact-output, and PositionManager operations stay inspect/quote-only until a code-hash-specific adapter exists. Oracle keeps `hookData=0x`, builds unsigned Universal Router calldata only for the bounded zero-hook path, and never signs or broadcasts.
+
+Sources: https://developers.uniswap.org/docs/protocols/v4/concepts/hooks and https://github.com/Uniswap/v4-core/blob/main/src/libraries/Hooks.sol

package/dist/assets/skills/oracle-x402/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: oracle-x402
+description: Inspect x402 payment requirements and prepare capped payment templates without signing or paying.
+---
+
+# x402
+
+Use x402 only as an explicit payment negotiation step. Oracle supports version 2 `PAYMENT-REQUIRED` payloads and the `exact` scheme.
+
+1. Decode and inspect the server's Base64 `PAYMENT-REQUIRED` header:
+
+```text
+oracle_cli data call x402 inspect paymentRequired=<base64-header>
+```
+
+2. Require the user to state all four controls: `network`, `asset`, `payTo`, and `maxAmount` in atomic units.
+
+3. Prepare the bounded template:
+
+```text
+oracle_cli data call x402 prepare paymentRequired=<base64-header> network=<caip-2> asset=<asset-id-or-address> payTo=<recipient> maxAmount=<atomic-cap>
+```
+
+The selected requirement must use `scheme=exact`, match every control, and fit under the cap. Re-inspect every new 402 response because requirements can change.
+
+Oracle does not create `PAYMENT-SIGNATURE`, sign EIP-3009 or Permit2 payloads, contact a facilitator, retry the paid HTTP request, or broadcast anything. The prepared artifact has `paymentReady=false`, `signingReady=false`, and `broadcastReady=false`. A user-controlled wallet integration must handle the scheme-specific authorization separately.
+
+Do not treat the public x402 facilitator as a production mainnet dependency. Verify the facilitator and scheme independently before any wallet integration.
+
+Sources: https://docs.x402.org/core-concepts/client-server, https://docs.x402.org/schemes/exact, and https://docs.x402.org/core-concepts/facilitator