Skip to content

Add LocalAgentCore product wedge and x402-paid API publisher - #12

Closed
atimics wants to merge 1 commit into
AnOversizedMooseWithSocks:mainfrom
atimics:product-x402-wedge
Closed

Add LocalAgentCore product wedge and x402-paid API publisher#12
atimics wants to merge 1 commit into
AnOversizedMooseWithSocks:mainfrom
atimics:product-x402-wedge

Conversation

@atimics

@atimics atimics commented Jul 14, 2026

Copy link
Copy Markdown

What this is

A narrow, product-facing surface for leCore plus a way to sell it per-call:

  • holographic_product.pyLocalAgentCore: local agent memory (remember/recall), skill routing over the live capability catalog, JSON persistence, and a readiness dashboard. Exposed as lecore.product.LocalAgentCore and documented in PRODUCT.md.
  • holographic_x402_api.py: publishes that wedge as an x402-paid HTTP API (FastAPI). Paid routes: POST /v1/recall, POST /v1/route, GET /v1/dashboard. Free: /health, /pricing, and a landing page. Writes are admin-token-gated (paying does not buy write access to the shared store).
  • Deploy: Dockerfile.x402 + fly.x402.toml + FLY_X402_DEPLOY.md (Fly.io default, volume-backed state, testnet defaults, documented mainnet flip). AWS_X402_DEPLOY.md kept as the alternative with the wallet-storage guidance (no private key in the container; cold/multisig receiving wallet).

Layout integration

Adapted to the reorganized package: engine imports use holographic.<family> paths, tests live in tests/, catalog registrations went into holographic/caching_and_storage/holographic_catalog.py, and API_QUICKREF.md / CAPABILITIES.md / capabilities.json were regenerated with apiquickref.py / capdoc.py.

Verification

  • 31 affected tests pass (tests/test_holographic_product.py, tests/test_holographic_x402_api.py, tests/test_lecore.py, tests/test_holographic_catalog.py) against x402 SDK 2.15.0.
  • Booted in paid mode locally: protected routes return a payment-required challenge header (x402 v2, USDC on Base Sepolia); free routes stay free; wrong admin token → 401; admin writes persist to LECORE_X402_STATE.
  • x402/FastAPI/uvicorn are an optional [x402] extra — the core package still needs only NumPy.

🤖 Generated with Claude Code

LocalAgentCore is the narrow first-product surface (local agent memory,
capability routing, readiness evidence), exposed via lecore.product and
sellable per-call through holographic_x402_api.py: x402 middleware on the
read/compute routes, free health/pricing, admin-token-gated writes.

Adapted to the reorganized package layout: engine imports use the
holographic.<family> paths, tests live in tests/, the capability catalog
registrations moved to holographic/caching_and_storage/holographic_catalog.py,
and API_QUICKREF.md / CAPABILITIES.md / capabilities.json are regenerated.

Fixes over the initial draft:
- admin writes now persist to LECORE_X402_STATE instead of dying on restart
- landing page endpoint and /pricing advertise a configurable
  LECORE_X402_PUBLIC_URL instead of a hardcoded domain and a false
  "Live on AWS" badge
- Fly.io is the default deploy path (fly.x402.toml + FLY_X402_DEPLOY.md,
  volume-backed state, testnet defaults, documented mainnet flip); the AWS
  doc remains as the alternative and keeps the wallet-storage guidance

31 affected tests pass (product, x402 API, lecore areas, catalog) against
x402 SDK 2.15.0; paid mode verified locally returning a payment-required
challenge (USDC on Base Sepolia) on protected routes.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@atimics

atimics commented Aug 8, 2026

Copy link
Copy Markdown
Author

Superseded by #10, which is rebased onto current main and preserves the deployed tenant isolation, durable state, replay-safe writes, and NoSQLite safeguards while adding the canonical HTTPS x402 challenge fix. Closing this duplicate so review and deployment track the hardened branch.

@atimics atimics closed this Aug 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant