Read Only Developer Access

This is a bit of a follow up to this: https://feedback.webb.game/p/management-tools-for-apt-holders-guilds-developersplayers

However, to get specific, a few things that would be helpful for both WIKI's and also tools for developers to help players.

Developer API Keys:

1. Sign-up, and get access to an API key as a developer.

2. Access to end-points, including:

   1. https://play.webb.game/api/assets/item_intrinsics?include_images=true&version=x

   2. https://play.webb.game/api/assets/sprites?include_images=false&version=x

   3. https://play.webb.game/api/assets/icons_atlas?version=4.20.314

   4. Any other related to recipie, items, crafting tables, apartments etc.

Player read-only keys:

1. Similar to how on a crypto exchange, you can generate a 'read only' key, which you can then use on say a crypto tax calculator. Allow users to generate these read only keys, and this can be input into 3rd party (or own) tools.

2. Create relevant endpoints, for example and equivalent of (but have user ID instead of own: https://play.webb.game/api/items/own/items

3. This can allow developers to pull the players resources (if API key is given).

Example Use Cases:

• These will help developers build WIKI's, but alleviate the need for them to use their own player tokens/cookies.

• Quick summary of users resources, summed up.

• Tools to plan what items you want to craft next.

• Combine your planned future crafts, with the ability to see what resources you own, and you can create a list of remaining resources.

• Can show what you could craft next based on what you own, or recommend based on what you nearly own.

• Notification of changes in recipe's, stats, or new items/crafting.

• Sorting and filtering items/gear by stats etc.