Clean public core buyer package surface

Author: Abiorh001

.dockerignore

@@ -2,7 +2,7 @@
 .env
 .env.*
 !.env.example
-hosted.env
+*.env
 *.key
 *.pem
 *.p12
@@ -29,8 +29,3 @@ video/
 apps/ops-console/.next
 apps/ops-console/node_modules
 apps/ops-console/.npm-cache
-services/hosted-facilitator/.venv
-services/hosted-facilitator/hosted.env
-services/hosted-facilitator/apps/ops-console/.next
-services/hosted-facilitator/apps/ops-console/node_modules
-services/hosted-facilitator/apps/ops-console/test-results

.gitignore

@@ -5,6 +5,7 @@
 .env.*
 !.env.example
 .env.local
+*.env
 *.pem
 *.key
 secrets.json

CHANGELOG.md

@@ -6,19 +6,23 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 
 ## [Unreleased]
 
+### Changed
+- Removed the obsolete secondary console entrypoint and pointed both console scripts at the unified `omniclaw.cli` buyer/core CLI.
+- Updated public docs and release verification so removed setup/server/doctor commands are no longer advertised.
+
 ## [0.0.6] - 2026-04-14
 
 ### Added
-- Added the owner/operator `omniclaw facilitator exact` command for self-hosted x402 exact settlement.
-- Added public facilitator documentation covering Circle Gateway, external facilitators, and OmniClaw self-hosted exact settlement.
+- Added x402 exact-settlement buyer support.
+- Added public documentation for Circle Gateway and x402 exact payment flows.
 - Added Arc Testnet exact-settlement support documentation using CAIP-2 `eip155:5042002`.
-- Added B2B SDK examples for vendor APIs, machine-to-vendor payments, external exact facilitators, and self-hosted exact settlement.
-- Added a public `.env.example` with role-based configuration for agents, vendors, facilitators, Circle Gateway, Thirdweb, and production hardening.
+- Added B2B SDK examples for machine-to-machine payments.
+- Added a public `.env.example` with role-based configuration for agents, Circle Gateway, Thirdweb, and production hardening.
 
 ### Changed
-- Moved the owner/operator CLI entrypoint to `omniclaw.admin_cli:main` so it no longer conflicts with the `omniclaw.cli` agent CLI package.
-- Updated release artifact verification for the new admin CLI module and package layout.
-- Reworked public README and docs around agent buyer, SDK buyer, vendor SDK seller, Financial Policy Engine, and facilitator deployment paths.
+- Moved the owner/operator CLI entrypoint away from the `omniclaw.cli` agent CLI package.
+- Updated release artifact verification for the package layout.
+- Reworked public README and docs around agent buyer, SDK buyer, and Financial Policy Engine paths.
 - Updated the OmniClaw CLI skill to require idempotency keys for x402 URL payments.
 - Bumped runtime and shipped CLI skill metadata to `0.0.6`.
 
@@ -50,8 +54,8 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 ## [0.0.3] - 2026-03-25
 
 ### Added
-- Multi-facilitator support: Circle Gateway, Coinbase CDP, OrderN, RBX, Thirdweb
-- Seller SDK: Full seller-side SDK for accepting x402 payments
+- Payment rail support: Circle Gateway, Coinbase CDP, OrderN, RBX, Thirdweb
+- x402 buyer support for paid HTTP resources
 - Trust Gate: ERC-8004 based identity and reputation verification
 - Payment Intents: 2-phase commit with fund reservation
 - Enhanced buyer SDK with smart payment routing

README.md

@@ -2,62 +2,25 @@
 
 Policy-controlled payment infrastructure for agent buyers.
 
-OmniClaw core is now focused on one job: letting agents and applications pay through controlled, auditable rails without giving software unrestricted wallet authority.
-
-The hosted facilitator is a separate deployable product under [`services/hosted-facilitator`](services/hosted-facilitator). It owns seller project API keys, hosted x402 settlement, ops console, reconciliation, and OIDC/OpenFGA control-plane auth. Seller middleware remains in each seller's own app and points at the facilitator URL.
+OmniClaw core is focused on one job: letting agents and applications pay through controlled, auditable rails without giving software unrestricted wallet authority.
 
 ## Product Boundary
 
 | Product | Directory | Owns |
 | --- | --- | --- |
 | OmniClaw core | `src/omniclaw` | buyer SDK, policy engine, wallet/payment routing, x402 buyer execution, Gateway buyer readiness |
-| Hosted facilitator | `services/hosted-facilitator` | seller project API keys, x402 facilitator URLs, exact settlement, hosted control plane, reconciliation, ops console |
 
-Core should not import hosted facilitator modules. The hosted facilitator service should be deployable from its own directory without installing OmniClaw core.
+Core should not include recipient-side paid endpoint hosting or settlement service code.
 
 ## Core Capabilities
 
 - Financial Policy Engine for budgets, approvals, trust checks, and execution control
 - Python buyer SDK via `OmniClaw().pay(...)`
 - Agent buyer CLI via `omniclaw-cli pay`, `inspect-x402`, and `can-pay`
 - Circle Gateway buyer funding/readiness helpers
-- Standard x402 buyer flow for paying external seller endpoints
+- Standard x402 buyer flow for paying external paid endpoints
 - Ledger, idempotency, simulation, and payment-intent controls
 
-## Hosted Facilitator
-
-The facilitator service has its own package, frontend, Dockerfile, infra config, docs, and tests:
-
-```text
-services/hosted-facilitator/
-  apps/ops-console/
-  docs/
-  infra/
-  scripts/
-  src/hosted_facilitator/
-  tests/
-```
-
-Local hosted stack:
-
-```bash
-cp services/hosted-facilitator/hosted.env.example hosted.env
-# edit hosted.env with the hosted facilitator signer private key and provider config
-docker compose -f docker-compose.hosted.yml up --build
-```
-
-Control plane:
-
-```text
-http://127.0.0.1:3001
-```
-
-Facilitator API:
-
-```text
-http://127.0.0.1:4022
-```
-
 ## Core Quickstart
 
 Install:
@@ -75,7 +38,7 @@ export OMNICLAW_AGENT_POLICY_PATH="./policy.json"
 export OMNICLAW_NETWORK="BASE-SEPOLIA"
 export OMNICLAW_RPC_URL="https://sepolia.base.org"
 
-omniclaw server --port 8080
+docker compose up --build omniclaw-agent
 ```
 
 Configure the buyer CLI:
@@ -85,11 +48,11 @@ export OMNICLAW_SERVER_URL="http://localhost:8080"
 export OMNICLAW_TOKEN="agent-token"
 ```
 
-Inspect and pay an x402 seller endpoint:
+Inspect and pay an x402 endpoint:
 
 ```bash
-omniclaw-cli inspect-x402 --recipient https://seller.example.com/compute
-omniclaw-cli pay --recipient https://seller.example.com/compute --idempotency-key job-123
+omniclaw-cli inspect-x402 --recipient https://paid.example.com/compute
+omniclaw-cli pay --recipient https://paid.example.com/compute --idempotency-key job-123
 ```
 
 ## Development
@@ -99,17 +62,3 @@ Run core tests:
 ```bash
 uv run pytest
 ```
-
-Run hosted facilitator tests:
-
-```bash
-cd services/hosted-facilitator
-uv run pytest
-```
-
-Run ops console tests:
-
-```bash
-cd services/hosted-facilitator/apps/ops-console
-npm test
-```

docs/API_REFERENCE.md

@@ -15,13 +15,13 @@ client = OmniClaw()
 ```python
 await client.pay(
     wallet_id="wallet-id",
-    recipient="https://seller.example.com/compute",
+    recipient="https://paid.example.com/compute",
     amount=None,
     idempotency_key="job-123",
 )
 ```
 
-Use `amount=None` for x402 URLs where the seller publishes the amount in `PAYMENT-REQUIRED`.
+Use `amount=None` for x402 URLs where the endpoint publishes the amount in `PAYMENT-REQUIRED`.
 
 ### Gateway Buyer Helpers
 
@@ -43,13 +43,5 @@ The local policy engine exposes buyer payment, wallet, ledger, policy, and x402
 Start it with:
 
 ```bash
-omniclaw server --port 8080
-```
-
-## Hosted Facilitator APIs
-
-Seller project APIs, facilitator `/supported`, `/verify`, `/settle`, ops APIs, and seller dashboard APIs belong to the hosted facilitator service:
-
-```text
-services/hosted-facilitator/docs/
+docker compose up --build omniclaw-agent
 ```

docs/FEATURES.md

@@ -12,9 +12,9 @@ OmniClaw core is the buyer-side policy and payment-control layer.
 
 ## x402 Buyer Support
 
-- Inspect seller `PAYMENT-REQUIRED` responses
+- Inspect x402 `PAYMENT-REQUIRED` responses
 - Select supported x402 routes
-- Pay standard `exact` seller endpoints
+- Pay standard `exact` x402 endpoints
 - Use Circle Gateway `GatewayWalletBatched` when the buyer is funded and the route is advertised
 
 ## Circle Gateway Buyer Operations
@@ -23,11 +23,3 @@ OmniClaw core is the buyer-side policy and payment-control layer.
 - On-chain Gateway balance checks
 - Deposit and withdraw helpers
 - Buyer readiness for nanopayment routes
-
-## Standalone Hosted Facilitator
-
-Hosted settlement, seller onboarding, ops console, reconciliation, OIDC/OpenFGA auth, and provider adapters live outside core:
-
-```text
-services/hosted-facilitator/
-```

docs/OmniClaw_Whitepaper_v2.md

@@ -133,7 +133,7 @@ The ledger stores durable intent state and attempt state. It is the source of tr
 
 ### 5.6 Execution Service
 
-The execution service is the only component permitted to trigger settlement. It uses provider integrations, facilitators, or rail-specific adapters, but only for already-approved intents.
+The execution service is the only component permitted to trigger payment execution. It uses provider integrations or rail-specific adapters, but only for already-approved intents.
 
 ### 5.7 Audit Layer
 
@@ -234,8 +234,8 @@ Not all recipients create the same risk.
 
 The task-derived architecture, which is consistent with OmniClaw’s broader control model, makes this explicit:
 
-- Human-operated vendor
-  Standard vendor allowlist, ordinary approval thresholds, and contractual accountability.
+- Human-operated service
+  Standard recipient allowlist, ordinary approval thresholds, and contractual accountability.
 
 - Internal service
   Potentially looser thresholds, but only when workload identity, service registry entry, destination account, and transaction class match internal control records.
@@ -319,7 +319,7 @@ The credibility of OmniClaw as a research system comes from the fact that these
 - trust-layer types and verdicts in `src/omniclaw/identity/types.py`
 - guard, reservation, and fund-lock documentation in `docs/FEATURES.md`
 - compliance framing in `docs/compliance-architecture.md`
-- product surfaces across buyer, seller, facilitator, and CLI workflows
+- product surfaces across buyer SDK, policy engine, and CLI workflows
 
 There is also substantial test evidence:
 

docs/POLICY_REFERENCE.md

@@ -260,20 +260,20 @@ Agent can pay everyone EXCEPT these addresses/domains.
 }
 ```
 
-### Seller Agent (Receives Payments)
+### Receive-Only Agent
 ```json
 {
   "version": "2.0",
   "tokens": {
-    "seller-agent": {
+    "receive-only-agent": {
       "wallet_alias": "primary",
       "active": true,
-      "label": "Seller Agent"
+      "label": "Receive-Only Agent"
     }
   },
   "wallets": {
     "primary": {
-      "name": "Seller Wallet",
+      "name": "Receive-Only Wallet",
       "limits": {
         "daily_max": "0",
         "per_tx_max": "0"

docs/PRODUCTION_HARDENING.md

@@ -15,7 +15,7 @@ OMNICLAW_WEBHOOK_DEDUP_DB_PATH=/var/lib/omniclaw/webhook_dedup.sqlite3
 
 Startup fails fast if these are missing or if strict settlement is disabled.
 
-For non-production package usage, `OMNICLAW_STRICT_SETTLEMENT` defaults to `false` so compatible x402 resources can still unlock even when a seller omits or delays settlement response metadata. Production deployments must opt into strict settlement explicitly.
+For non-production package usage, `OMNICLAW_STRICT_SETTLEMENT` defaults to `false` so compatible x402 resources can still unlock even when an endpoint omits or delays settlement response metadata. Production deployments must opt into strict settlement explicitly.
 
 ## Webhook Security Model
 
@@ -35,38 +35,25 @@ OMNICLAW_WEBHOOK_MAX_FUTURE_SKEW_SECONDS=300
 OMNICLAW_WEBHOOK_DEDUP_ENABLED=true
 ```
 
-## Product Boundary
-
-This document covers OmniClaw core. Seller project APIs, facilitator settlement, nonce replay protection for seller middleware, control-plane auth, and reconciliation are part of the standalone hosted facilitator service:
-
-```bash
-services/hosted-facilitator/
-```
-
 ## Settlement Semantics
 
 - `OMNICLAW_STRICT_SETTLEMENT=true` ensures success reflects irreversible settlement states.
 - Do not disable strict settlement in production.
 
-## External Facilitator Strategy
+## x402 Buyer Strategy
 
-OmniClaw core is facilitator-aware as a buyer. Production buyer deployments should inspect what the seller advertises and route only through a buyer-supported payment method:
+OmniClaw core is buyer-side infrastructure. Production buyer deployments should inspect what the paid endpoint advertises and route only through a buyer-supported payment method:
 
 - Circle Gateway `GatewayWalletBatched` for gasless batched nanopayments
-- standard x402 `exact` where the seller and facilitator advertise compatible requirements
-- external facilitator URLs selected by the seller
-
-Operate OmniClaw-hosted settlement from `services/hosted-facilitator`, not from the core package.
+- standard x402 `exact` where the endpoint advertises compatible requirements
 
-Before production traffic, validate the exact seller path with:
+Before production traffic, validate the exact paid endpoint path with:
 
 ```bash
-omniclaw-cli inspect-x402 --recipient https://seller.example.com/compute
-omniclaw-cli pay --recipient https://seller.example.com/compute --idempotency-key production-canary-001
+omniclaw-cli inspect-x402 --recipient https://paid.example.com/compute
+omniclaw-cli pay --recipient https://paid.example.com/compute --idempotency-key production-canary-001
 ```
 
-For hosted facilitator validation, use `services/hosted-facilitator/docs/` plus the external seller and buyer examples under root `examples/hosted_facilitator_*`.
-
 ## Canary and SLA
 
 Use the canary script to validate end-to-end payment lifecycle before/after deploys:
@@ -88,10 +75,10 @@ Exit behavior:
 ## Rollout Checklist
 
 1. Apply required production env vars.
-2. Run `omniclaw doctor`.
+2. Confirm the policy engine health endpoint and CLI configuration.
 3. Run canary in target environment.
-4. Confirm `inspect-x402` selects the expected seller scheme and network.
-5. Confirm settlement appears in the selected facilitator dashboard or explorer.
+4. Confirm `inspect-x402` selects the expected payment scheme and network.
+5. Confirm settlement appears in the expected explorer or provider record.
 6. Deploy with staged traffic.
 7. Monitor:
    - settlement latency

docs/README.md

@@ -2,8 +2,6 @@
 
 This docs tree is for OmniClaw core: buyer-side agent payment infrastructure, policy controls, wallet routing, and x402 payment execution.
 
-Hosted facilitator documentation now lives in [`../services/hosted-facilitator/docs`](../services/hosted-facilitator/docs).
-
 ## Core Guides
 
 | Guide | Covers |
@@ -15,11 +13,3 @@ Hosted facilitator documentation now lives in [`../services/hosted-facilitator/d
 | [Policy Reference](POLICY_REFERENCE.md) | Wallets, budgets, confirmations, recipient rules |
 | [Production Readiness](production-readiness.md) | Buyer/payment release checklist |
 | [Production Hardening](PRODUCTION_HARDENING.md) | Core deployment controls |
-
-## Hosted Facilitator Guides
-
-Use the hosted facilitator docs for seller onboarding, facilitator URLs, project API keys, settlement/reconciliation, ops-console, and provider expansion:
-
-```text
-services/hosted-facilitator/docs/
-```