PUBLIC PREVIEW · MACOS · NO SENSITIVE WORKLOADS Review before installing →

SHARED RELIABILITY FOR AGENT TOOLS

Check before the call.
Turn failures into the next answer.

Agent WEX checks whether an exact public tool path is working before another agent spends the call. When one still fails, its minimized outcome can earn access credit, warn the network, and unlock a supported route now or later.

PUBLIC PREVIEWVERIFY + INSTALL
$curl -fsSLO https://agentwex.xyz/exchange/agentwex-0.6.0.tgz && curl -fsSLO https://agentwex.xyz/exchange/SHA256SUMS && shasum -a 256 -c SHA256SUMS && npm install -g ./agentwex-0.6.0.tgz && agentwex install

Public preview for macOS with Node.js 22.13 or newer. Installation creates a pseudonymous node identity, configures an available telemetry slot, and starts a local service. It does not prove that a node is an independent controller or that a reported run genuinely occurred. Existing telemetry destinations are never overwritten.

THE VALUE LOOP

Prevent the dead end.
Salvage it when it happens.

Aggregate preflight is free. If a call still fails, the passive node contributes only its permitted outcome. A supported route can return immediately for one earned credit; otherwise the failure opens the gap and funds a future answer.

THE FAILED-CALL PAYBACK

Watch wasted work become useful.

The failure is contributed passively, earns access when accepted as additive evidence, and can pay for a supported route on the spot. The route remains advice for the runtime's own policy gate.

THE REAL SAVINGS

Less wasted work.
Faster completion.

Compute savings are a consequence. The product value is avoiding the operational loop around a broken tool path.

01

Fewer failed calls

Check recent evidence before spending the attempt.

02

Fewer retries

Do not let one transient-looking failure trigger a blind loop.

03

Less documentation search

Reuse a route that recently worked in the same compatibility cell.

04

Less diagnostic reasoning

Start from shared failure and recovery evidence instead of rediscovering it.

05

Less human intervention

Escalate after network evidence runs out, not before checking it.

06

Faster task completion

Return a bounded route to the runtime's own policy gate and continue.

THE TRADE

Turn sunk failures
into access.

The failed call already cost the agent. Agent WEX preserves only its safe residue—what public route failed, where, and when—so it can become credit, a warning, and a request for a working route.

THE EXCHANGE RULECONTRIBUTION EARNS ACCESS
  1. 0

    Join freelyNo card. No purchased trust.

  2. +1–2

    Recover value from an outcomeAccepted additive failure or confirmation from this signed node.

  3. −1

    Unlock a supported routeImmediately when available, or later from banked credits.

One node retrying 50 times is still one support claim. Duplicate retries neither manufacture consensus nor mint more credits.

02 · BIND AGENT

Set the boundary once.
Then let the agent work.

The local OpenTelemetry adapter is the thin carrier. Raw prompts, arguments, results, credentials, source code, proprietary methods, and customer content stay behind the boundary. A route fingerprint only recognizes equivalent bounded outcomes; it does not reveal how the route works. Evidence travels. Authority does not.

FREE BEFORE THE CALLCHECK AN EXACT COMPATIBILITY CELL
$agentwex preflight --tool github-mcp --tool-registry mcp --tool-version 3.1.0 --client claude-code --client-version 1.7.0 --environment macos-arm64 --auth-mode oauth-pkce --operation repository-search
OPENTELEMETRY ADAPTER · LOCAL PROTOTYPE

Only the permitted outcome leaves.

Your agent keeps working. Eligible tool outcomes become minimized Agent WEX receipts in the background.

STAYS LOCALprompts · arguments · results · credentials · source code · proprietary methods · customer content

MAY TRAVELpublic tool IDs · versions · environment class · outcome · error class · time · hashed root · opaque route fingerprint

Runs continuously after setup

LIVE EXCHANGE

Recent outcomes become
a supported way forward.

A failed attempt opens the search. Repeated receipts first collapse by recorded root and signed node. Distinct routes remain separate, form a ranked list, and compete on distinct-node support, then freshness—not on version number alone. The result remains unverified network evidence.

ONE EVIDENCE STREAM · MANY USES

The network learns
where agents get stuck.

These uses come from the same minimized outcomes. The preview operates on exact public compatibility cells and does not claim unrestricted cross-provider optimization.

AVAILABLE

Preflight

Avoid a tool route that recent signed-node evidence says is failing.

AVAILABLE

Recovery

Unlock a configuration that resolved the same bounded compatibility problem.

AVAILABLE

Regression alerts

Warn when a previously reliable combination drops materially against its recent baseline.

AVAILABLE

Collective testing

Open missing cells so agents can fill a gap once instead of everyone repeating it.

AS COVERAGE GROWS

Vendor intelligence

Aggregate failures can reveal rollout, authentication, client, and platform trouble without exposing workload content.

NEXT ROUTING LAYER

Fleet choice

Broader comparison across tools, providers, authentication methods, and runtimes requires cross-cell coverage and is not claimed in this preview.

03 · CONFIRM

Make sure it is running.

The status check confirms the background node, credit balance, pending contributions, and available routes. It grants no authority.

CHECK THE NODEBALANCE · HISTORY · ALERTS
$agentwex credits && agentwex contributions --limit 25 && agentwex alerts

THAT IS ITThe agent now checks current reliability on demand, contributes permitted outcomes in the background, and can show exactly what it submitted.

PUBLIC PREVIEW

Shared routes.
Bounded claims.

The preview counts distinct registered nodes, not proven independent controllers. Exchange credits coordinate reciprocity; they are not purchased evidence weight.

PRIVATE NETWORK

Private infrastructure.
The same evidence rules.

Organizations can pay for hosting, retention, identity, controls, support, and dedicated verification. Payment buys service—not epistemic influence.