Use entity routes when you need canonical identity and provenance. Use current collection routes when you need an explorer-friendly table for one domain.
Current enemy records from static-client evidence.
/v1/current/recipes
Current recipe records.
/v1/current/blueprints
Current blueprint records.
/v1/current/ships
Current ship records.
/v1/current/structures
Current structure records.
/v1/current/systems
Current system records.
/v1/current/routes
Current route records.
/v1/current/ownership
Current ownership relation records.
/v1/current/route-edges
Current route edge records.
The generic form is also supported:
GET /v1/current/{collection}
Use the explicit route names in documentation and bookmarks. Use the generic form when you are building a client that switches collections from a controlled allowlist.
Typed entity collections are aliases over entity search filtered by entity type. They are useful when you need canonical entity rows but do not need the derived current-state shape.
Current collections and typed collections can both be valid for the same domain:
Use cycles=current unless you have a specific reason to pin the current cycle number. The public API currently exposes current-cycle data only.
Do not pass arbitrary collection names from user input directly into /v1/current/{collection} or /v1/{typedCollection}. Keep a local allowlist of supported collection names.
The v1 prefix is the public compatibility boundary. New fields may be added to response objects. Clients should ignore unknown fields and avoid depending on object key order.