> For the complete documentation index, see [llms.txt](https://cloudinary.gitbook.io/cil-hackathon-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cloudinary.gitbook.io/cil-hackathon-guide/capitol360-november-2019-hackathon-guide/cloudinary/cloudinary-guide/neural-artwork.md).

# Neural Artwork

![Art+Photo + style\_transfer effect = new artwork](https://cloudinary-res.cloudinary.com/image/upload/v1500474546/blog_style_transfer_top.jpg)

If you are anything like me, one of the things you love about this digital era is that you can be artistic and creative, even if your drawing skills never made it much past stick figures. The average smartphone can take photographs of astonishing quality. And all sorts of special effects, filters, and overlays enable users to convert their favorite photos into unique expressions of themselves.

But all of this still generally remains within the realm of photographic content.

[Read full article and see demo here...](https://cloudinary.com/blog/from_photos_to_art_with_style_transfer)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cloudinary.gitbook.io/cil-hackathon-guide/capitol360-november-2019-hackathon-guide/cloudinary/cloudinary-guide/neural-artwork.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.