Skip to main content

​
Overview

This guide walks you through creating your first tool on Constants. By the end, you’ll have a governed, shareable tool with a UI — no local setup required for anyone who uses it.
1

Sign Up or Log In

Head to constants.io and create an account or sign in.You can sign up with your email address. No credit card required to get started.
2

Import Your Script

Click Create new Tool and choose your import method:Option A: Paste a GitHub URL
https://github.com/your-org/your-repo/blob/main/scripts/process_data.py
Option B: Upload a Script Drag and drop your .py, .js, .sh, or other script files directly into the composer.Option C: Describe in Plain English
Create a tool to help me run backend/batch_asr.py
For production use, importing from GitHub ensures logic is verifiable and pinned to a specific SHA.
3

Confirm the Entrypoint

Constants analyzes your code and identifies the main entrypoint. Review the detected:
  • Inputs: Parameters your script expects
  • Outputs: What the script produces (files, data, reports)
  • Dependencies: Required packages and environment
4

Review the Generated Spec

Constants generates a Tool spec with:
  • Input/output schema with types and validation
  • Resource limits (CPU, memory, timeout)
  • Permission boundaries
  • Version pinning (SHA)
You can customize any of these before creating the Tool.
5

Your Tool is Ready

Once confirmed, you get:
  • Shareable UI: A form-based interface where anyone can enter parameters and run the tool
  • Run History: Every execution is logged with inputs, outputs, timing, and artifacts
  • API Access: Programmatic access for automation (optional)

​
What’s Next?

Build Your First Tool

Follow a detailed tutorial with examples

Explore Features

Learn about the Constants primitives

​
Tips for Better Results

Importing from a repository gives you version pinning, provenance tracking, and the ability to update when the source changes.
Scripts with a clear if __name__ == "__main__" block or defined CLI arguments are easier to turn into Tools with accurate input/output specs.
If your script needs API keys or credentials, configure them in the Tool settings. Secrets are injected at runtime with scoped permissions.
Once your Tool is created, share the link with teammates. They can run it without any local setup — Constants handles the environment.