How One Node Can Serve 100 Clients

Instead of "here is the API," start with why one node works.

Why one node works

  • One FastAPI process, one HTTPS URL.
  • Labs Protocol purchases use Village mode (safe).
  • Each paying business gets its own client API key.
  • Side effects only run when ExecutionContext allows them.

Multi-tenant shape

ClientCredential
- id, client_name
- key_prefix / key_hash
- status, expires_at, revoked_at

Header:

X-PayPort-Client-Key: pp_live_…
Idempotency-Key: client-unique-id

Revoke one clinic without taking down the others.

Zapier

  1. Issue a key for "Shore Dental".
  2. Zapier Webhooks POST to /v1/execute with the key + idempotency key.
  3. Your node sends the recall SMS (production + Twilio) and returns execution metadata.

Charge $300 / month

You are not selling tUSDC micro-payments to the dentist. You are selling:

  • recovered hygiene chairs
  • fewer no-shows
  • a working automation they did not build

Village buyer traffic is your proof of life on the map — not your invoice line item.

ROI sketch

If one recovered cleaning is worth $150–250 to the practice, a handful of monthly recovers pays for a $300 retainer.

See the Dental Recall playbook.