opencrowd 0.2.0 → 0.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -58,20 +58,19 @@ First launch is two steps — there is no wallet setup:
58
58
 
59
59
  ## Providers
60
60
 
61
- The default provider is the **x402 token proxy** (`x402ProxyUrl`, an
62
- OpenAI-compatible route metered with x402 micropayments): requests pass
63
- through unchallenged, and when the route demands payment (HTTP 402) the
64
- challenge is signed with the shared AgentCash wallet — upto-style, so the
65
- service settles actual usage against a quoted ceiling. No API keys, no
66
- prepaid balance, OpenRouter-grade serving latency.
61
+ The default provider is **BlockRun**, an OpenAI-compatible route paid per
62
+ request with x402 USDC from the shared AgentCash wallet. It needs no API key
63
+ or prepaid provider balance. If a BlockRun call fails transiently twice, the
64
+ current **x402 token proxy** handles one ledgered rescue call; after three
65
+ rescues the primary is parked for the rest of the process. In `ask` mode the
66
+ rescue requires confirmation, while `auto` mode proceeds within the session
67
+ budget automatically.
67
68
 
68
69
  **Venice** is the wallet-native backup (`opencrowd config set provider
69
70
  venice` or `/provider venice`): SIWX authentication, prepaid Venice credit
70
71
  topped up with USDC, at most one bounded automatic top-up per exhausted
71
72
  call. **OpenRouter** direct is also available with `OPENROUTER_API_KEY`.
72
- There is no automatic fallback between providers — switching is always an
73
- explicit choice, and a provider failure surfaces with a remediation
74
- message.
73
+ The x402 proxy, Venice, and direct OpenRouter remain explicitly selectable.
75
74
 
76
75
  Model preferences are per provider (`auto` resolves from the live catalog at
77
76
  session start; resolved IDs are recorded on the session so `run --session`