wayfinder-paths 0.1.7__tar.gz → 0.1.9__tar.gz

{wayfinder_paths-0.1.7 → wayfinder_paths-0.1.9}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: wayfinder-paths
-Version: 0.1.7
+Version: 0.1.9
 Summary: Wayfinder Path: strategies and adapters
 Author: Wayfinder
 Author-email: dev@wayfinder.ai
@@ -54,9 +54,6 @@ cp wayfinder_paths/config.example.json config.json
 # Run a strategy locally (one-shot status check)
 poetry run python wayfinder_paths/run_strategy.py stablecoin_yield_strategy --action status --config config.json
 
-export WAYFINDER_API_KEY="sk_live_abc123..."
-poetry run python wayfinder_paths/run_strategy.py stablecoin_yield_strategy --config config.json
-
 # Run continuously (production mode)
 poetry run python wayfinder_paths/run_strategy.py stablecoin_yield_strategy --config config.json
 ```
@@ -125,6 +122,7 @@ We welcome contributions! This is an open-source project where community members
 ### Contributor Guidelines
 
 #### For Adapters
+
 - **Start from the template**: Copy `wayfinder_paths/templates/adapter/` as a starting point
 - Extend `BaseAdapter` from `wayfinder_paths/core/adapters/BaseAdapter.py`
 - Create a `manifest.yaml` (template at `wayfinder_paths/templates/adapter/manifest.yaml`) with:
@@ -138,6 +136,7 @@ We welcome contributions! This is an open-source project where community members
 - Validate your manifest: `just validate-manifests`
 
 #### For Strategies
+
 - **Start from the template**: Use `just create-strategy "Strategy Name"` to create a new strategy with its own wallet, or copy `wayfinder_paths/templates/strategy/` manually
 - Extend `Strategy` from `wayfinder_paths/core/strategies/Strategy.py`
 - Create a `manifest.yaml` (template at `wayfinder_paths/templates/strategy/manifest.yaml`) with:
@@ -151,6 +150,7 @@ We welcome contributions! This is an open-source project where community members
 - Validate your manifest: `just validate-manifests`
 
 #### General Guidelines
+
 - **Code Quality**: Follow existing patterns and use type hints
 - **Testing**: See [TESTING.md](TESTING.md) - minimum: smoke test for strategies, basic tests for adapters
 - **Documentation**: Update README files and add docstrings
@@ -205,11 +205,12 @@ poetry run python wayfinder_paths/run_strategy.py your_strategy --action status
 ## 🏗️ Architecture
 
 ### Client System
+
 The platform uses a unified client system for all API interactions. Clients are thin wrappers that handle low-level API calls, authentication, and network communication. **Strategies should not call clients directly** - use adapters instead for domain-specific operations.
 
 ### Clients vs Adapters
 
-- **Clients**: Low-level, reusable service wrappers that talk to networks and external APIs. They handle auth, headers, retries, and response parsing, and expose generic capabilities (e.g., token info, tx building). Examples: `TokenClient`, `TransactionClient`, `WalletClient`.
+- **Clients**: Low-level, reusable service wrappers that talk to networks and external APIs. They handle auth, headers, retries, and response parsing, and expose generic capabilities (e.g., token info, tx building). Examples: `TokenClient`, `WalletClient`.
 - **Adapters**: Strategy-facing integrations for a specific exchange/protocol. They compose one or more clients to implement a manifest of capabilities (e.g., `supply`, `borrow`, `place_order`). Adapters encapsulate protocol-specific semantics and raise `NotImplementedError` for unsupported ops.
 
 Recommended usage:
@@ -231,6 +232,7 @@ Adapter manifests declare the capabilities an adapter provides and the clients i
 **Template:** Copy `wayfinder_paths/templates/adapter/manifest.yaml` as a starting point.
 
 **Schema:**
+
 ```yaml
 schema_version: "0.1"
 entrypoint: "adapters.my_adapter.adapter.MyAdapter"
@@ -243,12 +245,14 @@ dependencies:
 ```
 
 **Fields:**
+
 - `schema_version`: Manifest schema version (currently `"0.1"`)
 - `entrypoint`: Full Python import path to the adapter class (required)
 - `capabilities`: List of abstract capabilities this adapter provides (required, non-empty)
 - `dependencies`: List of client class names from `core.clients` that this adapter requires (required, non-empty)
 
 **Example** (`wayfinder_paths/adapters/pool_adapter/manifest.yaml`):
+
 ```yaml
 schema_version: "0.1"
 entrypoint: "adapters.pool_adapter.adapter.PoolAdapter"
@@ -269,6 +273,7 @@ Strategy manifests declare permissions and required adapters with their capabili
 **Template:** Copy `wayfinder_paths/templates/strategy/manifest.yaml` as a starting point.
 
 **Schema:**
+
 ```yaml
 schema_version: "0.1"
 entrypoint: "strategies.my_strategy.strategy.MyStrategy"
@@ -282,6 +287,7 @@ adapters:
 ```
 
 **Fields:**
+
 - `schema_version`: Manifest schema version (currently `"0.1"`)
 - `entrypoint`: Full Python import path to the strategy class (required)
 - `name`: Strategy directory name (optional, used for wallet lookup - defaults to directory name)
@@ -291,6 +297,7 @@ adapters:
   - `capabilities`: List of capabilities required from this adapter
 
 **Example** (`wayfinder_paths/strategies/stablecoin_yield_strategy/manifest.yaml`):
+
 ```yaml
 schema_version: "0.1"
 entrypoint: "strategies.stablecoin_yield_strategy.strategy.StablecoinYieldStrategy"
@@ -308,12 +315,14 @@ adapters:
 #### Manifest Validation
 
 Manifests are automatically validated to ensure:
+
 - Schema compliance (all required fields present, correct types)
 - Entrypoint classes exist and are importable
 - Dependencies are valid client classes
 - Permissions policies are non-empty
 
 **Validate locally:**
+
 ```bash
 # Validate all manifests
 just validate-manifests
@@ -348,6 +357,7 @@ The `validate_manifests.py` script performs multi-stage validation:
    - Policy syntax is not parsed/validated (assumed to be valid at runtime)
 
 **Validation Flow:**
+
 ```
 For each manifest file:
   1. Load YAML → Parse with Pydantic (schema validation)
@@ -357,6 +367,7 @@ For each manifest file:
 ```
 
 The script automatically discovers all manifests by scanning:
+
 - `wayfinder_paths/adapters/*/manifest.yaml` for adapter manifests
 - `wayfinder_paths/strategies/*/manifest.yaml` for strategy manifests
 
@@ -367,12 +378,15 @@ All errors are collected and reported at the end, with the script exiting with c
 Capabilities are abstract operation identifiers (e.g., `"pool.read"`, `"swap.execute"`) declared in manifests. They represent what operations an adapter can perform, not specific method names. The manifest is the **single source of truth** for capabilities—they are not duplicated in code.
 
 When creating an adapter:
+
 1. Declare capabilities in your `manifest.yaml`
 2. Implement methods that fulfill those capabilities
 3. Capabilities are validated at manifest validation time (entrypoint must be importable)
 
 ### Configuration
+
 Configuration is split between:
+
 - **User Config**: Your credentials and preferences
 - **System Config**: Platform settings
 - **Strategy Config**: Strategy-specific parameters
@@ -384,9 +398,11 @@ See [CONFIG_GUIDE.md](wayfinder_paths/CONFIG_GUIDE.md) for details.
 Wayfinder Paths supports two authentication methods:
 
 #### 1. Service Account Authentication (API Key)
+
 For backend services and automated systems with higher rate limits:
 
 **Option A: Pass to Strategy Constructor**
+
 ```python
 from wayfinder_paths.strategies.stablecoin_yield_strategy.strategy import StablecoinYieldStrategy
 
@@ -396,29 +412,25 @@ strategy = StablecoinYieldStrategy(
 )
 ```
 
-**Option B: Set Environment Variable**
-```bash
-export WAYFINDER_API_KEY="sk_live_abc123..."
-# All clients will automatically discover and use this
-```
+**Option B: Add to config.json**
 
-**Option C: Add to config.json**
 ```json
 {
   "user": {
     "api_key": "sk_live_abc123..."
   },
   "system": {
-    "api_key": "sk_live_abc123..."  // Alternative: system-level API key
+    "api_key": "sk_live_abc123..." // Alternative: system-level API key
   }
 }
 ```
 
-**Priority Order:** Constructor parameter > `config.json` (user.api_key or system.api_key) > `WAYFINDER_API_KEY` environment variable
+**Priority Order:** Constructor parameter > `config.json` (user.api_key or system.api_key)
 
 **Note:** API keys in `config.json` are loaded directly by `WayfinderClient` via `_load_config_credentials()`, not through the `UserConfig` or `SystemConfig` dataclasses. This allows flexible credential loading.
 
 #### 2. Personal Access Authentication (OAuth)
+
 For standalone SDK users with username/password:
 
 ```json
@@ -426,12 +438,13 @@ For standalone SDK users with username/password:
   "user": {
     "username": "your_username",
     "password": "your_password",
-    "refresh_token": null  // Optional: use refresh token instead
+    "refresh_token": null // Optional: use refresh token instead
   }
 }
 ```
 
 **How It Works:**
+
 - API keys are automatically discovered by all clients (no need to pass explicitly)
 - When an API key is available, it's used for all API requests (including public endpoints) for rate limiting
 - If no API key is found, the system falls back to OAuth authentication
@@ -493,7 +506,7 @@ class MyStrategy(Strategy):
         super().__init__(api_key=api_key)  # Pass to base class for auto-discovery
         self.config = config or {}
         web3_service = DefaultWeb3Service(self.config)
-        # Adapters automatically discover API key from env var (set by Strategy.__init__)
+        # Adapters automatically discover API key from constructor or config.json
         balance_adapter = BalanceAdapter(self.config, web3_service=web3_service)
         self.register_adapters([balance_adapter])
         self.balance_adapter = balance_adapter
@@ -614,6 +627,7 @@ just create-wallets
 ```
 
 This creates:
+
 - `main` wallet - your main wallet for testing (labeled "main" in wallets.json)
 - `wallets.json` - wallet addresses and private keys for local testing
 
@@ -689,12 +703,14 @@ This package follows [Semantic Versioning](https://semver.org/) (SemVer) and is
 3. **Dependent changes**: Only after publishing can dependent changes be merged in other applications
 
 **Why this order matters:**
+
 - Other applications depend on this package from PyPI
 - They cannot merge changes that depend on new versions until those versions are available on PyPI
 - Publishing from `main` ensures the published version matches what's in the repository
 - This prevents dependency resolution failures in downstream applications
 
 **Example workflow:**
+
 ```bash
 # 1. Make changes in a feature branch
 git checkout -b feature/new-adapter
@@ -727,6 +743,7 @@ just publish
 ```
 
 **Important:**
+
 - ⚠️ **Publishing is only allowed from the `main` branch** - the publish command will fail if run from any other branch
 - ⚠️ **Versions must be unique** - ensure the version in `pyproject.toml` has been bumped and is unique
 - ⚠️ **Follow the order of operations** - see [Versioning](#-versioning) section above for the required workflow
@@ -749,6 +766,7 @@ pip install git+https://github.com/wayfinder-ai/wayfinder-paths.git
 ### Managing Package Access
 
 To add collaborators who can publish updates:
+
 1. Go to https://pypi.org/project/wayfinder-paths/
 2. Click "Manage" → "Collaborators"
 3. Add users as "Maintainers" (can publish) or "Owners" (full control)

{wayfinder_paths-0.1.7 → wayfinder_paths-0.1.9}/README.md

@@ -31,9 +31,6 @@ cp wayfinder_paths/config.example.json config.json
 # Run a strategy locally (one-shot status check)
 poetry run python wayfinder_paths/run_strategy.py stablecoin_yield_strategy --action status --config config.json
 
-export WAYFINDER_API_KEY="sk_live_abc123..."
-poetry run python wayfinder_paths/run_strategy.py stablecoin_yield_strategy --config config.json
-
 # Run continuously (production mode)
 poetry run python wayfinder_paths/run_strategy.py stablecoin_yield_strategy --config config.json
 ```
@@ -102,6 +99,7 @@ We welcome contributions! This is an open-source project where community members
 ### Contributor Guidelines
 
 #### For Adapters
+
 - **Start from the template**: Copy `wayfinder_paths/templates/adapter/` as a starting point
 - Extend `BaseAdapter` from `wayfinder_paths/core/adapters/BaseAdapter.py`
 - Create a `manifest.yaml` (template at `wayfinder_paths/templates/adapter/manifest.yaml`) with:
@@ -115,6 +113,7 @@ We welcome contributions! This is an open-source project where community members
 - Validate your manifest: `just validate-manifests`
 
 #### For Strategies
+
 - **Start from the template**: Use `just create-strategy "Strategy Name"` to create a new strategy with its own wallet, or copy `wayfinder_paths/templates/strategy/` manually
 - Extend `Strategy` from `wayfinder_paths/core/strategies/Strategy.py`
 - Create a `manifest.yaml` (template at `wayfinder_paths/templates/strategy/manifest.yaml`) with:
@@ -128,6 +127,7 @@ We welcome contributions! This is an open-source project where community members
 - Validate your manifest: `just validate-manifests`
 
 #### General Guidelines
+
 - **Code Quality**: Follow existing patterns and use type hints
 - **Testing**: See [TESTING.md](TESTING.md) - minimum: smoke test for strategies, basic tests for adapters
 - **Documentation**: Update README files and add docstrings
@@ -182,11 +182,12 @@ poetry run python wayfinder_paths/run_strategy.py your_strategy --action status
 ## 🏗️ Architecture
 
 ### Client System
+
 The platform uses a unified client system for all API interactions. Clients are thin wrappers that handle low-level API calls, authentication, and network communication. **Strategies should not call clients directly** - use adapters instead for domain-specific operations.
 
 ### Clients vs Adapters
 
-- **Clients**: Low-level, reusable service wrappers that talk to networks and external APIs. They handle auth, headers, retries, and response parsing, and expose generic capabilities (e.g., token info, tx building). Examples: `TokenClient`, `TransactionClient`, `WalletClient`.
+- **Clients**: Low-level, reusable service wrappers that talk to networks and external APIs. They handle auth, headers, retries, and response parsing, and expose generic capabilities (e.g., token info, tx building). Examples: `TokenClient`, `WalletClient`.
 - **Adapters**: Strategy-facing integrations for a specific exchange/protocol. They compose one or more clients to implement a manifest of capabilities (e.g., `supply`, `borrow`, `place_order`). Adapters encapsulate protocol-specific semantics and raise `NotImplementedError` for unsupported ops.
 
 Recommended usage:
@@ -208,6 +209,7 @@ Adapter manifests declare the capabilities an adapter provides and the clients i
 **Template:** Copy `wayfinder_paths/templates/adapter/manifest.yaml` as a starting point.
 
 **Schema:**
+
 ```yaml
 schema_version: "0.1"
 entrypoint: "adapters.my_adapter.adapter.MyAdapter"
@@ -220,12 +222,14 @@ dependencies:
 ```
 
 **Fields:**
+
 - `schema_version`: Manifest schema version (currently `"0.1"`)
 - `entrypoint`: Full Python import path to the adapter class (required)
 - `capabilities`: List of abstract capabilities this adapter provides (required, non-empty)
 - `dependencies`: List of client class names from `core.clients` that this adapter requires (required, non-empty)
 
 **Example** (`wayfinder_paths/adapters/pool_adapter/manifest.yaml`):
+
 ```yaml
 schema_version: "0.1"
 entrypoint: "adapters.pool_adapter.adapter.PoolAdapter"
@@ -246,6 +250,7 @@ Strategy manifests declare permissions and required adapters with their capabili
 **Template:** Copy `wayfinder_paths/templates/strategy/manifest.yaml` as a starting point.
 
 **Schema:**
+
 ```yaml
 schema_version: "0.1"
 entrypoint: "strategies.my_strategy.strategy.MyStrategy"
@@ -259,6 +264,7 @@ adapters:
 ```
 
 **Fields:**
+
 - `schema_version`: Manifest schema version (currently `"0.1"`)
 - `entrypoint`: Full Python import path to the strategy class (required)
 - `name`: Strategy directory name (optional, used for wallet lookup - defaults to directory name)
@@ -268,6 +274,7 @@ adapters:
   - `capabilities`: List of capabilities required from this adapter
 
 **Example** (`wayfinder_paths/strategies/stablecoin_yield_strategy/manifest.yaml`):
+
 ```yaml
 schema_version: "0.1"
 entrypoint: "strategies.stablecoin_yield_strategy.strategy.StablecoinYieldStrategy"
@@ -285,12 +292,14 @@ adapters:
 #### Manifest Validation
 
 Manifests are automatically validated to ensure:
+
 - Schema compliance (all required fields present, correct types)
 - Entrypoint classes exist and are importable
 - Dependencies are valid client classes
 - Permissions policies are non-empty
 
 **Validate locally:**
+
 ```bash
 # Validate all manifests
 just validate-manifests
@@ -325,6 +334,7 @@ The `validate_manifests.py` script performs multi-stage validation:
    - Policy syntax is not parsed/validated (assumed to be valid at runtime)
 
 **Validation Flow:**
+
 ```
 For each manifest file:
   1. Load YAML → Parse with Pydantic (schema validation)
@@ -334,6 +344,7 @@ For each manifest file:
 ```
 
 The script automatically discovers all manifests by scanning:
+
 - `wayfinder_paths/adapters/*/manifest.yaml` for adapter manifests
 - `wayfinder_paths/strategies/*/manifest.yaml` for strategy manifests
 
@@ -344,12 +355,15 @@ All errors are collected and reported at the end, with the script exiting with c
 Capabilities are abstract operation identifiers (e.g., `"pool.read"`, `"swap.execute"`) declared in manifests. They represent what operations an adapter can perform, not specific method names. The manifest is the **single source of truth** for capabilities—they are not duplicated in code.
 
 When creating an adapter:
+
 1. Declare capabilities in your `manifest.yaml`
 2. Implement methods that fulfill those capabilities
 3. Capabilities are validated at manifest validation time (entrypoint must be importable)
 
 ### Configuration
+
 Configuration is split between:
+
 - **User Config**: Your credentials and preferences
 - **System Config**: Platform settings
 - **Strategy Config**: Strategy-specific parameters
@@ -361,9 +375,11 @@ See [CONFIG_GUIDE.md](wayfinder_paths/CONFIG_GUIDE.md) for details.
 Wayfinder Paths supports two authentication methods:
 
 #### 1. Service Account Authentication (API Key)
+
 For backend services and automated systems with higher rate limits:
 
 **Option A: Pass to Strategy Constructor**
+
 ```python
 from wayfinder_paths.strategies.stablecoin_yield_strategy.strategy import StablecoinYieldStrategy
 
@@ -373,29 +389,25 @@ strategy = StablecoinYieldStrategy(
 )
 ```
 
-**Option B: Set Environment Variable**
-```bash
-export WAYFINDER_API_KEY="sk_live_abc123..."
-# All clients will automatically discover and use this
-```
+**Option B: Add to config.json**
 
-**Option C: Add to config.json**
 ```json
 {
   "user": {
     "api_key": "sk_live_abc123..."
   },
   "system": {
-    "api_key": "sk_live_abc123..."  // Alternative: system-level API key
+    "api_key": "sk_live_abc123..." // Alternative: system-level API key
   }
 }
 ```
 
-**Priority Order:** Constructor parameter > `config.json` (user.api_key or system.api_key) > `WAYFINDER_API_KEY` environment variable
+**Priority Order:** Constructor parameter > `config.json` (user.api_key or system.api_key)
 
 **Note:** API keys in `config.json` are loaded directly by `WayfinderClient` via `_load_config_credentials()`, not through the `UserConfig` or `SystemConfig` dataclasses. This allows flexible credential loading.
 
 #### 2. Personal Access Authentication (OAuth)
+
 For standalone SDK users with username/password:
 
 ```json
@@ -403,12 +415,13 @@ For standalone SDK users with username/password:
   "user": {
     "username": "your_username",
     "password": "your_password",
-    "refresh_token": null  // Optional: use refresh token instead
+    "refresh_token": null // Optional: use refresh token instead
   }
 }
 ```
 
 **How It Works:**
+
 - API keys are automatically discovered by all clients (no need to pass explicitly)
 - When an API key is available, it's used for all API requests (including public endpoints) for rate limiting
 - If no API key is found, the system falls back to OAuth authentication
@@ -470,7 +483,7 @@ class MyStrategy(Strategy):
         super().__init__(api_key=api_key)  # Pass to base class for auto-discovery
         self.config = config or {}
         web3_service = DefaultWeb3Service(self.config)
-        # Adapters automatically discover API key from env var (set by Strategy.__init__)
+        # Adapters automatically discover API key from constructor or config.json
         balance_adapter = BalanceAdapter(self.config, web3_service=web3_service)
         self.register_adapters([balance_adapter])
         self.balance_adapter = balance_adapter
@@ -591,6 +604,7 @@ just create-wallets
 ```
 
 This creates:
+
 - `main` wallet - your main wallet for testing (labeled "main" in wallets.json)
 - `wallets.json` - wallet addresses and private keys for local testing
 
@@ -666,12 +680,14 @@ This package follows [Semantic Versioning](https://semver.org/) (SemVer) and is
 3. **Dependent changes**: Only after publishing can dependent changes be merged in other applications
 
 **Why this order matters:**
+
 - Other applications depend on this package from PyPI
 - They cannot merge changes that depend on new versions until those versions are available on PyPI
 - Publishing from `main` ensures the published version matches what's in the repository
 - This prevents dependency resolution failures in downstream applications
 
 **Example workflow:**
+
 ```bash
 # 1. Make changes in a feature branch
 git checkout -b feature/new-adapter
@@ -704,6 +720,7 @@ just publish
 ```
 
 **Important:**
+
 - ⚠️ **Publishing is only allowed from the `main` branch** - the publish command will fail if run from any other branch
 - ⚠️ **Versions must be unique** - ensure the version in `pyproject.toml` has been bumped and is unique
 - ⚠️ **Follow the order of operations** - see [Versioning](#-versioning) section above for the required workflow
@@ -726,6 +743,7 @@ pip install git+https://github.com/wayfinder-ai/wayfinder-paths.git
 ### Managing Package Access
 
 To add collaborators who can publish updates:
+
 1. Go to https://pypi.org/project/wayfinder-paths/
 2. Click "Manage" → "Collaborators"
 3. Add users as "Maintainers" (can publish) or "Owners" (full control)

{wayfinder_paths-0.1.7 → wayfinder_paths-0.1.9}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "wayfinder-paths"
-version = "0.1.7"
+version = "0.1.9"
 description = "Wayfinder Path: strategies and adapters"
 readme = "README.md"
 authors = ["Wayfinder <dev@wayfinder.ai>"]

{wayfinder_paths-0.1.7 → wayfinder_paths-0.1.9}/wayfinder_paths/CONFIG_GUIDE.md

@@ -52,7 +52,6 @@ cp wayfinder_paths/config.example.json config.json
 **Option 1: Service Account (API Key) - Recommended for Production**
 - `user.api_key` - Your Wayfinder API key for service account authentication (loaded directly by clients from config.json)
 - OR `system.api_key` - System-level API key (alternative location, loaded directly by clients)
-- OR set `WAYFINDER_API_KEY` environment variable
 - OR pass `api_key` parameter to strategy constructor
 
 **Note:** API keys in `config.json` are loaded directly by `WayfinderClient` via `_load_config_credentials()`, not through the `UserConfig` or `SystemConfig` dataclasses. This is intentional to allow flexible credential loading.
@@ -229,7 +228,6 @@ The strategy system supports multiple wallet types through a wallet abstraction
 
 By default, adapters use `LocalWalletProvider` which resolves private keys from:
 - `wallets.json` (matched by address)
-- Environment variables (`PRIVATE_KEY`, `PRIVATE_KEY_STRATEGY`)
 - Wallet config in `config.json`
 
 No code changes are required - existing strategies continue to work.
@@ -270,7 +268,7 @@ Wayfinder Paths supports **dual authentication** for different use cases:
 
 **Best for:** Backend services, automated systems, and production deployments with higher rate limits.
 
-API keys provide service account authentication and are automatically discovered by all clients. You can provide an API key in three ways:
+API keys provide service account authentication and are automatically discovered by all clients. You can provide an API key in two ways:
 
 #### Option A: Strategy Constructor (Programmatic)
 ```python
@@ -278,16 +276,11 @@ from wayfinder_paths.strategies.stablecoin_yield_strategy.strategy import Stable
 
 strategy = StablecoinYieldStrategy(
     config={...},
-    api_key="sk_live_abc123..."  # Sets WAYFINDER_API_KEY env var automatically
+    api_key="sk_live_abc123..."  # API key is auto-discovered by all clients
 )
 ```
 
-#### Option B: Environment Variable
-```bash
-export WAYFINDER_API_KEY="sk_live_abc123..."
-```
-
-#### Option C: config.json
+#### Option B: config.json
 ```json
 {
   "user": {
@@ -299,14 +292,12 @@ export WAYFINDER_API_KEY="sk_live_abc123..."
 }
 ```
 
-**Priority Order:** Constructor parameter > `config.json` (user.api_key or system.api_key) > `WAYFINDER_API_KEY` environment variable
+**Priority Order:** Constructor parameter > `config.json` (user.api_key or system.api_key)
 
 **How It Works:**
-- When a strategy receives an `api_key`, it sets `os.environ["WAYFINDER_API_KEY"]`
 - All clients created by adapters automatically discover the API key from:
   - Constructor parameter (if passed)
   - `config.json` (via `WayfinderClient._load_config_credentials()` which reads `user.api_key` or `system.api_key`)
-  - `WAYFINDER_API_KEY` environment variable
 - API keys are included in **all** API requests (including public endpoints) for rate limiting
 - No need to pass API keys explicitly to adapters or clients—they auto-discover it
 - **Note:** API keys in `config.json` are loaded directly by clients, not stored in the `UserConfig` or `SystemConfig` dataclasses
@@ -379,7 +370,7 @@ To use custom RPC endpoints, update the `strategy.rpc_urls` section in `config.j
 **Issue:** "Authentication failed"
 - **If using API key:**
   - Verify API key is correct and not expired
-  - Check that API key is set in one of: constructor parameter, `config.json` (user.api_key or system.api_key), or `WAYFINDER_API_KEY` env var
+  - Check that API key is set in one of: constructor parameter or `config.json` (user.api_key or system.api_key)
   - Ensure API key has proper permissions for the operations you're performing
 - **If using OAuth:**
   - Check that `username` and `password` are correct in `config.json`

{wayfinder_paths-0.1.7 → wayfinder_paths-0.1.9}/wayfinder_paths/adapters/brap_adapter/README.md

@@ -17,7 +17,7 @@ The adapter uses the BRAPClient which automatically handles authentication and A
 
 The BRAPClient will automatically:
 - Use the WAYFINDER_API_URL from settings
-- Handle authentication via environment variables or config.json
+- Handle authentication via config.json
 - Manage token refresh and retry logic
 
 ## Usage

{wayfinder_paths-0.1.7 → wayfinder_paths-0.1.9}/wayfinder_paths/adapters/brap_adapter/adapter.py

@@ -10,10 +10,6 @@ from wayfinder_paths.core.adapters.BaseAdapter import BaseAdapter
 from wayfinder_paths.core.adapters.models import SWAP
 from wayfinder_paths.core.clients.BRAPClient import BRAPClient, BRAPQuote
 from wayfinder_paths.core.clients.LedgerClient import TransactionRecord
-from wayfinder_paths.core.clients.SimulationClient import (
-    SimulationClient,
-    SimulationResult,
-)
 from wayfinder_paths.core.clients.TokenClient import TokenClient
 from wayfinder_paths.core.constants import DEFAULT_SLIPPAGE
 from wayfinder_paths.core.constants.base import DEFAULT_TRANSACTION_TIMEOUT
@@ -45,7 +41,6 @@ class BRAPAdapter(BaseAdapter):
         config: dict[str, Any] | None = None,
         *,
         web3_service: Web3Service,
-        simulation: bool = False,
     ):
         super().__init__("brap_adapter", config)
         self.brap_client = BRAPClient()
@@ -55,8 +50,6 @@ class BRAPAdapter(BaseAdapter):
         self.web3_service = web3_service
         self.wallet_provider = web3_service.evm_transactions
         self.token_transactions = web3_service.token_transactions
-        self.simulation = simulation
-        self.simulation_client = SimulationClient() if simulation else None
 
     async def get_swap_quote(
         self,
@@ -147,8 +140,7 @@ class BRAPAdapter(BaseAdapter):
             )
 
             # Extract best quote from response
-            quotes = data.get("quotes", {})
-            best_quote = quotes.get("best_quote")
+            best_quote = data["best_route"]
 
             if not best_quote:
                 return (False, "No quotes available")
@@ -368,12 +360,6 @@ class BRAPAdapter(BaseAdapter):
             if not approve_success:
                 return (False, approve_response)
 
-        if self.simulation:
-            simulation = await self._simulate_swap(
-                from_token, to_token, from_address, chain_id, quote
-            )
-            return (True, {"quote": quote, "simulation": simulation})
-
         broadcast_success, broadcast_response = await self._broadcast_transaction(
             transaction
         )
@@ -678,44 +664,6 @@ class BRAPAdapter(BaseAdapter):
             / 10 ** int(decimals)
         )
 
-    async def _simulate_swap(
-        self,
-        from_token: dict[str, Any],
-        to_token: dict[str, Any],
-        from_address: str,
-        chain_id: int,
-        quote: dict[str, Any],
-    ) -> SimulationResult:
-        client = await self._get_simulation_client()
-        initial_balances = {"native": "5000000000000000000"}
-        if from_token.get("address"):
-            initial_balances[from_token.get("address")] = "1000000000000000000000000"
-
-        slippage = quote.get("slippage") or quote.get("slippage_percent")
-        if isinstance(slippage, str):
-            try:
-                slippage = float(slippage)
-            except ValueError:
-                slippage = DEFAULT_SLIPPAGE
-        slippage = slippage or DEFAULT_SLIPPAGE
-
-        amount = quote.get("input_amount") or quote.get("inputAmount") or "0"
-        return await client.simulate_swap(
-            from_token_address=from_token.get("address"),
-            to_token_address=to_token.get("address"),
-            from_chain_id=chain_id,
-            to_chain_id=chain_id,
-            amount=str(amount),
-            from_address=from_address,
-            slippage=float(slippage),
-            initial_balances=initial_balances,
-        )
-
-    async def _get_simulation_client(self) -> SimulationClient:
-        if not self.simulation_client:
-            self.simulation_client = SimulationClient()
-        return self.simulation_client
-
     def _chain_id(self, chain: Any) -> int:
         if isinstance(chain, dict):
             chain_id = chain.get("id") or chain.get("chain_id")