Route reference

Related concepts

POST/v1/knowledge/concepts/relatedsearch:read

Moves from a principle or strategy into adjacent concepts from other fields. Use it for cross-domain ideation and explanation.

When to use it

  • You have a principle, design pattern, or functional statement and want adjacent concepts.
  • You need prompts for ideation tools, facilitation software, or research assistants.
  • You want conceptual context after an agent produces a strategy.

Request

principle_statement
Required concise statement to match from.
principle_functions
Optional functions the principle is meant to serve.
top_k
Optional result count, 1 through 50. Defaults to 8.

Response

related_concepts[]
Concepts with id, name, definition, applications, and field context.
count
Number of related concepts returned.
meta.principle_statement
The submitted statement for reconciliation.

How output is produced

  • Combines the statement and functions into a matching signal.
  • Compares that signal with concept names and definitions in the public knowledge surface.
  • Returns compact concept records plus field context for adjacent exploration.

Trust and caution

  • This is a relatedness helper, not proof of causality, equivalence, or fit.
  • Concise statements work better than long paragraphs.
  • If the result is empty, try semantic concept search with shorter function terms.
Request example
curl https://api.agentecology.com/v1/knowledge/concepts/related \
  -X POST \
  -H "X-API-Key: ae_live_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '{
    "principle_statement": "Route decisions to the local team closest to the signal",
    "principle_functions": ["coordinate actors", "adapt to changing conditions"],
    "top_k": 5
  }'
Response example
{
  "related_concepts": [
    {
      "id": "concept_distributed_sensing",
      "name": "Distributed sensing",
      "definition": "A system in which local units detect conditions and contribute to collective response.",
      "applications": ["operations", "ecological monitoring", "team coordination"],
      "from_fields": [
        {
          "id": "field_complex_systems",
          "name": "Complex systems"
        }
      ]
    }
  ],
  "count": 1,
  "source": "concepts",
  "meta": {
    "request_id": "req_...",
    "timestamp": "2026-05-26T17:30:00Z",
    "principle_statement": "Route decisions to the local team closest to the signal",
    "metered": true
  }
}