Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.constants.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

By the end of this guide, you’ll have a working tool with a UI, API access, and Slack integration — no local setup required for anyone who uses it.
1

Sign Up or Log In

Head to constants.io and create an account. No credit card required.
2

Create a New Tool

Click Create new Tool and choose how to start: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 .py, .js, .sh, or other script files into the composer.Option C: Describe in Plain English
Create a tool that takes a CSV file, filters rows where status = 'active',
and outputs a filtered CSV.
Importing from GitHub gives you provenance tracking. Use the scan feature to discover multiple tools from a repo at once.
3

Watch It Build

Constants analyzes your request, defines the inputs and outputs, then builds the UI and backend code. Progress streams in real time — the whole process takes about a minute.
4

Run Your Tool

Once generated, fill in the input form, click Run, and watch streaming logs as it executes. Download artifacts when the run completes. Every run is logged with full context.
5

Share & Integrate

Your tool is ready to use across multiple interfaces:
  • Share the link — recipients run without any local setup
  • Slack bot — mention the bot to run tools conversationally
  • API — POST /v1/run/your-tool-name with an API key
  • MCP — connect AI agents to discover and use your tool

​
What’s Next?

Build Your First Tool

Follow a detailed tutorial with examples

Scan a GitHub Repo

Let AI discover tool candidates in your codebase

​
Tips for Better Results

Importing from a repo gives you provenance tracking and easy updates. Use the scan feature to discover multiple tools at once.
Scripts with a clear if __name__ == "__main__" block or defined CLI arguments produce better tools with more accurate input/output specs.
If your script needs API keys or cloud credentials, add them in the tool’s credential settings. They’re encrypted and injected at runtime — never exposed to tool users.
Create a team workspace to share tools, credentials, and usage quotas with teammates. Invite members by email with role-based access.
Generate an API key and configure your agent to use the Constants MCP endpoint. Every tool you create is automatically available.