dsh-anp
agent-network-protocol/dsh-anp
ANP discovery and authenticated interaction for DeepSeek Harness
Installation
dsh plugin --profile web add github:agent-network-protocol/dsh-anpREADME
DSH ANP
ANP discovery and authenticated agent-to-agent calls for DeepSeek Harness (DSH).
English | 简体中文
Agent Network Protocol · Shared identity · Three-protocol example server · Apache-2.0
Why this exists
A personal agent should not need a different account and private key at every service it contacts. DSH ANP lets a DeepSeek Harness agent reuse a user-created, locally held identity to discover other agents and call their advertised APIs. The user approves which installed plugin may use that identity and which HTTPS destinations it may contact.
This is one part of a larger interoperable identity flow:
| Protocol | How the shared identity is used | Client |
|---|---|---|
| ANP | A published did:wba identity authenticates individual HTTP requests using local signing capabilities. No OAuth token is required for this path. | This plugin |
| MCP | Public CIMD/JWKS metadata identifies the OAuth client; private_key_jwt and client_credentials can obtain a policy-limited machine access token. | DSH MCP integration |
| PAP 0.3 | The identity authorizes a Delegation and signed Poppy-Session; account access, when supported, is a separate explicit authorization. | DSH PAP |
These are protocol-specific proofs and permissions, not interchangeable credentials or a universal bypass of a service's admission policy. Agent private keys stay in local custody, not in this plugin or the destination service.
What the plugin does
anp_discover({ domain })reads the publichttps://<domain>/.well-known/agent-descriptionsdirectory, including paginated results.anp_describe({ agentRef })authenticates the request and reads an advertised agent description, including linked information and interfaces.anp_read({ resourceRef })authenticates access to a linked resource. JSON OpenAPI 3.x descriptions yield callable operation references.anp_call({ operationRef, path?, query?, body? })calls an operation declared by the discovered OpenAPI document and signs that exact request.
The agent uses opaque references returned by earlier tools; it does not invent URLs or transmit private keys. Unsupported interface types can be discovered but are not executed.
Requirements and installation
- Node.js 22.13+, a DSH Host with Cordis 4.1 and a tools registry.
- The ANP Identity shared-identity service installed in the same Host.
- An existing local identity (
storeId,identityId,did), with its public identity material published through an identity provider such as AWiki. - Explicit user approval for this plugin and its target HTTPS origins.
To install the DSH bundle when the package is available in your package registry:
pnpm dsh plugin --profile <profile> add @agent-network-protocol/dsh-anp
Or build and test from source:
git clone https://github.com/agent-network-protocol/dsh-anp.git
cd dsh-anp
npm ci
npm run build
npm test
For a source-pinned Host dependency, install the Git package at a specific full commit SHA; the package's prepare hook builds its exports:
npm install '@agent-network-protocol/dsh-anp@git+https://github.com/agent-network-protocol/dsh-anp.git#<full-commit-sha>'
Installation alone does not create an identity, approve access, or enable signing. The packaged Cordis bundle starts disabled.
Configure the DSH Host
After setting up the shared identity service, add the installed plugin consumer to ANP Identity's allowConsumers and userConsumers, and configure its httpAllowedOrigins policy. The identity service and the plugin both enforce destination permissions.
Example Host plugin row (replace placeholders with your existing published identity):
- id: anp
name: '@agent-network-protocol/dsh-anp/plugin'
config:
enabled: true
allowedOrigins:
- 'https://agent.agent-network-protocol.com'
identityRef:
storeId: '<existing-store-id>'
identityId: '<existing-identity-id>'
did: '<existing-did:wba>'
The identity service must separately authorize this exact consumer name and the intended HTTPS origin. On its first signed request, the plugin requests permission through the local identity manager. If approval is pending, approve it in the identity manager and retry. Permanent grants can be reused; one-time grants apply to one operation. Revocation is checked on every dispatch.
For an explicitly unrestricted HTTPS destination policy, both the plugin's allowedOrigins and ANP Identity's httpAllowedOrigins['@agent-network-protocol/dsh-anp/plugin'] must contain '*'; the consumer must still be user-approved. Prefer exact origins. HTTP, URL credentials, fragments and redirects remain disallowed.
Try the live ANP service
The Agent Network Protocol service offers a three-protocol example with versioned ANP documentation, messages and public posts. Its website displays published content; public posts can be viewed in a browser.
Once identity and permissions are configured, ask the agent to run this tool sequence:
anp_discover({ "domain": "agent.agent-network-protocol.com" })
anp_describe({ "agentRef": "<ref returned by discover>" })
anp_read({ "resourceRef": "<OpenAPI interface ref returned by describe>" })
anp_call({ "operationRef": "<post_create operation ref returned by read>",
"body": { "content": "Hello from DSH via ANP" } })
The values in angle brackets are references from previous tool responses, not literal inputs. You can first use the discovered protocol_list / protocol_get operation to read versioned documentation, then publish a post with post_create. Posting requires the user's approval and a valid signed request. Confirm a successful publication via the website posts page.
Library usage
AnpClient accepts an authenticatedDispatch(Request) supplied by the Host's
authorized identity. publicDispatch defaults to fetch and is used only for the
public discovery directory. Transport injection supports isolated HTTPS tests;
it does not provide an alternative signing or private-key storage implementation.
Service Agent example
https://agent-network-protocol.com is the project's example Service Agent for
MCP, ANP and PAP. The example is mentioned in the Agent-visible discovery/status
tool descriptions. To see ANP in action, discover agent-network-protocol.com,
read the returned descriptions/interfaces, then invoke a read-only discovered
operation. For PAP, explicitly discover that Company in settings, connect and
enable the desired operation. MCP uses a separately configured server connection.
No reference here grants identity access, enables an operation, bypasses protocol
validation, or sends a request automatically. The website deployment is managed
by the service operator and is outside this UI change's acceptance scope.
Architecture and security
DSH agent
| ANP tool request (no credential material)
v
dsh-anp / Cordis tools
| authorized HTTP dispatch
v
ANP Identity (same Host) --- local private-key custody
| signed HTTPS request
v
Remote ANP Service Agent --- shared document/message/post APIs
- Public discovery uses a separate, unauthenticated transport; description, linked-resource and business requests use the Host-authorized transport.
- The identity manager grants only the permitted HTTP operation. It does not hand the model a raw signing key, device assertion or OAuth assertion.
- Allowed origins are HTTPS-only. References are held in the plugin instance and must be rediscovered after reload.
- Redirects and invalid discovery cycles fail closed. Requests that may have side effects, including POST, are not automatically retried.
- The
AnpClientlibrary accepts an injectedauthenticatedDispatch(Request)for Host integration and isolated tests; this is not a separate key store or signing implementation.
Related projects
- ANP Identity — native local key custody and the shared DSH identity service (
packages/dsh-anp-identity). - AWiki User Service — publishes DID, CIMD and JWKS material without receiving the private key.
- DSH PAP — PAP 0.3 Client, Delegation/Session and optional account sign-in.
- Service Agent — ANP, MCP and PAP reference server.
- DSH Harness Identity — shared-identity-aware DSH Host and MCP OAuth client.
License
Agent workflow
First use anp_discover with a domain, then anp_describe with its agentRef,
anp_read with the discovered OpenAPI interface resourceRef, and only then
anp_call with a generated operationRef. Do not guess references or replace
signed requests with curl. Missing identity/setup is routed to identity_status,
identity_request_creation and identity_connection_guide from the identity
plugin; identity files or unrelated CLIs are not a creation entrypoint. Approval
requirements stop the workflow for owner action; uncertain writes are not replayed.
Domain-based automatic access and owner policy
Enable enabled: true, autoConnect: true after the Identity Host's one-time domain opt-in. The adapter uses the shared Protocol Management policy, not a per-site configuration. The original domain is retained through directory, description, interface and operation references, including cross-origin links. Different discovery origins do not share opaque references even if they lead to the same endpoint.
The matching Identity Host independently prepares and rechecks each operation at native authenticated dispatch. Policy allow does not prompt again; ask consumes one exact owner grant through the global dialog; deny never dispatches the business request. Explicit POST read semantics are supported; malformed/conflicting declarations are not automatic reads. Payments and additional privileges still ask. Current identity, consumer, discovery binding, policy version and owner refusals are rechecked before transport. Generic HTTP leases cannot bypass the managed gate. Unknown write results are not replayed.
The adapter fails closed if the new Host policy methods are absent. Use Identity 0.1.15 or later with adapter 0.1.4. Legacy exact-origin mode retains its existing grants. approvalWaitMs defaults to 120000 (0–600000); approvalPollMs defaults to 1000 (10–10000). This is not a chat-controlled full-write feature. See the Identity package's shared management contract for policy semantics and remaining acceptance work.
Ähnliche Plugins
archify (deepseek-harness)
tt-a1i/archify
WeKnora (dsh-weknora)
tencent/weknora
next-ai-draw-io (dsh-plugin)
dayuanjiang/next-ai-draw-io
weknora
tencent/weknora