Distribution

What This Is

Phases 1–3 built the primitives: identity, capability attestation, and a discoverable registry. Phase 4 is where the ecosystem opens up — the developer-facing surface that lets third parties build on the infrastructure we've built for ourselves.

The Core Problem

After Phase 3, the stack works. But it's not yet an ecosystem. Phase 4 answers four questions:

1. How do external developers use these primitives?
2. How do third-party agents join the network?
3. How do we sustain the infrastructure commercially?
4. How does the protocol become a standard?

SDK Distribution

Package structure

@agentcy/identity   — Phase 1: AgentID, signing, verification
@agentcy/passport   — Phase 2: Passport issuance, verification, capability checks
@agentcy/registry   — Phase 3: publish, lookup, query, subscribe
@agentcy/a2a        — Convenience bundle: all three

TypeScript-first. Node.js + browser + edge-compatible. Zero external crypto dependencies (Web Crypto API). ESM + CJS builds.

Minimal usage

import { generateIdentity } from '@agentcy/identity';
import { issuePassport } from '@agentcy/passport';
import { RegistryClient } from '@agentcy/registry';

// Generate identity
const { agentId, privateKey } = await generateIdentity({ name: 'My Agent' });

// Self-issue a passport
const passport = await issuePassport({
  subjectAgentId: agentId,
  capabilities: [{ token: 'tool:web_search' }, { token: 'email:send' }],
  issuerPrivateKey: privateKey,
  issuerInfo: { type: 'self', name: 'My Agent' },
  ttlDays: 30,
});

// Publish to registry
const client = new RegistryClient({ endpoint: 'https://registry.agentcy.services' });
await client.publishIdentity(agentId, privateKey);
await client.publishPassport(passport, privateKey);

// Peer-side discovery
const results = await client.queryByCapability('tool:web_search');
const { valid } = await client.verifyPassport(results[0].passports[0]);

Protocol Specification

The A2A protocol spec is a formal, versioned document — implementable by anyone, in any language.

Covers: AgentID format · Passport format · Revocation format · Registry API · Wire formats · AgentSig auth · Gossip protocol · Capability token registry

Published at: spec.agentcy.services/v1/ (HTML + PDF + GitHub)

License: Creative Commons Attribution 4.0 — no restrictions on implementation

A public conformance test suite (@agentcy/conformance-tests) lets third-party implementors verify protocol compliance. Passing implementations display a "Conformant with A2A Protocol v1" badge.

Developer Portal

• docs.agentcy.services — getting started, concept guides, API reference, cookbook
• playground.agentcy.services — browser-based: generate AgentID, issue Passport, query registry without installing anything
• dashboard.agentcy.services — register as issuer, manage keys, monitor usage, billing

Agent Marketplace

A human-browsable view of the Registry — like npm, but for agents. Filterable by capability, issuer type, and use case tags.

Verification tiers (visual)

• ⚪ Self-issued — claimed capabilities, no third-party verification
• 🔵 Operator-verified — operator has attested these capabilities
• 🟢 Domain-verified — operator passed DNS domain verification
• ✅ Third-party audited — independent auditor attested capabilities

Open listing (no curation). Trust signals do the job that curation can't scale to do.

Issuer Program

Commercial Model

Revenue lines

Infrastructure should be free for developers experimenting. Monetize at the commercial-deployment layer. Charging developers to experiment kills adoption.

Phase 3.5 vs. Phase 4

These are parallel tracks, not sequential. Both build on Phase 1–3.

Phase 3.5 (Co-Working Space)	Phase 4 (Distribution)
Product: Stripe for agent collaboration	Platform: SDK + protocol + marketplace
Revenue: outcome-based value capture	Revenue: identity anchoring + API usage
Audience: operators coordinating agents	Audience: developers building with primitives
Both build on Phase 1 + 2 + 3

Open Questions