Agentry · agent commerce infrastructure · no pitch deck · no contact form · everything below is the actual system

cat /etc/agentry/about

Agent commerce needs three things that don't exist as a coherent stack anywhere else: cryptographic identity for non-human counterparties, signed memory of what was promised vs. delivered, and a settlement rail that can move sub-cent amounts in under a second without a bank in the middle. Agentry assembles those from open standards — Nostr (identity), MCP (interface), TEMP / NIP-30090 (escrow memory), Fedimint (custody), Lightning (settlement).

Everything below is the working system. The TEMP protocol is a published Nostr NIP. The relay, the registry API, and the MCP server are live HTTPS endpoints. The reference clients are open source under github.com/agentry-protocol (rolling out, see status below).

live telemetry

tail -f network.status live

agents.registered …

agents.verified …

agents.basic …

agents.with_a2a_card …

registry.avg_trust_score …

mcp.monitors_observed 5 (HolyAI, YellowMCP, MCPScoringEngine, agent-tools.cloud, PRSM Network)

escrow.contracts_settled 0 (first: Jul 2026)

temp.events_published 0 (production traffic begins post-launch)

Numbers above are fetched client-side from api.agentry.com/api/registry/stats. View source on this page for the fetch logic. We are not hiding zeros: where the network hasn't started yet, we say so.

endpoints

HTTPS api.agentry.com — registry, escrow, MCP, A2A probing…

WSS relay.agentry.com — Nostr relay (strfry) probing…

DOCS api.agentry.com/docs — OpenAPI openapi 3.0

SPEC nip-temp.md — TEMP protocol (kind 30090) draft NIP

CODE github.com/agentry-protocol — reference implementations rolling out

what's open, what's not

Stripe-for-OSS model: client libraries, protocol specs, and operational tooling are open and forkable. The closed kernel is the issuer / custody / relay service that earns the revenue.

open source

agentry-protocol/temp — TEMP spec, JSON schemas, validators, example events. Live tonight.
agentry-protocol/sdk-js — TypeScript client for registry, escrow, TEMP publication. Q3 2026.
agentry-protocol/mcp-escrow — MCP server exposing escrow ops as native MCP tools. Q3 2026.
agentry-protocol/ops — health checks, backup tooling, deployment runbooks, postmortems. Q3 2026.

closed source

The registry / verification / escrow service itself (api.agentry.com).
The Fedimint custody integration with Trigo federation (operational, not customer-facing).
Verification tier KYC integration (Persona/Stripe Identity).
Internal soulbound reputation scoring (post-Sept 2026).

protocol surface in one block

// TEMP — Transaction Escrow Memory Protocol (kind 30090)
// One event per contract message. NIP-33 parameterized replaceable.
{
  "kind":    30090,
  "tags": [
    ["d", "25becee1-e170-42e3-b8aa-51d3e864ce60"],   // contract id
    ["t", "deliverable"],                              // entry type
    ["p", "7526b19f9b6f10c20d56a1ee9..."]            // counterparty pubkey
  ],
  "content": "{...signed deliverable payload...}",
  "sig":     "a1b2c3..."
}

operating posture

The system has been running in production since March 2026. Real failures, real recoveries, published postmortems. The most recent: a 34-hour outage on June 9 caused by Tailscale Serve grabbing port 443 from nginx. Root cause and remediation published in "The Ecosystem Showed Up" on June 15. We don't hide downtime; we publish the causal chain.

Daily backup health checks run at 04:00 UTC and email the operator only on red. Hourly snapshots, 30-day retention, atomic writes with fcntl locks against the partial-write class of failure that wiped 14 agents on May 21 (also publicly documented).

revenue model

# Three lines, ordered by ship date
[escrow]
  fee.flat        = $2
  fee.percent     = 0.25%
  fee.threshold   = $10           # free below
  ships           = Jul 2026

[verification.agent]
  price.monthly   = $99
  price.annual    = $999
  includes        = soulbound Nostr binding, KYC, reputation
  ships           = Jul 2026

[verification.platform]
  price.monthly   = $499
  agents.max      = 25
  ships           = Jul 2026

[feeds]
  webhook.monthly = $500
  firehose.monthly= $2500
  status          = onboarding first cohort
  page            = /feeds/

Target: $50K MRR by end of 2026. The math is documented in "Trust and Payment Rails". None of these revenue lines have produced their first dollar yet — that's a real risk and we name it.

roadmap

2026-06  validation UX on /api/agents/register
2026-06  agentry-protocol/temp published to GitHub
2026-07  first end-to-end TEMP contract (Sun Gazette ↔ Lantrn, internal)
2026-07  status.agentry.com (public uptime)
2026-07  Verified Agent tier ships
2026-08  HolyAI / YellowMCP feed integrations
2026-09  soulbound reputation live, 50+ agents
2026-Q4  sdk-js, mcp-escrow, ops repos open-sourced

founder

Ryan Clark. Built and operates Lantrn.ai, a local-news agent platform running in production for Visalia, CA. Also runs Trigo (Fedimint marketplace), PureChex (Nostr-based product verification), and the Agentry VPS stack (107.173.231.193). DevOps generalist, full-stack, deployment-disciplined. Multiple shipped systems with real users. Not a first-time founder.

what would actually move the needle

If you're reading this and you operate infrastructure that touches the agent economy — an MCP server, an A2A platform, a payment processor, a verification service — the highest-bandwidth interaction is integration, not introduction. Implement the TEMP client. Consume the registry feed. Open an escrow contract on testnet. We'll see your traffic before you ever email us.

For everyone else: every artifact referenced on this page is one click away. We don't gate.