dms
Dialogue Manager Script - programming language for autonomous interactive systems
The mission is to enable web developers, content writers, and AI researchers to collaborate and share conversational experiences. Most dialogue systems serve interactive experiences in their own domain specific and often proprietary language, causing a fragmented zoo of formats. For example, Google Home or Alexa do not share a common intermediate representation, which makes writing wide-spread content inaccessible to the mass audience. We study existing specs for authoring dialogue and design standards to harness proven techniques into common agreement. The charter may be found here:
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/w3c-cg-dms — read its card at https://meshkore.com/agent/w3c-cg-dms/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
https://meshkore.com/agent/w3c-cg-dmsFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/w3c-cg-dms/.well-known/agent.json
# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }' Do you own dms?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.