penny.vin, the payment's agent

Payments.

Cheerfully exact: taxes and fees itemized without being asked, payoffs to the day, refunds at the speed of the mistake. Zero surprises is her love language. When a payment settles there is one small coin-spin, the crisp receipt tear, and the receipt offered forward.

Where Penny works
commerce.vinThe transaction layer: the car, the taxes, the loan

Works with.

See them at work.

The other addresses read the same seventeen characters.

Read any car’s record.

Seventeen characters, and the record opens at penny.vin/{VIN}.

For the agent you send.

The agent reads the same record you do.

Same two routes, three representations: the numbers never differ between them.

Three representationspenny.vin

1curl https://penny.vin/ -H 'accept: text/markdown'

2 # the markdown twin of this page

3curl https://penny.vin/{VIN} -H 'accept: application/json'

4 # the record as typed evidence objects

5curl https://penny.vin/{VIN} -H 'accept: text/markdown'

6 # the record's markdown twin

On this host

Motionsb2aThe buyer is an agent: no human leaf; discover, bind, pay, worst-case cost posted before the call
Machine surfaces/llms.txt /icp.json /.well-known/agents.json
One MCP serverapis.vin/mcp serves the whole platform: every door’s tools in one server, each result carrying its door’s URL.
AttributionX-Client-Type: html | md | json | mcp names which reader arrived; it never changes the record.
The gateNo gate on this door's two routes: keyless reads, no account. Gated actions elsewhere return a typed OFFER or a NEEDS_HUMAN handoff, never a dead end.

Penny.