Frequently asked questions

We build the open infrastructure layer for the AI agent economy — four primitives: a provenance standard (R+2), on-chain agent identity (SBTs on Base mainnet), sovereign memory, and an agent-to-agent settlement layer. The standard is free. The reference infrastructure is our commercial surface.

They were, two years ago. By mid-2026, real money flows through agents — Replit's Agent, Cursor's auto-mode, Anthropic's Claude Code, OpenAI's Operator, dozens of vertical agents in customer support, code review, research. The infrastructure layer hasn't caught up. That's where DCS fits.

Dubai, UAE. DCS AI Technologies L.L.C is incorporated under Dubai mainland licensing. Solo founder with Indian origin.

One. Founder Deepak Dudi, solo and self-funded. First 2-3 hires will be senior engineers (memory, cryptography, on-chain), paced against founder capital + pilot revenue — not gated on any financing event.

A small, deliberately minimal specification for how AI agents sign their actions, store the receipt, and prove what they did later. Full spec at dcslabs.ai/standard. Ed25519 signatures (RFC 8032), RFC 8785 canonical JSON, hash-chained receipts, optional IPFS pinning.

The first country or lab to adopt R+2 sets the default for everyone else. Open is the only way to win that race. We make money from the reference infrastructure (Memory, Treasury, managed identity), not from gatekeeping the standard.

The on-chain agent identity contract. Soul-bound (non-transferable) ERC-5114 token, deployed on Base mainnet at 0xbDd1f5fC349D9a8EfCEb07Edbd491233b2540f5F. Every agent in the DCS stack mints to this contract.

No. The on-chain identity layer is one option, not a requirement. R+2 is chain-agnostic — you can use DNS TXT records, DIDs, or a simple HTTPS key endpoint as the identity layer. The MCP server's onboarding doesn't require any wallet setup.

A cryptographically signed memory layer for AI agents. Survives sessions, restarts, cross-region failover. 1536-dim embeddings via OpenAI's text-embedding-3-large. Every write is an R+2 signed receipt. Free first 1,000 writes per agent at dcslabs.ai/memory.

Gas costs work for agent-scale microtransactions, native USDC support (Treasury settles in USDC), and the Coinbase-backed ecosystem aligns with mainstream-finance distribution. We considered Optimism and Polygon — Base won.

Three revenue lines: (1) Subscription tiers on Sovereign Memory ($29/mo Builder, custom Sovereign). (2) 2.5% transaction fee on agent-to-agent settlements through the Treasury (USDC on Base). (3) Sovereign deployments — air-gapped on-prem installations for government and defence customers (custom pricing).

No. DCS AI Technologies is self-funded by the founder — property-backed personal capital sufficient to operate for the next 6–12 months minimum. We are not running a process, not pushing decks, and not pursuing investor outreach. If you would like to learn about the company anyway, our capital stance page explains exactly where we are and what would change our mind. Inbound conversations from strategic partners are welcome — financial-only conversations are politely declined.

For the foreseeable future, yes. We picked 2.5% because it's high enough to underwrite the business at scale ($2B annual settlement = $50M revenue) but low enough to win every comparison against alternatives. We'd rather have 100x volume at 2.5% than 10x volume at 25%.

No. The SBT identity contract is non-transferable and has no exchange value. We have no plans to issue an ERC-20 token or any tradable asset. The Treasury settles in USDC. Anyone telling you "DCS is launching a token" is lying.

No. Never. Memory writes, agent action data, and user content are not used to train any model. This is a permanent commitment, documented in our Privacy Policy.

No. We don't sell or share data with advertisers, data brokers, or any third party not listed in Privacy Policy §4 (which is limited to infrastructure subprocessors operating under DPAs).

No. None of our surfaces show ads. We have no plans to introduce them. The business model doesn't require it.

No. We use Plausible — privacy-respecting, cookie-free analytics. No cross-site profiling, no third-party advertising cookies.

Yes. Privacy Policy documents our GDPR alignment — lawful basis (Art. 6), data subject rights (Art. 12-22), DPA-bound subprocessors, breach notification.

Yes. Full clause-by-clause compliance documented at dcsai.ai/dpdp. We treat the DPDP §8(6) 72-hour breach notification as a hard SLA.

R+2 was designed in part to make Art. 12 (Transparency) and Art. 26 (Logging) compliance demonstrable rather than asserted. Every agent action produces an immutable signed receipt — exactly what the Act requires high-risk AI systems to maintain.

Sovereign-tier deployments are designed for this. Air-gappable installations, sectoral profiles (r2-health-v1, r2-gov-v1, r2-finance-v1 — in draft), DPA-grade data processing. Email [email protected] for sector-specific adoption guidance.

LangChain is an agent framework — it orchestrates LLM tool calls and chains. DCS is the infrastructure layer underneath — identity, memory, provenance, settlement. They're complementary: a LangChain agent can use DCS for persistent memory and signed receipts. The MCP server plugs into LangChain.

Letta focuses on the agent memory architecture (how the LLM uses memory at inference time). DCS focuses on the storage layer beneath memory — cryptographic receipts, on-chain identity, multi-tenant persistence, audit trails. You could run Letta on top of DCS's Sovereign Memory layer.

VC is for credentials — static claims about an identity. R+2 is for actions — dynamic events produced at runtime. We considered VC; the data-model overhead added cost without value for high-volume action streams. An R+2 receipt can be embedded in a VC if a deployment prefers VC's transport semantics.

No. MCP is Anthropic's protocol but model-agnostic. Our MCP server works with Claude Desktop, Cursor, Windsurf, Zed, and any other MCP-compatible client. It produces R+2 receipts irrespective of which LLM is calling it.

It's not an acronym — it's a brand. We considered "Deep Cryptographic Systems" and "Digital Coordination Stack" during naming; ultimately landed on "DCS" as a standalone brand. Better than overloading three letters.

Not yet at scale. Selective senior hires (memory, cryptography, on-chain, customer success) will open as pilot traction warrants — paced against founder capital plus pilot revenue, not gated on any financing event. See dcsai.ai/careers for the early-access list.

See the contact list on our about page. Builders → [email protected]. Press → [email protected]. Investors (inbound only — not raising) → [email protected]. Founder direct → [email protected].