WARNING: This product contains nicotine.
Nicotine is an addictive chemical.

Display Guidelines for using the JuiceDB API
Anywhere that you display data from JuiceDB must follow these display guidelines.

Display Requirements and Guidelines

Below you’ll find some of our display requirements and guidelines in addition to those presented in our API Terms of Service. This is a living document, so please check back from time to time for updates.

Required
Anywhere information from JuiceDB is displayed will require full attribution back to JuiceDB so a consumer knows the data originated with JuiceDB
JuiceDB attribution requires the use of our logo (provided in the assets section) and a link back to the relevant content provided directly via the API via the www field
Don't set rel="nofollow" on your links back to JuiceDB
If you are using JuiceDB in addition to other similar data sources, the JuiceDB API content must be easily identifiable as coming from JuiceDB
While not required, you are encouraged to use the JuiceDB name and logo for materials related to your integration, such as promotional content or marketing materials, just make sure you follow the branding guidelines
Always display JuiceDB results in the same order they are received from the API
Not Allowed
Don’t copy the look, feel and experience of JuiceDB. After all, JuiceDB already exists so no need to go out and recreate it
The name of your app shouldn’t include the word JuiceDB.
Don’t suggest partnership or that JuiceDB endorses your app in your messaging. Things like “We use the JuiceDB API” are okay, but “We partner with JuiceDB” are not okay
Don't enable/allow users to generate rating content similar to JuiceDB content
JuiceDB Branding and Assets

API use requires attribution via brand assets available below, with links back to applicable sections (links sent via API). The JuiceDB trademarks, including the JuiceDB logos and the JuiceDB color, are the sole and exclusive property of JuiceDB., and all uses thereof are subject to the applicable license agreement (in this case, the API License Agreement). Any unauthorized use is strictly prohibited.