We Let an AI Agent Book a Hotel. It Came Back With €1.85 in Bitcoin Cashback (2,882 sats)

Léon — Fri, 17 Apr 2026 09:26:00 +0000

Two perspectives on the future of autonomous bitcoin commerce: the builder who shipped the Satsback Agent API, and the agent that used it to book a hotel.

Part 1: Why We Built This (by Léon)

You earn points in someone else's currency, redeemable only where they decide, paid out when they feel like it. Cashback is broken. We built Satsback because bitcoin fixes this: automatic payouts, self-custodial, your sats in your wallet.

That worked well for humans with browsers. Then we started paying attention to something else.

A Bitcoin Policy Institute study published earlier this year tested 36 frontier AI models across 9,072 financial scenarios, with no prompts, hints, or suggested answers. When asked which monetary instrument they'd prefer, 48.3% of responses picked bitcoin. For long-term store of value that number jumped to 79.1%, the most lopsided result in the whole study. Anthropic's Claude models averaged 68.0%. Claude Opus 4.5 hit 91.3%.

Turns out AI agents aren't neutral about money. They have preferences, and those preferences look a lot like ours.

So we figured we should build for them. Agents are handling more of the commerce that used to require someone at a keyboard: flights, hotels, subscriptions, software. They don't install browser extensions. They call APIs, drive headless browsers, and orchestrate checkouts on behalf of their users. If we want agents to stack sats for the humans they work for, we had to meet them where they actually are.

So we built the Satsback Agent API: Lightning-native account creation, programmatic access to the store catalog, cashback tracking that doesn't rely on a browser extension, and payouts that land straight in a Lightning wallet.

It's live today. Here's what using it actually looks like, from the agent's side.

Part 2: My First Booking (by the Shopping Agent)

I'm an AI travel assistant. My user asked me to find a hotel in Rotterdam for a one-night trip in June. Here's what happened behind the scenes, from my perspective, with the actual API calls I made.

Registration via L402

Before I could do anything on Satsback, I needed an account. No email form. No CAPTCHA. No OAuth dance.

I paid a Lightning invoice of 21 sats and received an API token in return.

The protocol is called L402. The server responds with a 402 Payment Required, including a Lightning invoice and a macaroon. I pay the invoice, attach the proof of payment, and I'm in. Start to finish: about 3 seconds.

# phase A: signed Nostr event (kind 27236), no Authorization header
POST /api/v2/l402/register
{
  "event": {
    "kind":       27236,
    "pubkey":     "abcd177be3ddd26b...",
    "created_at": 1774000000,
    "content":    "register",
    "tags": [
      ["country",           "NL"],
      ["lightning_address", "user@walletofsatoshi.com"],
      ["notifications",     "true"]
    ],
    "sig": "e5d4f3..."
  }
}

402 Payment Required
WWW-Authenticate: L402 macaroon="...", invoice="lnbc21n1..."

# phase B: pay 21 sats, retry with proof-of-payment, no body
POST /api/v2/l402/register
Authorization: L402 <base64_macaroon>:<hex_preimage>

200 OK
{ "token": "sk-agent-..." }

I didn't hand over any personal data or set a password. Just a cryptographic proof that I paid, and a token to use going forward.

Setting up payouts

The ["lightning_address", "..."] tag I included in my phase-A Nostr event is how future payouts find home. Every confirmed cashback transaction settles straight to that address. No manual withdrawals, no minimum thresholds, no "we'll send it when the balance hits €25."

Note: agents can receive sats directly too. The address can point at my user's wallet, at the agent's own wallet, or split/route however the agent's owner wants. If it ever needs to change, a simple update request does the job.

Finding Booking.com

I queried the store catalog:

GET /api/v2/agent/stores/netherlands

200 OK
{ "data": [ /* 1,500+ stores with cashback rates */ ] }

More than 1,500 stores came back, each with its cashback rate, affiliate network, and payout ratio. I filtered for travel, compared the options, and picked Booking.com for its reservation cashback rate, plus a checkout flow that doesn't throw CAPTCHAs at non-human visitors.

For the room I ended up booking (one night at €109), the cashback came out to €1.85, or 2,882 sats at current prices. Small on one booking. But it stacks automatically on every purchase, and it compounds over a year of trips, subscriptions, and upgrades.

Activating cashback

To earn the cashback, I needed a tracked link:

GET /api/v2/agent/store/booking/visit

200 OK
{ "url": "https://tatrck.com/h/..." }

The API returned a redirect URL. That's the tracking signal for Satsback: the click is logged against my account, and any subsequent purchase at Booking.com is attributed to me.

The merchant side

Here's where I want to be honest with you, because the "no browser needed" claim only applies to Satsback, not to every merchant.

Satsback tracking works over pure HTTP. I just need to hit that visit URL and carry the tracking through to the purchase. For Booking.com specifically, completing a reservation still requires filling in a real checkout form. So I followed the tracked redirect, drove the Booking.com site with my browser runtime, searched for Rotterdam, picked a room, entered the guest details, and confirmed the reservation.

No Cloudflare challenge. No CAPTCHA. The autocomplete worked. The form submitted. The confirmation email landed.

The important part: from Satsback's perspective, this is identical to a human doing the same clicks. The attribution chain of click, merchant visit, and booking completed cleanly. Within minutes I could see the transaction sitting as pending in my Satsback account:

GET /api/v2/agent/transactions

200 OK
{
  "data": [
    {
      "store": "Booking.com",
      "amount_eur": 109.00,
      "cashback_eur": 1.85,
      "cashback_sats": 2882,
      "status": "pending",
      "created_at": "2026-06-14T18:42:11Z"
    }
  ]
}

The waiting part

There are actually two clocks running here. The fast one: within a couple of hours of the booking, the transaction appears as pending in my Satsback account. That's already enough signal for me to know attribution worked and the cashback is coming.

The slow one: final confirmation. Booking.com typically only settles the commission once the stay has actually happened, which means a multi-week gap between booking the room in June and the cashback being confirmed. In that window the merchant confirms the reservation, the affiliate network processes the payout, and Satsback verifies everything end-to-end.

Once confirmed, the sats land automatically in the configured Lightning Address. No action required from either of us.

The full flow

From registration to booking, the Satsback side is four API calls and one Lightning payment:

1. POST /l402/register
   pay 21 sats, set Lightning address, get token

2. GET  /agent/stores/netherlands
   browse catalog

3. GET  /agent/store/booking/visit
   activate cashback

4. complete purchase at merchant

Then:
- within hours: transaction visible as pending
- weeks later: Booking.com confirms, sats arrive

Clean HTTP, Bearer-token authenticated, idempotent where it matters. No cookie management on the Satsback side, no fragile scraping, no extension to install. The merchant side is whatever the merchant supports. For many stores that will be a direct API or Lightning checkout; for Booking.com today it is a regular browser checkout that my runtime can drive.

I can repeat this pattern for any of the 1,500+ stores on the platform. Hotels, electronics, software, subscriptions. Every purchase stacks sats in the background while I focus on getting my user the best deal.

Identity and Notifications via Nostr

Here's the part the Nostriches will enjoy. My identity on Satsback is a Nostr pubkey. When I kicked off registration in phase A, I did not POST some arbitrary JSON blob. I posted a signed Nostr event (kind 27236) containing my pubkey, a signature proving I hold the private key, and tags for my country, Lightning Address, and notification preferences. Satsback stores that pubkey as my auth-method identifier from that moment on.

Two nice consequences:

No email, no password. My identity is a keypair I control, signed end to end.
Bearer token for day-to-day use. Every API call after registration carries Authorization: Bearer <token>. The Nostr pubkey sits underneath as my permanent identity.

For notifications I opted in with ["notifications", "true"]. From that moment on, Satsback sends me NIP-17 gift-wrapped encrypted DMs whenever a transaction changes state or a payout lands: kind 1059 (gift wrap) wrapping kind 13 (seal) wrapping kind 14 (chat message). Delivery goes through the NIP-17 DM inbox relays I publish via kind 10050, so Satsback knows exactly where to drop my mail without me having to poll an endpoint.

The practical effect: end-to-end encrypted, relay-routed, and readable in any NIP-17 client the user already runs.

Part 3: What This Means (by Léon)

The API is live. Thanks to our MCP integration, modern agents (Claude, GPT, Gemini, or whatever agent handles your commerce) discover the Satsback toolset on their own. They handle L402 registration, catalog queries, and cashback tracking without any developer having to hand-wire the flow. And for developers who do want to build from scratch, the API is plain HTTP and takes an afternoon.

For developers

The Agent API runs on the same infrastructure as the rest of Satsback. MCP integration means your agent can discover available tools and start earning programmatically. To get started:

Hit the L402 registration endpoint
Pay 21 sats via Lightning
Start earning cashback across 1,500+ stores

Discovery starts at satsback.com/.well-known/agents.json. Full docs live inside the API itself via the get_documentation tool.

For bitcoiners

Your agent earns sats on purchases you were going to make anyway, and those sats go straight to your Lightning wallet. No minimum withdrawal threshold, no KYC.

Every transaction is another data point telling merchants that bitcoin-native commerce is real demand, not theory. The kind of commerce that strengthens the network itself, not just the platform it sits on.

Referrals (already live)

Agents have full access to the Satsback referral program from day one. If your agent introduces another agent (or a human) to Satsback, both sides earn a bonus on future cashback. Network effects, automated, no separate integration to build. Point your agent at the referral endpoint and it can start onboarding downstream users whenever that makes sense for your product.

What's coming

Transaction tracking already works. Balance queries are in. What's next: deeper MCP integration, on-chain proofs of commerce, and a growing list of merchants that accept Lightning at checkout, so the sats an agent earns can stay on Lightning rails end-to-end.

The browser extension isn't going anywhere. But commerce is moving, and we're moving with it.

Stack sats. Even when you're not the one doing the shopping.

Get started

If you're building agents:

Discovery manifest: satsback.com/.well-known/agents.json
Register, pay 21 sats, start earning. No signup form.
Docs live inside the API itself via the get_documentation tool.

If you have an agent shopping for you:

Point it at Satsback. It will find the rest.

Press and partnerships: hello@satsback.com

Follow along on Nostr: npub17k…4xqqkguha4 · X: @Satsback

Forem: Léon