Tired of wasting thousands of dollars on API subscriptions to support all your automations? What if there was a free alternative?
The 100% FREE No-Code Architects Toolkit API processes different types of media. It is built in Python using Flask.
The API can convert audio files. It creates transcriptions of content. It translates content between languages. It adds captions to videos. It can do very complicated media processing for content creation. The API can also manage files across multiple cloud services like Google Drive, Amazon S3, Google Cloud Storage, and Dropbox.
You can deploy this toolkit in several ways. It works with Docker. It runs on Google Cloud Platform. It functions on Digital Ocean. You can use it with any system that hosts Docker.
Easily replace services like ChatGPT Whisper, Cloud Convert, Createomate, JSON2Video, PDF(dot)co, Placid and OCodeKit.
Want help? Join a supportive community and get dedicated tech support.
Join the ONLY community where you learn to leverage AI automation and content to grow your business (and streamline your biz).
Who's this for?
- Coaches and consultants
- AI Automation agencies
- SMMA & Content agencies
- SaaS Startup Founders
Get courses, community, support, daily calls and more.
Join the No-Code Architects Community today!
Each feature is supported by robust payload validation and detailed API documentation to facilitate easy integration and usage.
- Description: Provides a flexible way to compose and manipulate media files using FFmpeg. Supports complex media operations like transcoding, concatenation, and filtering.
- Documentation Link: FFmpeg Compose Documentation
- Description: Adds captions to a video file, including options for font, position, and styling. It also supports automated language detection and custom replacements in captions.
- Documentation Link: Video Caption Documentation
- Description: Combines multiple video files into a single video file. The input files are concatenated in the specified order, and the final video is uploaded to cloud storage.
- Documentation Link: Video Concatenate Documentation
- Description: Executes Python code on the server in a controlled environment. Useful for scripting, prototyping, or dynamically running Python scripts with secure execution.
- Documentation Link: Execute Python Documentation
- Description: Converts an image into a video file with configurable options like duration, frame rate, and zoom effects. Ideal for creating video slideshows or transitions.
- Documentation Link: Image to Video Documentation
- Description: Transforms media files into MP3 format, supporting advanced options for encoding like bit rate and sample rate configuration.
- Documentation Link: Media Transform to MP3 Documentation
- Description: Transcribes audio files to text using advanced speech-to-text processing. Supports various languages and audio formats.
- Documentation Link: Audio Transcribe Documentation
- Description: A basic endpoint to verify the availability and functionality of the API. Useful for initial setup and connection tests.
- Documentation Link: Test Endpoint Documentation
- Description: Verifies the provided API key and authenticates the user. Returns a success message if the API key is valid.
- Documentation Link: Authenticate Endpoint Documentation
docker build -t no-code-architects-toolkit .
- Purpose: Used for API authentication.
- Requirement: Mandatory.
- Purpose: The JSON credentials for the GCP Service Account.
- Requirement: Mandatory if using GCP storage.
- Purpose: The name of the GCP storage bucket.
- Requirement: Mandatory if using GCP storage.
- Purpose: Endpoint URL for the S3-compatible service.
- Requirement: Mandatory if using S3-compatible storage.
- Purpose: The access key for the S3-compatible storage service.
- Requirement: Mandatory if using S3-compatible storage.
- Purpose: The secret key for the S3-compatible storage service.
- Requirement: Mandatory if using S3-compatible storage.
- Ensure all required environment variables are set based on the storage provider in use (GCP or S3-compatible).
- Missing any required variables will result in errors during runtime.
docker run -d -p 8080:8080 \
-e API_KEY=your_api_key \
-e GCP_SA_CREDENTIALS='{"your":"service_account_json"}' \
-e GCP_BUCKET_NAME=your_gcs_bucket_name \
no-code-architects-toolkit
Watch Detailed Video Instructions to set up the No-Code Architects Toolkit API.
-
Use the Docker Image below:
stephengpope/no-code-architects-toolkit:latest
Or use the guide below walks you through the steps to install the NCA Toolkit API on GCP.
- A Google Cloud account. Sign up here if you don’t already have one.
- New users receive $300 in free credits.
- Basic knowledge of GCP services such as Cloud Run and Cloud Storage.
- A terminal or code editor for managing files.
- Log into the GCP Console.
- Click on the Project Selector in the top navigation bar and select New Project.
- Enter a project name, such as
NCA Toolkit Project
. - Click Create.
Enable the following APIs:
- Cloud Storage API
- Cloud Storage JSON API
- Cloud Run API
- In the GCP Console, navigate to APIs & Services > Enable APIs and Services.
- Search for each API, click on it, and enable it.
- Navigate to IAM & Admin > Service Accounts in the GCP Console.
- Click + Create Service Account.
- Enter a name (e.g.,
NCA Toolkit Service Account
).
- Enter a name (e.g.,
- Assign the following roles to the service account:
- Storage Admin
- Viewer
- Click Done to create the service account.
- Open the service account details and navigate to the Keys tab.
- Click Add Key > Create New Key.
- Choose JSON format, download the file, and store it securely.
- Navigate to Storage > Buckets in the GCP Console.
- Click + Create Bucket.
- Choose a unique bucket name (e.g.,
nca-toolkit-bucket
). - Leave default settings, but:
- Uncheck Enforce public access prevention.
- Set Access Control to Uniform.
- Choose a unique bucket name (e.g.,
- Click Create to finish.
- Go to the bucket permissions, and add allUsers as a principal with the role:
- Storage Object Viewer.
- Save changes.
- Open the Cloud Run service in the Google Cloud Console.
-
Click Create Service.
-
Then Deploy one revision from Docker Hub using the image below:
stephengpope/no-code-architects-toolkit:latest
- Check the box to allow unauthenticated invocations.
- Set Memory:
16 GB
. - Set CPU:
4 CPUs
. - Set CPU Allocation: Always Allocated.
- Minimum Instances:
0
(to minimize cost during idle times). - Maximum Instances:
5
(adjustable based on expected load).
- Scroll to Platform Version and select Second Generation.
- Second-generation servers offer better performance and feature support for advanced use cases.
- Add the following environment variables:
API_KEY
: Your API key (e.g.,Test123
).GCP_BUCKET_NAME
: The name of your Cloud Storage bucket.GCP_SA_CREDENTIALS
: The JSON key of your service account.- Paste the entire contents of the downloaded JSON key file into this field.
- Ensure:
- Proper JSON formatting.
- No leading or trailing spaces.
- Set the Container Port: Default to
8080
. - Request Timeout:
300 seconds
(to handle long-running requests). - Enable Startup Boost to improve performance for the first request after a cold start.
- Verify all settings and click Create.
- The deployment process might take a few minutes. Once completed, a green checkmark should appear in the Cloud Run dashboard.
By following these steps, the NCA Toolkit will be successfully deployed and accessible via Google Cloud Run with second-generation servers for optimal performance.
- Install Postman Template on your computer.
- Import the API example requests from the NCA Toolkit GitHub repository.
- Configure two environment variables in Postman:
base_url
: Your deployed Cloud Run service URL.x-api-key
: The API key you configured in Step 5.
- Use the example requests to validate that the API is functioning correctly.
- Use the NCA Toolkit API GPT to learn more.
By following these steps, your NCA Toolkit API should be successfully deployed on Google Cloud Platform.
We welcome contributions from the public! If you'd like to contribute to this project, please follow these steps:
- Fork the repository
- Create a new branch for your feature or bug fix
- Make your changes
- Submit a pull request to the "build" branch
- Ensure any install or build dependencies are removed before the end of the layer when doing a build.
- Update the README.md with details of changes to the interface, this includes new environment variables, exposed ports, useful file locations and container parameters.
Thank you for your contributions!
Get courses, community, support daily calls and more.
Join the No-Code Architects Community today!
This project is licensed under the MIT License.