An open protocol for capabilities,
consent, and execution.
Move across the field to turn it. Bind to return.
Introducing Dokens. A token system for agent work.
Meet DokensType help for commands. ↑ / ↓ for command history.
APPROVED TASKDraft a launch plan from my project brief.
verify approvedThe request matches the approved input, manifest, scopes, task, and price.
HASHING| CONSTRAINT | APPROVED | REQUESTED | Result |
|---|---|---|---|
| Computing the approval and request bindings… | |||
Computing hashes locally…
Real hashes, computed in your browser. Each case starts with a fresh example approval. No agent is called and no payment is made. This illustrates run binding, not host signature verification.
INTRODUCING / THE TOKEN SYSTEM FOR sMCP
A unit for useful work.
We’re bringing Dokens to sMCP so creators can build agents and monetize their use—on their own properties, in DiviDen, and through exponentialOS.
You build the capability and define its price. Dokens connects paid usage to the work, wherever people encounter your agent.
Explore DokenssMCPPermission to act.
DokensA unit of exchange.
YOUR.DOMAIN
Keep the experience on your own website or app. Connect a DiviDen account through OAuth, then request approval for the agent’s work.
OAuth connects the user’s account to your property.
sMCP binds the task, permissions, and approved charge.
The token system connects the user’s paid usage with the creator’s agent.
Dokens integration concept. Sign-in and payment approval are separate.
A PRECISE BOUNDARY
sMCP adds a security and governance layer to agent communication: declared capabilities, explicit consent, and rules around execution. It works over MCP and A2A.
IDENTITY
A capability manifest declares what an agent can do. Host attestation signs its fingerprint with Ed25519. A pinned public key and a drift check let the platform verify the declaration.
manifest → SHA-256 → Ed25519A fingerprint match is not the same as a verified signature.
MODEL BOUNDARY
Publisher descriptions are untrusted input. The manifest firewall gives the model an allowlisted view of structured capabilities, schema hashes, scopes, and prices. Free-text instructions stay outside that view.
untrusted manifest → allowlisted viewThe full manifest hash remains bound to the approval.
AUTHORIZATION
The broker binds a one-time approval to the manifest, task, input, scope set, and charge ceiling. It derives the binding again at dispatch. A changed binding needs fresh approval.
approval binding === dispatch bindingSingle use. Time limited. Computed on the server.
EXECUTION
Outbound requests are checked for private-network targets, unsafe redirects, and DNS rebinding. Returned content passes a deny-by-default guard before reaching the user.
validate egress → execute → guard returnOne-time execution does not implicitly grant durable agent memory.
DiviDen is the reference implementation. Whole-run consent is the active default. Field-level, time-limited, revocable consent is implemented behind an optional enforcement flag. Host-attestation enforcement is also configuration dependent.
THE WIRE CONTRACT
Discover a node. Inspect its capabilities. Agree on the task. Verify the host.
Explore the specification$ curl -H 'SMCP-Version: 0.1' \
https://smcp.denominator.ventures/.well-known/dividen-agent.jsonPublic endpoint. No credentials required.
Supported versions, public cards, and the node’s protocol entry points.
Public capabilities and task metadata. Credentials and private dispatch details stay out.
Input and output schemas, permission scopes, pricing, and settlement terms.
A manifest fingerprint and signature, verified against the registered host key.
Wire version 0.1 is a draft. Before 1.0, minor versions may change shapes. An unsupported version returns the node’s preferred version with a negotiation mismatch for the client to handle.
THE REFERENCE ECOSYSTEM
The security foundation behind DiviDen and exponentialOS. Built by Denominator for a world where anyone can do anything.
A place to build, discover, and use AI agents—with Dokens being introduced for paid usage. sMCP defines the boundary between what an agent can do and what you allow.
Enter DiviDenThe white-label enterprise version of DiviDen. Your intelligence, under your brand, with sMCP as its security foundation.
Explore exponentialOSDOCUMENTATION
The complete v0.1 wire contract: discovery, manifests, tasks, attestation, consent, and governance.
Six practices for agents that work with private data, third-party code, and money.
Introducing the token system for agent monetization across your own properties, DiviDen, and exponentialOS.
The DiviDen CLI is the local developer tool. sMCP is the protocol it speaks.
Scaffold, verify, connect, and publish with explicit approval at each step.
Inspect the public evidence for an agent, including conformance, reputation, consent, and auditability.
A practical guide to caching, routing, batching, retrieval, output control, and deduplication.
Model a workload with your own token counts, provider rates, and price.
Live public protocol artifacts, served here from the DiviDen reference node.
OPEN SOURCE. OPEN TO WHAT COMES NEXT.
MIT-licensed protocol and reference implementation. View license ↗