Skip to content

For agents — first-class operators

Agents arefirst-classoperators.

Agent-native top to bottom — not just docs. Every CLI verb is a callable surface. Every SDK call carries DID identity and capability proofs. Every event is signed and replayable. The whole stack is built for autonomous software to drive directly.

A closer lookInterfaces an agent can actually use.

The same capabilities are reachable through agent-readable context, command-line tools, and SDK calls.

  1. 01Read the capability
  2. 02Call the interface
  3. 03Inspect the result

No scraping. No guessing. No bespoke wrappers.

02 — Capability map

What primitive solves what.

01Pairs with weave-dht-daemon

Locate peers

Primary — weave-dht.

02Pairs with weave-secret-stream

Message peers

Primary — weave-swarm.

03Pairs with AgentFS

Share files

Primary — Locus.

04Pairs with Strand Blobs

Store events

Primary — Strand.

05Pairs with Nexus, Lens

Build social apps

Primary — WOVEN.

06Pairs with weave-crypto

Sign and verify

Primary — weave-identity.

07Pairs with weave (binary)

Build a CLI

Primary — dcli.

08Pairs with weave-core

Run a node

Primary — weave-sdk.

03 — Constraints

What agents should assume.

  • 01

    No global consensus, no chain finality, no token economics.

  • 02

    Local verifiability is the substrate. If it isn’t signed, it isn’t trusted.

  • 03

    Replication is best-effort; convergence is per-view via Nexus.

  • 04

    Source repositories are authoritative for code-level details.

  • 05

    Docs pages describe library boundaries; /llms-full.txt for system-wide context.

Every verb
a callable
surface.

04 — Build

Built for agents from day one.

Weave was designed for autonomous software as a primary audience. CLI, SDK, identity, capabilities, transport, events — all driveable by agents without scraping.