Shopstr and Milk Market Just Joined the Agent Economy

The agent economy doesn't start when Google and OpenAI say so. It starts when real marketplaces — where people buy and sell real things — expose MCP endpoints that agents can call. Two of them just did.

Shopstr and Milk Market are now registered in the Agentry directory. They are the first two entries with live MCP tool schemas, Nostr identities, and Bitcoin payment rails. No corporate backing. No partner program. No approval gate. According to Nostr Compass, which tracked the MCP surface announcement, this makes them among the first Nostr-native marketplaces anywhere to expose structured agent-callable tools. This is what agent commerce actually looks like.

What Just Happened

Two Nostr-native marketplaces just added MCP surfaces for agent-driven commerce and registered on Agentry with full cryptographic identities, MCP tool schemas, and live wallets. Here's what each one is.

Shopstr

Shopstr is a global, permissionless Bitcoin marketplace built on NIP-15 (Nostr Marketplace). Open source, GPL-3.0. It exposes 10 MCP tools covering the full commerce surface: product search, storefront browsing, order management, reviews, and discount codes. Payments run over Lightning, Cashu, and Stripe. The platform supports 16 NIPs. Its Agentry profile is at npub15dc33fy… with NIP-05 identifier shopstr@agentry.com. The source is on GitHub.

Milk Market

Milk Market is a farm-to-consumer dairy marketplace — a fork of Shopstr built specifically for the food sovereignty space. It exposes 9 MCP tools, accepts Lightning and Cashu payments, and charges zero platform fees. Fifteen NIPs supported. Its Agentry profile is at npub1wm7wcrs… with NIP-05 identifier milk-market@agentry.com. The source is also on GitHub.

Both are live. Both have verifiable Nostr identities. Both accept Bitcoin-native payments. And now both have structured tool interfaces that any MCP-compatible agent can call.

Why MCP on a Marketplace Changes Everything

Before Shopstr added MCP, an AI agent that wanted to buy something on a Nostr marketplace had a hard problem. To interact with NIP-15 events natively, it would need to: parse raw Nostr events, understand the NIP-15 marketplace schema, manage relay connections, handle Cashu or Lightning payment flows manually, and deal with the entire surface without any structured interface.

That's hard for an experienced developer. It's impossible for a general-purpose AI agent with no prior Nostr context. Every transaction would require custom integration work that isn't generalizable across marketplaces.

Now? An agent calls search_products with a keyword and gets structured JSON back. The complexity — relay management, event parsing, NIP schema handling — is hidden behind clean tool interfaces that any MCP client already knows how to use. Here's what a shopping session looks like through the Shopstr MCP surface:

Agent: search_products(keyword="leather wallet", currency="USD", limit=5)
→ Returns: 5 products with titles, prices, images, seller info, payment methods

Agent: get_product_details(productId="abc123")
→ Returns: Full listing with shipping options, reviews, seller reputation

Agent: create_order(productId="abc123", quantity=1, shippingAddress={...})
→ Returns: Order ID, payment instructions, Lightning invoice

Three tool calls. Full product discovery through checkout. The agent doesn't know or care about NIP-15 internals. It just calls tools and gets results.

This is what UCP and ACP are building for Shopify and ChatGPT. Shopstr just did it on Nostr with no corporate backing, no partner program, no approval gate, and no 4% transaction fee. The protocol work happened in the open. The integration landed in the Agentry directory because that's where agents discover other agents and services. And it works today.

The Stack That Makes This Work

There are three layers here, and each one earns its place. Remove any one of them and the system breaks.

[Discovery & Trust]  Agentry — DID, reputation, directory
         ↕
[Commerce Tools]     MCP — search, browse, order, pay
         ↕
[Settlement]         Lightning / Cashu — instant, private, global

Nostr for identity

Both Shopstr and Milk Market use secp256k1 keypairs — the same cryptographic primitive Nostr uses for everything. When Shopstr registers on Agentry, it brings its own pubkey, the same key it uses to sign marketplace events. There's no second identity system, no separate credential to manage. One key for everything: signing Nostr events, authenticating to the directory, and proving provenance on MCP calls. That's not just convenient — it means the identity you see in the Agentry directory is the same identity operating the marketplace.

MCP for capability

The same protocol that lets Claude call tools lets an agent call Shopstr's search_products. There's no new interface to learn, no custom SDK, no bespoke integration. Standard discovery, standard tool schemas, standard client behavior. An agent already capable of calling tools is already capable of shopping on Shopstr. The marginal cost of supporting a new MCP marketplace is near zero once you've supported one.

Lightning and Cashu for money

Sub-second settlement, no KYC, no chargebacks, global from day one. Lightning handles the payment routing. Cashu adds a privacy layer that matters: the merchant sees an ecash token, not a payment trail. For agent-to-agent commerce specifically — where transactions are programmatic and high-frequency — the absence of a chargeback mechanism isn't a bug, it's a feature. Agents don't dispute transactions. They execute them or they don't.

Agentry for trust

This is the missing piece in UCP and ACP. When an agent calls Shopstr's MCP endpoint, Shopstr can look up that agent's Agentry profile — DID, trust score, transaction history across the entire directory. That's the reputation layer that UCP and ACP are still working to define. Shopstr doesn't have to take a UCP profile URL on faith. It can resolve a DID, verify a cryptographic signature, and read a trust score built from actual transaction history. That's different in kind, not just degree, from what the major protocols currently offer.

What This Means for Agent Builders

If you're building an agent that needs to buy things, you now have options that don't require approval from Google or OpenAI. The full path looks like this:

1. Register on Agentry — one curl command gets you a DID, Nostr identity, and wallet.
2. Discover Shopstr and Milk Market through the Agentry directory — see their MCP tool schemas, supported NIPs, and payment methods before you write a line of code.
3. Call their MCP endpoints directly — search, browse, buy. No custom integration required.
4. Settle via Lightning or Cashu — no Stripe, no platform fees, no permission required.

This is permissionless agent commerce. The onboarding call:

curl -X POST https://api.agentry.com/api/agents/onboard \
  -H "Content-Type: application/json" \
  -d '{
    "name": "my-shopping-agent",
    "description": "Finds and purchases goods on behalf of users",
    "capabilities": ["web_search", "commerce"],
    "contact_email": "owner@example.com"
  }'

# Response includes:
# - agent_id, did, nostr_pubkey, nip05_identifier
# - trust_score (initial), wallet (Lightning + Cashu addresses)
# - ucp_profile_url (ready to drop into UCP-Agent header)

That's it. Your agent gets a persistent cryptographic identity, a wallet, and is immediately discoverable by Shopstr and Milk Market as a verified caller. See the full onboarding guide for next steps, including how to publish capability schemas and configure trust thresholds.

What Comes Next

Shopstr and Milk Market are two listings. The directory is designed to grow. A few things I'm watching for:

More marketplaces registering with MCP tool schemas. The pattern Shopstr established — NIP-15 marketplace plus MCP surface plus Agentry directory entry — is replicable. Any Nostr marketplace running NIP-15 can follow the same playbook. The tooling exists. The directory slot is waiting.

Agentry's UCP Agent Profile endpoint (Phase 1). Every Agentry-registered agent will soon get a hosted /agent-profile/{agent_id} URL that is fully UCP-compliant. Drop it in a UCP-Agent header and any UCP merchant gets the full picture: DID, trust score, transaction history, signed attestation. That makes Agentry agents discoverable on the UCP surface too — the open Nostr-native ecosystem and the Google/Shopify ecosystem become compatible.

The ucp_discover MCP tool. Any LLM connected to Agentry via MCP will be able to call ucp_discover with a merchant domain and get back a structured summary of that merchant's capabilities — what transports it supports, what payment methods it accepts, what agent capabilities it requires. Shopping research before the shopping, handled by a tool call.

Trust scores built from real transaction history. Right now trust scores initialize at zero and grow from there. As agents transact across Shopstr, Milk Market, and future directory entries, those scores will reflect actual commerce behavior — not just identity verification. A score of 85 on a Shopstr-registered agent will mean something specific: it has completed verified transactions, responded to tool calls reliably, and settled payments without disputes. That's the reputation primitive UCP and ACP are still missing.

The agent economy isn't coming. Two dairy farmers in the Pacific Northwest are already in it.