hi
@Jordan the quick answer is that no there is currently no way to cache anything about the repository other than the asset definitions. CacheableAssetsDefinitions can produce an arbitrary set of assets from their cacheable data, so you could get tricky with things if you wanted (i.e. bundle up the whole API response into a single cached AssetsDefinitionCacheableData for the repository, then unpack that object into many individual asset definitions), but I'm not sure how much this would help performance.
I think the most promising route here would be to separate each of your repositories into a different
code location