Route reference
Field search
GET/v1/search/fieldssearch:read
Finds academic or professional fields that can frame a problem. Use it to choose lenses and filters.
When to use it
- You want to help a user choose a domain lens before concept search.
- You need candidate field IDs for field_id_filter on concept search.
- You are building a cross-domain browser, curriculum, or strategy library.
Request
- query
- Required search text.
- top_k
- Optional result count, 1 through 50. Defaults to 10.
Response
- items[]
- Field candidates with id, name, description, and score.
- score
- Retrieval relevance for the submitted query.
How output is produced
- Compares the query against the public field search surface.
- Returns compact field records designed for filters, labels, and second-step searches.
Trust and caution
- Fields are scoping aids, not claims that a problem belongs only to one discipline.
- Do not rank fields as more important just because their score is higher for one query.
- A field result is often best used as a prompt for the next search step.
Request example
curl "https://api.agentecology.com/v1/search/fields?query=repairable%20materials&top_k=3" \
-H "X-API-Key: ae_live_YOUR_KEY" \
-H "Accept: application/json"Response example
{
"items": [
{
"id": "field_materials_science",
"name": "Materials science",
"description": "Study and design of material structure, properties, and performance.",
"score": 0.79
}
],
"count": 1,
"source": "fields",
"meta": {
"request_id": "req_...",
"timestamp": "2026-05-26T17:30:00Z",
"vector_search": true,
"metered": true
}
}