Production Servers

• Generate Images
• Image Generation Routes
• Project Information

The /generate endpoint of the API is used to produce various pictures. The Generate Endpoint is made up of several routes, each with its own goal of generating unique images.

Example

GET /generate/wanted?avatar=https://avatars.githubusercontent.com/u/88582190?v=4

The generate/wanted route is used to generate a wanted image with the provided avatar image link. Check The API Reference for all different routes, API Reference.

It will send you the file as the response body whenever you request an image. If you're using code to produce, you'll need to use an Image Libary to parse the image raw data from the response content. Here's an example in Python

import requests
from PIL import Image

data=requests.get("https://aphro.vercel.app/generate/wanted?avatar=https://avatars.githubusercontent.com/u/88582190?v=4",stream=True).raw
im=Image.open(data)
im.save("wanted.png")

The code above requests the API to generate a wanted image with the provided avatar image link and using .raw to load the raw content of the requests. Then using Pillow Libary to read the Raw Data into an actual image and saving it as wanted.png.

All the routes in this Image Generation Section Requires the Parameter avatar or image or Either Both In Its URL.

GET /generate/wanted?avatar={AVATAR_IMAGE_LINK}

GET /generate/beautiful?avatar={AVATAR_IMAGE_LINK}

GET /generate/3000years?avatar={AVATAR_IMAGE_LINK}

GET /generate/expose?avatar={AVATAR_IMAGE_LINK}

GET /generate/hail?avatar={AVATAR_IMAGE_LINK}

GET /generate/deepfuck?avatar={AVATAR_IMAGE_LINK}

GET /generate/circle?avatar={AVATAR_IMAGE_LINK}

GET /generate/blur?avatar={AVATAR_IMAGE_LINK}

This Route Specifically Requires Both The avatar and image parameter in its URL

GET /generate/batslap?avatar={AVATAR_IMAGE_LINK}&image={SECOND_AVATAR_LINK}

Because the API is still in development and will be, small errors in endpoints and routes are to be expected. I still have a lot more things in mind for this API, which I will implement soon.

At the moment, this API is not open-source since I still have a lot of stuff to add, correct, and improve. I'm willing to preserve it as a Free To Use API, but not as an open-source project. Although, I may change my mind in the near future.

Developed And Maintained By Cookey