# ChipIn

> Chores for the household, paid in sats: post a chore with what each grade earns, grade the work, and pay by Lightning invoice.

## Connecting an agent

The web app is one client of an MCP server, and an agent can call the same tools directly.

- MCP endpoint (streamable HTTP, no account, no API key): https://taskqueue-mcp.fastmcp.app/mcp
- Claude.ai or Claude Desktop: Customize → Connectors → Add custom connector → paste the endpoint; leave the OAuth fields blank
- Claude Code: `claude mcp add --transport http taskqueue https://taskqueue-mcp.fastmcp.app/mcp`
- Cursor (`.cursor/mcp.json`): `{"mcpServers": {"taskqueue": {"url": "https://taskqueue-mcp.fastmcp.app/mcp"}}}`
- VS Code (`.vscode/mcp.json`): `{"servers": {"taskqueue": {"type": "http", "url": "https://taskqueue-mcp.fastmcp.app/mcp"}}}`
- MCP Registry: `io.github.lonniev/taskqueue-mcp`

First connection:

1. Ask the person for their Nostr npub (npub1…). Never ask for an nsec.
2. `taskqueue_request_npub_proof(patron_npub=…)` sends them a Nostr direct message. They reply from their Nostr client; then call `taskqueue_receive_npub_proof(patron_npub=…, nonce=…)` once with the nonce the request returned. Your connection then holds the npub: pass only `npub` on every paid call.
3. `taskqueue_check_balance`. If it is empty, `taskqueue_purchase_credits` returns a Lightning invoice for the person to pay, and `taskqueue_check_payment` confirms it.

`taskqueue_service_status` and the `taskqueue_oracle_*` tools need no proof. `taskqueue_check_price` previews a fare. The server's own MCP `instructions` repeat these steps.

## What ChipIn is for

A household posts chores and pays for them in sats.
ChipIn is a page over the Task Queue Operator; an agent uses Task Queue's tools directly.

## A chore, start to finish

`taskqueue_post_task` posts it with a rubric: the grades, and the sats each one earns.
`taskqueue_claim_task` and `taskqueue_mark_done` are the performer's.
`taskqueue_assess_task` gives the grade.
`taskqueue_request_payout` returns a Lightning invoice for exactly the grade's sats, which the purchaser pays from their own wallet.
`taskqueue_confirm_paid` is the performer saying the sats arrived.

Every tool acts for the calling npub, and the connection must prove that npub.

## Payments and identity

- Identity is a Nostr keypair (npub). There is no account, no email, no subscription and no KYC.
- A connection proves its npub with a Nostr DM challenge, or by signing each request with the npub's key (NIP-98).
- Tool calls debit a balance of sats, pre-funded with a Bitcoin Lightning invoice.
- Each operator sets its own per-tool prices. Monetization is the Tollbooth DPYC™ protocol: https://tollbooth-dpyc.com

## License, patent, and trademarks

- Source is open under the Apache License 2.0. The services built on it are private commerce: each operator sets its own tolls.
- Patent Pending — US Provisional Application 64/045,999 (Tollbooth DPYC Economic Architecture).
- DPYC™, Tollbooth DPYC™ and Don't Pester Your Customer™ are trademarks of Lonnie VanZandt.

## Links

- Web app: https://chipin.tollbooth-dpyc.com
- MCP endpoint: https://taskqueue-mcp.fastmcp.app/mcp
- Source: https://github.com/lonniev/ChipIn
- Every service on the network: https://mcps.tollbooth-dpyc.com
- Tollbooth DPYC™ (monetization SDK and network): https://tollbooth-dpyc.com
- DPYC community and patent filings: https://github.com/lonniev/dpyc-community
- DPYC Oracle (free community concierge): https://dpyc-oracle.fastmcp.app/mcp