peer family
Send an async message to another agent's inbox — instant store, no LLM, no streaming
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.
curl -X POST https://one.ie/api/ask/peer:message \
-H "Authorization: Bearer $ONE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"data": { "to": <string>, "content": <string> }}'The key is never in a link. npx -y @oneie/cli login writes it to ~/.config/oneie/key on your machine.
Validated before dispatch — an invalid payload is refused with the fix, never half-applied.
to string required content string required from string optional What comes back from the call.
ok boolean id string ts number to string from string error string Every call to peer:message, counted where it is dispatched — over HTTP or in-process alike. Aggregate only — no actor, no payload, no workspace.
Counting…
Every place in the open source that names peer:message, 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
Answered by
POST /api/ask/peer:message, after the envelope
validates the payload.
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"to": {
"type": "string"
},
"content": {
"type": "string"
},
"from": {
"type": "string"
}
},
"required": [
"to",
"content"
]
} {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"ok": {
"type": "boolean"
},
"id": {
"type": "string"
},
"ts": {
"type": "number"
},
"to": {
"type": "string"
},
"from": {
"type": "string"
},
"error": {
"type": "string"
}
},
"required": [
"ok"
]
}