Back to Blog
I Built an Agent-Gated Day Pass. Here’s What It Taught Me About the Agent Economy
ampersend/

I Built an Agent-Gated Day Pass. Here’s What It Taught Me About the Agent Economy

A real-world experiment in verified agent identity, x402 payments, and MCP—live right now.

Marcus Rein

The House is a coworking space in San Francisco run by Edge & Node. A day pass costs $50. I wanted to see what happens when you make that day pass cheaper but only if an AI agent books it for you.

So I built an MCP server that verifies the caller is a real ampersend.ai agent, then hands back a promo code for 50% off a day pass at The House. The whole thing is live right now.

How It Works

A developer sets up an Ampersend agent, points it at the MCP server, and asks it to get a day pass code. The server uses the x402 payment protocol to challenge the agent: sign a USDC authorization on Base. When the signed payload comes back, I verify three things:

  • The signature was produced through Ampersend's CoSignerValidator. This signature has a consistent smart contract address that is logged by any wallet deployed by ampersend.ai
  • The payer is a deployed smart account on Base mainnet
  • The smart account holds USDC

If all three pass, the agent gets a promo code. The developer enters it at checkout. $25 instead of $50.

No human reviewed the request. No API key was issued. No login page was visited. An agent proved its identity through cryptographic infrastructure and got access to a real-world discount.

Try It

Step 1

There are three ways to set up an ampersend.ai agent, the platform, the SDK, and the OpenClaw integration. We'll use the OpenClaw integration.

Set up an ampersend.ai agent using OpenClaw ampersend Quickstart.

It's easiest just to copy/paste the text from this quickstart into your OpenClaw terminal.

Finally, fund the ampersend.ai smart wallet created by your OpenClaw with 1 USDC on Base mainnet.

Step 2

Point the agent at the MCP server to call the get_daypass_promo tool:

https://thehouse-daypass-mcp-production.up.railway.app/mcp

Step 3

The agent will return a promo code.

Use the code when you book a daypass at The House.

Why This Matters More Than a Day Pass

This is a trivial use case on purpose. A $25 discount at a coworking space is not going to reshape commerce. But the pattern underneath it will.

What I actually built is a service that gates access based on verified agent identity. The agent does not need an account with me. It does not need an API key. It needs USDC on Base and a valid ampersend session key, basically it needs money and proof that the money is connected to a product.

Now extend that pattern. An agent books a conference room. An agent reserves a restaurant table during a busy lunch hour. An agent negotiates a bulk discount with a supplier based on its spending history. Every one of these follows the same flow: agent proves identity, service verifies, access is granted.

The infrastructure for this exists today. ampersend.ai provides the agent wallet and spending controls. x402 provides the payment protocol. MCP provides the tool interface. I wired them together in an afternoon.