The following default rules apply to all Apps:
Advertising. No advertising or sponsorship of any kind may appear on or be associated with any App (unless included in the Content made available by Marvel).
No Charge. All Apps must be offered free of charge to download or otherwise access and may not contain any in-App purchase features or any other method of monetization, unless approved in writing by Marvel pursuant to a separate written agreement as described below.
Use of our Content. You may not change or edit the Content (e.g., modify, augment).
These terms apply to the free usage of their API.
I have no doubt that if you had a good idea that monetized their API data well, and you wanted to do things not allowed by this default license agreement, you could reach out to them and get a different license that allowed you to charge money and/or do more, probably in exchange for a revenue sharing or something.
Since this is a new(ish) service, they are probably not actively promoting a paid option while they hammer out any bugs or issues in v1 (since the SLA for paying customers is likely more involved).
Obviously this is all speculation, but just because this is the license displayed on the site doesn't mean it's the only license they are prepared to offer.
Still, it's a start.
It's also possible that they have no idea what to charge for their API right now, and they are waiting to see what kinds of offers come in.
That's also smart (or ruthless?) since it allows them to tailor their price to your idea (i.e. maximize their share of the potential revenue).
I hope people figure out cool things to do with this though.
That's from Google's TOS , which applies to GMail. So Google can, in theory, publicly display your email.
I guess that's my way of saying that I'm much more interested in the fact this API is available for exploration and experimentation and much less interested that it doesn't meet an impossible standard that no one here can actually articulate or provide an example of.
I wouldn't be surprised if opening up this API was a non-unanimous decision with lots of internal dissent.
Especially when talking about the kind of API most likely to be used by clever teenagers on a fansite.
What, is this an NDA? (If it is, you just broke it. Along with everyone else in this item that says they did something with their API...)
I am surely biased, but it's a pretty fun way to rediscover comics you might have forgotten about.
UPDATE: The code that queries the API (while messy) is entirely written in client-side JQuery, so feel free to view the source.
I was emailed with my email and password in plain text, meaning that Marvel stores the passwords in plain text. Knowing that, I'm not sure how comfortable I would be building something on top of this API.
The comic industry needs more of this. There is a wealth of information out there, nearly all of which is user created. Its nice to see Marvel offering this.
I'm very interested in seeing what people make with this. Now let's pester DC, Image, Dark Horse, etc to get on the bandwagon!
To use the API you must display a copyright link whose href points at a url included in the API's response.
Ignoring the nice boost this gives to Google rank, the urls change based on the request and so can point to a place where the viewer can buy the API response's content from Marvel.
Plus each url includes a tag so Marvel can know which app sent them the customer.
Not sure why they're putting such a powerful linkback/affiliate scheme in the copyright notice though. If they're sending back custom urls it's no extra effort to include call to action text for the link as well eg: Buy 'Avengers: The Quest For Profit'.
More info in the linking section of http://developer.marvel.com/documentation/attribution
The project is now in its 20th year and this shows in that the database schema isn't as canonicalized as could be (for example, creator credits and character fields are just text fields and not DB references. Yet slowly but surely improvements are being made, faster in the last couple of years.
We could use some help if anybody is interested - our code is GPL (https://github.com/GrandComicsDatabase/gcd-django) and since the dev team is limited and everything happens on our free time, all kinds of help are appreciated.
our wiki: http://docs.comics.org/
our tech mailing list: http://groups.google.com/group/gcd-tech
I used that data a few months ago to create a chart of the most popular Marvel characters: http://i.imgur.com/KVAT3Xn.png
Code for retrieving the data here: https://github.com/minimaxir/all-marvel-comics-characters (I have absolutely no idea if this still works)
Feedback/contributions welcome if you feel like it
edit: I might just break down and write a Go client generator for Swagger...
Has both Marvel and DC characters, so that's a huge plus.
HOWEVER the geek in me wants to see the "comic graph" and someone map the hell out of all the cross appearances and so forth.
And the code: http://www.raymondcamden.com/index.cfm/2014/2/2/Examples-of-...
That seems to imply there is might be a `v1/private` namespace as well.
if anybody has an idea of app he is welcome.