Route reference

Concept detail

GET/v1/knowledge/concepts/{id}search:read

Reads one concept and its field context by ID. Use it after discovery when your UI needs stable details.

When to use it

  • A user selected a concept from search and you need the detail view.
  • Your product stores concept IDs and needs to refresh display text.
  • You need field context next to a concept.

Request

id
Concept ID returned by search or text lookup.

Response

item
Concept detail object with public concept fields.
item.fields[]
Related field records with public display fields.
meta
Request metadata for observability.

How output is produced

  • Looks up one concept by exact ID in the public knowledge surface.
  • Attaches related fields so a builder can display domain context.
  • Returns a detail object that is more stable than copying fields from a search result.

Trust and caution

  • A concept detail explains the stored concept; it does not prove that it fits a user's situation.
  • A 404 means the ID is unavailable to this route, wrong, or no longer present.
  • Cache successful detail responses when rendering the same concept repeatedly.
Request example
curl https://api.agentecology.com/v1/knowledge/concepts/concept_adaptive_coordination \
  -H "X-API-Key: ae_live_YOUR_KEY" \
  -H "Accept: application/json"
Response example
{
  "item": {
    "id": "concept_adaptive_coordination",
    "canonical_name": "Adaptive coordination",
    "definition": "Coordination that changes as local conditions change.",
    "fields": [
      {
        "id": "field_organizational_design",
        "name": "Organizational design",
        "description": "How roles, information flow, and decision rights shape collective work."
      }
    ]
  },
  "source": "concepts",
  "meta": {
    "request_id": "req_...",
    "timestamp": "2026-05-26T17:30:00Z",
    "metered": true
  }
}