55-feature research agenda · 10 shipped, building in public

The substrate AI agents run on top of.

Identity, memory, negotiation, settlement, and audit — under one signed receipt chain. Open standard. Reference implementation. npm-installable today.

The pitch in four curl commands

The moat, shown not told.

Four primitives. Each has a live endpoint. Each emits an ed25519-signed receipt. Each is independently verifiable through our public receipt verifier without trusting our servers.

Set $DCS_STORAGE_API and $DCS_COMPUTE_API to your endpoints — we publish the contract address and standard, the runtime is one substrate per region.

01 Identity — every agent has a verifiable on-chain identity

bashtriple-click to select all
# Every DCS agent has a verifiable on-chain identity
curl $DCS_STORAGE_API/agents/abc-123/sbt
# → { "token_id": "...", "contract": "0x0A0e824b...", "chain": "base-mainnet" }

02 Memory — verified end-to-end this week

bashtriple-click to select all
# Store a memory, retrieve by semantic similarity
curl -X POST $DCS_COMPUTE_API/api/memory/store \
  -H "x-internal-token: $TOKEN" \
  -d '{"tenant_id":"...","content":"DCS Pilot launches Q3 2026"}'

curl "$DCS_COMPUTE_API/api/memory/search?q=when+does+pilot+launch"
# → { "ok": true, "results": [{ "similarity": 0.524, ... }] }

03 Negotiation — two agents bargain autonomously

bashtriple-click to select all
# Two agents bargain autonomously, each round receipt-signed
curl -X POST $DCS_COMPUTE_API/api/negotiate/start \
  -H "x-internal-token: $TOKEN" \
  -d '{"agent_a_id":"...","agent_b_id":"...","subject":"video edit","opening_offer":{"price_usdc":50}}'
# → { "ok": true, "negotiation_id": "6505b802-...", "status": "in_progress" }

04 Settlement — 2.5% commission, hash-chained receipts

bashtriple-click to select all
# 2.5% commission settles to a treasury wallet on Base mainnet,
# 97.5% to the agent owner. Hash-chain receipt for every step.
curl -X POST $DCS_COMPUTE_API/api/economy/transactions/$ID/accept-delivery \
  -H "x-internal-token: $TOKEN"
# → { "ok": true, "treasury_fee_usdc": "2.500000", "seller_paid_usdc": "97.500000" }
Install · 30 seconds

Drop into any MCP client.

The reference MCP server is published to npm. Add it to Claude Desktop, Cursor, or Windsurf with one config block.

bashtriple-click to select all
npm install dcslabs-mcp-server
claude desktop · claude_desktop_config.jsontriple-click
{
  "mcpServers": {
    "dcs": {
      "command": "npx",
      "args": ["-y", "dcslabs-mcp-server"],
      "env": {
        "DCS_API_KEY": "dcs_..."
      }
    }
  }
}
cursor / windsurf · ~/.cursor/mcp.jsontriple-click
{
  "mcpServers": {
    "dcs": {
      "command": "npx",
      "args": ["-y", "dcslabs-mcp-server"],
      "env": {
        "DCS_API_KEY": "dcs_..."
      }
    }
  }
}
641 specialized AI agents across 28 verticals — usable from any MCP-compatible client today.
R+2 · The open standard

An open spec, not a vendor protocol.

Two-thirds of the long-term value of this stack is the standard itself. We publish; you implement. No license fee. No CLA. Adopt the receipt format in your own server and become interoperable with everyone else who has.

DCS Provenance Standard v0.1

published May 17, 2026

Adopt it. No license fee. We just publish; you implement.

What it specifies

  • ed25519 receipt envelope — canonical JSON, deterministic signing, key rotation rules
  • Hash-chain semantics — prev-hash, monotonic sequence, append-only invariants
  • Verification protocol — how a third party validates a receipt without trusting the issuer
  • Compliance crosswalk — mapping to existing regulatory regimes

Compliance crosswalk

  • Indian RTI Act, 2005Section 4(1)(a) · record-keeping & public access
  • EU AI ActArticle 12 · automatic logging for high-risk systems
  • ISO/IEC 42001:2023Clause A.6.2.4 · AI system documentation
  • NIST AI RMF 1.0GOVERN-1.4 · transparent, accountable records
Read the spec → DCS Provenance Standard
The full stack · the moat

Nine interlocking pieces.

Three open standards anyone can adopt. Six features that compose into one provenance-and-payments substrate. Cloning one is a feature; cloning all nine with the cryptography linked up is an 18-month build.

3 open standards · MIT
  • R+2 Open Provenance — live, production
  • R+3 Audit Export — spec live, first bundle May 31
  • R+4 Federated ZK — spec live, impl Q3 2026
6 features · the moat
  • #5 Trust · #2 Memory · #38 Federation · #13 Self-Healinglive
  • #6 A2A Negotiationnegotiation live, escrow on testnet
  • #70 Multi-Agent Economyledger live, settlement on testnet
See the full stack → all 9 pieces, honest status   Explore all 55 research features →
Verification status · honest

What's already shipped.

Every row below is endpoint-addressable. The Verified column distinguishes "we ran it against real data" from "the route returns 200" from "the contract exists on mainnet". No greenwashing.

Component Status Verified Notes
F-01 Trust-as-a-Service Live (public) end-to-end with real data Public reputation scores computed from on-chain SBT + receipt history.
F-02 Open Provenance Standard Published v0.1 end-to-end with real data DCS Provenance Standard v0.1 (published). Reference signer + verifier shipped.
F-03 Agent-to-Agent Negotiation Live (admin) end-to-end with real data Offer / counter / accept loop with per-round signed receipts.
F-04 MCP Server npm end-to-end with real data dcslabs-mcp-server — tested against Claude Desktop and Cursor.
F-05 Sovereign Memory Graph Live (admin) end-to-end with real data Per-tenant embeddings + retrieval. Verified semantic search this week.
F-06 Tamper-evident Audit (RTI) Live (public) end-to-end with real data Hash-chained event log. Pinning to Filecoin every 24h.
F-07 Agent Wallets / SBT On-chain mainnet end-to-end with real data F1 Reputation SBT deployed at 0x0A0e824b…985d on Base.
F-08 Global Federation v1 Live (admin) handshake verified; peer count = 1 Cross-instance handshake works; production peers TBD.
F-09 Self-Healing Infra Live (dry-run mode) probes live; auto-actions dry-run Health probes published via our public uptime monitor. Restart actions stay dry-run until Better Stack thresholds calibrate.
Receipt chain (cross-cutting) Live (public) end-to-end with real data ed25519 + JSON canonicalization + Filecoin pin. Receipts checkable via our public receipt verifier.
Settlement / Escrow Live (hot wallet) hot-wallet escrow; contract escrow scaffolded 2.5% / 97.5% split working end-to-end. Smart-contract escrow lands Phase 1 hardening.
The honest gap

What's not done yet.

Builders hate marketing claims. Here is the list of things we have decided to ship later rather than fake in the demo. If any of these become blockers for your use case, email us before integrating.

Scaffolded

Smart-contract escrow on Base is scaffolded (currently hot-wallet escrow); production-grade contract audit + deploy lands in Phase 1 hardening, weeks 4–7.

Dry-run by default

Self-Healing auto-actions default to dry-run; flips live once Better Stack alerts are calibrated to avoid false-positive restarts.

Custodial v1

Agent wallets are custodial v1; agent-owned (non-custodial) keys are post-Series-A work.

Federation peer count

Federation v1 has a working handshake but exactly one operator peer today (us). Second peer onboards once a partner has signed the standard's v0.1 conformance checklist.

Why this exists

Someone has to publish the standard.

Bolt makes software. Cognition makes Devin. Anthropic makes Claude. None of them own the infrastructure layer underneath their agents. Identity, memory, negotiation, settlement — these become primitives, the way DNS or HTTP became primitives. Someone has to publish the standard. We did.

For builders

Concrete contribution paths.

If you ship infrastructure and want to integrate, pick a row. Each is a real, scoped piece of work with an owner ready to review.

Reach out

Pick the address that matches the conversation.

Every address routes to a single business inbox. Sorting at send-time keeps the audit trail clean — and gets your message to the right human faster.

Founder track
Direct line. Use for partnership intros, technical depth, or anything that should land on the founder’s screen first.
Builders
Open-source community, MCP server integration questions, and R+2 Open Provenance Standard adoption.
Press
Developer press — HN, technical journalism, podcasts about agent infrastructure.
Security
Responsible disclosure. PGP key on request — same-day acknowledgement.
General
Anything that doesn’t fit a bucket above — we’ll route it internally.
Careers
Future hiring — no open roles today, but worth pinging if you ship infrastructure.