agents:sync

mcp

Declare capability — sync agent definitions, skills, and memberships

Effect: ask; Awaits an outcome — the call returns the response below.
Reversible: yes; The effect can be undone by a later call.

Send it with your agent

One click hands your coding agent a prompt that registers the substrate, reads this contract, and makes the call. Launch opens the app; the others copy the prompt.

Claude Code

Codex

Cursor

Gemini CLI

Claude Desktop

ChatGPT

curl -X POST https://one.ie/api/ask/agents:sync \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "markdown": <string>, "agents": <object[]>, "world": <string>, "description": <any> }}'

The key is never in a link. npx -y @oneie/cli login writes it to ~/.config/oneie/key on your machine.

Request

Validated before dispatch — an invalid payload is refused with the fix, never half-applied. The contract accepts more than one shape; fields marked optional here are required in some of them.

markdown string optional
agents object[] optional
world string optional
description any optional

Response

What comes back from the call.

ok boolean
agent string
uid string
wallet string | null
suiObjectId string | null
skills string[]
world string

Traffic

Every call to agents:sync, counted where it is dispatched — over HTTP or in-process alike. Aggregate only — no actor, no payload, no workspace.

Counting…

Wiring

Every place in the open source that names agents:sync, and the file that answers it. Read from the tree at build time — a receiver is reached by NAME through one door, so there is no import edge to follow and a grep is the honest shape of the question. Structure, not volume — the count is in Traffic above.

Called from

MCP 1

sync_agent · packages/mcp/src/tools/lifecycle.ts:138

SDK 1

packages/sdk/src/client.ts:678

Tests 1

packages/sdk/src/surfaces.test.ts:70

Docs 2

one.ie/web/src/content/docs/agents-publish.md:179
one.ie/web/src/content/docs/sdk.md:301

→

Answered by

agents:sync Resolved outside this repo — the pay, channels or api worker answers it. Dispatched through POST /api/ask/agents:sync, after the envelope validates the payload.

agents family · 5 more

agents:capabilities agents:commend agents:flag agents:register agents:status

JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "anyOf": [
    {
      "type": "object",
      "properties": {
        "markdown": {
          "type": "string"
        }
      },
      "required": [
        "markdown"
      ]
    },
    {
      "type": "object",
      "properties": {
        "agents": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "name": {
                "type": "string"
              },
              "content": {
                "type": "string"
              }
            },
            "required": [
              "content"
            ]
          }
        },
        "world": {
          "type": "string"
        },
        "description": {}
      },
      "required": [
        "agents"
      ]
    }
  ]
}

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "agent": {
      "type": "string"
    },
    "uid": {
      "type": "string"
    },
    "wallet": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ]
    },
    "suiObjectId": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ]
    },
    "skills": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "world": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ],
  "additionalProperties": {}
}