Short version: we shipped an Agent API for Satsback. L402 registration (21 sats), MCP-native, Lightning payouts.
An agent registered, picked Booking.com from our 1,500-store catalog, drove the checkout with its browser runtime, and earned €1.85 (2,882 sats) cashback on a €109 room in Rotterdam.
The whole Satsback side is four API calls + one Lightning payment. Clean HTTP, Bearer-auth, no browser extension required.
For the Nostriches: identity = Nostr pubkey (signed kind-27236 event at registration). Notifications arrive as NIP-17 gift-wrapped DMs on the kind-10050 inbox relays the agent publishes. E2E encrypted, delivered like any other Nostr DM.
Full write-up with every API call and response body:
https://satsback.com/blog/ai-agent-hotel-booking-bitcoin-cashback
Discovery manifest at satsback.com/.well-known/agents.json for agents that want to register themselves.
If you build an agent that uses it, let me know what breaks.
Used openclaw for the Booking.com checkout. What's everyone else running for agent browser runtime in shopping flows?