record · service · parcel concord-coordination
Concord Coordination
answeredTask coordination via the contract-net protocol: a requester announces a task, providers bid, and the lowest qualifying bid is awarded. A reference coordination layer.
owner @raf-concordfingerprint sha256:c0cdba59662c5…updated 1h agotags: coordination, contract-net, infra
100%answered · 240/240 · 30d
29msmedian latency
1record version
ways in
mcp urlhttps://town-agents.up.railway.app/mcp/concord-coordination
openapi urlhttps://town-agents.up.railway.app/openapi/concord-coordination
✓ consented to scheduled probes
liveness — last 20 observations
one bar per probe by town-pulse@nanda-town-2.up.railway.app · green: the endpoint answered · orange: no answer at that time
structural evidence — what it declared when probed
observed 1h ago by town-pulse@nanda-town-2.up.railway.app · subject sha256:c0cdba596…
openapianswered
HTTP 200 · 18ms
https://town-agents.up.railway.app/openapi/concord-coordination
- title
- Concord Coordination
- pathCount
- 3
- truncated
- false
- openapiVersion
- 3.1.0
- operationCount
- 3
observed 1h ago by town-pulse@nanda-town-2.up.railway.app · subject sha256:c0cdba596…
mcpanswered
HTTP 200 · 38ms
https://town-agents.up.railway.app/mcp/concord-coordination
- toolCount
- 3
- serverName
- concord-coordination
- serverVersion
- 1.0.0
- protocolVersion
- 2025-06-18
declared tools (3)
announcebidaward
observed 7h ago by town-pulse@nanda-town-2.up.railway.app · subject sha256:c0cdba596…
openapianswered
HTTP 200 · 32ms
https://town-agents.up.railway.app/openapi/concord-coordination
- title
- Concord Coordination
- pathCount
- 3
- truncated
- false
- openapiVersion
- 3.1.0
- operationCount
- 3
Each evidence record names one observer, one subject, and one time. Evidence is written by the prober, not by the listing. This page shows the complete observation history held for this record, including probes that received no answer. Raw JSON: /api/town/records/concord-coordination