within the grasp of library services, but the individual researcher. In the pub after the main mashcat event had finished, we were chatting about the possibilities offered by Blacklight/VuFind and SolrMARC. I used a phrase I know I borrowed from someone else, but I don't know who -- 'boutique search' -- highly customised search interfaces that server a specific audience or collection. A final note -- we have the software, what we need is data -- unless more libraries followed the lead of Harvard , Cambridge and others and make MARC records available to use, any software which produces consumes MARC records is of limited use ... Now Ian Mulvany talking about Mendeley and how they use APIs -- both publishing and consuming. Try to expose all the metadata being added by users via an API -- a "social catalogue". This enables 'discovery', but not 'delivery' -- this is where Mendeley can make use of external APIs -- such as the WorldCat API. Mendeley invest in APIs because It helps them extend their product, but integrating data/functionality from other places It enables others to extend their product -- they don't have time to build everything that users are asking for. E.g. Android client built by users, as company didn't have the resource Mendeley uses WorldCat registry to find/suggest appropriate OpenURL resolver depending on users location -- as most users won't know what an OpenURL resolver is, or what the detail are. Mendeley uses OAuth -- which means they can integrate