Tag Info

A library should take an app key, not have an app key. Don't register it.
Also, make absolutely sure your wrapper demands an app key at initialization. You don't want a user locked into the No Key request limit erroneously.
If libraries had keys an application abusively using your library (through no fault of yours) could get every application that uses ...

Remember, you should only publicize
your app if it can actually be used!
I'm working on an idea for an app.
In true "customer development" fashion, I'd like to publish the idea, with a screenshot of what it will look like, to see what kind of reaction it gets and what features people want it to have. It's not difficult to implement, but I'd rather ...

Do you mean to say how do I use this stuff?
You can find the documentation here or there's a Get Started section at the right of this page.
For example if you want to see a list of users you could send a web request to http://api.stackoverflow.com/1.0/users and parse then JSON response.
Now if you want to find out details about a particular user lets say ...

Historical Note
StackList is no longer available - the features that made it an attractive supplement to listing your app here have found their way into Stack Apps itself.
This answer remains for historical purposes.
Don't forget to also publish your app on stacklist.quickmediasolutions.com (404 Not Found)
The site is shaping into a nice ...

It is acceptable, so long as it is usable in some form.
What we object to is people listing an app that exists only in their imagination and not reality. That's not helping people looking for, y'know, actual apps that run on our API...