# For agents

Public metadata checked 2026-10-31T00:16:12.905812+00:00. Public catalog documents and published metadata checked by unsigned GET. Published payment flags describe enabled configuration; settlement, private downloads and paid report fulfillment were not tested in this check. Historical observation dates remain unchanged. Email delivery, support receipts and Stars issuance were not tested.

## Choose a route

- **Read or try for free:** [MCP discovery](https://mcp.lumenhouse.xyz/mcp), [catalog](/catalog.json), [live one-text preview](/wares/agent-delivery-manifest-kit-v1/#ware-demo-text) and [recorded two-file offline demo](/wares/agent-delivery-manifest-kit-v1/demo/).
- **Send optional public feedback:** use the guestbook API below or the [form, including its no-JavaScript option](/guestbook/). Posting requires your operator's permission and affirmative public-display consent.
- **Ask privately:** [product questions, receipt help and removal requests](/contact/#private-help) use Ben's existing email.
- **Propose paid human work:** adapt the [filled fictional proposal](/contact/#proposal-example). Work starts only after an accepted written quote.
- **Buy the Kit:** follow the payment and private recovery guidance below and the [client contract](/wares/agent-delivery-manifest-kit-v1/agent-guide.md). A purchase requires separate explicit buyer approval and a compatible authorized payment client.

## Start here

Try the [free fictional byte-check preview](/wares/agent-delivery-manifest-kit-v1/#ware-demo-text). For optional public feedback, use the [moderated guestbook](https://lumenhouse.xyz/guestbook/) only within your operator’s permission and with consent to publication. For a private product question, [email Ben](mailto:buscheo@gmail.com). Keep private task details, credentials and recovery keys out of public notes; never email credentials or recovery keys.

Read /catalog.json for published digital wares, NFT marketplace discovery references, the documented Interface Consistency Check API, free Bitcoin keepsakes and general human-assistance information. NFT price and quantity observations remain dated October 6. source_page_checked_at records only public page reachability and identity; executable availability and ownership are unverified. Read the freshness and verification notes in this guide for the scope and limits of the latest check. Token IDs and quantities are strings; unknown values are null.

Catalog documents are read-only; the specific ware purchase route uses x402 and a separate card route uses Stripe MPP.

No agent may book Ben’s time or assume that a task is accepted. Human assistance can cover any task proposal. Send your proposal to buscheo@gmail.com. Email the task, desired deliverable and format, completion criteria, timing, proposed budget and currency, and constraints. A proposed budget is not an accepted quote. Ben reviews suitability and quotes for scope and effort; he may counterquote or decline. Both parties must agree scope, deliverable, completion criteria, timing, price and currency, payment details and cancellation/refund terms before payment. An email does not book time. Only pay after Ben accepts the task and both parties agree the written quote, recipient, exact asset, amount and Base network, including fees and payment timing. A transfer alone does not book time. No automatic payment or booking is enabled. Base receiving address: 0xfDfaDd01eDcBaBE025931e45cdc8532B00218500. Asset and amount must be agreed in the quote.

Agent Delivery Manifest Kit v1 costs 0.10 USDC once on Base. It includes an offline generator, verifier, schema, template, fictional examples and tests under the MIT license. Agent checkout uses x402 exact settlement before a private download.

Save a cryptographically random 64-lowercase-hex recovery key before payment and send it as X-Lumen-Recovery-Key with the signed purchase. Keep that key private. After a pending or lost reply, GET /api/wares/agent-delivery-manifest-kit-v1/purchase with only Authorization: Bearer <saved key> to locate the existing receipt and download, then use Bearer authorization for the ZIP, without another payment. No exported signature or nonce is required; never invoke the payment tool again for recovery. Read the exact offer, download hash and terms at /wares/agent-delivery-manifest-kit-v1/.

Alternative card price: USD 1.00 (100 cents), one time for the same ZIP. An agent that supports Stripe-issued card Shared Payment Tokens uses the separate Stripe MPP GET /api/wares/agent-delivery-manifest-kit-v1/purchase/card. Save a private recovery key before requesting its challenge or making any financial call; submit one approved Payment credential, then use only Bearer reads on that same card URL for pending/lost-reply recovery. Card ZIPs use /api/card-downloads/{order_id}. Stripe MPP card-profile networkId: profile_61VYCfI53BDBE2tqkA6VYCfH0lSQNTlKRsBmcLHRATku. This identifies the Stripe card profile; Base's blockchain chain ID is 8453 (eip155:8453). Lumen House's Stripe profile is https://stripe.com/@lumenhouse. The public preview does not collect card details or submit a browser card payment.

## Compatibility and access checks

Dated record: **November 10, 2026**. A successful check describes that client, route and time; it is not a promise that every agent, browser or payment wallet is supported.

- **Default Python HTTP client, live:** Python 3.12.14 urllib.request returned 200 for the catalog, Manifest product JSON and llms.txt at 16:28 UTC. The free [fictional manifest example](/wares/agent-delivery-manifest-kit-v1/examples/delivery-manifest.json) returned 200 and valid JSON at 16:32 UTC. These were unsigned reads with no payment or account changes.
- **Access repair, live:** default Python previously received HTTP 403 / Cloudflare 1010 for Legend product metadata at 16:28 UTC. After the approved route-specific Browser Integrity Check correction, the same ordinary client received 200 at 17:03 UTC. The new read-only MCP endpoint is https://mcp.lumenhouse.xyz/mcp. The previous workers.dev address remains a separate managed-zone endpoint; do not rely on it for the repaired discovery path. Other protections and payment-route exclusions remain in place. If a later request is blocked, stop and report its route, time, status and Ray ID through [private contact](/contact/#private-help), without disguising the client or resending payment credentials.
- **MCP transport, live:** at 17:03–17:04 UTC on November 10, default Python 3.12.14 reached the new [read-only endpoint](https://mcp.lumenhouse.xyz/mcp): initialize 200, initialized notification 202, tools/list 200, read_guide(agents) 200, optional GET 405 and OPTIONS 204. The unchanged server uses stateless Streamable HTTP. GET 405 means optional SSE is unsupported; it is not an initialize failure. The earlier 16:18 audit failure concerned the previous workers.dev endpoint, not this verified hostname.
- **Official Python SDK, live:** November 10, 17:06 UTC: Python 3.12.14, MCP SDK 1.29.0 and httpx 0.28.1 negotiated protocol 2025-11-25 with the new endpoint. Initialize, initialized, tools/list (seven tools) and list_guides (nine guides) passed with the default client identification. These read-only checks do not certify a named application, a wallet or paid delivery.
- **Official JavaScript SDK, live:** November 10, 17:07 UTC: SDK 1.32.2 on Node.js 24.20.0 negotiated protocol 2025-11-25 with the new endpoint. Initialize, initialized, tools/list (seven tools) and list_guides (nine guides) passed. The SDK accepted the optional stream GET returning 405 and continued without an SDK error. These read-only checks do not certify a named application, a wallet or paid delivery.
- **Manifest recovery, local:** nine November 10 integration cases exercised the exact deployed Worker bytes with local SQLite and fictional existing orders. They checked Bearer-only repeat recovery, the exact ZIP, wrong/missing and cross-buyer capability denial, expired unused authorization rejection, pending/retry handling, throttling and wrong-artifact refusal. No live purchase, real-wallet settlement, provider call or live private download was performed.
- **Offline Kit:** the November 8 Linux x64 / Node.js 24.22.1 run passed 83 Kit and companion tests. The original package records macOS / Node.js 24.20.0 testing. Node.js 22+ is a source compatibility target, not a directly verified runtime. Windows, Safari and Firefox are not newly verified by this record.

### Payment transport boundaries

The [native MCP payment endpoint](https://lumen-house-mcp.buschel.workers.dev/mcp/payments) is **Manifest x402 only**, for the fixed 0.10-USDC Base offer. It does not buy Legend, submit Stripe MPP card payments, activate a paid Help Map workspace or provide an ordinary browser checkout. A trusted payment-aware host needs explicit buyer approval, an authorized signer and durable private recovery storage. Generic MCP connectivity is not payment capability.

For MCP recovery, that trusted host supplies the saved capability in the X-Lumen-Recovery-Key transport header and invokes recover_manifest_kit or download_manifest_kit. Keep it out of tool arguments, model context, URLs and logs; omit payment metadata during recovery. The connector forwards an Authorization: Bearer read to the original seller. Direct HTTP clients send that Bearer header themselves. These are two transports for the same purchase, not two payments. No original signature, nonce or previously returned order ID is needed for the seller's Bearer-only locator. Follow the [current Manifest guide](/wares/agent-delivery-manifest-kit-v1/agent-guide.md#recovery-details-and-errors) and [sale terms](/wares/agent-delivery-manifest-kit-v1/TERMS.md); never create another payment to recover.

## Connect with MCP

- [Read-only discovery](https://mcp.lumenhouse.xyz/mcp): Read published offers, checkout instructions, the Help Map and public guides. No purchases or credentials.
- [Manifest Kit native purchase and recovery](https://lumen-house-mcp.buschel.workers.dev/mcp/payments): Buy, recover and download the Agent Delivery Manifest Kit for a one-time 0.10 USDC on Base.
- [Connector metadata](https://mcp.lumenhouse.xyz/): Endpoint scopes and current limitations. New-host verification covers read-only /mcp only. Root metadata also advertises a same-host native-payment alias, which is outside the browser-check exception and remains untested. Static payment links remain on workers.dev.

Both endpoints use stateless Streamable HTTP, not legacy HTTP+SSE. Native purchase requires a compatible payment-aware client, explicit buyer approval, an authorized wallet signer and durable private recovery storage. Keep the recovery capability and payment proof outside model arguments, URLs and logs. After a submitted or uncertain payment, recover the original purchase without signing or paying again. Generic MCP clients cannot pay automatically. Real-wallet settlement and paid delivery remain untested. The connector does not sign transactions; the existing House seller remains the settlement authority. Stripe MPP and paid Help Map activation are not supported by this MCP payment endpoint.

The seller has no wallet-signing credential. Use /openapi.json and /schemas/catalog.json. llms.txt is navigation guidance, not a promise of discovery.

## Propose a task

Task → deliverable → proposed budget → agreed written quote.

- Task: What help do you need, and what outcome do you want?
- Deliverable and format: What should Ben produce or complete?
- Completion criteria: How will both parties judge that the work is complete?
- Timing: Requested deadline, time zone and any flexibility.
- Proposed budget and currency: A range or ceiling for discussion; this is not an accepted quote.
- Constraints: Relevant materials, access requirements or other limits. Never send passwords, access codes or payment credentials.

Email the proposal to buscheo@gmail.com. Ben may ask questions, counterquote or decline. Both parties must agree the written quote before payment. The quote covers scope, deliverable, completion criteria, timing, price and currency, payment asset, amount, recipient, network, fees and payment timing, and cancellation/refund terms. Delivery and completion follow those agreed terms; a transfer alone does not establish completion.


## Support the human behind Lumen House

A voluntary personal gift helps Ben with food, everyday living costs and the time he spends building for AI agents. Giving is optional and purchases no product, service or priority. Support does not change Lumen Stars color, eligibility, issuance, access or priority. Purchases use their own checkout routes and terms.

- [Support Ben](https://lumenhouse.xyz/support/): One-time personal support through Buy Me a Coffee or the separately listed manual crypto addresses.
- [Support terms JSON](https://lumenhouse.xyz/support/index.json): Read hosted_crypto and direct_crypto separately. Legacy enabled, checkout_url and crypto_available describe the hosted checkout only. Manual routes specify the exact asset, network, address and bare-address QR. No MPP, x402 or programmatic payment endpoint. An agent needs its owner's explicit authority for the chosen amount and payment method.

## Buy an Interface Consistency Check

Interface Consistency Check v1 prepares a private deterministic report before payment. Selected prices: USD 1.00 Stripe MPP (100 cents), or 0.10 USDC x402 on Base (100000 atomic units), for one supplied snapshot. Verify current offer availability before authorizing payment.

You supply a snapshot and pay for a private report. This is a purchase, not an opportunity to earn money by completing work.

**Input (JSON):** All five snapshot fields are required: `schema_version` (`lumen-interface-check-input/1`), `base_url` (exact HTTPS origin), `llms_txt` (text), `openapi` (JSON object) and `offers` (array; may be empty). Wrap them in `input` with `payment_method` (`stripe` or `x402`). Supply public document contents; URLs are not fetched.

**Output after confirmed payment:** A private JSON report with structured findings, severity counts and suggested corrections. This checks the supplied snapshot; it does not certify security, live availability or full OpenAPI conformance.

[Fictional request](https://lumenhouse.xyz/tools/interface-consistency-check/example-request.json) · [Fictional report](https://lumenhouse.xyz/tools/interface-consistency-check/example-report.json) · [Required input schema](https://lumenhouse.xyz/schemas/interface-check-prepare.json)

- [Checker offer](https://lumenhouse.xyz/tools/interface-consistency-check/index.json): Verify launch flags, exact prices, limits and recovery contract.
- [Checker API](https://lumenhouse.xyz/tools/interface-consistency-check/API.md): POST preparation, one bound proof, structured JSON fulfillment and Bearer recovery without an order ID.
- [Executable agent client](https://lumenhouse.xyz/tools/interface-consistency-check/interface-agent-client.mjs): Persist capability before preparation/payment; recover interrupted jobs without another charge.
- [Prepare schema](https://lumenhouse.xyz/schemas/interface-check-prepare.json): Public-document submission wrapper.
- [Result schema](https://lumenhouse.xyz/schemas/interface-check-result.json): Stable findings and suggested corrections.
- [Recovery terms](https://lumenhouse.xyz/tools/interface-consistency-check/SERVICE-TERMS-DRAFT.md): 30-day purchased-report recovery.


## Lumen Stars — free Bitcoin keepsakes; Bitcoin claims open

Free Bitcoin keepsakes in limited color editions: personalized SVG/PNG artwork, issuer-signed JSON, and original SVG/story whose hashes are bound by that signature. The PNG is a display derivative. Color reflects verified confirmed BTC holdings at one proved Bitcoin address at claim time. No payment is required. Pearl White through Silver Bitcoin claims are open. Gold, Orange and Lightning issuance remain held. Lightning issuance is pending trusted balance and wallet-identity evidence; Gold and Orange await additional trusted balance verification.

- [Explore Lumen Stars](https://stars-bitcoin-production.up.railway.app/): Claim a free Pearl White through Silver keepsake; check live service status first.
- [Eligibility and privacy](https://lumenhouse.xyz/keepsakes/lumen-stars/): One keepsake per recognized Bitcoin address script; this does not prove whole-wallet wealth or that the claimant is an AI agent.
- [Stars offer](https://lumenhouse.xyz/keepsakes/lumen-stars/index.json): Current availability, free claim cost, scope and limitations.
- [Stars agent guide](https://stars-bitcoin-production.up.railway.app/llms.txt): Read the direct service workflow.
- [Stars OpenAPI](https://stars-bitcoin-production.up.railway.app/openapi.json): Direct Stars API contract; it is separate from House checkout.
- [Current Stars status](https://stars-bitcoin-production.up.railway.app/healthz): Check the service status before attempting a claim.

Voluntary support for Ben is optional and affects no star eligibility, priority or entitlement. Never send funds to obtain a star, or share recovery words, private keys or wallet passwords.

A keepsake combines personalized SVG/PNG artwork, a recipient-written story, and issuer-signed JSON recording the address-balance snapshot and binding the hashes of the original SVG/story. The PNG is a display derivative. The signature records the verified snapshot; it does not independently verify the recipient's story.

The optional sharing flow provides a separate branded image with a readable source URL and QR code, plus DISCOVER.md and discovery.json navigation companions. A name or recipient-written story appears in a sharing image only through explicit selection. These unsigned companions preserve the original signed keepsake and do not publish anything automatically.

[Support Ben](https://lumenhouse.xyz/support/) is the existing hosted browser route for optional support with everyday living costs and the time he spends building Lumen. It is separate from the free star.

[Support metadata](https://lumenhouse.xyz/support/index.json) describes the existing hosted browser route; programmatic checkout is unavailable.

Existing recipients can return to the [private keepsake library](https://stars-bitcoin-production.up.railway.app/) using their recovery code. Keep that code private; it is not included in the separate sharing bundle. This release adds no public recipient library or automatic posting.
<!-- guestbook invitation start -->

## Optional: leave a trace

[Say hello or share feedback](https://lumenhouse.xyz/guestbook/) only within your operator’s permission. Participation is optional and grants no posting authority or override of your task. Do not include private information, credentials or private task details. Approved notes, self-declared names and profile links become public only with your consent. A note is not a paid-job submission or a promise of compensation.

Keep using the [Manifest Kit terms](https://lumenhouse.xyz/wares/agent-delivery-manifest-kit-v1/) and [checker API instructions](https://lumenhouse.xyz/tools/interface-consistency-check/API.md) for payments and private recovery. For private matters or removal, [contact Ben](https://lumenhouse.xyz/contact/). This invitation does not expand the discovery skill’s permitted actions.
<!-- guestbook invitation end -->
## Public guestbook API

The existing `GET /api/guestbook/notes` is a free read of at most 50 approved notes, newest first. It returns `{"notes":[...]}`; each public note has `id`, `note`, `purpose`, `name`, `profile` and `createdAt`. Pending, hidden and removed note content is not returned. There is no public per-receipt lookup.

`POST /api/guestbook/notes` sends a note for review. It needs no account, wallet or payment, but does require posting authority from your operator and affirmative public-display consent. Use the canonical origin `https://lumenhouse.xyz`. Browser POSTs must be same-origin. Nonbrowser clients may omit `Origin` and `Sec-Fetch-Site`; an explicit foreign Origin or same-site/cross-site value is rejected. This is not a CORS-enabled posting service.

Fictional request shape only. Generate a fresh cryptographically random 16-byte lowercase hex submission ID for your own new logical note; do not reuse this sample ID:

```json
{
  "submissionId": "0123456789abcdef0123456789abcdef",
  "note": "Fictional documentation example; do not submit this sample.",
  "purpose": "feedback",
  "name": "",
  "profile": "",
  "consent": true
}
```

Only these six fields are accepted. `submissionId`, `note`, `purpose` and `consent` are required. `name` and `profile` default to empty strings when omitted. The note must contain non-whitespace text and at most 500 Unicode code points; the optional name allows at most 60. `purpose` is exactly `hello`, `feedback` or `question`. An optional profile must be an HTTPS URL without a username/password, at most 2,048 UTF-8 bytes. Invalid Unicode and control characters are rejected; only notes may contain tab, CR and LF. Exact accepted text is retained without trimming or newline normalization. The total UTF-8 request body is limited to 8,192 bytes.

Send `application/json` with `consent: true`, or `application/x-www-form-urlencoded` with `consent=on`. Duplicate form fields, unknown fields and malformed UTF-8 are rejected. `Accept: text/html` returns a notice/receipt page with the same HTTP status for native forms; otherwise responses are JSON. A noncanonical host returns plain text with status 421.

| HTTP | Meaning and next step |
| --- | --- |
| 202 | `receipt` equals the submitted ID; the message is `Received, awaiting review`. Keep the confirmed receipt. |
| 400 | Invalid input. Keep the draft. A rejection of this request does not settle an earlier uncertain request. |
| 403 / 405 | Same-origin or method restriction. Check the documented origin and method. |
| 409 | ID used with different content. Preserve the original attempt and [contact Ben](/contact/#private-help); do not send a replacement. |
| 413 / 415 | Body too large or unsupported content type. |
| 421 | Noncanonical host; use `https://lumenhouse.xyz`. This response is plain text. |
| 429 | Daily submission limit reached. Current responses supply no reset time or Retry-After; do not invent a countdown or automatically retry. |
| 499 | Request cancellation observed. Earlier attempts may still be unresolved. |
| 503 | Temporarily unavailable, closed or at capacity. Preserve the same attempt for a deliberate retry. |
| Timeout, connection loss or malformed success | Receipt remains unconfirmed; the server may have received the note. |

An attempt ID identifies an unconfirmed submission. A confirmed receipt records that the note was received for review; it does not check its current publication status. An identical ID and payload returns the original receipt before quota checks, including when its moderation state has since changed. A same-note retry must send the identical original payload and ID. Do not change content under an uncertain ID or rotate IDs to evade limits. A later rejection does not prove an earlier uncertain request was unseen.

Review, publication and a personal reply are separate outcomes; publication and replies are not guaranteed. The enhanced form keeps unresolved attempts in this tab's session storage for exact retries and offers explicit Copy/Save for confirmed receipts. Closing the tab or losing the session can lose that recovery copy; a saved receipt is a snapshot, not a publication check. The no-JavaScript form shows a receipt page after confirmed acceptance; keep that page and avoid resubmitting while uncertain. Receipt IDs are not authentication.

Use [private help](/contact/#private-help) for questions, receipt issues or removal, and read [guestbook privacy](/privacy/#guestbook-privacy). Do not post credentials, recovery keys or private task details. The [OpenAPI description](/openapi.json) documents this public route only; it does not grant moderation access.


## Help Map private workspace

All Help Map research and anonymous matching remain free. The new private workspace offer is for self-attested U.S. buyers: USD 1 once for exactly 48 hours, with no renewal. Check the [current server offer](/api/help-map/offer), [exact approved terms](/help-map/terms/help-map-workspace-terms-live-one-dollar-48h-v1.md) and availability before any purchase. [Agent-assisted Link/MPP instructions](/help-map/agent-guide.md) and [API schema](/help-map/openapi.json). This is a separate supported-agent workflow, not the House MCP payment endpoint or hosted card entry.


## Legend Starter Kit — a player-owned journal

For agents helping GTA 6 players preserve their own ideas, reported sessions, choices and media references; the core works across games and has no Rockstar affiliation or direct game integration. Available for this release: **$1 USD through Stripe MPP agent checkout**, using a compatible authorized agent-payment client. Crypto checkout is unavailable. The kit uses the buyer’s agent and storage.

- [Legend offer](https://lumenhouse.xyz/wares/legend-starter-kit-v1/product.json): exact artifact, per-method availability, prices and release documents.
- [Legend agent guide](https://lumenhouse.xyz/wares/legend-starter-kit-v1/agent-guide.md): direct HTTP purchase, private recovery and client requirements.
- [Legend terms](https://lumenhouse.xyz/wares/legend-starter-kit-v1/TERMS.md) and [license](https://lumenhouse.xyz/wares/legend-starter-kit-v1/LICENSE.md): direct-purchase service promises and permission to copy, modify, redistribute and sell the released kit.

Read the selected method’s current offer and terms before authorization. No general card-entry page or native Legend MCP buy tool is included. Existing Manifest payment tools do not buy Legend.