Bind AlchemyAPI Instance
I don't see why I am not allowed to bind in an already instantiated instance of the AlchemyAPI service on Bluemix into a second application. Why does a second AlchemyAPI need to be generated, I already have one being used by another application.
The crazy thing is that I can implicitly use the Alchemy API with my existing key, in a new application, but not bind it in using the Bluemix web interface.
We got an error "Service broker error: {"description"=>"Only one free key is allowed per account in a 24-hour period."}"
so I think the issue is the if create an unbound Alchemy API and delete it, you cant bind it again
All binding a service does (for AlchemyAPI services, anyway) is create a key. Because of the way previous services have been implemented on Bluemix (a unique set of credentials per application rather than one key for all services), we don't have the tooling necessary to allow binding of the service to multiple apps with the same key. We will be changing our error message to make this clear. We'll be recommending that for additional apps using AlchemyAPI, if you want the key stored in an environment variable you can set it manually using your already existing key (at least until we can create a better fix).
Figured out that in Node-RED if you don't bind in the service, then the node prompts for the credentials. This allows for reuse of a key that has already been allocated. Not elegant, but it works.
@Zach: I don't understand your answer!
In Cloud Foundry, I can bind one service to many applications, always using the same credentials. Cloud Foundry has the tooling necessary to inject the credentials into the VCAP_SERVICES variable of multiple applications. Only requirement is, they need to be on the same space.
If you try to create a new key every time a user tries to bind the service to another application I suggest the developers of the AlchemyAPI service broker go to the Cloud Foundry Docs page and read the documentation.