Open Protocol · Reference Implementation · MCP-Native

People
API.

Services got APIs. Now people get them too.

An open protocol for machine-readable intent manifests. People publish what they want. Vendors come to them with structured, scored offers. Privacy is progressive. AI agents are first-class.

Endpoints
13
MCP tools
6
Privacy tiers
3
The flip

You chase vendors today.
They come to you tomorrow.

Commerce is a demand-side protocol waiting to happen. Everyone has built the supply-side.

Today
PYOU

You search. You tab through catalogs. You fill forms. You do the work.

With People API
PYOU · AGENTOFFER$240 · 2dOFFER$280 · 3dOFFER$320 · 5dOFFER$360 · 7d82716854

You publish what you want. Vendors compete for it. Your agent ranks, filters, and can auto-accept.

How it works

One flow. Six steps.

From a sentence in a chat box to an accepted vendor offer — the same pink-sink example end-to-end.

  1. 01

    Declare

    You · Agent

    A person tells an AI assistant: "Pink undermount kitchen sink, porcelain, 30", NYC, $200-400."

  2. 02

    Publish

    Protocol

    The agent creates an intent via People API. Category, budget, metro become publicly discoverable. Identity stays hidden.

  3. 03

    Discover

    Tier 1

    Vendors browse the registry, filter by category, metro, and urgency. They see public fields only.

  4. 04

    Offer

    Vendor

    A vendor submits a structured offer — price, delivery, attributes, an optional alternative. No free-text pitch required.

  5. 05

    Score

    Server

    The server scores the offer 0-100 across six factors. Very bad offers are auto-rejected. Qualifying offers under an auto-approve price are auto-accepted.

  6. 06

    Transact

    Tier 2 → 3

    On acceptance, the vendor gets Tier 2 (ZIP + full requirements via session token). Tier 3 (identity, address) unlocks only on confirmed purchase.

What makes it different

Four load-bearing ideas.

01

A protocol, not a platform.

Self-hostable. Any URL that implements the endpoints is a valid node. Federation is a design goal, not a future feature.

Read the spec
02

Privacy enforced at the protocol level.

Three tiers of progressive disclosure. Vendors can't see who you are until you choose to transact — not by policy, by filter function.

Three tiers
03

Scoring is the quality flywheel.

Every offer is scored 0-100. Vendors who match well get Tier 2 access; vendors who spam get auto-rejected before the buyer ever sees them.

The formula
04

AI agents are first-class.

Ships as an MCP server with six tools. Claude, Cursor, or any MCP-compatible assistant can create intents, view offers, and accept deals natively.

Six tools
Scoring

Every offer scored 0-100.

A rule-based engine turns offer noise into a ranked queue. The buyer never sees the bottom 20% because the server refuses them at submission time.

See the full engine
scoring.tspts out of 100
  1. Price fit
    How close the offer price is to the budget band.
    +30
  2. Attribute match
    How well the offer's attributes line up with what the intent specified.
    +25
  3. Delivery speed
    Urgency-weighted delivery window.
    +15
  4. Vendor rating
    Normalized five-star rating.
    +15
  5. In stock
    Binary — can you ship it today?
    +10
  6. Alternative (counter-offer)
    Flat penalty for proposing a different product.
    -5
Auto-accept if price ≤ autoApproveBelow AND score ≥ 70. Auto-reject if score < 20, price > 1.5× budget.max, or a material_exclude constraint matches.
Stack

Boring parts, chosen carefully.

Why each choice
Backend
Node.jsTypeScriptExpressSQLite (WAL)Zod
Agent
MCP SDK
Frontend
React 19ViteTailwindReact Router 7
Realtime
Server-Sent Events
Testing
Vitest
Demo

See it running.

A reference React SPA ships with the server. Five screens, SSE live updates, seeded demo data.

Full walkthrough
Dashboard · buyer view1-dashboard.png
Buyer dashboard showing active intents with offer counts.

Ship it

Services got APIs. Now people get them too.

MIT-licensed. Self-host it, fork it, run a private registry for your team.