Version: 1.0.0
Purpose: Query endpoints split from endpoints.md for context window efficiency
This directory contains query endpoints organized by entity type. This allows AI agents to load only the endpoints they need, reducing context window usage.
Use Case: Load specific entity query endpoints when working with that entity, instead of loading the entire endpoints.md (1153 lines).
player.md - Player query endpoints (~50 lines)planet.md - Planet query endpoints (~60 lines)struct.md - Struct query endpoints (~40 lines)fleet.md - Fleet query endpoints (~50 lines)guild.md - Guild query endpoints (~40 lines)reactor.md - Reactor query endpoints (~40 lines) ✅substation.md - Substation query endpoints (~40 lines) ✅provider.md - Provider query endpoints (~40 lines) ✅agreement.md - Agreement query endpoints (~60 lines) ✅allocation.md - Allocation query endpoints (~70 lines) ✅system.md - System queries (block-height, params, etc.) (~50 lines) ✅address.md - Address query endpoints (~50 lines) ✅permission.md - Permission query endpoints (~70 lines) ✅To get Player endpoints:
api/endpoints.md (1153 lines)To get Player endpoints:
api/queries/player.md (~50 lines){
"load": "api/queries/player.md"
}
{
"load": [
"api/queries/player.md",
"api/queries/planet.md"
]
}
../endpoints.md - Complete endpoint catalog (index)../transactions/ - Transaction endpoints../webapp/ - Webapp API endpoints (if split)../../LOADING_STRATEGY.md - How to load efficientlyLast Updated: January 2025